You are not logged in.

#1 2012-10-26 15:04:46

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Systemd poweroff not working [SOLVED]

I have installed systemd on both my laptop and my desktop pc. The laptop is working fine, but the desktop PC will not poweroff any more.

systemctl reboot, halt or poweroff simply run to "Stopped target Remote File Systems" and then sits winking at me.

Adding --force just gets to the winking quicker.

To be honest, I don't know where to look.

Thanks

Andrew

arch x86_64 up to date

Last edited by fdservices (2013-02-14 15:49:23)

Offline

#2 2012-10-26 15:09:26

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: Systemd poweroff not working [SOLVED]

Have you tried to wait it out?  There is a way to set the timeout to somethig lower, but I have not had issues with this, so I am not sure specifically how to do it.   

I did have something stalling my system for a couple reboots a while back.  The first time I had walked away from the computer, got a cup of coffee and saw it just shutting down when I came back. So the next time it happened (next reboot) I knew that it had not frozen.  Maybe you should wait it out and see what messages are printed to your screen during that time.

Also, I believe persistent logging is the default now.  Maybe you could see if there is any relevent information regarding this delay in your journal/syslog.  Post that information here.  At this point, you really have no more information that your title states.  So debugging is near impossible.

Offline

#3 2012-10-26 15:32:58

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

I did wait all night once, but will try again. I will also check the logs again, but I haven't found any error messages so far.

Offline

#4 2012-10-26 15:37:04

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: Systemd poweroff not working [SOLVED]

You do have persisten loggin enabled, right?  Check out what it is working on when it freezes, or if there is a big gap in the time from one event to the next.  No one can help you until you are able to determine what it is that is hanging the shutdown process.

BTW, I think all night is a legitimate amount of time to have waited.  I find that often times, people post asking for help with a "frozen" shutdown, only to later reveal that they waited a whole 20-30 seconds, and then just held the power button.  So I am just making sure...

Offline

#5 2012-10-30 15:25:39

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

Here is the journal from my last shutdown:

