[EN] Survey on systemd Who uses it?

[GoinEasy9]

I've been using systemd 44-12 for a week or so and until the dist-upgrade last night I didn't see any problems, but, I'm having trouble with reboot.  Even using Restart from the KDE menu the reboot hangs with the cursor in the upper left hand corner of the screen.  Using ctrl-alt-delete, once, frees up whereever it's stuck, but, it still doesn't reboot until I use the "systemctl --force reboot" command.

I see some interesting lines in some of the log files, but, before I start trying to solve the problem, is there a more recent version that I can update to?  Or, is anyone else seeing this?

[dibl]

Yes, I started seeing hangs on shutdown yesterday.  So far I'm only seeing it on the two 32-bit systems that I have.  I need to check the 64-bit systems -- so far no one has complained about them.  Also running systemd 44-12 here.


EDIT:  After updating, the 64-bit systems are showing the same issue.  Either from the user X session, or from a root console login, the shutdown sequence hangs with a blinking cursor in the upper left corner, which is totally nonresponsive to the keyboard. Ctrl-Alt-Del will resume the shutdown sequence, which becomes a restart, not a shutdown/power off.

These systems are a variety of video hardware -- Intel, AMD, and Nvidia, so I'm confident that the issue is not directly graphics-related.  And since it happens on a root tty1 console, with X shut down, I don't think it has anything to do with the X server, either.

[vilde]

I have the same issue since a few days but it's not happening every shutdown sometimes shutdown works. 64 bit xfce

[GoinEasy9]

While shutdown worked originally, last night, it failed.  The only way I was able to power down was a cold halt.

There was an update to init-system-helpers in my last du.  I'm going to check that out first.

[dibl]

I can see that when I press Ctrl-Alt-Del, the next bit that is executed is "Sending SIGTERM to remaining processes" followed by "Sending SIGKILL to remaining processes" and then it shuts down/restarts.  So it is hanging before the running processes are killed off.

[piper]

I am in England with very limited computer access so I can't test

[GoinEasy9]

You're seeing the same thing I am dibl.  I found that "systemctl poweroff --force" works for shutdown.  Without the --force, it just reboots, after a ctrl-alt-del to get past the stuck service.

Quote from "man systemctl poweroff"

If combined with --force shutdown of all running services is skipped, however all processes are killed and all file systems are unmounted or mounted read-only, immediately followed by the powering off.

So, one of the running services is holding up shutdown ... I guess.
I'm hoping journalctl will finally give us a way of logging the scroll from shutdown.  I'd really like to see what shutdown is stuck on.  I looked at dmesg and messages and many other logs and didn't come up with anything I thought was interesting.
Gotta work for a few days, so, I guess I'll have to wait to investigate some more.  Maybe I missed something in the logs.

[der_bud]

I do not observe shutdown/reboot problems with systemd on two virtual machines, one kdm/KDE and one slim/lxde on a win host. As they got a fresh install of systemd today, did you try to reinstall or dpkg-reconfigure systemd? Is libpam-systemd installed?

Perhaps this one could help to gather logs during late shutdown: https://wiki.frugalware.org/index.php/SystemD#When_shutdown_hangs

[ralul]

I don't know why you work on bugs of that old systemd-44. It is coming a new one soonishly. And as default init system!

[vilde]

I don't know why you work on bugs of that old systemd-44. It is coming a new one soonishly. And as default init system!

I'm tired of this now. How do I get rid of systemd and go back "normal boot" while waiting for systemd  to get ready and default on siduction?

[dibl]

If you set systemd-sysv on hold, then you can simply take it off hold and run a d-u, and then reboot.

[DeepDayze]

I don't know why you work on bugs of that old systemd-44. It is coming a new one soonishly. And as default init system!

Isn't there a new version of systemd in experimental? Perhaps try that one

[ralul]

@DeepDayze, I would have tried it and told you so ...

My guess, the actual upgrades of sysvinit packages are preconditions of future systemd: They work on a hassel free path for the users. That would explain some minor problems now with old systemd-44

Meanwhile you would like to here L.Poettering talking about the benefits of systemd-journal instead of rsyslog:
https://www.youtube.com/watch?v=i4CACB7paLc
In Short: server management advantages ...

[vilde]

If you set systemd-sysv on hold, then you can simply take it off hold and run a d-u, and then reboot.

Done... Thanks dibl

[dibl]

Oddly, I have one fully-updated system that does not show the shutdown problem.  I will post it here, just for future info:

Code: [Select]

System:    Host: delle6500 Kernel: 3.10-0.towo-siduction-amd64 x86_64 (64 bit)
           Desktop: KDE 4.10.5 Distro: siduction 12.1-RC1 Desperado - kde - (201205152133)
Machine:   System: Dell product: Latitude E6500
           Mobo: Dell model: 0PP476 Bios: Dell version: A14 date: 07/31/2009
CPU:       Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx)
           Clock Speeds: 1: 2401.00 MHz 2: 2401.00 MHz
Graphics:  Card: NVIDIA G98M [Quadro NVS 160M]
           X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1200@60.0hz
           GLX Renderer: Gallium 0.4 on NV98 GLX Version: 3.0 Mesa 9.1.4
Audio:     Card: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture ver: k3.10-0.towo-siduction-amd64
Network:   Card-1: Broadcom BCM4312 802.11b/g LP-PHY driver: b43-pci-bridge
           IF: wlan0 state: up mac: 00:23:4e:ab:86:7a
           Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e
           IF: eth1 state: down mac: 00:21:70:d4:d3:04
Drives:    HDD Total Size: 120.0GB (45.4% used) 1: id: /dev/sda model: OCZ_VERTEX size: 120.0GB
Partition: ID: / size: 9.8G used: 9.1G (99%) fs: ext4 ID: swap-1 size: 1.61GB used: 0.00GB (0%) fs: swap
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 51.5C mobo: N/A gpu: 41.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 190 Uptime: 4 min Memory: 851.9/3948.5MB Client: Shell (bash) inxi: 1.9.12