[opensuse-factory] Possible systemd crash after testing for bug in Leap 42.2 Beta 3
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I did: :~ > NOTIFY_SOCKET=/run/systemd/notify systemd-notify "" :~ > I saw in the log: Oct 8 22:05:40 linux-qyxj systemd[1]: Assertion 'n > 0' failed at src/core/manager.c:1510, function manager_invoke_notify_message(). Aborting. Oct 8 22:05:40 linux-qyxj systemd[1]: Caught <ABRT>, dumped core as pid 4130. Oct 8 22:05:40 linux-qyxj systemd[1]: Freezing execution. Oct 8 22:05:42 linux-qyxj systemd-coredump[4131]: Process 4130 (systemd) of user 0 dumped core. Then I tried as root: linux-qyxj:~ # NOTIFY_SOCKET=/run/systemd/notify systemd-notify "" Failed to notify init system: Connection refused linux-qyxj:~ # I thought that was all. Some time later I had to reconfigure sshd and restart it, but it fails: linux-qyxj:~ # rcsshd restart rcsshd: no such service sshd linux-qyxj:~ # systemctl status ssh[tab]Failed to list unit files: Activation of org.freedesktop.systemd1 timed out Failed to list units: Activation of org.freedesktop.systemd1 timed out Failed to list unit files: Activation of org.freedesktop.systemd1 timed out Failed to list units: Activation of org.freedesktop.systemd1 timed out Failed to list unit files: Activation of org.freedesktop.systemd1 timed out Failed to list units: Activation of org.freedesktop.systemd1 timed out ^C linux-qyxj:~ # The log shows: Oct 08 22:09:17 linux-qyxj dbus[978]: [system] Activating systemd to hand-off: service name='org.freedesktop.PackageKit' unit='packagekit.service' Oct 08 22:09:42 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out Oct 08 22:09:42 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:09:56 linux-qyxj dbus[978]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper) Oct 08 22:09:57 linux-qyxj dbus[978]: [system] Successfully activated service 'org.opensuse.Snapper' Oct 08 22:15:01 linux-qyxj cron[4431]: pam_unix(crond:session): session opened for user root by (uid=0) Oct 08 22:15:26 linux-qyxj cron[4431]: pam_systemd(crond:session): Failed to create session: Connection timed out Oct 08 22:15:26 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:15:26 linux-qyxj systemd-logind[1010]: Failed to start user slice user-0.slice, ignoring: Activation of org.freedesktop.systemd1 timed out (org.freede Oct 08 22:15:26 linux-qyxj su[4502]: (to nobody) root on none Oct 08 22:15:27 linux-qyxj su[4502]: pam_unix(su:session): session opened for user nobody by (uid=0) Oct 08 22:15:51 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:15:51 linux-qyxj systemd-logind[1010]: Failed to start user service, ignoring: Connection timed out Oct 08 22:15:52 linux-qyxj su[4502]: pam_systemd(su:session): Failed to create session: Connection timed out Oct 08 22:15:58 linux-qyxj su[4502]: pam_unix(su:session): session closed for user nobody Oct 08 22:16:16 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:16:16 linux-qyxj systemd-logind[1010]: Failed to start session scope session-4.scope: Activation of org.freedesktop.systemd1 timed out Oct 08 22:16:41 linux-qyxj systemd-logind[1010]: Failed to stop user service: Connection timed out Oct 08 22:16:41 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:17:06 linux-qyxj systemd-logind[1010]: Failed to stop user slice: Connection timed out Oct 08 22:17:06 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:17:23 linux-qyxj CRON[4431]: pam_unix(crond:session): session closed for user root Oct 08 22:18:59 linux-qyxj wickedd-dhcp4[1068]: eth0: Committed DHCPv4 lease with address 192.168.74.129 (lease time 1800 sec, renew in 900 sec, rebind in 1575 Oct 08 22:18:59 linux-qyxj wickedd[1074]: route ipv4 0.0.0.0/0 via 192.168.74.2 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv Oct 08 22:19:25 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:19:50 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:20:15 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:30:01 linux-qyxj cron[21487]: pam_unix(crond:session): session opened for user root by (uid=0) Oct 08 22:30:26 linux-qyxj cron[21487]: pam_systemd(crond:session): Failed to create session: Connection timed out Oct 08 22:30:26 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out I thought that this bug had already been patched, but that is not so. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlf5Xp0ACgkQtTMYHG2NR9WQSwCfS2vXP9g2+cXlRXr4yCSHHBZa OgwAn11s5Yhl7QoKqu/VZo5jIiMbjjK7 =arvp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello! Due to https://bugzilla.suse.com/show_bug.cgi?id=1001765 Leap 42.1/2 is not patched yet. Waiting... 09.10.2016 00:01, Carlos E. R. пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I did:
:~ > NOTIFY_SOCKET=/run/systemd/notify systemd-notify "" :~ >
I saw in the log:
Oct 8 22:05:40 linux-qyxj systemd[1]: Assertion 'n > 0' failed at src/core/manager.c:1510, function manager_invoke_notify_message(). Aborting. Oct 8 22:05:40 linux-qyxj systemd[1]: Caught <ABRT>, dumped core as pid 4130. Oct 8 22:05:40 linux-qyxj systemd[1]: Freezing execution. Oct 8 22:05:42 linux-qyxj systemd-coredump[4131]: Process 4130 (systemd) of user 0 dumped core.
Then I tried as root:
linux-qyxj:~ # NOTIFY_SOCKET=/run/systemd/notify systemd-notify "" Failed to notify init system: Connection refused linux-qyxj:~ #
I thought that was all.
Some time later I had to reconfigure sshd and restart it, but it fails:
linux-qyxj:~ # rcsshd restart rcsshd: no such service sshd linux-qyxj:~ # systemctl status ssh[tab]Failed to list unit files: Activation of org.freedesktop.systemd1 timed out Failed to list units: Activation of org.freedesktop.systemd1 timed out Failed to list unit files: Activation of org.freedesktop.systemd1 timed out Failed to list units: Activation of org.freedesktop.systemd1 timed out Failed to list unit files: Activation of org.freedesktop.systemd1 timed out Failed to list units: Activation of org.freedesktop.systemd1 timed out ^C linux-qyxj:~ #
The log shows:
Oct 08 22:09:17 linux-qyxj dbus[978]: [system] Activating systemd to hand-off: service name='org.freedesktop.PackageKit' unit='packagekit.service' Oct 08 22:09:42 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out Oct 08 22:09:42 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:09:56 linux-qyxj dbus[978]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper) Oct 08 22:09:57 linux-qyxj dbus[978]: [system] Successfully activated service 'org.opensuse.Snapper' Oct 08 22:15:01 linux-qyxj cron[4431]: pam_unix(crond:session): session opened for user root by (uid=0) Oct 08 22:15:26 linux-qyxj cron[4431]: pam_systemd(crond:session): Failed to create session: Connection timed out Oct 08 22:15:26 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:15:26 linux-qyxj systemd-logind[1010]: Failed to start user slice user-0.slice, ignoring: Activation of org.freedesktop.systemd1 timed out (org.freede Oct 08 22:15:26 linux-qyxj su[4502]: (to nobody) root on none Oct 08 22:15:27 linux-qyxj su[4502]: pam_unix(su:session): session opened for user nobody by (uid=0) Oct 08 22:15:51 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:15:51 linux-qyxj systemd-logind[1010]: Failed to start user service, ignoring: Connection timed out Oct 08 22:15:52 linux-qyxj su[4502]: pam_systemd(su:session): Failed to create session: Connection timed out Oct 08 22:15:58 linux-qyxj su[4502]: pam_unix(su:session): session closed for user nobody Oct 08 22:16:16 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:16:16 linux-qyxj systemd-logind[1010]: Failed to start session scope session-4.scope: Activation of org.freedesktop.systemd1 timed out Oct 08 22:16:41 linux-qyxj systemd-logind[1010]: Failed to stop user service: Connection timed out Oct 08 22:16:41 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:17:06 linux-qyxj systemd-logind[1010]: Failed to stop user slice: Connection timed out Oct 08 22:17:06 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:17:23 linux-qyxj CRON[4431]: pam_unix(crond:session): session closed for user root Oct 08 22:18:59 linux-qyxj wickedd-dhcp4[1068]: eth0: Committed DHCPv4 lease with address 192.168.74.129 (lease time 1800 sec, renew in 900 sec, rebind in 1575 Oct 08 22:18:59 linux-qyxj wickedd[1074]: route ipv4 0.0.0.0/0 via 192.168.74.2 dev eth0#2 type unicast table main scope universe protocol dhcp covered by a ipv Oct 08 22:19:25 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:19:50 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:20:15 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Oct 08 22:30:01 linux-qyxj cron[21487]: pam_unix(crond:session): session opened for user root by (uid=0) Oct 08 22:30:26 linux-qyxj cron[21487]: pam_systemd(crond:session): Failed to create session: Connection timed out Oct 08 22:30:26 linux-qyxj dbus[978]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
I thought that this bug had already been patched, but that is not so.
- -- Cheers
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlf5Xp0ACgkQtTMYHG2NR9WQSwCfS2vXP9g2+cXlRXr4yCSHHBZa OgwAn11s5Yhl7QoKqu/VZo5jIiMbjjK7 =arvp -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-08 23:12, Mikhail Kasimov wrote:
Hello!
Due to https://bugzilla.suse.com/show_bug.cgi?id=1001765 Leap 42.1/2 is not patched yet. Waiting...
:-( -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-10-09 01:27, Carlos E. R. wrote:
On 2016-10-08 23:12, Mikhail Kasimov wrote:
Hello!
Due to https://bugzilla.suse.com/show_bug.cgi?id=1001765 Leap 42.1/2 is not patched yet. Waiting...
:-(
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Sunday 2016-10-09 01:56, Carlos E. R. wrote:
On 2016-10-09 01:27, Carlos E. R. wrote:
On 2016-10-08 23:12, Mikhail Kasimov wrote:
Hello!
Due to https://bugzilla.suse.com/show_bug.cgi?id=1001765 Leap 42.1/2 is not patched yet. Waiting...
:-(
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off.
Many virtualization frontends have a default that the red icon is configured to do the soft off event. Just go to Settings.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-09 02:59, Jan Engelhardt wrote:
On Sunday 2016-10-09 01:56, Carlos E. R. wrote:
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off.
Many virtualization frontends have a default that the red icon is configured to do the soft off event. Just go to Settings..
It is supposed to do the hard thing. But it probably first talks to the vmtoolsd daemon in the client. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Sunday 2016-10-09 14:51, Carlos E. R. wrote:
On 2016-10-09 02:59, Jan Engelhardt wrote:
On Sunday 2016-10-09 01:56, Carlos E. R. wrote:
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off.
Many virtualization frontends have a default that the red icon is configured to do the soft off event. Just go to Settings..
It is supposed to do the hard thing. But it probably first talks to the vmtoolsd daemon in the client.
It is normally an ACPI event, and if I am not mistaken, systemd handles the softoff ACPI event these days. No tools involved. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-09 17:00, Jan Engelhardt wrote:
On Sunday 2016-10-09 14:51, Carlos E. R. wrote:
On 2016-10-09 02:59, Jan Engelhardt wrote:
On Sunday 2016-10-09 01:56, Carlos E. R. wrote:
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off.
Many virtualization frontends have a default that the red icon is configured to do the soft off event. Just go to Settings..
It is supposed to do the hard thing. But it probably first talks to the vmtoolsd daemon in the client.
It is normally an ACPI event, and if I am not mistaken, systemd handles the softoff ACPI event these days. No tools involved.
I thought it was a power supply event. At least after two seconds. Cut the cable. How does one cut the cable in vmware? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Sunday 2016-10-09 19:32, Carlos E. R. wrote:
It is normally an ACPI event, and if I am not mistaken, systemd handles the softoff ACPI event these days. No tools involved.
I thought it was a power supply event. At least after two seconds. Cut the cable. How does one cut the cable in vmware?
This is not a VMware help forum. But do look at the settings for the virtual machine, it's the sane place for it to be in. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-09 20:37, Jan Engelhardt wrote:
On Sunday 2016-10-09 19:32, Carlos E. R. wrote:
It is normally an ACPI event, and if I am not mistaken, systemd handles the softoff ACPI event these days. No tools involved.
I thought it was a power supply event. At least after two seconds. Cut the cable. How does one cut the cable in vmware?
This is not a VMware help forum. But do look at the settings for the virtual machine, it's the sane place for it to be in.
I had to kill -9 the container. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Sunday 2016-10-09 10:04, Martin Pluskal wrote:
On 09.10.2016 1:56, Carlos E. R. wrote:
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off. You should be glad that your computer is not on fire now.
Note how the Samsung Notes (being Android) do *not* run systemd, and now they *are* on fire. Not too long ago, the systemd Google+ page also used an extinguisher as its icon. It all makes sense now! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-09 10:04, Martin Pluskal wrote:
On 09.10.2016 1:56, Carlos E. R. wrote:
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off. You should be glad that your computer is not on fire now.
That's why I tried on a virtual machine. I was convinced that the issue had already been patched. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Hello! Stay strong and calm. :) 09.10.2016 15:49, Carlos E. R. пишет:
On 2016-10-09 10:04, Martin Pluskal wrote:
On 09.10.2016 1:56, Carlos E. R. wrote:
The crash is so bad that the virtual machine (vmware player) in which this 42.2 system is running can not be powered off. You should be glad that your computer is not on fire now. That's why I tried on a virtual machine. I was convinced that the issue had already been patched.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Carlos E. R. -
Carlos E. R. -
Jan Engelhardt -
Martin Pluskal -
Mikhail Kasimov