Ubuntu – how to fix “ a start job is running for the raise network ” in ubuntu server 16.0 LTS

networkingserver

I have recently installed ubuntu server 16.04 LTS.a message is coming at the starting time " a start job is running for the raise network " & it takes too much time under offline network. but, when it comes to online makes no problem. how to make faster the startup process without this annoying message if I want to come offline ? and also there is a bridge connection named "virbr0" but not the simple ethernet network, why is this happening ?

need help .

Best Answer

I seem to get the same issue and I also have a bridged network interface, probably from my VirtualBox setup, enp0s31f6:avahi.

My system is ubuntu 16.04 LTS server variant, installed on a laptop, so primary use is as a workstation. As pr the comments this still applies for ubuntu 20.04 LTS.

The issue is there if the bridged interface is there, not if it's not present, say if VirtualBox has not been started inbetween reboots.

The reason is as in the other answer that this interface lacks init info.

My sollution was to reduce the timeout, and to do so without messing with the base installed networking.services systemd file. This will persist during updates in any package.

sudo mkdir -p /etc/systemd/system/networking.service.d/
sudo bash -c 'echo -e "[Service]\nTimeoutStartSec=20sec" > /etc/systemd/system/networking.service.d/timeout.conf'
sudo systemctl daemon-reload

Related Solutions

Wireless Networking on Ubuntu Server – How to Set Up WiFi

The declarations 'auto p4p1' and 'auto wlan0' ask the system to automatically start both interfaces. When you start with the ethernet detached and have asked that the interface start anyway, the system stumbles: "waiting up to 60 more seconds for network configuration."

It would be more efficient, but certainly not automatic, to leave out the 'auto' declaration:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

#auto wlan0
iface wlan0 inet dhcp
wpa-ssid <my_ssid>
wpa-psk <my_ssid_password>

# The primary network interface
#auto p4p1
iface p4p1 inet dhcp

And start either interface manually as needed:

sudo ifup -v wlan0

Ubuntu – Ethernet not working on Ubuntu – Driver r8169: link down

The driver r8169 is problematic and there are several things we might try. Let's start with the simplest first and see if we can fix it. If not, I will edit this answer to proceed to the more complex.

Please open a terminal and do:

sudo ethtool -s eth0 speed 100 duplex full autoneg off

Now check:

dmesg | grep eth0

Does the link come back up? Note that it was previously:

r8169 0000:02:00.0 eth0: link down

I notice that you are dual-booting with Windows. This is an issue with the driver r8169 in some cases. Please see: https://en.opensuse.org/SDB:Realtek_8169_driver_problem In particular:

You enable "Wake-on-lan after shutdown." in the Windows device manager. This prevents the Windows driver to disable the card. With newer Windows driver versions this option is not available anymore, instead there is an option "Shutdown Wake On Lan". Changing that new option from "Enabled" to "Disabled" cannot be confirmed to fix the issue.

Please find and reverse the setting for Wake-on-LAN in Windows. Reboot into Ubuntu and check again:

dmesg | grep -e r8169 -e eth0

Any improvement?

If you have compiled the r8168 driver, I suggest you blacklist r8169:

sudo -i
echo "blacklist r8169"  >>  /etc/modprobe.d/blacklist.conf
exit

Reboot. Confirm that r8168 is loaded:

lsmod

Any improvement?

Best Answer

Related Solutions

Wireless Networking on Ubuntu Server – How to Set Up WiFi

Ubuntu – Ethernet not working on Ubuntu – Driver r8169: link down

Related Question