Oct 30 15:54:40 ezcool login[432]: ROOT LOGIN ON tty1
Oct 30 15:54:44 ezcool systemd-logind[428]: Removed session 1.
Oct 30 15:55:01 ezcool /usr/sbin/crond[1326]: pam_unix(crond:session): session opened for user root by (uid=0)
Oct 30 15:55:01 ezcool /USR/SBIN/CROND[1327]: (root) CMD (scanimage -n)
Oct 30 15:55:02 ezcool /USR/SBIN/CROND[1326]: (root) CMDOUT (sh: /sbin/ifconfig: No such file or directory)
Oct 30 15:55:02 ezcool /USR/SBIN/CROND[1338]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Oct 30 15:55:05 ezcool systemd[1]: Deactivating swap /dev/sda5...
Oct 30 15:55:05 ezcool systemd[1]: Deactivating swap /dev/sda5...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Bluetooth.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Bluetooth.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Sound Card.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Sound Card.
Oct 30 15:55:05 ezcool systemd[1]: Stopping RPC Port Mapper.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target RPC Port Mapper.
Oct 30 15:55:05 ezcool systemd[1]: Stopping clamav updater...
Oct 30 15:55:05 ezcool systemd[1]: Stopping clamav daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Dynamic DNS Update Client...
Oct 30 15:55:05 ezcool systemd[1]: Stopping UDisks...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Daemon for power management...
Oct 30 15:55:05 ezcool systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Console Manager...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Daemon for monitoring attached scanners and registering them with colord...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Oct 30 15:55:05 ezcool systemd[1]: Stopping CUPS Printing Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Graphical Interface.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Graphical Interface.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Multi-User.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Multi-User.
Oct 30 15:55:05 ezcool systemd[1]: Stopping NFSv4 ID-name mapping daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping NFS Mount Daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Periodic Command Scheduler...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Network Time Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Samba SMB/CIFS server...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Samba Winbind daemon...
Oct 30 15:55:05 ezcool rpc.mountd[626]: Caught signal 15, un-registering and exiting.
Oct 30 15:55:05 ezcool avahi-daemon[422]: Got SIGTERM, quitting.
Oct 30 15:55:05 ezcool avahi-daemon[422]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.100.5.
Oct 30 15:55:05 ezcool winbindd[584]: [2012/10/30 15:55:05.500858,  0] winbindd/winbindd.c:212(winbindd_sig_term_handler)
Oct 30 15:55:05 ezcool winbindd[584]: Got sig[15] terminate (is_parent=1)
Oct 30 15:55:05 ezcool avahi-daemon[422]: avahi-daemon 0.6.31 exiting.
Oct 30 15:55:05 ezcool sshd[424]: Received signal 15; terminating.
Oct 30 15:55:05 ezcool NetworkManager[421]: <warn> disconnected by the system bus.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Samba NetBIOS name server...
Oct 30 15:55:05 ezcool systemd[1]: Stopping OpenSSH Daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping D-Bus System Message Bus...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Arch Daemons.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Arch Daemons.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Login Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Login Prompts.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Login Prompts.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Getty on tty1...
Oct 30 15:55:05 ezcool systemd[1]: Stopping K Display Manager...
Oct 30 15:55:05 ezcool systemd[1]: Starting Store Sound Card State...
Oct 30 15:55:05 ezcool systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Oct 30 15:55:05 ezcool NetworkManager[421]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on
Oct 30 15:55:05 ezcool kdm[1296]: :0[1296]: Abnormal termination of greeter for display :0, code 0, signal 11
Oct 30 15:55:05 ezcool systemd[1]: Stopped OpenSSH Daemon.
Oct 30 15:55:05 ezcool systemd[1]: Stopped D-Bus System Message Bus.
Oct 30 15:55:05 ezcool systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Oct 30 15:55:05 ezcool login[432]: pam_unix(login:session): session closed for user root
Oct 30 15:55:05 ezcool systemd[1]: Stopped Login Service.
Oct 30 15:55:05 ezcool systemd[1]: Unit systemd-logind.service entered failed state
Oct 30 15:55:05 ezcool systemd[1]: Stopped K Display Manager.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Manage, Install and Generate Color Profiles.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Console Manager.
Oct 30 15:55:05 ezcool systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Samba SMB/CIFS server.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Samba Winbind daemon.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Samba NetBIOS name server.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Network Time Service.
Oct 30 15:55:05 ezcool systemd[1]: rpc-mountd.service: main process exited, code=exited, status=1/FAILURE
Oct 30 15:55:05 ezcool systemd[1]: Stopped NFS Mount Daemon.
Oct 30 15:55:05 ezcool systemd[1]: Unit rpc-mountd.service entered failed state
Oct 30 15:55:05 ezcool systemd[1]: Stopped NFSv4 ID-name mapping daemon.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Daemon for power management.
Oct 30 15:55:05 ezcool systemd[1]: Stopped UDisks.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Dynamic DNS Update Client.
Oct 30 15:55:05 ezcool systemd[1]: freshclamd.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 30 15:55:05 ezcool systemd[1]: Stopped clamav updater.
Oct 30 15:55:05 ezcool systemd[1]: Unit freshclamd.service entered failed state
Oct 30 15:55:05 ezcool systemd[1]: Stopped clamav daemon.
Oct 30 15:55:05 ezcool systemd[1]: Deactivated swap /dev/sda5.
Oct 30 15:55:06 ezcool systemd[1]: Started Store Sound Card State.
Oct 30 15:55:06 ezcool systemd[1]: Unmounting RPC pipe filesystem...
Oct 30 15:55:06 ezcool systemd[1]: Stopping NFS server...
Oct 30 15:55:06 ezcool systemd[1]: Deactivated swap /dev/disk/by-uuid/b134f334-2434-456d-9b29-1551b70a7e04.
Oct 30 15:55:06 ezcool kernel: nfsd: last server has exited, flushing export cache
Oct 30 15:55:06 ezcool systemd[1]: Deactivated swap /dev/disk/by-id/ata-MAXTOR_STM380215AS_6QZ11948-part5.
Oct 30 15:55:06 ezcool systemd[1]: Stopped CUPS Printing Service.
Oct 30 15:55:06 ezcool systemd[1]: Unmounted RPC pipe filesystem.
Oct 30 15:55:06 ezcool systemd[1]: Stopped NFS server.
Oct 30 15:55:06 ezcool systemd[1]: Stopping RPC Bind...
Oct 30 15:55:06 ezcool rpcbind[586]: rpcbind terminating on signal. Restart with "rpcbind -w"
Oct 30 15:55:06 ezcool login[432]: pam_systemd(login:session): Failed to connect to system bus: Did not receive a reply. Possible causes include: th
Oct 30 15:55:06 ezcool systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 30 15:55:06 ezcool systemd[1]: Stopped RPC Bind.
Oct 30 15:55:06 ezcool systemd[1]: Unit rpcbind.service entered failed state
Oct 30 15:55:06 ezcool systemd[1]: Stopped Getty on tty1.
Oct 30 15:55:06 ezcool systemd[1]: Stopping /etc/rc.local Compatibility...
Oct 30 15:55:06 ezcool systemd[1]: Stopped /etc/rc.local Compatibility.
Oct 30 15:55:06 ezcool systemd[1]: Stopping Permit User Sessions...
Oct 30 15:55:06 ezcool systemd[1]: Stopping Network.
Oct 30 15:55:06 ezcool systemd[1]: Stopped target Network.
Oct 30 15:55:06 ezcool systemd[1]: Stopping Network Manager...
Oct 30 15:55:06 ezcool NetworkManager[421]: <info> caught signal 15, shutting down normally.
Oct 30 15:55:06 ezcool dhcpcd[453]: received SIGTERM, stopping
Oct 30 15:55:06 ezcool dhcpcd[453]: eth0: removing interface
Oct 30 15:55:06 ezcool NetworkManager[421]: <info> exiting (success)
Oct 30 15:55:06 ezcool systemd[1]: Stopped Network Manager.
Oct 30 15:55:06 ezcool systemd[1]: Stopped Permit User Sessions.
Oct 30 15:55:06 ezcool systemd[1]: Stopping Remote File Systems.
Oct 30 15:55:06 ezcool systemd[1]: Stopped target Remote File Systems.
Oct 30 15:56:35 ezcool systemd[1]: colord-sane.service stopping timed out. Killing.
Oct 30 15:58:05 ezcool systemd[1]: colord-sane.service still around after SIGKILL. Ignoring.
Oct 30 15:59:35 ezcool systemd[1]: colord-sane.service stopping timed out (2). Killing.
Oct 30 16:01:05 ezcool systemd[1]: colord-sane.service still around after SIGKILL (2). Entering failed mode.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Daemon for monitoring attached scanners and registering them with colord.
Oct 30 16:01:05 ezcool systemd[1]: Unit colord-sane.service entered failed state
Oct 30 16:01:05 ezcool systemd[1]: Stopping Basic System.
Oct 30 16:01:05 ezcool systemd[1]: Stopped target Basic System.
Oct 30 16:01:05 ezcool systemd[1]: Starting /etc/rc.local.shutdown Compatibility...
Oct 30 16:01:05 ezcool systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopping CUPS Printer Service Spool.
Oct 30 16:01:05 ezcool systemd[1]: Stopped CUPS Printer Service Spool.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Daily Cleanup of Temporary Directories.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Stopped target Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Stopping CUPS Printing Service Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Closed CUPS Printing Service Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Closed D-Bus System Message Bus Socket.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Load Kernel Modules...
Oct 30 16:01:05 ezcool systemd[1]: Stopped Load Kernel Modules.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Apply Kernel Variables.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Setup Virtual Console.
Oct 30 16:01:05 ezcool systemd[1]: Unmounting /tmp...
Oct 30 16:01:05 ezcool systemd[1]: Started /etc/rc.local.shutdown Compatibility.
Oct 30 16:01:05 ezcool systemd[1]: Started Console System Shutdown Logging.
Oct 30 16:01:05 ezcool systemd[1]: Unmounted /tmp.
Oct 30 16:01:05 ezcool systemd[1]: Unmounted /home.
Oct 30 16:01:05 ezcool systemd[1]: Starting Unmount All Filesystems.
Oct 30 16:01:05 ezcool systemd[1]: Reached target Unmount All Filesystems.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Local File Systems (Pre).
Oct 30 16:01:05 ezcool systemd[1]: Stopped target Local File Systems (Pre).
Oct 30 16:01:05 ezcool systemd[1]: Stopping Remount Root and Kernel File Systems...
Oct 30 16:01:05 ezcool systemd[1]: Stopped Remount Root and Kernel File Systems.
Oct 30 16:01:05 ezcool systemd[1]: Starting Shutdown.
Oct 30 16:01:05 ezcool systemd[1]: Reached target Shutdown.
Oct 30 16:01:05 ezcool systemd[1]: Starting Update UTMP about System Shutdown...
Oct 30 16:01:05 ezcool systemd[1]: Starting Save Random Seed...
Oct 30 16:01:05 ezcool systemd[1]: Started Update UTMP about System Shutdown.
Oct 30 16:01:05 ezcool systemd[1]: Started Save Random Seed.
Oct 30 16:01:05 ezcool systemd[1]: Starting Final Step.
Oct 30 16:01:05 ezcool systemd[1]: Reached target Final Step.
Oct 30 16:01:05 ezcool systemd[1]: Starting Power-Off...
Oct 30 16:01:05 ezcool systemd[1]: Shutting down.
Oct 30 16:01:05 ezcool systemd-journal[153]: Journal stopped

but it lies, the final messages to the terminal were:

Disabling Swaps
Detaching Loop Devices
Detaching DM Devices

it did not power down or shut down.

Andrew

Offline

#6 2012-11-01 12:52:11

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

I found one problem, the cronie.service was stuck in waiting. I see from the forums that others have had the same problem, but I have not discovered why, or what the solution is.

Offline

#7 2012-11-03 13:15:15

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

Installed dcron instead of cronie and it seems to work better at shutdown.

Offline

#8 2012-11-04 17:04:35

wilberfan
Member
From: So. Cal
Registered: 2010-12-18
Posts: 240

Re: Systemd poweroff not working [SOLVED]

My TWO arch installs (one an upgrade, the other a brand-new install) both hang after the "Detaching DM Devices" message, too...


Hey, be nice...I'm new at this!

Offline

#9 2012-11-05 09:25:41

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

I installed the debug console and now I shutdown to a point - systemctl list-jobs shows no jobs running, ps -el shows multiple processes running.

If I then ctrl-alt-del the shutdown continues but reboots instead of shutting down.

I will try some more tests to see if I can get more details.

Seems that it may be a bit early to adopt systemd in place of initscripts

Andrew

Last edited by fdservices (2012-11-05 09:26:09)

Offline

#10 2012-11-06 02:21:28

JKAbrams
Member
From: Sweden
Registered: 2011-11-07
Posts: 81

Re: Systemd poweroff not working [SOLVED]

Same problem on my two arch installs (one is a laptop) after switching to pure systemd.
Obervation: I no longer have the halt or reboot binary's
Workaround: When it hangs on shutdown, I press the power-button once, shortly, which triggers what I believe is the rest of the shutdown procedure.
Wanted: real solution...
Solution: install systemd-sysvcompat (found it in this thread)

Last edited by JKAbrams (2012-11-06 02:29:40)

Offline

#11 2012-11-06 04:51:48

wilberfan
Member
From: So. Cal
Registered: 2010-12-18
Posts: 240

Re: Systemd poweroff not working [SOLVED]

JKAbrams wrote:

Solution: install systemd-sysvcompat (found it in this thread)

I haven't tried this yet on my XFCE system (is this solution only for KDE?)...but what puzzles me is that both my 'old' arch install AND my brand-new (ie, pure systemd) install both freeze at the same place.   The solution mentioned above would seem appropriate for a "mixed" install--but makes no sense to me for an install ("pure systemd") using the latest (2012.11.01) arch .iso...


Hey, be nice...I'm new at this!

Offline

#12 2012-11-06 08:22:00

matse
Member
Registered: 2011-04-27
Posts: 276

