I successfully installed 12.1 on an old box. My problem is that the system boots in 40 sec, but the network is available only after 5 minutes.
Nov 19 19:00:56 dolo systemd[1]: Failed to read PID file /var/run/haveged.pid after start. The service might be broken.
Nov 19 19:00:56 dolo haveged: arch: x86#012vendor: intel#012generic: 0#012i_cache: 16#012d_cache: 16#
012loop_idx: 34#012loop_idxmax: 40#012loop_sz: 14081#012loop_szmax: 91882#012etime: 113409#012havege_ndpt 0
Nov 19 19:00:56 dolo SuSEfirewall2: Firewall rules set to CLOSE.
Nov 19 19:00:56 dolo SuSEfirewall2_init[496]: Loading basic firewall rules ..done
Nov 19 19:00:57 dolo network[601]: Setting up (localfs) network interfaces:
Nov 19 19:00:58 dolo network[601]: lo
Nov 19 19:00:58 dolo ifup: lo
Nov 19 19:00:58 dolo ifup: lo
Nov 19 19:00:58 dolo ifup: IP address: 127.0.0.1/8
Nov 19 19:00:58 dolo network[601]: lo IP address: 127.0.0.1/8
Nov 19 19:00:58 dolo ifup:
Nov 19 19:00:59 dolo network[601]: ..done eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet
Nov 19 19:00:59 dolo ifup: eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet
Nov 19 19:00:59 dolo kernel: 21.457332] ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 19 19:00:59 dolo kernel: 21.460304] e100 0000:01:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
Nov 19 19:00:59 dolo kernel: 21.460650] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 19 19:00:59 dolo ifup: eth0
Nov 19 19:00:59 dolo ifup: IP address: 192.168.2.210/24
Nov 19 19:00:59 dolo network[601]: eth0 IP address: 192.168.2.210/24
Nov 19 19:00:59 dolo ifup:
Nov 19 19:03:33 dolo systemd-logind[498]: New user root logged in.
Nov 19 19:03:33 dolo systemd-logind[498]: New session 1 of user root.
Nov 19 19:03:33 dolo dbus-daemon[538]: dbus[538]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit'
unit='console-kit-daemon.service'
Nov 19 19:03:33 dolo dbus[538]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-
daemon.service'
Nov 19 19:03:33 dolo console-kit-daemon[963]: missing action
Nov 19 19:03:33 dolo dbus-daemon[538]: dbus[538]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servic
ehelper)
Nov 19 19:03:33 dolo dbus[538]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Nov 19 19:03:33 dolo polkitd[1030]: started daemon version 0.102 using authority implementation `local' version `0.102'
Nov 19 19:03:33 dolo dbus-daemon[538]: dbus[538]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Nov 19 19:03:33 dolo dbus[538]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Nov 19 19:03:33 dolo dbus-daemon[538]: dbus[538]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Nov 19 19:03:33 dolo dbus[538]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
**Nov 19 19:05:56 dolo systemd[1]: network.service operation timed out. Terminating.**
Nov 19 19:05:56 dolo systemd[1]: Unit network.service entered failed state.
Nov 19 19:05:56 dolo ntp[1093]: /etc/rc.status: line 54: /dev/stderr: No such device or address
Nov 19 19:05:57 dolo SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Nov 19 19:05:57 dolo sshd[1090]: Starting SSH daemon..done
Nov 19 19:05:57 dolo SuSEfirewall2: using default zone 'ext' for interface eth0
Nov 19 19:05:57 dolo ntp[1093]: 19 Nov 19:05:57 sntp[1143]: Started sntp
Nov 19 19:05:58 dolo ntp[1093]: 2011-11-19 19:05:57.517275 (-0100) +0.544886
Nov 19 19:05:58 dolo ntp[1093]: 2011-11-19 19:05:58.076751 (-0100) +0.000774 +/- 0.057709 secs
Nov 19 19:05:58 dolo ntp[1093]: 2011-11-19 19:05:58.094171 (-0100) +0.001204 +/- 0.053436 secs
That’s right. I also experienced strange network- and all kind of other issues with systemd. E.g. machine went offline after a few minutes, without any log entry anywhere what went wrong. sysvinit has fixed that for me. Sadly, as I think systemd conceptually the definitely superior way, but if it does fail in basic operations like maintaining a reliable network collection…>:)
Definitely not the best advertisment for openSUSE QA.
On 2011-11-20 12:36, Knurpht wrote:
>
> systemd is causing this. Install sysvinit-init, it will tell you to
> remove systemd-init. Accept that. reboot and you’'ll be fine.
You do not need to install anything to try.
At the boot grub screen, there is a little menu. F5 (Init program) lets you
choose: Default, systemd, system V, and shell. Choose system V, and try. If
it solves the issue, report bug in bugzilla, please.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I use the system as a server, without keyboard and monitor. I have the opportunity next week to test the little menu in grub. Until next week, i hope i do not have to reboot it
On 11/20/2011 09:26 AM, Larx wrote:
>
> That’s right. I also experienced strange network- and all kind of other
> issues with systemd. E.g. machine went offline after a few minutes,
> without any log entry anywhere what went wrong. sysvinit has fixed that
> for me. Sadly, as I think systemd conceptually the definitely superior
> way, but if it does fail in basic operations like maintaining a reliable
> network collection…>:)
>
> Definitely not the best advertisment for openSUSE QA.
As systemd is relatively new, there will be problems. If you had tested the
developmental versions AND reported any such bugs to the Bugzilla, then you
should expect them to have been addressed. Let me guess: you did neither of the
above. In that case go back to using systemv. The method is documented in the
Release Notes. Have you read them?
I have 4 systems running 12.1 with three of them starting correctly with
systemd. As to the fourth, I have not yet taken the time to discover why it
fails as it is intermittent. Using systemv is a perfectly good work around.
Yo, guys, let’s keep the tone friendly and respectful. Let’s concentrate on getting the appropriate info together to file a new and accurate bugreport.
A couple of things:
I installed on 4 machines, systemd initially ran OK on all four, i.e. on the first boot(s) after install. Now it does not on 3 machines. The error is the same on all three: Failed to read PID file, this for haveged and dbus, like described in the bugreports. I experienced similar things on Tumbleweed, but then systemd was removed from Tumbleweed, so I decided to wait for 12.1.
I did google around and found bugreports on the matter, already indicating duplicates.
For now, I’ll reboot using systemd, then paste the lines that I think matter for a good bugreport.
Please guys, let’s keep it friendly and respectful. And concentrate on getting the info together to file a decent bugreport.
Funny thing is, I installed on a couple of machines and systemd worked on the first “normal” boot. But, except for one machine, stopped doing so. The errors are the same on all three machines: Failed to read PID file, this for “haveged” and “dbus”. My 2 cents are that these are the origin of f.e. networkmanager and others.
Googled a bit and found some bugreports on this already, but a bit older. To quicken things, I’d rather have some more documentation (i.e. logfiles.errors)
ill return to systemd now, and copy and paste the lines containing the error messages. If others report the same, I’ll file a bugreport.
Weird, behaviour/log is not the same on every boot … I’m now finding this:
Nov 20 21:13:38 knurpht xdm[1003]: Starting service gdm
Nov 20 21:13:38 knurpht xdm[1003]: ** (gdm:1073): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Bestand of map bestaat niet
Nov 20 21:13:38 knurpht startproc: startproc: exit status of parent of /usr/sbin/gdm: 1
Nov 20 21:13:38 knurpht xdm[1003]: ..failed
Having systemd throws a console login prompt. If I do “init 3”, xdm starts !!! I don’t get this at all. Tried disabling apparmor (since that does not run on the one machine where systemd works. But in the meantime systemd does not work on that machine anymore.
BTW: if the laptop manages to boot through systemd, I find a 100% cpu load for the dbus process.
My problem simply starts with the fact that I don’t know what went wrong with systemd as I find no documentation where I find the logs when booting. Not even errors seem to be reported to the unsuspecting user, some things simply don’t work without notification to the user (at least for my update this was the case, don’t know if clean installs work better).
I guess for the next months the best advice for many 12.1 update problems will be “disable systemd” (as it was in former times for audio problems with pulseaudio). I get this experience from reading the posts here, which describe quite a few problems, especially network related, when using 12.1, so it’s not me alone.
Thank’s a lot for that hint. I tried quite a while to fix the problem with different configurations with no success. Until I saw that error message “network.service operation timed out. Terminating.” and found this thread here. Now I am more happy with 12.1.
Kind regards
Peter
For those encountering similar 5-minute waits during boot due to network.service operation timing out, this bug fix resolved my issue. It wasn’t clear that the original poster had samba (smb/nmb) services enabled at boot time, but I certainly did. The opensuse 12.1 update repository had this fix as of 22 Feb 2012. For now this allows me to stick with systemd.
Now I can move on to verifying the gnucash issue on opensuse 12.1.
… I’m now finding this: