The NetworkManager and rsyslog services were failing to start after the upgrade of the systems from Fedora 14. The workaround was working so well that I did not get around to looking into the issue till today.
A quick search for the error:
Since this was likely to be the solution, I also tried
I removed the workaround script in /etc/rc.local. As expected, the system worked fine.
If I come across any more services which fail to start at boot time, e.g. nfs, I know what to try first.
I am, though, still curious - why is the ethernet device still eth0!
A quick search for the error:
The solution appeared to be that I needed to enable the service:Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory.
$sudo systemctl enable NetworkManager.service
It created symlinks in /etc/systemd/system and /etc/systemd/system/multi-user.target.wants/ folders.Since this was likely to be the solution, I also tried
$sudo systemctl enable rsyslog.service
This also created a symlink in /etc/systemd/system/multi-user.target.wants/.
I removed the workaround script in /etc/rc.local. As expected, the system worked fine.
If I come across any more services which fail to start at boot time, e.g. nfs, I know what to try first.
I am, though, still curious - why is the ethernet device still eth0!
Maybe Matt's positional network names were postponed. Good question though. Not that I am all that enthusiastic about it... It may be a problem for Dell, but sure wasn't a problem for anyone else. Heck I once talked to a sysadmin. He said "oh just just run ifup on all of them and let DHCP sort things out".
ReplyDelete