Results 1 to 4 of 4

Thread: systemd logging (journalctl) defaults

  1. #1
    Join Date
    Apr 2010
    Location
    Canada
    Beans
    15

    systemd logging (journalctl) defaults

    Systemd has its own logging tool, journalctl. In some cases the the traditional logs such as syslog and kern.log continue to exist; but in the case of pm-suspend.log it is no longer updated. Now you must rely on journalctl for power management event logging. The default settings for systemd in 15.04 only keep journalctl logs since the last reboot. This has been a problem for me as I'm trying to diagnose a system that occasionally hangs on resuming from suspend.

    To keep records across boots you must change the default settings.
    Details:
    -journalctl settings are in /etc/systemd/journald.conf.
    -to keep logs across boots setting "Storage=auto" needs to be "Storage=persistent"
    -I created a modified journald.conf in /etc/systemd/journald.conf.d/

    I think the default should be to keep these logs. I considered opening a launchpad bug against systemd but this is a feature request not a true bug and support is aware of this default.

    Is it possible to have pm-suspend.log work under systemd?
    Last edited by merc82; March 30th, 2015 at 03:46 PM.

  2. #2
    Join Date
    Mar 2006
    Location
    Williams Lake
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: systemd logging (journalctl) defaults

    We are in Feature Freeze now, but I'd suggest you create a feature request bug for W* W* (15.10).

  3. #3
    Join Date
    Apr 2007
    Location
    NH USA
    Beans
    1,484
    Distro
    Ubuntu Development Release

    Re: systemd logging (journalctl) defaults

    Quote Originally Posted by cariboo907 View Post
    We are in Feature Freeze now, but I'd suggest you create a feature request bug for W* W* (15.10).
    BTW, I had a great idea for W* W*. What do you think of this:

    Warty Warthog



    (Warty was my first Ubuntu installation - that's starting to be a long time ago...)

  4. #4
    Join Date
    Jun 2006
    Location
    Nux Jam
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: systemd logging (journalctl) defaults

    Quote Originally Posted by merc82 View Post
    Systemd has its own logging tool, journalctl. In some cases the the traditional logs such as syslog and kern.log continue to exist; but in the case of pm-suspend.log it is no longer updated. Now you must rely on journalctl for power management event logging. The default settings for systemd in 15.04 only keep journalctl logs since the last reboot. This has been a problem for me as I'm trying to diagnose a system that occasionally hangs on resuming from suspend.

    To keep records across boots you must change the default settings.
    Details:
    -journalctl settings are in /etc/systemd/journald.conf.
    -to keep logs across boots setting "Storage=auto" needs to be "Storage=persistent"
    -I created a modified journald.conf in /etc/systemd/journald.conf.d/

    I think the default should be to keep these logs. I considered opening a launchpad bug against systemd but this is a feature request not a true bug and support is aware of this default.

    Is it possible to have pm-suspend.log work under systemd?
    you can also create /var/log/journal/ to store persistent data, without tweaking the conf file.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •