Bug 918585

Summary: Zombie processes after update
Product: [openSUSE] openSUSE 13.1 Reporter: Michal Svec <msvec>
Component: BasesystemAssignee: Fridrich Strba <fstrba>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: msvec, thomas.blume
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Michal Svec 2015-02-19 10:17:51 UTC 
After a recent 13.1 update I suddenly have many zombie processes:

35032 ?        Z      0:00 [nrpe] <defunct>
35036 ?        Z      0:00 [nrpe] <defunct>
35040 ?        Z      0:00 [nrpe] <defunct>
35044 ?        Z      0:00 [nrpe] <defunct>
[...]

Not sure yet, which update caused it, but messages like this are in the log:

dbus[656]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
dbus[656]: [system] Failed to activate service 'org.freedesktop.login1': timed out
dbus[656]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Comment 1 Michal Svec 2015-02-19 10:22:37 UTC 
Downgrading systemd from 208-28.1 to 208-23.3 did not help.
So I suppose the culprit seems to be dbus.
Comment 2 Michal Svec 2015-02-19 10:34:39 UTC 
The version of dbus installed is 1.8.16-4.36.2
Downgrading to 1.8.14-4.32.3 or 1.8.12-4.28.2 didn't help.
Comment 3 Michal Svec 2015-02-19 10:36:48 UTC 
Nor did downgrade to systemd 208-23.3 helped.
Comment 4 Michal Svec 2015-02-19 10:47:35 UTC 
The system behaves really strange:

bash# systemctl status apache2
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
Comment 5 Michal Svec 2015-02-19 10:49:00 UTC 
Also, this is in the log:

systemd[2010]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
Comment 6 Thomas Blume 2015-02-20 14:03:03 UTC 
duplicate of bug 915218

*** This bug has been marked as a duplicate of bug 915218 ***
Comment 7 Thomas Blume 2015-02-20 15:09:36 UTC 

*** This bug has been marked as a duplicate of bug 918226 ***