Why I'm giving message `A start job is running for raise network interfaces` at boot after disabling predictable network interfaces names?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX
line in /etc/default/grub from:
GRUB_CMDLINE_LINUX="pci=nomsi"
to:
GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"
on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.
After disabling predictable network interfaces names I'm giving following message at boot:
A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)
and system boots long.
My /etc/network/intefaces
file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
Why am I giving this message at boot? How can I avoid long booting of my system?
debian systemd network-interface
add a comment |Â
up vote
1
down vote
favorite
I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX
line in /etc/default/grub from:
GRUB_CMDLINE_LINUX="pci=nomsi"
to:
GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"
on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.
After disabling predictable network interfaces names I'm giving following message at boot:
A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)
and system boots long.
My /etc/network/intefaces
file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
Why am I giving this message at boot? How can I avoid long booting of my system?
debian systemd network-interface
A background question on the jargon: unix.stackexchange.com/questions/310737
â JdeBP
Aug 11 '17 at 5:29
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX
line in /etc/default/grub from:
GRUB_CMDLINE_LINUX="pci=nomsi"
to:
GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"
on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.
After disabling predictable network interfaces names I'm giving following message at boot:
A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)
and system boots long.
My /etc/network/intefaces
file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
Why am I giving this message at boot? How can I avoid long booting of my system?
debian systemd network-interface
I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX
line in /etc/default/grub from:
GRUB_CMDLINE_LINUX="pci=nomsi"
to:
GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"
on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.
After disabling predictable network interfaces names I'm giving following message at boot:
A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)
and system boots long.
My /etc/network/intefaces
file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
Why am I giving this message at boot? How can I avoid long booting of my system?
debian systemd network-interface
debian systemd network-interface
edited Aug 10 '17 at 16:59
asked Aug 10 '17 at 16:39
java-devel
255215
255215
A background question on the jargon: unix.stackexchange.com/questions/310737
â JdeBP
Aug 11 '17 at 5:29
add a comment |Â
A background question on the jargon: unix.stackexchange.com/questions/310737
â JdeBP
Aug 11 '17 at 5:29
A background question on the jargon: unix.stackexchange.com/questions/310737
â JdeBP
Aug 11 '17 at 5:29
A background question on the jargon: unix.stackexchange.com/questions/310737
â JdeBP
Aug 11 '17 at 5:29
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Solved by changing file /etc/network/interfaces.d/setup
from:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
to:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
This worked for me in Debian 9.1
â Ajeeb.K.P
Aug 14 '17 at 8:33
add a comment |Â
up vote
1
down vote
Disable the service that waits to start the network interfaces.
systemctl disable NetworkManager-wait-online.service
And to enable:
systemctl enable NetworkManager-wait-online.service
Alternatively you can reduce the amount of time that it waits to start the job.
vim /etc/systemd/system/network-online.target.wants/networking.service
TimeoutStartSec=5min ##Change parameter, should be at the end of the page.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Solved by changing file /etc/network/interfaces.d/setup
from:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
to:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
This worked for me in Debian 9.1
â Ajeeb.K.P
Aug 14 '17 at 8:33
add a comment |Â
up vote
3
down vote
accepted
Solved by changing file /etc/network/interfaces.d/setup
from:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
to:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
This worked for me in Debian 9.1
â Ajeeb.K.P
Aug 14 '17 at 8:33
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Solved by changing file /etc/network/interfaces.d/setup
from:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
to:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
Solved by changing file /etc/network/interfaces.d/setup
from:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
to:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
answered Aug 10 '17 at 19:01
java-devel
255215
255215
This worked for me in Debian 9.1
â Ajeeb.K.P
Aug 14 '17 at 8:33
add a comment |Â
This worked for me in Debian 9.1
â Ajeeb.K.P
Aug 14 '17 at 8:33
This worked for me in Debian 9.1
â Ajeeb.K.P
Aug 14 '17 at 8:33
This worked for me in Debian 9.1
â Ajeeb.K.P
Aug 14 '17 at 8:33
add a comment |Â
up vote
1
down vote
Disable the service that waits to start the network interfaces.
systemctl disable NetworkManager-wait-online.service
And to enable:
systemctl enable NetworkManager-wait-online.service
Alternatively you can reduce the amount of time that it waits to start the job.
vim /etc/systemd/system/network-online.target.wants/networking.service
TimeoutStartSec=5min ##Change parameter, should be at the end of the page.
add a comment |Â
up vote
1
down vote
Disable the service that waits to start the network interfaces.
systemctl disable NetworkManager-wait-online.service
And to enable:
systemctl enable NetworkManager-wait-online.service
Alternatively you can reduce the amount of time that it waits to start the job.
vim /etc/systemd/system/network-online.target.wants/networking.service
TimeoutStartSec=5min ##Change parameter, should be at the end of the page.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Disable the service that waits to start the network interfaces.
systemctl disable NetworkManager-wait-online.service
And to enable:
systemctl enable NetworkManager-wait-online.service
Alternatively you can reduce the amount of time that it waits to start the job.
vim /etc/systemd/system/network-online.target.wants/networking.service
TimeoutStartSec=5min ##Change parameter, should be at the end of the page.
Disable the service that waits to start the network interfaces.
systemctl disable NetworkManager-wait-online.service
And to enable:
systemctl enable NetworkManager-wait-online.service
Alternatively you can reduce the amount of time that it waits to start the job.
vim /etc/systemd/system/network-online.target.wants/networking.service
TimeoutStartSec=5min ##Change parameter, should be at the end of the page.
answered Aug 10 '17 at 17:06
Hunter.S.Thompson
4,66931334
4,66931334
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f385281%2fwhy-im-giving-message-a-start-job-is-running-for-raise-network-interfaces-at%23new-answer', 'question_page');
);
Post as a guest
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
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
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
A background question on the jargon: unix.stackexchange.com/questions/310737
â JdeBP
Aug 11 '17 at 5:29