A start job is running for wait for network to be configured. Ubuntu server 17.10What is the difference between “systemctl mask” and “systemctl disable”?Start job is running for wait for network to be configured. Ubuntu server 18.04Can't SSH to Raspberry Pi via wired connection with static IPHow do I decrease the timeout on ifup?How to disable ethernet check during bootListing network hardware - why does Ubuntu sometimes hide eth0 until it is connected?How I made my new ubuntu server 17.10 installation only use WiFiStart job is running for wait for network to be configured. Ubuntu server 18.04Ubuntu 18.04.1 does not boot without ethernet cable
How to "Start as close to the end as possible", and why to do so?
PhD Length: are shorter PhD degrees (from different countries) valued differently in other counter countries where PhD Is a longer process?
What is the meaning of first flight and introduction in aircraft production?
Why does `FindFit` fail so badly in this simple case?
Missing quartile in boxplot
Confusion regarding control system of Mars Rover?
All over the place
Giving a good fancy look to a simple table
Can anyone give me the reason why music is taught this way?
Does the US Armed Forces refuse to recruit anyone with an IQ less than 83?
Replace zeros in a list with last nonzero value
Could Boris Johnson face criminal charges for illegally proroguing Parliament?
Would a horse be sufficient buffer to prevent injury when falling from a great height?
Everyone Gets a Window Seat
Can I bring this power bank on board the aircraft?
Why do personal finance apps focus on outgoings rather than income
What does "execute a hard copy" mean?
Disable all sound permanently
Shell Sort, Insertion Sort, Bubble Sort, Selection Sort Algorithms (Python)
Does the 'java' command compile Java programs?
Can the President of the US limit First Amendment rights?
How to interpret the challenge rating of creatures?
Why does it seem the best way to make a living is to invest in real estate?
Meaning of "fin" in "fin dai tempi"
A start job is running for wait for network to be configured. Ubuntu server 17.10
What is the difference between “systemctl mask” and “systemctl disable”?Start job is running for wait for network to be configured. Ubuntu server 18.04Can't SSH to Raspberry Pi via wired connection with static IPHow do I decrease the timeout on ifup?How to disable ethernet check during bootListing network hardware - why does Ubuntu sometimes hide eth0 until it is connected?How I made my new ubuntu server 17.10 installation only use WiFiStart job is running for wait for network to be configured. Ubuntu server 18.04Ubuntu 18.04.1 does not boot without ethernet cable
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
i just installed ubuntu server on my laptop and everything works fine except for the fact that at boot if the laptop is not connected to ethernet or in range of my wi-fi i get this message "A start job is running for wait for network to be configured" that stays for about 2 minutes. I looked up online for solutions and i tried to:
- Disable network manager
- Edit timeout settings in /etc/systemd/system.conf
- Disable systemd.networkd-wait-online.service
None of these solutions worked for me. Any possible fixes?
networking 17.10
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
add a comment
|
i just installed ubuntu server on my laptop and everything works fine except for the fact that at boot if the laptop is not connected to ethernet or in range of my wi-fi i get this message "A start job is running for wait for network to be configured" that stays for about 2 minutes. I looked up online for solutions and i tried to:
- Disable network manager
- Edit timeout settings in /etc/systemd/system.conf
- Disable systemd.networkd-wait-online.service
None of these solutions worked for me. Any possible fixes?
networking 17.10
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
Those are the fixes. After each change, did you reload NM/systemd? They only read their config files at start.
– user535733
Nov 2 '17 at 17:55
Yes i used systemctl daemon-reload, still the same result
– vlad27
Nov 2 '17 at 18:23
add a comment
|
i just installed ubuntu server on my laptop and everything works fine except for the fact that at boot if the laptop is not connected to ethernet or in range of my wi-fi i get this message "A start job is running for wait for network to be configured" that stays for about 2 minutes. I looked up online for solutions and i tried to:
- Disable network manager
- Edit timeout settings in /etc/systemd/system.conf
- Disable systemd.networkd-wait-online.service
None of these solutions worked for me. Any possible fixes?
networking 17.10
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
i just installed ubuntu server on my laptop and everything works fine except for the fact that at boot if the laptop is not connected to ethernet or in range of my wi-fi i get this message "A start job is running for wait for network to be configured" that stays for about 2 minutes. I looked up online for solutions and i tried to:
- Disable network manager
- Edit timeout settings in /etc/systemd/system.conf
- Disable systemd.networkd-wait-online.service
None of these solutions worked for me. Any possible fixes?
networking 17.10
networking 17.10
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
asked Nov 2 '17 at 17:37
vlad27vlad27
1861 gold badge2 silver badges3 bronze badges
1861 gold badge2 silver badges3 bronze badges
Those are the fixes. After each change, did you reload NM/systemd? They only read their config files at start.
– user535733
Nov 2 '17 at 17:55
Yes i used systemctl daemon-reload, still the same result
– vlad27
Nov 2 '17 at 18:23
add a comment
|
Those are the fixes. After each change, did you reload NM/systemd? They only read their config files at start.
– user535733
Nov 2 '17 at 17:55
Yes i used systemctl daemon-reload, still the same result
– vlad27
Nov 2 '17 at 18:23
Those are the fixes. After each change, did you reload NM/systemd? They only read their config files at start.
– user535733
Nov 2 '17 at 17:55
Those are the fixes. After each change, did you reload NM/systemd? They only read their config files at start.
– user535733
Nov 2 '17 at 17:55
Yes i used systemctl daemon-reload, still the same result
– vlad27
Nov 2 '17 at 18:23
Yes i used systemctl daemon-reload, still the same result
– vlad27
Nov 2 '17 at 18:23
add a comment
|
5 Answers
5
active
oldest
votes
Use
systemctl disable systemd-networkd-wait-online.service
to disable the wait-online service to prevent the system from waiting on a network connection, and use
systemctl mask systemd-networkd-wait-online.service
to prevent the service from starting if requested by another service (the service is symlinked to /dev/null).
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
What means masking in this context?.
– Jaime Hablutzel
Mar 27 '18 at 3:37
It worked. :) Can you please describe what we have done here? I am just curious.
– SD.
Apr 14 '18 at 5:22
3
@SD @jaime-hablutzel See askubuntu.com/a/816378/445084 for an explanation ofsystemctl mask. Long story short: masking a service redirects it to/dev/null, preventing it from being re-enabled in the case that it is required by another service.
– timelmer
Apr 18 '18 at 22:43
add a comment
|
Don't mask or disable the systemd service.
Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.
sudo netplan apply
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
1
In my case it only worked after setting all interfaces to optional: true
– duli
Mar 4 at 14:11
1
In what way is this superior to disabling the systemd service?
– Andreas Hartmann
Aug 16 at 13:42
For me with Ubuntu 18.04 on Vmware, the corresponding file was /etc/netplan/50-cloud-init.yaml; adding optional: true & reboot worked! Related thread: askubuntu.com/questions/1090631/…. Related info on netplan: linux.com/learn/intro-to-linux/2018/9/… (Configuring DHCP)
– Snidhi Sofpro
Aug 21 at 7:29
Thisx worked for me with Ubuntu 18.04.03 LTS (Desktop) where I have disabled NetworkManager and set up networkd with netplan, ans set up br0 for kdvm/qenu virtualisation and dns caching with dnsmaquerade. Newer did not find what goes wrong with my settings, but booys take over 2 minutes without optional: true -setting. With that setting boot is normal and so is functionality also with network.
– Reijo Korhonen
Sep 9 at 21:26
add a comment
|
This means systemd-networkd-wait-online.service is hanging. There's a few known bugs with it. Check what services want network-online.target with:
systemctl show -p WantedBy network-online.target
You can disable those services if you want. Otherwise, you may have to mask the service as Mr.Ecco indicated.
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
add a comment
|
Masking systemd-networkd-wait-online.service, as suggested in other answers, may help in simple setups but it does not fix the problem. If you mask the service then all other services depending on it will also fail. That means, all services needed to wait until the network is online will fail.
I run into this problem because I use a dynamic fail-over setup for my laptops with bonding the wired (enp9s0) and wireless (wlp12s0) interface that are used as slaves for the main interface bond0. Exactly the same situation do you have if you use a bridge (br0 with slave interfaces). Only the main interfaces bond0 or br0 will get online but not the slaves so systemd-networkd-wait-online.service will fail on the slaves.
The solution to this problem is to modify the service and check only for the interfaces that should go online. You will find with:
~$ sudo systemctl cat systemd-networkd-wait-online.service | grep --after-context=3 '[Service]'
[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-networkd-wait-online
RemainAfterExit=yes
The program systemd-networkd-wait-online has a parameter to test specific interfaces. Check with /lib/systemd/systemd-networkd-wait-online --help. So I make a drop in file to modify the service:
~$ sudo systemctl edit systemd-networkd-wait-online.service
In the empty editor insert these statements, of course with your interface, save them an quit the editor:
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-networkd-wait-online --interface=bond0 --quiet
The empty ExecStart= is important because it disables the "old" command. You can check for more than on interface (look at the help).
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
Excellent, very good answer, that was exactly my problem
– kaklon
Sep 13 at 10:40
add a comment
|
Use commands:
$ sudo systemctl stop systemd-networkd-wait-online.service
$ sudo systemctl disable systemd-networkd-wait-online.service
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
7
Could you explain why this is better than the top answer?
– Melebius
Sep 19 '18 at 11:31
4
Welcome to Ask Ubuntu! When you answer, please refrain from posting commands without context. We'd like to see why a given command fixes a problem. Also, as a side note, unless you manually enabled systemd-networkd-wait-online.service, those two commands are not sufficient.
– Duncan X Simpson
Sep 19 '18 at 14:31
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/4.0/"u003ecc by-sa 4.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%2f972215%2fa-start-job-is-running-for-wait-for-network-to-be-configured-ubuntu-server-17-1%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Use
systemctl disable systemd-networkd-wait-online.service
to disable the wait-online service to prevent the system from waiting on a network connection, and use
systemctl mask systemd-networkd-wait-online.service
to prevent the service from starting if requested by another service (the service is symlinked to /dev/null).
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
What means masking in this context?.
– Jaime Hablutzel
Mar 27 '18 at 3:37
It worked. :) Can you please describe what we have done here? I am just curious.
– SD.
Apr 14 '18 at 5:22
3
@SD @jaime-hablutzel See askubuntu.com/a/816378/445084 for an explanation ofsystemctl mask. Long story short: masking a service redirects it to/dev/null, preventing it from being re-enabled in the case that it is required by another service.
– timelmer
Apr 18 '18 at 22:43
add a comment
|
Use
systemctl disable systemd-networkd-wait-online.service
to disable the wait-online service to prevent the system from waiting on a network connection, and use
systemctl mask systemd-networkd-wait-online.service
to prevent the service from starting if requested by another service (the service is symlinked to /dev/null).
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
What means masking in this context?.
– Jaime Hablutzel
Mar 27 '18 at 3:37
It worked. :) Can you please describe what we have done here? I am just curious.
– SD.
Apr 14 '18 at 5:22
3
@SD @jaime-hablutzel See askubuntu.com/a/816378/445084 for an explanation ofsystemctl mask. Long story short: masking a service redirects it to/dev/null, preventing it from being re-enabled in the case that it is required by another service.
– timelmer
Apr 18 '18 at 22:43
add a comment
|
Use
systemctl disable systemd-networkd-wait-online.service
to disable the wait-online service to prevent the system from waiting on a network connection, and use
systemctl mask systemd-networkd-wait-online.service
to prevent the service from starting if requested by another service (the service is symlinked to /dev/null).
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
Use
systemctl disable systemd-networkd-wait-online.service
to disable the wait-online service to prevent the system from waiting on a network connection, and use
systemctl mask systemd-networkd-wait-online.service
to prevent the service from starting if requested by another service (the service is symlinked to /dev/null).
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
edited Apr 19 '18 at 2:50
fosslinux
2,4832 gold badges21 silver badges38 bronze badges
2,4832 gold badges21 silver badges38 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
answered Nov 23 '17 at 12:33
Mr.EccoMr.Ecco
3992 silver badges2 bronze badges
3992 silver badges2 bronze badges
What means masking in this context?.
– Jaime Hablutzel
Mar 27 '18 at 3:37
It worked. :) Can you please describe what we have done here? I am just curious.
– SD.
Apr 14 '18 at 5:22
3
@SD @jaime-hablutzel See askubuntu.com/a/816378/445084 for an explanation ofsystemctl mask. Long story short: masking a service redirects it to/dev/null, preventing it from being re-enabled in the case that it is required by another service.
– timelmer
Apr 18 '18 at 22:43
add a comment
|
What means masking in this context?.
– Jaime Hablutzel
Mar 27 '18 at 3:37
It worked. :) Can you please describe what we have done here? I am just curious.
– SD.
Apr 14 '18 at 5:22
3
@SD @jaime-hablutzel See askubuntu.com/a/816378/445084 for an explanation ofsystemctl mask. Long story short: masking a service redirects it to/dev/null, preventing it from being re-enabled in the case that it is required by another service.
– timelmer
Apr 18 '18 at 22:43
What means masking in this context?.
– Jaime Hablutzel
Mar 27 '18 at 3:37
What means masking in this context?.
– Jaime Hablutzel
Mar 27 '18 at 3:37
It worked. :) Can you please describe what we have done here? I am just curious.
– SD.
Apr 14 '18 at 5:22
It worked. :) Can you please describe what we have done here? I am just curious.
– SD.
Apr 14 '18 at 5:22
3
3
@SD @jaime-hablutzel See askubuntu.com/a/816378/445084 for an explanation of
systemctl mask. Long story short: masking a service redirects it to /dev/null, preventing it from being re-enabled in the case that it is required by another service.– timelmer
Apr 18 '18 at 22:43
@SD @jaime-hablutzel See askubuntu.com/a/816378/445084 for an explanation of
systemctl mask. Long story short: masking a service redirects it to /dev/null, preventing it from being re-enabled in the case that it is required by another service.– timelmer
Apr 18 '18 at 22:43
add a comment
|
Don't mask or disable the systemd service.
Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.
sudo netplan apply
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
1
In my case it only worked after setting all interfaces to optional: true
– duli
Mar 4 at 14:11
1
In what way is this superior to disabling the systemd service?
– Andreas Hartmann
Aug 16 at 13:42
For me with Ubuntu 18.04 on Vmware, the corresponding file was /etc/netplan/50-cloud-init.yaml; adding optional: true & reboot worked! Related thread: askubuntu.com/questions/1090631/…. Related info on netplan: linux.com/learn/intro-to-linux/2018/9/… (Configuring DHCP)
– Snidhi Sofpro
Aug 21 at 7:29
Thisx worked for me with Ubuntu 18.04.03 LTS (Desktop) where I have disabled NetworkManager and set up networkd with netplan, ans set up br0 for kdvm/qenu virtualisation and dns caching with dnsmaquerade. Newer did not find what goes wrong with my settings, but booys take over 2 minutes without optional: true -setting. With that setting boot is normal and so is functionality also with network.
– Reijo Korhonen
Sep 9 at 21:26
add a comment
|
Don't mask or disable the systemd service.
Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.
sudo netplan apply
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
1
In my case it only worked after setting all interfaces to optional: true
– duli
Mar 4 at 14:11
1
In what way is this superior to disabling the systemd service?
– Andreas Hartmann
Aug 16 at 13:42
For me with Ubuntu 18.04 on Vmware, the corresponding file was /etc/netplan/50-cloud-init.yaml; adding optional: true & reboot worked! Related thread: askubuntu.com/questions/1090631/…. Related info on netplan: linux.com/learn/intro-to-linux/2018/9/… (Configuring DHCP)
– Snidhi Sofpro
Aug 21 at 7:29
Thisx worked for me with Ubuntu 18.04.03 LTS (Desktop) where I have disabled NetworkManager and set up networkd with netplan, ans set up br0 for kdvm/qenu virtualisation and dns caching with dnsmaquerade. Newer did not find what goes wrong with my settings, but booys take over 2 minutes without optional: true -setting. With that setting boot is normal and so is functionality also with network.
– Reijo Korhonen
Sep 9 at 21:26
add a comment
|
Don't mask or disable the systemd service.
Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.
sudo netplan apply
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
Don't mask or disable the systemd service.
Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.
sudo netplan apply
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
edited Feb 20 at 22:19
Kristopher Ives
3,5542 gold badges17 silver badges30 bronze badges
3,5542 gold badges17 silver badges30 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
answered Jan 17 at 5:35
user914826user914826
3012 silver badges2 bronze badges
3012 silver badges2 bronze badges
1
In my case it only worked after setting all interfaces to optional: true
– duli
Mar 4 at 14:11
1
In what way is this superior to disabling the systemd service?
– Andreas Hartmann
Aug 16 at 13:42
For me with Ubuntu 18.04 on Vmware, the corresponding file was /etc/netplan/50-cloud-init.yaml; adding optional: true & reboot worked! Related thread: askubuntu.com/questions/1090631/…. Related info on netplan: linux.com/learn/intro-to-linux/2018/9/… (Configuring DHCP)
– Snidhi Sofpro
Aug 21 at 7:29
Thisx worked for me with Ubuntu 18.04.03 LTS (Desktop) where I have disabled NetworkManager and set up networkd with netplan, ans set up br0 for kdvm/qenu virtualisation and dns caching with dnsmaquerade. Newer did not find what goes wrong with my settings, but booys take over 2 minutes without optional: true -setting. With that setting boot is normal and so is functionality also with network.
– Reijo Korhonen
Sep 9 at 21:26
add a comment
|
1
In my case it only worked after setting all interfaces to optional: true
– duli
Mar 4 at 14:11
1
In what way is this superior to disabling the systemd service?
– Andreas Hartmann
Aug 16 at 13:42
For me with Ubuntu 18.04 on Vmware, the corresponding file was /etc/netplan/50-cloud-init.yaml; adding optional: true & reboot worked! Related thread: askubuntu.com/questions/1090631/…. Related info on netplan: linux.com/learn/intro-to-linux/2018/9/… (Configuring DHCP)
– Snidhi Sofpro
Aug 21 at 7:29
Thisx worked for me with Ubuntu 18.04.03 LTS (Desktop) where I have disabled NetworkManager and set up networkd with netplan, ans set up br0 for kdvm/qenu virtualisation and dns caching with dnsmaquerade. Newer did not find what goes wrong with my settings, but booys take over 2 minutes without optional: true -setting. With that setting boot is normal and so is functionality also with network.
– Reijo Korhonen
Sep 9 at 21:26
1
1
In my case it only worked after setting all interfaces to optional: true
– duli
Mar 4 at 14:11
In my case it only worked after setting all interfaces to optional: true
– duli
Mar 4 at 14:11
1
1
In what way is this superior to disabling the systemd service?
– Andreas Hartmann
Aug 16 at 13:42
In what way is this superior to disabling the systemd service?
– Andreas Hartmann
Aug 16 at 13:42
For me with Ubuntu 18.04 on Vmware, the corresponding file was /etc/netplan/50-cloud-init.yaml; adding optional: true & reboot worked! Related thread: askubuntu.com/questions/1090631/…. Related info on netplan: linux.com/learn/intro-to-linux/2018/9/… (Configuring DHCP)
– Snidhi Sofpro
Aug 21 at 7:29
For me with Ubuntu 18.04 on Vmware, the corresponding file was /etc/netplan/50-cloud-init.yaml; adding optional: true & reboot worked! Related thread: askubuntu.com/questions/1090631/…. Related info on netplan: linux.com/learn/intro-to-linux/2018/9/… (Configuring DHCP)
– Snidhi Sofpro
Aug 21 at 7:29
Thisx worked for me with Ubuntu 18.04.03 LTS (Desktop) where I have disabled NetworkManager and set up networkd with netplan, ans set up br0 for kdvm/qenu virtualisation and dns caching with dnsmaquerade. Newer did not find what goes wrong with my settings, but booys take over 2 minutes without optional: true -setting. With that setting boot is normal and so is functionality also with network.
– Reijo Korhonen
Sep 9 at 21:26
Thisx worked for me with Ubuntu 18.04.03 LTS (Desktop) where I have disabled NetworkManager and set up networkd with netplan, ans set up br0 for kdvm/qenu virtualisation and dns caching with dnsmaquerade. Newer did not find what goes wrong with my settings, but booys take over 2 minutes without optional: true -setting. With that setting boot is normal and so is functionality also with network.
– Reijo Korhonen
Sep 9 at 21:26
add a comment
|
This means systemd-networkd-wait-online.service is hanging. There's a few known bugs with it. Check what services want network-online.target with:
systemctl show -p WantedBy network-online.target
You can disable those services if you want. Otherwise, you may have to mask the service as Mr.Ecco indicated.
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
add a comment
|
This means systemd-networkd-wait-online.service is hanging. There's a few known bugs with it. Check what services want network-online.target with:
systemctl show -p WantedBy network-online.target
You can disable those services if you want. Otherwise, you may have to mask the service as Mr.Ecco indicated.
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
add a comment
|
This means systemd-networkd-wait-online.service is hanging. There's a few known bugs with it. Check what services want network-online.target with:
systemctl show -p WantedBy network-online.target
You can disable those services if you want. Otherwise, you may have to mask the service as Mr.Ecco indicated.
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
This means systemd-networkd-wait-online.service is hanging. There's a few known bugs with it. Check what services want network-online.target with:
systemctl show -p WantedBy network-online.target
You can disable those services if you want. Otherwise, you may have to mask the service as Mr.Ecco indicated.
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
edited Sep 19 '18 at 9:44
Afriza N. Arief
1537 bronze badges
1537 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
answered Mar 5 '18 at 18:01
Duncan X SimpsonDuncan X Simpson
4245 silver badges16 bronze badges
4245 silver badges16 bronze badges
add a comment
|
add a comment
|
Masking systemd-networkd-wait-online.service, as suggested in other answers, may help in simple setups but it does not fix the problem. If you mask the service then all other services depending on it will also fail. That means, all services needed to wait until the network is online will fail.
I run into this problem because I use a dynamic fail-over setup for my laptops with bonding the wired (enp9s0) and wireless (wlp12s0) interface that are used as slaves for the main interface bond0. Exactly the same situation do you have if you use a bridge (br0 with slave interfaces). Only the main interfaces bond0 or br0 will get online but not the slaves so systemd-networkd-wait-online.service will fail on the slaves.
The solution to this problem is to modify the service and check only for the interfaces that should go online. You will find with:
~$ sudo systemctl cat systemd-networkd-wait-online.service | grep --after-context=3 '[Service]'
[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-networkd-wait-online
RemainAfterExit=yes
The program systemd-networkd-wait-online has a parameter to test specific interfaces. Check with /lib/systemd/systemd-networkd-wait-online --help. So I make a drop in file to modify the service:
~$ sudo systemctl edit systemd-networkd-wait-online.service
In the empty editor insert these statements, of course with your interface, save them an quit the editor:
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-networkd-wait-online --interface=bond0 --quiet
The empty ExecStart= is important because it disables the "old" command. You can check for more than on interface (look at the help).
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
Excellent, very good answer, that was exactly my problem
– kaklon
Sep 13 at 10:40
add a comment
|
Masking systemd-networkd-wait-online.service, as suggested in other answers, may help in simple setups but it does not fix the problem. If you mask the service then all other services depending on it will also fail. That means, all services needed to wait until the network is online will fail.
I run into this problem because I use a dynamic fail-over setup for my laptops with bonding the wired (enp9s0) and wireless (wlp12s0) interface that are used as slaves for the main interface bond0. Exactly the same situation do you have if you use a bridge (br0 with slave interfaces). Only the main interfaces bond0 or br0 will get online but not the slaves so systemd-networkd-wait-online.service will fail on the slaves.
The solution to this problem is to modify the service and check only for the interfaces that should go online. You will find with:
~$ sudo systemctl cat systemd-networkd-wait-online.service | grep --after-context=3 '[Service]'
[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-networkd-wait-online
RemainAfterExit=yes
The program systemd-networkd-wait-online has a parameter to test specific interfaces. Check with /lib/systemd/systemd-networkd-wait-online --help. So I make a drop in file to modify the service:
~$ sudo systemctl edit systemd-networkd-wait-online.service
In the empty editor insert these statements, of course with your interface, save them an quit the editor:
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-networkd-wait-online --interface=bond0 --quiet
The empty ExecStart= is important because it disables the "old" command. You can check for more than on interface (look at the help).
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
Excellent, very good answer, that was exactly my problem
– kaklon
Sep 13 at 10:40
add a comment
|
Masking systemd-networkd-wait-online.service, as suggested in other answers, may help in simple setups but it does not fix the problem. If you mask the service then all other services depending on it will also fail. That means, all services needed to wait until the network is online will fail.
I run into this problem because I use a dynamic fail-over setup for my laptops with bonding the wired (enp9s0) and wireless (wlp12s0) interface that are used as slaves for the main interface bond0. Exactly the same situation do you have if you use a bridge (br0 with slave interfaces). Only the main interfaces bond0 or br0 will get online but not the slaves so systemd-networkd-wait-online.service will fail on the slaves.
The solution to this problem is to modify the service and check only for the interfaces that should go online. You will find with:
~$ sudo systemctl cat systemd-networkd-wait-online.service | grep --after-context=3 '[Service]'
[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-networkd-wait-online
RemainAfterExit=yes
The program systemd-networkd-wait-online has a parameter to test specific interfaces. Check with /lib/systemd/systemd-networkd-wait-online --help. So I make a drop in file to modify the service:
~$ sudo systemctl edit systemd-networkd-wait-online.service
In the empty editor insert these statements, of course with your interface, save them an quit the editor:
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-networkd-wait-online --interface=bond0 --quiet
The empty ExecStart= is important because it disables the "old" command. You can check for more than on interface (look at the help).
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
Masking systemd-networkd-wait-online.service, as suggested in other answers, may help in simple setups but it does not fix the problem. If you mask the service then all other services depending on it will also fail. That means, all services needed to wait until the network is online will fail.
I run into this problem because I use a dynamic fail-over setup for my laptops with bonding the wired (enp9s0) and wireless (wlp12s0) interface that are used as slaves for the main interface bond0. Exactly the same situation do you have if you use a bridge (br0 with slave interfaces). Only the main interfaces bond0 or br0 will get online but not the slaves so systemd-networkd-wait-online.service will fail on the slaves.
The solution to this problem is to modify the service and check only for the interfaces that should go online. You will find with:
~$ sudo systemctl cat systemd-networkd-wait-online.service | grep --after-context=3 '[Service]'
[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-networkd-wait-online
RemainAfterExit=yes
The program systemd-networkd-wait-online has a parameter to test specific interfaces. Check with /lib/systemd/systemd-networkd-wait-online --help. So I make a drop in file to modify the service:
~$ sudo systemctl edit systemd-networkd-wait-online.service
In the empty editor insert these statements, of course with your interface, save them an quit the editor:
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-networkd-wait-online --interface=bond0 --quiet
The empty ExecStart= is important because it disables the "old" command. You can check for more than on interface (look at the help).
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
answered Jul 23 at 17:58
IngoIngo
1113 bronze badges
1113 bronze badges
Excellent, very good answer, that was exactly my problem
– kaklon
Sep 13 at 10:40
add a comment
|
Excellent, very good answer, that was exactly my problem
– kaklon
Sep 13 at 10:40
Excellent, very good answer, that was exactly my problem
– kaklon
Sep 13 at 10:40
Excellent, very good answer, that was exactly my problem
– kaklon
Sep 13 at 10:40
add a comment
|
Use commands:
$ sudo systemctl stop systemd-networkd-wait-online.service
$ sudo systemctl disable systemd-networkd-wait-online.service
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
7
Could you explain why this is better than the top answer?
– Melebius
Sep 19 '18 at 11:31
4
Welcome to Ask Ubuntu! When you answer, please refrain from posting commands without context. We'd like to see why a given command fixes a problem. Also, as a side note, unless you manually enabled systemd-networkd-wait-online.service, those two commands are not sufficient.
– Duncan X Simpson
Sep 19 '18 at 14:31
add a comment
|
Use commands:
$ sudo systemctl stop systemd-networkd-wait-online.service
$ sudo systemctl disable systemd-networkd-wait-online.service
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
7
Could you explain why this is better than the top answer?
– Melebius
Sep 19 '18 at 11:31
4
Welcome to Ask Ubuntu! When you answer, please refrain from posting commands without context. We'd like to see why a given command fixes a problem. Also, as a side note, unless you manually enabled systemd-networkd-wait-online.service, those two commands are not sufficient.
– Duncan X Simpson
Sep 19 '18 at 14:31
add a comment
|
Use commands:
$ sudo systemctl stop systemd-networkd-wait-online.service
$ sudo systemctl disable systemd-networkd-wait-online.service
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
Use commands:
$ sudo systemctl stop systemd-networkd-wait-online.service
$ sudo systemctl disable systemd-networkd-wait-online.service
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
edited Sep 19 '18 at 11:31
Melebius
7,0065 gold badges29 silver badges51 bronze badges
7,0065 gold badges29 silver badges51 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
answered Sep 19 '18 at 10:46
Jeewan PrakashJeewan Prakash
13 bronze badges
13 bronze badges
7
Could you explain why this is better than the top answer?
– Melebius
Sep 19 '18 at 11:31
4
Welcome to Ask Ubuntu! When you answer, please refrain from posting commands without context. We'd like to see why a given command fixes a problem. Also, as a side note, unless you manually enabled systemd-networkd-wait-online.service, those two commands are not sufficient.
– Duncan X Simpson
Sep 19 '18 at 14:31
add a comment
|
7
Could you explain why this is better than the top answer?
– Melebius
Sep 19 '18 at 11:31
4
Welcome to Ask Ubuntu! When you answer, please refrain from posting commands without context. We'd like to see why a given command fixes a problem. Also, as a side note, unless you manually enabled systemd-networkd-wait-online.service, those two commands are not sufficient.
– Duncan X Simpson
Sep 19 '18 at 14:31
7
7
Could you explain why this is better than the top answer?
– Melebius
Sep 19 '18 at 11:31
Could you explain why this is better than the top answer?
– Melebius
Sep 19 '18 at 11:31
4
4
Welcome to Ask Ubuntu! When you answer, please refrain from posting commands without context. We'd like to see why a given command fixes a problem. Also, as a side note, unless you manually enabled systemd-networkd-wait-online.service, those two commands are not sufficient.
– Duncan X Simpson
Sep 19 '18 at 14:31
Welcome to Ask Ubuntu! When you answer, please refrain from posting commands without context. We'd like to see why a given command fixes a problem. Also, as a side note, unless you manually enabled systemd-networkd-wait-online.service, those two commands are not sufficient.
– Duncan X Simpson
Sep 19 '18 at 14:31
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%2f972215%2fa-start-job-is-running-for-wait-for-network-to-be-configured-ubuntu-server-17-1%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
Those are the fixes. After each change, did you reload NM/systemd? They only read their config files at start.
– user535733
Nov 2 '17 at 17:55
Yes i used systemctl daemon-reload, still the same result
– vlad27
Nov 2 '17 at 18:23