You are not logged in.

#1 2014-03-05 13:08:09

dizzib
Member
Registered: 2013-12-09
Posts: 7

[SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

The 'Sending SIGTERM to remaining processes...' with subsequent scrolling messages do not appear, instead the console disappears immediately.

I noticed some new errors in messages.log:

Mar  5 12:56:55 roo systemd[1]: Stopping Session 1 of user andy.
Mar  5 12:56:55 roo org.gtk.vfs.Daemon[508]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Mar  5 12:56:55 roo org.gtk.vfs.Daemon[508]: A connection to the bus can't be made
Mar  5 12:56:55 roo ntpd[351]: ntpd exiting on signal 15
Mar  5 12:56:55 roo systemd[1]: Stopped Session 1 of user andy.
Mar  5 12:56:55 roo systemd[1]: Stopping system-systemd\x2dfsck.slice.
Mar  5 12:56:55 roo systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Mar  5 12:56:55 roo systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Mar  5 12:56:55 roo systemd[1]: Stopping Disk Manager...
Mar  5 12:56:55 roo systemd[1]: Stopping Authorization Manager...
Mar  5 12:56:55 roo systemd[1]: Stopping User Manager for UID 1000...
Mar  5 12:56:55 roo systemd[1]: Stopped target Graphical Interface.
Mar  5 12:56:55 roo systemd[1]: Stopped target Multi-User System.
Mar  5 12:56:55 roo systemd[1]: Stopping Network Time Service...
Mar  5 12:56:55 roo systemd[1]: Stopped Automatic wired network connection using netctl profiles.
Mar  5 12:56:55 roo systemd[1]: Stopping system-netctl\x2difplugd.slice.
Mar  5 12:56:55 roo systemd[1]: Removed slice system-netctl\x2difplugd.slice.
Mar  5 12:56:55 roo systemd[1]: Stopping Periodic Command Scheduler...
Mar  5 12:56:55 roo systemd[1]: Stopping Samba SMB/CIFS server...
Mar  5 12:56:55 roo systemd[1]: Stopping Login Prompts.
Mar  5 12:56:55 roo systemd[1]: Stopped target Login Prompts.
Mar  5 12:56:55 roo systemd[1]: Stopping Getty on tty1...
Mar  5 12:56:55 roo systemd[1]: Stopping Login Service...
Mar  5 12:56:55 roo systemd[419]: Stopping Default.
Mar  5 12:56:55 roo systemd[419]: Stopped target Default.
Mar  5 12:56:55 roo systemd[1]: Stopping D-Bus System Message Bus...
Mar  5 12:56:55 roo systemd[419]: Stopping Basic System.
Mar  5 12:56:55 roo systemd[419]: Stopped target Basic System.
Mar  5 12:56:55 roo systemd[1]: Stopping System Logger Daemon...
Mar  5 12:56:55 roo systemd[419]: Stopping Paths.
Mar  5 12:56:55 roo systemd[419]: Stopped target Paths.
Mar  5 12:56:55 roo systemd[419]: Stopping Timers.
Mar  5 12:56:55 roo systemd[419]: Stopped target Timers.
Mar  5 12:56:55 roo systemd[419]: Stopping Sockets.
Mar  5 12:56:55 roo systemd[419]: Stopped target Sockets.
Mar  5 12:56:55 roo systemd[419]: Starting Shutdown.
Mar  5 12:56:55 roo systemd[419]: Reached target Shutdown.
Mar  5 12:56:55 roo systemd[419]: Starting Exit the Session...
Mar  5 12:56:55 roo systemd[1]: Starting Generate shutdown-ramfs...
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for mkinitcpio-generate-shutdown-ramfs.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for syslog.socket: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for syslog-ng.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for dbus.socket: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for dbus.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for systemd-logind.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for getty@tty1.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for getty.target: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for smbd.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for cronie.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for system-netctl\x2difplugd.slice: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for ntpd.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for user@1000.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for polkit.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for udisks2.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for rtkit-daemon.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for system-systemd\x2dfsck.slice: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Unmounted /run/user/1000/gvfs.
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for proc-sys-fs-binfmt_misc.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for sys-fs-fuse-connections.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for mnt-project.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for mnt-backup.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for boot.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for home.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for mnt-global.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for sys-kernel-config.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for tmp.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for sys-kernel-debug.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for dev-hugepages.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for dev-mqueue.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for -.mount: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Stopped Periodic Command Scheduler.
Mar  5 12:56:55 roo systemd[1]: Stopped D-Bus System Message Bus.
Mar  5 12:56:55 roo systemd[1]: Stopped Network Time Service.
Mar  5 12:56:55 roo systemd[1]: Stopped Getty on tty1.
Mar  5 12:56:55 roo systemd[1]: Stopped Login Service.
Mar  5 12:56:55 roo systemd[1]: Stopped Samba SMB/CIFS server.
Mar  5 12:56:55 roo systemd[1]: Stopped Authorization Manager.
Mar  5 12:56:55 roo systemd[1]: Stopped Disk Manager.
Mar  5 12:56:55 roo systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for smbd.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for systemd-logind.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for getty@tty1.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for ntpd.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for dbus.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Failed to send out specific PropertiesChanged signal for cronie.service: Transport endpoint is not connected
Mar  5 12:56:55 roo systemd[1]: Stopping system-getty.slice.
Mar  5 12:56:55 roo systemd[1]: Removed slice system-getty.slice.

This is what my good messages.log looked like before the regression:

Mar  5 12:42:03 roo systemd[1]: Stopping Session 1 of user andy.
Mar  5 12:42:03 roo systemd[1]: Stopped Session 1 of user andy.
Mar  5 12:42:03 roo systemd[1]: Stopping Disk Manager...
Mar  5 12:42:03 roo systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Mar  5 12:42:03 roo systemd[1]: Stopping Authorization Manager...
Mar  5 12:42:03 roo systemd[1]: Stopping User Manager for 1000...
Mar  5 12:42:03 roo systemd[1]: Stopped target Graphical Interface.
Mar  5 12:42:03 roo systemd[1]: Stopped target Multi-User System.
Mar  5 12:42:03 roo systemd[1]: Stopping Network Time Service...
Mar  5 12:42:03 roo systemd[423]: Stopping Default.
Mar  5 12:42:03 roo systemd[423]: Stopped target Default.
Mar  5 12:42:03 roo systemd[423]: Starting Shutdown.
Mar  5 12:42:03 roo systemd[423]: Reached target Shutdown.
Mar  5 12:42:03 roo systemd[423]: Starting Exit the Session...
Mar  5 12:42:03 roo systemd[1]: Stopped Automatic wired network connection using netctl profiles.
Mar  5 12:42:03 roo systemd[1]: Stopping system-netctl\x2difplugd.slice.
Mar  5 12:42:03 roo systemd[1]: Removed slice system-netctl\x2difplugd.slice.
Mar  5 12:42:03 roo systemd[1]: Stopping Periodic Command Scheduler...
Mar  5 12:42:03 roo systemd[1]: Stopping Samba SMB/CIFS server...
Mar  5 12:42:03 roo systemd[1]: Stopping Login Prompts.
Mar  5 12:42:03 roo systemd[1]: Stopped target Login Prompts.
Mar  5 12:42:03 roo systemd[1]: Stopping Getty on tty1...
Mar  5 12:42:03 roo systemd[1]: Stopping Login Service...
Mar  5 12:42:03 roo systemd[1]: Stopping D-Bus System Message Bus...
Mar  5 12:42:03 roo systemd[1]: Stopping System Logger Daemon...
Mar  5 12:42:03 roo systemd[1]: Starting Generate shutdown-ramfs...
Mar  5 12:42:03 roo systemd[1]: Stopped Periodic Command Scheduler.
Mar  5 12:42:03 roo systemd[1]: Stopped Login Service.
Mar  5 12:42:03 roo systemd[1]: Stopped D-Bus System Message Bus.

Arch Linux 3.13.5-1 running in VirtualBox 4.3.8

Cheers!

Last edited by dizzib (2014-05-14 08:43:04)

Offline

#2 2014-03-05 13:19:03

kokoko3k
Member
Registered: 2008-11-14
Posts: 1,432

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

Does it happens all the times?

Offline

#3 2014-03-05 13:22:25

dizzib
Member
Registered: 2013-12-09
Posts: 7

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

Yes, it happens consistently.

I'm running a fully up to date system (via pacman -Syu).

Offline

#4 2014-03-05 14:01:21

karol
Archivist
Registered: 2009-05-06
Posts: 25,423

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

dizzib, please edit your post.
When posting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode

like this

It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Offline

#5 2014-03-07 07:52:03

dizzib
Member
Registered: 2013-12-09
Posts: 7

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

I spoke too soon smile

Sometimes issuing a "systemctl poweroff" causes an immediate system freeze.

Don't know if it's related, but I also had a random system freeze which has never happened before.

Anyway, I've rolled back my system for now.

Cheers!

Offline

#6 2014-03-07 07:53:17

pcxz
Member
From: Italy
Registered: 2008-01-13
Posts: 67

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

In my case new systemd 2.10-2 ( also 2.10-3 in testing ) stop boot with this error in journalctl:

mar 07 08:30:55 localhost systemd[1]: Job dev-sda1.device/start timed out.
mar 07 08:30:55 localhost systemd[1]: Timed out waiting for device dev-sda1.device.
-- Subject: The unit dev-sda1.device failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda1.device failed.
-- 
-- The result is timeout.
mar 07 08:30:55 localhost systemd[1]: Dependency failed for /media/win7.
-- Subject: The unit media-win7.mount failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit media-win7.mount failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for Local File Systems.
-- Subject: The unit local-fs.target failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit local-fs.target failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
mar 07 08:30:56 localhost systemd[1]: Job dev-sda6.device/start timed out.
mar 07 08:30:56 localhost systemd[1]: Timed out waiting for device dev-sda6.device.
-- Subject: The unit dev-sda6.device failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda6.device failed.
-- 
-- The result is timeout.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for /media/devel.
-- Subject: The unit media-devel.mount failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit media-devel.mount failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Job dev-sda7.device/start timed out.
mar 07 08:30:56 localhost systemd[1]: Timed out waiting for device dev-sda7.device.
-- Subject: The unit dev-sda7.device failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda7.device failed.
-- 
-- The result is timeout.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for /dev/sda7.
-- Subject: The unit dev-sda7.swap failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda7.swap failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for Swap.
-- Subject: The unit swap.target failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit swap.target failed.
-- 

..and i switch to old 2.0.8-11 ..work ok.

Offline

#7 2014-03-07 09:09:21

-ss
Member
Registered: 2014-03-07
Posts: 2

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

pcxz wrote:

In my case new systemd 2.10-2 ( also 2.10-3 in testing ) stop boot with this error in journalctl:

mar 07 08:30:55 localhost systemd[1]: Job dev-sda1.device/start timed out.
mar 07 08:30:55 localhost systemd[1]: Timed out waiting for device dev-sda1.device.
-- Subject: The unit dev-sda1.device failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda1.device failed.
-- 
-- The result is timeout.
mar 07 08:30:55 localhost systemd[1]: Dependency failed for /media/win7.
-- Subject: The unit media-win7.mount failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit media-win7.mount failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for Local File Systems.
-- Subject: The unit local-fs.target failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit local-fs.target failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
mar 07 08:30:56 localhost systemd[1]: Job dev-sda6.device/start timed out.
mar 07 08:30:56 localhost systemd[1]: Timed out waiting for device dev-sda6.device.
-- Subject: The unit dev-sda6.device failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda6.device failed.
-- 
-- The result is timeout.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for /media/devel.
-- Subject: The unit media-devel.mount failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit media-devel.mount failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Job dev-sda7.device/start timed out.
mar 07 08:30:56 localhost systemd[1]: Timed out waiting for device dev-sda7.device.
-- Subject: The unit dev-sda7.device failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda7.device failed.
-- 
-- The result is timeout.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for /dev/sda7.
-- Subject: The unit dev-sda7.swap failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dev-sda7.swap failed.
-- 
-- The result is dependency.
mar 07 08:30:56 localhost systemd[1]: Dependency failed for Swap.
-- Subject: The unit swap.target failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit swap.target failed.
-- 

..and i switch to old 2.0.8-11 ..work ok.


same thing. can't boot normally + long shutdown.


during boot (after 1m30s timeout)

systemctl daemon-reload
systemctl default 

helps

Last edited by -ss (2014-03-07 09:09:50)

Offline

#8 2014-03-12 12:52:39

-ss
Member
Registered: 2014-03-07
Posts: 2

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

pcxz wrote:

In my case new systemd 2.10-2 ( also 2.10-3 in testing ) stop boot with this error in journalctl:

[..]

..and i switch to old 2.0.8-11 ..work ok.


turned out to be due to missing kernel option.
select CONFIG_FHANDLE=y in your .config.

Offline

#9 2014-03-21 11:13:08

dizzib
Member
Registered: 2013-12-09
Posts: 7

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

Same problem with 211-1.

I suspect the problem may be with virtualbox since I'm not seeing this issue on physical machines.

Offline

#10 2014-04-23 14:58:53

dizzib
Member
Registered: 2013-12-09
Posts: 7

Re: [SOLVED] systemd upgrade [208-11 --> 210-2] breaks system poweroff

This seems to be fixed in Virtualbox 4.3.10 with systemd 212-3.

Offline

Board footer

Powered by FluxBB