You are not logged in.

#1 2013-10-03 18:43:04

johanPO
Member
Registered: 2013-09-24
Posts: 4

Systemd 208: hang on reboot

Hi,

I have installed Arch on an acer V5-573G. I popped in a SSD drive as a system drive and I have pretty much everything working as I had hoped
The only thing that does not work is a shutdown. Looking in the log files I have the following

Oct 03 20:21:01 acerV5 systemd[1]: Stopped target Local File Systems (Pre).
Oct 03 20:21:01 acerV5 systemd[1]: Stopping Remount Root and Kernel File Systems...
Oct 03 20:21:01 acerV5 systemd[1]: Stopped Remount Root and Kernel File Systems.
Oct 03 20:21:01 acerV5 systemd[1]: Starting Shutdown.
Oct 03 20:21:01 acerV5 systemd[1]: Reached target Shutdown.
Oct 03 20:21:01 acerV5 systemd[1]: Starting Final Step.
Oct 03 20:21:01 acerV5 systemd[1]: Reached target Final Step.
Oct 03 20:21:01 acerV5 systemd[1]: Starting Power-Off...
Oct 03 20:21:01 acerV5 systemd[1]: Shutting down.
Oct 03 20:21:01 acerV5 systemd-journal[129]: Journal stopped

To me that all looks good, with the exception that it does not turn of the computer. It's not a big thing, I guess as I can physically turn it off.
Any pointers would be appreciated

Cheers
Johan

Offline

#2 2013-10-03 19:18:58

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

Re: Systemd 208: hang on reboot

Are you using systemd 208?

Offline

#3 2013-10-03 20:12:18

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,364

Re: Systemd 208: hang on reboot

After updating 2 machines (both have been kept up-to-date) to systemd 208 and trying to reboot I have seen both machines hang, anyone else experiencing this?

I suppose it is not the expected behavior.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#4 2013-10-03 20:20:41

andrekp
Member
Registered: 2012-06-07
Posts: 112

Re: Systemd 208: hang on reboot

It seems as if whenever systemd is upgraded, that my system hangs if I try to reboot it.  It drops to the console output, then does nothing.  When I force it by powering off and repowering, it gives me "recovering journal" messages on boot.

It does this every time systemd upgrades.  I presume that it has to do with the new systemd not being able to properly reboot a system when a new version is just dropped into the middle of it (for lack of a better explanation).  Is there something ELSE I should be doing specifically after a systemd upgrade, or...

FYI: Arch + Openbox, if it matters.

Thanks

Offline

#5 2013-10-03 20:40:57

decaturguy
Member
From: Sweden
Registered: 2006-11-28
Posts: 117

Re: Systemd 208: hang on reboot

My server hangs too during reboot and shutdown.
I had to downgrade systemd 207 to 204 and the problem is gone.
There is a patch for systemd 207 that fixes this issue but i haven't tried it.

Patch: http://lists.freedesktop.org/archives/s … 13334.html

Offline

#6 2013-10-03 20:44:08

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

Re: Systemd 208: hang on reboot

decaturguy, is this issue present with systemd 208?

Offline

#7 2013-10-03 20:49:09

Yamashita Ren
Member
Registered: 2013-08-26
Posts: 12

Re: Systemd 208: hang on reboot

[quentin@VaioLaptop ~]$ yaourt -Syua
:: Synchronisation des bases de données de paquets...
 core                                                                                                                    105,4 KiB   197K/s 00:01 [##########################################################################################] 100%
 extra                                                                                                                  1529,2 KiB   631K/s 00:02 [##########################################################################################] 100%
 community                                                                                                              2019,7 KiB   678K/s 00:03 [##########################################################################################] 100%
 multilib est à jour
 archlinuxfr est à jour
 apathism est à jour
 musepack-tools : Orphelin    
 Paquets étrangers: - 46 / 46

==> Nouvelle révision des paquets :
extra/gconf             3.2.6-2 2 -> 3

==> Mise à jour des logiciels (nouvelle version) :
core/systemd            207-5   -> 208-1
core/systemd-sysvcompat 207-5   -> 208-1

==> Continuer la mise à jour ? [O/n]
==> [V]oir les détails.   Sélectionner les paquets [M]anuellement.
==> --------------------------------------------------------------
==> O
:: Début de la mise à jour complète du système...
:: Remplacer heirloom-mailx par core/s-nail ? [O/n] O
résolution des dépendances...
recherche des conflits entre paquets...

Paquets (5): gconf-3.2.6-3  heirloom-mailx-12.5-3 [suppression]  s-nail-14.4.3-1  systemd-208-1  systemd-sysvcompat-208-1

Taille totale de téléchargement : 3,23 MiB
Taille totale installé :           19,51 MiB
Taille de mise à jour net :        -1,20 MiB

:: Procéder à l’installation ? [O/n] O
:: Récupération des paquets...
 s-nail-14.4.3-1-x86_64                                                                                                  209,6 KiB   326K/s 00:01 [##########################################################################################] 100%
 systemd-208-1-x86_64                                                                                                      2,1 MiB   783K/s 00:03 [##########################################################################################] 100%
 systemd-sysvcompat-208-1-x86_64                                                                                           5,7 KiB  0,00B/s 00:00 [##########################################################################################] 100%
 gconf-3.2.6-3-x86_64                                                                                                    915,0 KiB   575K/s 00:02 [##########################################################################################] 100%
(4/4) vérification des clés dans le trousseau                                                                                                     [##########################################################################################] 100%
(4/4) vérification de l’intégrité des paquets                                                                                                     [##########################################################################################] 100%
(4/4) chargement des fichiers des paquets                                                                                                         [##########################################################################################] 100%
(4/4) analyse des conflits entre fichiers                                                                                                         [##########################################################################################] 100%
(5/5) vérification de l’espace disque disponible                                                                                                  [##########################################################################################] 100%
(1/1) désinstallation de heirloom-mailx                                                                                                           [##########################################################################################] 100%
(1/4) mise à jour de gconf                                                                                                                        [##########################################################################################] 100%
(2/4) installation de s-nail                                                                                                                      [##########################################################################################] 100%
Dépendances optionnelles pour s-nail
    smtp-forwarder: for sending mail
(3/4) mise à jour de systemd                                                                                                                      [##########################################################################################] 100%
avertissement: les permissions pour le répertoire /var/log/journal/ sont différentes
système de fichier : 755, paquet : 2755
(4/4) mise à jour de systemd-sysvcompat   

avertissement: les permissions pour le répertoire /var/log/journal/ sont différentes
système de fichier : 755, paquet : 2755

Don't you think the problem is lying there ?

Last edited by Yamashita Ren (2013-10-03 20:49:54)

Offline

#8 2013-10-03 20:51:28

progandy
Member
Registered: 2012-05-17
Posts: 2,151

Re: Systemd 208: hang on reboot

karol wrote:

decaturguy, is this issue present with systemd 208?

v208 should already have a patch for the bug with Type=notify. http://cgit.freedesktop.org/systemd/sys … eade18666e

Offline

#9 2013-10-03 20:58:40

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

Re: Systemd 208: hang on reboot

progandy wrote:
karol wrote:

decaturguy, is this issue present with systemd 208?

v208 should already have a patch for the bug with Type=notify. http://cgit.freedesktop.org/systemd/sys … eade18666e

I know https://bugs.archlinux.org/task/37007 :-)

@Yamashita Ren
That's a different thing: https://bbs.archlinux.org/viewtopic.php?id=170749

BTW, when posting on the forum, please prepend your commands with LC_ALL=C so that the output is in English.

Last edited by karol (2013-10-03 20:59:27)

Offline

#10 2013-10-03 21:02:16

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,364

Re: Systemd 208: hang on reboot

For me the systemd updates have always been problem free.

Only for the update (207-5 -> 208-1) I have experienced this.

For me the experience is more similar to what is described on the second link, in my case xfce was terminated and I was dropped into a black blank screen(1).

On one of the systems I could see that the system was still responsive because pressing ctrl-alt-del would make the HD light blink but the system wouldn't restart, since systemd now manages that I guess that if it was not working then ctrl-alt-del would not work. I could also see the kernel messages telling the sysrq actions I was requesting were not allowed.

On another system the behavior was exactly the same, with the difference that I configured things so I could use all the functionality of sysrq which allowed me to reboot the system that way.

For both systems, after restarting with systemd 208 both reboot and shutdown now work fine.

(1) I don't use a login manager so every time I reboot/shutdown I see some systemd messages about mounting some partitions on access before seeing the messages that briefly show up before reboot/shutdown, this time I was just dropped into a black blank screen as if X was still running somehow and things didnt reach the VT yet.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#11 2013-10-03 21:07:03

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

Re: Systemd 208: hang on reboot

The second link R00KIE mentions is now https://bbs.archlinux.org/viewtopic.php … 7#p1332847
I might have experienced this once, but I don't recall which systemd 207 release it was.

Offline

#12 2013-10-03 21:53:55

Yamashita Ren
Member
Registered: 2013-08-26
Posts: 12

Re: Systemd 208: hang on reboot

@Karol
Thank you for the information smile

Offline

#13 2013-10-04 01:46:30

Potomac
Member
Registered: 2011-12-25
Posts: 343

Re: Systemd 208: hang on reboot

I get also a random hang during reboot and shutdown under virtualbox with systemd 208 ( i686 version of archlinux )

I have this bug since systemd 207, with systemd 203 all is ok, I guess it's an upstream bug,

it's similar to this bug :

https://bugs.archlinux.org/task/37007

Last edited by Potomac (2013-10-04 01:50:54)

Offline

#14 2013-10-04 05:15:08

decaturguy
Member
From: Sweden
Registered: 2006-11-28
Posts: 117

Re: Systemd 208: hang on reboot

karol wrote:

decaturguy, is this issue present with systemd 208?

I haven't tried it yet, I think I'll wait and see.

Offline

#15 2013-10-04 05:18:35

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

Re: Systemd 208: hang on reboot

Why wait?

Offline

#16 2013-10-04 07:55:19

decaturguy
Member
From: Sweden
Registered: 2006-11-28
Posts: 117

Re: Systemd 208: hang on reboot

karol wrote:

Why wait?

It's a server and i usually update it once every month or two. Anyhow I'll try 208 this weekend.

Offline

#17 2013-10-04 10:33:14

Runiq
Member
From: Germany
Registered: 2008-10-29
Posts: 1,053

Re: Systemd 208: hang on reboot

Systemd 208 has changed some permissions for its journaling. The place where systemd stores its journal data is supposed to belong to group "systemd-journal" and have the SETGID bit set (the bit which is usually designated by a "2" before the normal permissions, such as 2755 in one of the posts above). Maybe just setting the /var/log/journal permissions to 2755 and the group to systemd-journal helps?

Edit: Wait, that's done by default already. Sorry for mucking things up. hmm

Last edited by Runiq (2013-10-04 10:37:45)

Offline

#18 2013-10-04 14:26:41

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 318

Re: Systemd 208: hang on reboot

@Runiq: so the following is already done by the pacman upgrade itself (from your link to the 208 announcement): "However, we recommend adjusting it manually after upgrades too (or from RPM scriptlets), so that the change is not delayed until next reboot."? Or is that the issue at hand here? This thread is not marked [fixed], so I just want to make sure this is not a required manual step for upgrading systemd 207 to 208?

Last edited by twelveeighty (2013-10-04 14:27:08)

Offline

#19 2013-10-04 14:31:20

Runiq
Member
From: Germany
Registered: 2008-10-29
Posts: 1,053

Re: Systemd 208: hang on reboot

twelveeighty wrote:

Or is that the issue at hand here? This thread is not marked [fixed], so I just want to make sure this is not a required manual step for upgrading systemd 207 to 208?

Nah, that's not the issue. I haven't done anything after the upgrade and my /var/log/journal has the correct permissions set by pacman. I don't encounter OP's reboot problem either.

Offline

#20 2013-10-06 13:31:06

kostas213
Member
From: Zürich
Registered: 2012-04-11
Posts: 53

Re: Systemd 208: hang on reboot

I also had curious problem with systemd 208-1.It took about 15-20 seconds for KDE Dolphin to open with systemd 208-1. After downgrading to 207-5 (to make sure that systemd was the root of the problem), Dolphin starts normally.

Last edited by kostas213 (2013-10-06 13:34:08)

Offline

#21 2013-10-06 15:31:59

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 5,670

Re: Systemd 208: hang on reboot

I think it matters (according to the bug) whether you are using persistent journal files or not. If journald is logging to /var/log/journal/..., the problem shouldn't manifest because the permissions should be right. If it is logging to /run/..., however, you may see the bug because initially the permissions were not being set correctly in that case. So whether it is the issue in the OP's case or not, for example, may depend on whether the OP has disabled persistent journalling.

If, that is, I've understood this correctly (which may very well not be the case).


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | grub2 | systemd | LVM2 on LUKS
Lenovo x121e | Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz GenuineIntel | Intel Centrino Wireless-N 1000 | US keyboard with Euro | 320G 7200 RPM Seagate HDD

Offline

#22 2013-10-06 19:17:12

johanPO
Member
Registered: 2013-09-24
Posts: 4

Re: Systemd 208: hang on reboot

karol wrote:

Are you using systemd 208?

Yes I am, systemd 208-1

I guess I will dig into this and see if a downgrade solves it

Offline

#23 2013-10-07 10:30:37

karenslfs
Member
Registered: 2008-06-27
Posts: 19

Re: Systemd 208: hang on reboot

Got the same issue hanging:

but I had to chroot & downgrade back to 207, at least I can boot now. Thanks to all for the support. I did notice that when I upgraded to 208 there was a warning msg.

warning: directory permissions differ on /var/log/journal filestystem: 755 package: 2755.

But when I chroot & downgrade back to 207 the msg reads;

warning: directory permissions differ on /var/log/journal filesystem: 2755 package: 755

Probably nothing I guess but ......

Thanks to all again.

Offline

#24 2013-10-07 10:32:54

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

Re: Systemd 208: hang on reboot

wrt to the permissions warning: https://bugs.archlinux.org/task/37170

Offline

#25 2013-10-08 16:17:50

Sanjeev K Sharma
Member
Registered: 2013-08-14
Posts: 68

Re: Systemd 208: hang on reboot

for folks who had the hang, maybe there are clues in the systemd logs?   maybe the entry near the bottom of this comment  showed up in your logs when you upgraded  - get the logs using this

journalctl -e -n999999

then search for the entry below - I found it with

?systemd.*208

The question mark is to search backwards, because that journalctl command puts less at the bottom of the logs,  This was the entry where systemd was restarted by pacman.  Maybe your entry, (or more entries surrounding it) has more information.

Oct 04 10:46:14 sam systemd[1]: Reexecuting.
Oct 04 10:46:14 sam systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)

Another command with much more information, (if those search terms don't yield anything)

   journalctl -o verbose 

and some search terms to get you started - again, this is the entry where pacman restarted systemd.

 _CMDLINE=/usr/lib/systemd/systemd --system --deserialize 20

  I thought it would use the command 

systemctl daemon-reexec

I can't tell you what to look for as this didn't happen to me.

Last edited by Sanjeev K Sharma (2013-10-08 16:22:22)

Offline

Board footer

Powered by FluxBB