Re: Systemd poweroff not working [SOLVED]

Even on a pure systemd install you still need systemd-sysvcompat installed. It's even hilighted on the systemd wiki page

Warning: Do not remove systemd-sysvcompat, as that package is in the base group.

Offline

#13 2012-11-06 10:03:31

tommykr
Member
From: Poland
Registered: 2009-03-15
Posts: 38

Re: Systemd poweroff not working [SOLVED]

Read this post on our Forum:

Shutdown Reboot Halt Never Finish

Offline

#14 2012-11-06 16:13:53

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

Thanks

Further analysis showed that this was a KDE related problem, shutdown,reboot from a terminal worked fine

Installing systemd-sysvcompat solved the problem.


Andrew

Offline

#15 2012-11-06 17:00:25

wilberfan
Member
From: So. Cal
Registered: 2010-12-18
Posts: 240

Re: Systemd poweroff not working [SOLVED]

matse wrote:

Even on a pure systemd install you still need systemd-sysvcompat installed. It's even hilighted on the systemd wiki page

Warning: Do not remove systemd-sysvcompat, as that package is in the base group.

I get that it might be required--what I DON'T get is why wouldn't it be automatically included in a brand-new install?

Last edited by wilberfan (2012-11-06 17:02:25)


Hey, be nice...I'm new at this!

Offline

#16 2012-11-06 17:03:13

matse
Member
Registered: 2011-04-27
Posts: 276

Re: Systemd poweroff not working [SOLVED]

You used pacstrap's "-i" switch and gave the "wrong" answer wink
Install the base system

Offline

#17 2012-11-06 17:16:39

wilberfan
Member
From: So. Cal
Registered: 2010-12-18
Posts: 240

Re: Systemd poweroff not working [SOLVED]

matse wrote:

You used pacstrap's "-i" switch and gave the "wrong" answer wink
Install the base system

I remember specifically skipping the "-i" option.

And, it turns out, systemd-sysvcompat WAS installed.  When I tried installing it just now:

# pacman -S systemd-sysvcompat
warning: systemd-sysvcompat-195-2 is up to date -- reinstalling 

So, unless I've neglected to do something, the presence of that package hasn't helped my poweroff problem.

20121105161615.th.jpg


Hey, be nice...I'm new at this!

Offline

#18 2012-11-06 19:03:42

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

Just to recap, installing systemd-sysvcompat on my PC seems to have solved the shutdown problem I have systemd running on my laptop and there are no problems with the shutdown there. I do NOT have systemd-sysvcompat in stalled on the laptop!

Curious

@wilberfan - if you open a terminal, su to root, and run "systemctl poweroff" does that work? Also install the debug terminal on F9 and see if you can see what is holding up the shutdown - systemctl enable debug-shell.service - it is all here



Andrew

Offline

#19 2012-11-07 10:14:51

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

@wilberfan  - you did replace cronie with dcron didn't you? The last error looks similar to those thrown by cronie.

Andrew

Offline

#20 2012-11-08 18:20:35

wilberfan
Member
From: So. Cal
Registered: 2010-12-18
Posts: 240

Re: Systemd poweroff not working [SOLVED]

fdservices wrote:

@wilberfan  - you did replace cronie with dcron didn't you? The last error looks similar to those thrown by cronie.

Andrew

I haven't tried that yet--I probably will--but I just found this, this morning (from http://freedesktop.org/wiki/Software/sy … bug_Shell) :

If shutdown (whether it be to reboot or power-off) of your system gets stuck, first test if the kernel itself is able to reboot or power-off the machine forcedly using one of these commands:

sync && reboot -f
sync && poweroff -f
If either one of the commands does not work, it is a kernel bug, not systemd.

Neither of those commands are working for me, so...kernel bug??  (I upgraded yesterday to 3.6.6-1-ARCH #1 SMP PREEMPT)


Hey, be nice...I'm new at this!

Offline

#21 2012-11-09 08:00:40

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

They did not work for me either. I do not think it is a kernel bug.

Remove cronie and try again,

Offline

#22 2012-11-10 01:29:22

wilberfan
Member
From: So. Cal
Registered: 2010-12-18
Posts: 240

Re: Systemd poweroff not working [SOLVED]

fdservices wrote:

They did not work for me either. I do not think it is a kernel bug.

Remove cronie and try again,

I installed dcron (which prompted me to remove cronie).  Did an # systemctl enable dcron and a # systemctl start dcron, rebooted, then tried a #systemctl reboot, but it hung at the exact same place as illustrated in my #17, above...


Hey, be nice...I'm new at this!

Offline

#23 2012-11-10 04:51:15

Dren
Member
From: Canada
Registered: 2010-12-14
Posts: 27

Re: Systemd poweroff not working [SOLVED]

I have the exact same issue, I end up with the screen in post 17 when shutting down or rebooting. The last 2 lines are reprinted every 2 minutes.
Systemd was just starting to work really well, then a few upgrades broke shutdown, rebooting, and suspending. They all seem to be affected by the same issue. The upgrades seemed innocent enough, although I'm not sure what all the packages are.
I was tinkering with the boot process at the time - as you can see I was installing xdm when this happened. So there may be something else I changed, and forgot about, which caused the issue. But I'm suspicious of the update.

[2012-11-09 19:09] Running 'pacman -Syu'
[2012-11-09 19:09] synchronizing package lists
[2012-11-09 19:09] starting full system upgrade
[2012-11-09 19:11] removed pyatspi (2.4.0-1)
[2012-11-09 19:11] upgraded chromium (22.0.1229.94-1 -> 23.0.1271.64-1)
[2012-11-09 19:11] upgraded libgusb (0.1.3-1 -> 0.1.4-1)
[2012-11-09 19:11] upgraded colord (0.1.24-1 -> 0.1.24-2)
[2012-11-09 19:11] upgraded libcanberra (0.30-1 -> 0.30-2)
[2012-11-09 19:11] upgraded libcanberra-pulse (0.30-1 -> 0.30-2)
[2012-11-09 19:11] upgraded gtk3 (3.6.1-1 -> 3.6.1-2)
[2012-11-09 19:11] upgraded ibus (1.4.99.20121006-1 -> 1.4.99.20121109-1)
[2012-11-09 19:11] upgraded gnome-settings-daemon (3.6.1-2 -> 3.6.2-1)
[2012-11-09 19:11] installed python2-beaker (1.6.3-2)
[2012-11-09 19:11] installed python2-mako (0.7.2-2)
[2012-11-09 19:11] upgraded gobject-introspection (1.34.1.1-1 -> 1.34.1.1-2)
[2012-11-09 19:11] upgraded gvfs (1.14.1-1 -> 1.14.1-2)
[2012-11-09 19:11] upgraded gvfs-obexftp (1.14.1-1 -> 1.14.1-2)
[2012-11-09 19:11] upgraded htop (1.0.1-1 -> 1.0.2-1)
[2012-11-09 19:11] upgraded icedtea-web-java7 (1.3-1 -> 1.3.1-1)
[2012-11-09 19:11] upgraded kdelibs (4.9.2-3 -> 4.9.3-2)
[2012-11-09 19:11] upgraded libmikmod (3.1.12-4 -> 3.2.0-1)
[2012-11-09 19:11] upgraded lm_sensors (3.3.2-5 -> 3.3.3-1)
[2012-11-09 19:11] installed python2-atspi (2.6.0-2)
[2012-11-09 19:11] upgraded sdl_sound (1.0.3-3 -> 1.0.3-4)
[2012-11-09 19:12] Running 'pacman-color -R cinnamon-git netrek-client-cow package-query'
[2012-11-09 19:12] removed package-query (1.0.1-1)
[2012-11-09 19:12] removed netrek-client-cow (3.2.8-1)
[2012-11-09 19:12] removed cinnamon-git (20121005-1)
[2012-11-09 19:12] Running 'pacman -S -- xdm-archlinux'
[2012-11-09 19:12] installed xorg-xdm (1.1.11-4)
[2012-11-09 19:12] installed xorg-xmessage (1.0.3-2)
[2012-11-09 19:12] installed xorg-xclock (1.0.6-1)
[2012-11-09 19:12] installed xorg-xwininfo (1.1.2-1)
[2012-11-09 19:12] 
[2012-11-09 19:12]   Using sysvinit, make the xdm line near the end of /etc/inittab read;
[2012-11-09 19:12]     x:5:respawn:/usr/bin/xdm -nodaemon -config /etc/X11/xdm/archlinux/xdm-config
[2012-11-09 19:12] 
[2012-11-09 19:12]   Using systemd, execute
[2012-11-09 19:12]     systemctl enable xdm-archlinux
[2012-11-09 19:12] 
[2012-11-09 19:12]   If you want an xconsole on the login screen, or don't want the clock or the
[2012-11-09 19:12]   halt and reboot buttons, edit /etc/X11/xdm/archlinux/Xsetup
[2012-11-09 19:12] 
[2012-11-09 19:12] installed xdm-archlinux (0.4-1)

Also, cronie is disabled.
And unfortunately the debug console on F9 stops working by the time I actually need to use it.

Last edited by Dren (2012-11-10 04:54:00)

Offline

#24 2012-11-10 08:17:27

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 318

Re: Systemd poweroff not working [SOLVED]

And unfortunately the debug console on F9 stops working by the time I actually need to use it.

Sounds like the same problem I had for a long time. The system has halted but not powered off. Does ctrl-alt-del do anything? Try logging out, killing xdm/kdm, logging in to the F1 console as root and # systemctl poweroff

Check journalctl for any error messages there.

Seems that it may be a bit early to adopt systemd in place of initscripts

In view of others problems I will remove [SOLVED] from this thread

Andrew

Offline

#25 2012-11-10 12:58:13

Dren
Member
From: Canada
Registered: 2010-12-14
Posts: 27

Re: Systemd poweroff not working [SOLVED]

Thanks for your suggestions. I doubt xdm is an issue - I even tried shutting down from rescue mode, to no avail. It is strange, because it seems like everything in the shutdown process has been completed, except actually shutting down. Every time I shut down, I hear what I think is my hard drive (but I really have no idea) clicking and turning itself off, the moment before the computer is turned off. Well, I can even hear that when I do # systemctl poweroff. It just doesn't do the final step.

This is what's put into journalctl during a(n attempted) reboot (from rescue mode):

--- removed ---

I didn't see anything really suspicious - systemd even seems to think shutdown was successful... I'll see if downgrading some packages helps.

Edit: Oops. It's my kernel. I'm using the 3.7 kernel from the aur because of graphics card issues. I didn't think that would be the problem because it was definitely working before. The 3.6 kernel works in terms of shutting down.
I need to experiment some more.

Edit: I found the issue, I'd disabled nmi_watchdog in an attempt to speed up the boot process. It worked with the 3.6 kernel but not 3.7. Re-enabling it brought everything back to normal.

Last edited by Dren (2012-11-10 15:43:37)

Offline

Board footer

Powered by FluxBB