[systemd-devel] Debugging systemd shutdown problem on openSuSE 12.3

Andrey Borzenkov arvidjaar at gmail.com
Thu May 16 10:51:36 PDT 2013


В Mon, 13 May 2013 11:16:34 -0700
"Kok, Auke-jan H" <auke-jan.h.kok at intel.com> пишет:

> On Mon, May 13, 2013 at 6:28 AM, Rainer Krienke <krienke at uni-koblenz.de> wrote:
> > I i trouble on a openSuSE 12.3 system that is using autofs to mount
> > users home directories and other shares. The system basically works fine.
> >
> > When I try to shut down or reboot the system sometimes this works, but
> > most of the time the system terminates kdm and other processes (eg ssh
> > access no longer works then) but it won't reboot or turn power off in
> > case of shutdown.
> >
> > I added
> > systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
> > systemd.sysv_console=1
> > to the kernel command line and created a debug.sh file
> >
> > #!/bin/sh
> > mount -o remount,rw /
> > dmesg > /shutdown-log.txt
> > mount -o remount,ro /
> >
> > in /usr/lib/systemd/system-shutdown. Once I found a /shutdown-log.txt
> > log file but it did not contain any real hint for me why rebooting seems
> > to hang.
> >
> > The problem is that I do not see what is hanging. How can I get better
> > debugging results from systemd to find out more? Is it possible to
> > redirect all steps systemd makes when rebooting to a virtual tty? What
> > else could I do to get more information of what happens during
> > reboot/shutdown?
> 
> I guess what we need is a similar mechanism that is used to display
> messages when we're starting up and waiting for tasks, and have this
> appear at shutdown for tasks taking a long time to shut down.
> 

Should not 03b717a3c4f9348807fc56e7a7d711d72d4ec0cb also work for
shutdown case? I do not really see any condition limiting it to
booting, although I of course may misunderstand it.



More information about the systemd-devel mailing list