On Fri, Jun 13, 2014 at 9:31 AM, Jay D Bhatt <jay.bh...@igate.com> wrote:
> I logged in shell script using init=/bin/sh and executed journalctl --boot, 
> It says "No journal files were found. Failed to set boot id: No such file or 
> directory" .
>
> I don't get login prompt when I use init=/sbin/init, so tried with 
> init=/bin/sh. Is it correct?

Ah, then you would only have logs from the previous boot, not the
current one. Also, it seems that the system only logs to /run, not to
/var/log.

If you're running this on a PC and have a tty9, you could enable
"debug-shell.service" to start an early shell on that terminal. (Could
be easily modified for another tty or serial access too.)

Otherwise, you'll need to enable persistent logging:
- Create a directory /var/log/journal,
- and make sure /etc/systemd/journald.conf has either
Storage=persistent or Storage=auto (the default).
- Then reboot to systemd.
- When it hangs, reboot again with init=/bin/sh,
- and use `journalctl --boot -1` to get the previous boot's log.

-- 
Mantas Mikulėnas <graw...@gmail.com>
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to