Eno1 interface failure at boot

Question

Hi all,
EDIT: I've now spent most of the day on this, but unfortunately haven't progressed at all. I've gone through the debugging steps suggested in the Networking Configuration article. I've also been reading through lots of other posts about networking problems. It sounds like it *might* be a race condition brought on by the kernel and udev having different names for the device? So the kernel starts doing stuff and then udev changes it's name, or something like that. Unfortunately, I still don't have any idea how to push this forward. Any advice, even just regarding where to look next, would be super helpful.
I've run Arch as my home workstation for a couple of years now, but I've recently installed it on a new machine and I'm out of my depth with the new networking tools and conventions. I'm hoping you can point me to the best place to look for debug information.
The recently created machine was working well for a couple of weeks, but a recent update has caused it to lose the eno1 device.
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu ...
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
(by the way, because the machine has no connection to the outside world, I'm typing all this output by hand, so I'm truncating much of it)
# lspci -v | grep -A 9 Ethernet
00:19.0 Ethernet controller: Intel Corporaion 82579V Gigabit Network Connection (rev 06)
Subystem: ASUSTek Computer Inc. P8P67 Deluxe Motherboard
Flags: bus master, fast devsel, latency 0, IRQ15
... (some stuff about it's ports and memory)
Note: I know that previously lspci was able to also tell me the kernel driver used for the ethernet device. It was e1000e. Now, for some reason, that information is not longer listed there.
# dmesg | grep e1000e
That kernel driver is not automatically loaded. I did try modprobe e1000e, but that didn't seem to make any difference. There's probably something else I'd have to do after that, but I don't know what.
# cat /etc/systemd/system/multi-user.target.wants/[email protected]
[Unit]
Description=dhcpcd on %I
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=system-subsystem-net-devices-%i.device
[Service]
Type=forking
PIDFile=/run/dhcpcd-%I.pid
ExecStart=/usr/bin/dhcpcd -q -w %I
ExecStop=/usr/bin/dhcpcd -x %I
[Install]
WantedBy=multi-use.target
Note: I did not create this file. I'm pretty sure it was created for me when I ran systmctl enable [email protected] (or something like that) during initial installation.
# journalctl -x -u network
nothing here. Grep-ing for eno1 shows something like: (it's a lot of text, so I'm paraphrasing)
# journalctl -x | grep eno1
Expecting device sys-subsystem-net-devices-eno1.device...
Job sys-subsystem-net-devices-eno1.device/start timed out.
Timed out waiting for device sys-subsystem-net-devices-eno1.device
Subject: Unit sys-subsystem-net-devices-eno1.device has failed.
Dependency failed for dhcpcd on eno1.
Subject: Unit [email protected] has failed
As I was debugging (using this post, and this post for ideas) I found a log saying "renaming eth0 to eno1", but I can't figure out what command or file displayed that information. Note that, I as far as I know, the wired network device has been called eno1 since the initial installation. I've never configured it to be called eth0. This document seems to suggest that the kernel uses eth0 to name the device before it turns things over to udev.
Unfortunately, other than searching the machine for useful error messages, I haven't been able to progress much farther than that. I'm at a loss as to what to do next.
The very first thing I'd *like* to do is manually get the interface working, so that I can connect to this board via that machine. Being able to copy/paste would save me a ton of time in future posts.
Any suggestions?
Last edited by aarondev (2014-04-13 22:51:30)

Answer 1

solved! if I change host in sabnzbd from localhost (the default) to 0.0.0.0 it works
not sure why? I'm a new user so have a lot to learn it seems =/