How do I change the order in which systemd services are started up
Ubuntu 18.04 server on my home network
I'm running:
- dnsmasq for DHCP and DNS
- nginx as a reverse proxy to some web applications (running on localhost and on other hosts)
The nginx reverse proxy config uses hostnames, eg:
location / {
proxy_pass http://nas.mydomain.com:8080;
However, when rebooting the server, nginx tries to start up but fails due to not being able to resolve the hostnames in its config. If I start nginx up manually after boot, it starts up without error.
This leads me to believe that nginx is starting before dnsmasq is available to resolve the hostnames.
Is there a way to force nginx to start after dnsmasq?
server systemd nginx dnsmasq
add a comment |
Ubuntu 18.04 server on my home network
I'm running:
- dnsmasq for DHCP and DNS
- nginx as a reverse proxy to some web applications (running on localhost and on other hosts)
The nginx reverse proxy config uses hostnames, eg:
location / {
proxy_pass http://nas.mydomain.com:8080;
However, when rebooting the server, nginx tries to start up but fails due to not being able to resolve the hostnames in its config. If I start nginx up manually after boot, it starts up without error.
This leads me to believe that nginx is starting before dnsmasq is available to resolve the hostnames.
Is there a way to force nginx to start after dnsmasq?
server systemd nginx dnsmasq
add a comment |
Ubuntu 18.04 server on my home network
I'm running:
- dnsmasq for DHCP and DNS
- nginx as a reverse proxy to some web applications (running on localhost and on other hosts)
The nginx reverse proxy config uses hostnames, eg:
location / {
proxy_pass http://nas.mydomain.com:8080;
However, when rebooting the server, nginx tries to start up but fails due to not being able to resolve the hostnames in its config. If I start nginx up manually after boot, it starts up without error.
This leads me to believe that nginx is starting before dnsmasq is available to resolve the hostnames.
Is there a way to force nginx to start after dnsmasq?
server systemd nginx dnsmasq
Ubuntu 18.04 server on my home network
I'm running:
- dnsmasq for DHCP and DNS
- nginx as a reverse proxy to some web applications (running on localhost and on other hosts)
The nginx reverse proxy config uses hostnames, eg:
location / {
proxy_pass http://nas.mydomain.com:8080;
However, when rebooting the server, nginx tries to start up but fails due to not being able to resolve the hostnames in its config. If I start nginx up manually after boot, it starts up without error.
This leads me to believe that nginx is starting before dnsmasq is available to resolve the hostnames.
Is there a way to force nginx to start after dnsmasq?
server systemd nginx dnsmasq
server systemd nginx dnsmasq
asked Nov 29 '18 at 12:50
J. le RouxJ. le Roux
182
182
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Systemd tries to start multiple services in parallel, unless you tell it not do. If you have dependencies, you need to use directives like After in the services definition file.
In this case, if you need to start the nginx service after the dnsmasq service is running, you can add
After=dnsmasq.service
into the nginx.service file.
Hope this helps.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1097111%2fhow-do-i-change-the-order-in-which-systemd-services-are-started-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Systemd tries to start multiple services in parallel, unless you tell it not do. If you have dependencies, you need to use directives like After in the services definition file.
In this case, if you need to start the nginx service after the dnsmasq service is running, you can add
After=dnsmasq.service
into the nginx.service file.
Hope this helps.
add a comment |
Systemd tries to start multiple services in parallel, unless you tell it not do. If you have dependencies, you need to use directives like After in the services definition file.
In this case, if you need to start the nginx service after the dnsmasq service is running, you can add
After=dnsmasq.service
into the nginx.service file.
Hope this helps.
add a comment |
Systemd tries to start multiple services in parallel, unless you tell it not do. If you have dependencies, you need to use directives like After in the services definition file.
In this case, if you need to start the nginx service after the dnsmasq service is running, you can add
After=dnsmasq.service
into the nginx.service file.
Hope this helps.
Systemd tries to start multiple services in parallel, unless you tell it not do. If you have dependencies, you need to use directives like After in the services definition file.
In this case, if you need to start the nginx service after the dnsmasq service is running, you can add
After=dnsmasq.service
into the nginx.service file.
Hope this helps.
answered Nov 29 '18 at 13:36
Lewis MLewis M
5406
5406
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1097111%2fhow-do-i-change-the-order-in-which-systemd-services-are-started-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown