[opensuse] 13.1 updates -> lengthy shutdown/reboot delay
From the man page I can't tell what the syntax is supposed to be to get the
I have a number of 13.1 installations. I've not been formally tracking, but it seems every time lately that I do zypper up, the immediately following shutdown or reboot is delayed several minutes. The subsequent boots' reboots/shutdowns are normal. Anyone else noticed this? How would someone troubleshoot something like this to maybe facilitate filing a bug? Journalctl -b -1 generates a usage error: Failed to look up boot -1: Cannot assign requested address previous boot's log. As is normal for man pages, there are no useful examples - it gives journalctl -k -b -1, but it generates the same error, and this on both 13.1 and TW. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-06-12 10:36, Felix Miata wrote:
I have a number of 13.1 installations. I've not been formally tracking, but it seems every time lately that I do zypper up, the immediately following shutdown or reboot is delayed several minutes. The subsequent boots' reboots/shutdowns are normal. Anyone else noticed this?
I think so, yes. I'm not sure, I think it happens with updates related to systemd. It doesn't bother me much, I don't reboot every day. It can be once or twice a month.
Journalctl -b -1 generates a usage error:
Failed to look up boot -1: Cannot assign requested address
Telcontar:~ # journalctl -b -1 Failed to look up boot -1: Cannot assign requested address Telcontar:~ # That's because I don't use a persistent journal. The previous boot log doesn't exist in my systemd journal. I have it on /var/log/messages. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (2)
-
Carlos E. R.
-
Felix Miata