Several errors in boot log 13.1

English Install/Boot/Login
#1

Hi,

though I have searched far and wide for explanations and/or solutions to these errors, none have either been found or helped. Despite those errors, my appliance (built in suseStudio) boots normally, with everything working in the suseStudio’s TestDrive. My wits and knowledge are running low, still learning about systemd, but it hasn’t helped yet.

Cut the long story short, I’m politely asking that someone tells me should I worry about these

Jan 14 12:03:37 linux-prgk systemd[1]: Failed to start ifup managed network interface ens3.

Jan 14 12:03:39 linux-prgk postfix/postfix-script[8576]: fatal: the Postfix mail system is not running // it gets started few lines below, not sure if relevant

Jan 14 12:03:59 linux-prgk systemd[1]: Failed to start LSB: Configure network interfaces and set up routing. // despite that, /etc/resolv.conf gets written in, ifcfg-ens3 created, also says it’s not able to contact DNS server

Jan 14 12:04:04 linux-prgk systemd[9814]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory // there really isn’t. research said not to worry about these, but would like to get rid of them if possible…

Jan 14 12:07:17 linux-prgk systemd[9932]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory

Most of my concern is about those ifup and LSB network errors… I updated dhcpcd to v5, that got rid of some network problems, but not these.

output of systemctl status network

network.service - LSB: Configure network interfaces and set up routing Loaded: loaded (/usr/lib/systemd/system/network.service; enabled)
Active: failed (Result: exit-code) since Tue 2014-01-14 12:31:49 CET; 6min ago

Jan 14 12:31:48 linux-xlq1 network[859]: 25 23 22 20 18 17 15 14 12 11 9 8 6 5 3 2 0
Jan 14 12:31:48 linux-xlq1 network[859]: ens3 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139
Jan 14 12:31:49 linux-xlq1 network[859]: ens3 DHCP4 client NOT running
Jan 14 12:31:49 linux-xlq1 network[859]: ens3 valid_lft forever preferred_lft forever IP address: 10.0.2.15/24
Jan 14 12:31:49 linux-xlq1 network[859]: ens3 is up
Jan 14 12:31:49 linux-xlq1 network[859]: …failed ens3 interface could not be set up until now
Jan 14 12:31:49 linux-xlq1 network[859]: …failedSetting up service network . . . . . . . . . . . . …failed
Jan 14 12:31:49 linux-xlq1 systemd[1]: network.service: control process exited, code=exited status=7
Jan 14 12:31:49 linux-xlq1 systemd[1]: Failed to start LSB: Configure network interfaces and set up routing.
Jan 14 12:31:49 linux-xlq1 systemd[1]: Unit network.service entered failed state.

network@ens3.service - ifup managed network interface ens3
Loaded: loaded (/usr/lib/systemd/system/network@.service; static)
Active: failed (Result: exit-code) since Tue 2014-01-14 12:31:21 CET; 8min ago

Jan 14 12:31:20 linux-xlq1 ifup[1411]: ens3 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)
Jan 14 12:31:21 linux-xlq1 ifup-dhcp[1509]: Starting DHCP4 client on ens3
Jan 14 12:31:21 linux-xlq1 ifup-dhcp[1585]: . .
Jan 14 12:31:21 linux-xlq1 ifup[1368]: Starting DHCP4 client on ens3. .
Jan 14 12:31:21 linux-xlq1 ifup-dhcp[1587]: Jan 14 12:31:21 linux-xlq1 ifup[1368]: ens3 DHCP4 client NOT running
Jan 14 12:31:21 linux-xlq1 ifup-dhcp[1591]: ens3 DHCP4 client NOT running
Jan 14 12:31:21 linux-xlq1 systemd[1]: network@ens3.service: control process exited, code=exited status=7
Jan 14 12:31:21 linux-xlq1 systemd[1]: Failed to start ifup managed network interface ens3.
Jan 14 12:31:21 linux-xlq1 systemd[1]: Unit network@ens3.service entered failed state.

#2

Wrong forum ?

#3

It is working right?? The network works?

It is not uncommon to have some failures in the logs

#4

It works, not exactly sure how, but still no solution to failed start of network and network@[device] services…

#5

Are you sure. If the network works those failure reports only represents a failed attempt and later it may try another way/method and it apparently works.

#6

Maybe it’s this issue?
https://www.suse.com/releasenotes/i386/openSUSE/13.1/RELEASE-NOTES.en.html#sec.131.systemd-networkif

Please post the output of “ifconfig”. Maybe your ens3 is such a duplicated interface and should just be removed.

#7

Thank you, I’ll accept that as a solution, it certainly looks like that’s happening, and wait for dist-updates, maybe it gets fixed.

dhcpcd fails to set IP address, and ifup-dhcp does it.

linux-scd7:~ # ifconfig -a
ens3 Link encap:Ethernet HWaddr 52:54:00:12:34:56
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::5054:ff:fe12:3456/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1975 errors:0 dropped:0 overruns:0 frame:0
TX packets:1447 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:122605 (119.7 Kb) TX bytes:260920 (254.8 Kb)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 b) TX bytes:480 (480.0 b)

There is no mentioning of another or duplicate interface, everything looks clean.

#8

Posting this as an another possible solution, updating sysconfig-network is said to fix this problem

https://bugzilla.novell.com/show_bug.cgi?id=853908

Current sysconfig-network
Repository: openSUSE 13.1 UpdatesVersion: 0.81.5-10.1

Marking as solved, thanks to everyone.

#9

I spoke too soon.

(Following instructions worked in my case, and are no guarantee in solving your problem, but if you have similar errors logged, you could give it a try)

Found out that, if your DHCP isn’t starting itself, make it! (D’oh! to myself)

To do that, you must run it at boot before ifcfg gets a chance to try and assign IP address to any interface it found.
With dhcpcd installed, there should be a dhcpcd.service file included, not in my case, so I created one.

Create a service called dhcpcd.service in /usr/lib/systemd/system/ folder, and put the following in it:


[Unit]
Description=dhcpcd on all interfaces
Wants=network.target
Before=network.target


[Service]
Type=forking
ExecStart=/sbin/dhcpcd -q -b
ExecStop=/sbin/dhcpcd -x
RemainAfterExit=yes


[Install]
WantedBy=multi-user.target graphical.target

Mind that lines ExecStart/Stop= depend on whether dhcpcd executable is in /sbin or /usr/bin or somewhere else.

Then do (as root)


systemctl enable dhcpcd
systemctl daemon-reload

To see it in action, reboot, or just “systemctl start dhcpcd”.

Hope someone can confirm this soon and that it helps someone, as a possible solution, at least.
Cheers