Revision history [back]

Hi.

I have noticed that journalctl systemd service stops logging messages after some time running. I have journalctd.conf set to "Storage=volatile" which means it should continuosly log messages and rotate periodically.

I have to restart systemd-journald service every now and then.

My device has been running 10 straight days since last reboot, but I have had to restart the service three times since last device reboot.

This is not convenient if you want to help tracing bugs in the device.....

To check this you may want to type "journalctl -f" as root from console, and check the last time/date logged...

[root@Sailfish ~]# journalctl -f
-- Logs begin at Fri 2017-11-10 17:09:54 CET. --
Nov 10 17:20:28 Sailfish kernel: PM: suspend entry 2017-11-10 16:20:28.668519100 UTC
Nov 10 17:20:28 Sailfish kernel: PM: Syncing filesystems ... done.
Nov 10 17:20:28 Sailfish kernel: Freezing user space processes ... 
Nov 10 17:20:28 Sailfish kernel: active wakeup source: IPA_WS
Nov 10 17:20:28 Sailfish kernel: 
Nov 10 17:20:28 Sailfish kernel: Freezing of tasks aborted after 0.001 seconds
Nov 10 17:20:28 Sailfish kernel: Restarting tasks ... done.
Nov 10 17:20:28 Sailfish kernel: Abort: Pending Wakeup Sources: IPA_WS 
Nov 10 17:20:28 Sailfish kernel: PM: suspend exit 2017-11-10 16:20:28.719794824 UTC
Nov 10 17:20:30 Sailfish kernel: PM: suspend entry 2017-11-10 16:20:30.040474420 UTC
^C
[root@Sailfish ~]#

In this capture it's been logging only for 11 minutes!

Best regards.

Hi.

I have noticed that journalctl systemd service stops logging messages after some time running. I have journalctd.conf set to "Storage=volatile" which means it should continuosly log messages and rotate periodically.

I have to restart systemd-journald service every now and then.

My device has been running 10 straight days since last reboot, but I have had to restart the service three times since last device reboot.

This is not convenient if you want to help tracing bugs in the device.....

To check this you may want to type "journalctl -f" as root from console, and check the last time/date logged...

[root@Sailfish ~]# journalctl -f
-- Logs begin at Fri 2017-11-10 17:09:54 CET. --
Nov 10 17:20:28 Sailfish kernel: PM: suspend entry 2017-11-10 16:20:28.668519100 UTC
Nov 10 17:20:28 Sailfish kernel: PM: Syncing filesystems ... done.
Nov 10 17:20:28 Sailfish kernel: Freezing user space processes ... 
Nov 10 17:20:28 Sailfish kernel: active wakeup source: IPA_WS
Nov 10 17:20:28 Sailfish kernel: 
Nov 10 17:20:28 Sailfish kernel: Freezing of tasks aborted after 0.001 seconds
Nov 10 17:20:28 Sailfish kernel: Restarting tasks ... done.
Nov 10 17:20:28 Sailfish kernel: Abort: Pending Wakeup Sources: IPA_WS 
Nov 10 17:20:28 Sailfish kernel: PM: suspend exit 2017-11-10 16:20:28.719794824 UTC
Nov 10 17:20:30 Sailfish kernel: PM: suspend entry 2017-11-10 16:20:30.040474420 UTC
^C
[root@Sailfish ~]#

In this capture it's been logging only for 11 minutes!

Best regards.

Hi.

I have noticed that journalctl systemd service stops logging messages after some time running. I have journalctd.conf set to "Storage=volatile" which means it should continuosly log messages and rotate periodically.

I have to restart systemd-journald service every now and then.

My device has been running 10 straight days since last reboot, but I have had to restart the service three times since last device reboot.

This is not convenient if you want to help tracing bugs in the device.....

To check this you may want to type "journalctl -f" as root from console, and check the last time/date logged...

[root@Sailfish ~]# journalctl -f
-- Logs begin at Fri 2017-11-10 17:09:54 CET. --
Nov 10 17:20:28 Sailfish kernel: PM: suspend entry 2017-11-10 16:20:28.668519100 UTC
Nov 10 17:20:28 Sailfish kernel: PM: Syncing filesystems ... done.
Nov 10 17:20:28 Sailfish kernel: Freezing user space processes ... 
Nov 10 17:20:28 Sailfish kernel: active wakeup source: IPA_WS
Nov 10 17:20:28 Sailfish kernel: 
Nov 10 17:20:28 Sailfish kernel: Freezing of tasks aborted after 0.001 seconds
Nov 10 17:20:28 Sailfish kernel: Restarting tasks ... done.
Nov 10 17:20:28 Sailfish kernel: Abort: Pending Wakeup Sources: IPA_WS 
Nov 10 17:20:28 Sailfish kernel: PM: suspend exit 2017-11-10 16:20:28.719794824 UTC
Nov 10 17:20:30 Sailfish kernel: PM: suspend entry 2017-11-10 16:20:30.040474420 UTC
^C
[root@Sailfish ~]#

In this capture it's been logging only for 11 minutes!

Best regards.