I have a home built NAS that up untill recently had been running wheezy with no graphical interface (console only as it is headless and boots off a SD card).
I decided that it is time to upgrade and I did a system upgrade to Jessie with no problems.
I then upgraded to Stretch and while it is running I am plagued by a really long (5 minute) boot time.
On boot I am seeing that the job that is taking long to start is networking.services and after booting and running a systemctl status networking.service i get the following:
Code: Select all
* networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-10-08 13:06:20 SAST; 13s ago
Docs: man:interfaces(5)
Process: 3911 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 3907 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=1/FAILURE)
Main PID: 3911 (code=exited, status=1/FAILURE)
Oct 08 13:06:20 debian systemd[1]: Starting Raise network interfaces...
Oct 08 13:06:20 debian ifup[3911]: ifup: unknown interface eth0
Oct 08 13:06:20 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Oct 08 13:06:20 debian systemd[1]: Failed to start Raise network interfaces.
Oct 08 13:06:20 debian systemd[1]: networking.service: Unit entered failed state.
Oct 08 13:06:20 debian systemd[1]: networking.service: Failed with result 'exit-code'.
root@debian:~# systemctl start networking.service
Job for networking.service failed because the control process exited with error code.
See "systemctl status networking.service" and "journalctl -xe" for details.
So it is definitely the network cards (board has 4 of them but I am only using one) that is causing the issue.
The outcome from journalctl -xe is linked here http://www.tunguydesmarais.com/journalctl.txt
Looking at it it is clear that the system is going into a roudn about loop of DHCP requesting and offering.
Since the netowrk is up after startup (as I am SSHing into the box) but networking.service is in a failed state I am assuming that there is some legacy networkign mechanism from wheezy or jessie that is fighting with networking.services but here my knowledge get limited.
Is anyone able to help step me through debugging this?
The contents of /etc/network/interfaces is:
Code: Select all
# 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
# The primary network interface
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
Also worth noting that there is no /dev/eth0 device in the system so I am not sure how it is working
I