[XperiaX] Journalctl randomly stops working [solved] [answered]

Question

4

[XperiaX] Journalctl randomly stops working [solved] [answered]

asked 2017-11-11 11:28:45 +0300

Pasko
937 ●11 ●26 ●27

updated 2017-12-22 23:12:21 +0300

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.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by olf
close date 2017-12-23 03:49:06.912607

Comments

Don't know if this is related but I get "Error was encountered while opening journal files: Bad message" from "journalctl -f". I got SailfishX 2.1.3.5 .

kaappikello ( 2017-11-11 17:28:55 +0300 )edit

Don't know if this is related but I get "Error was encountered while opening journal files: Bad message" from "journalctl -f". I got SailfishX 2.1.3.5 .
kaappikello ( 2017-11-11 17:28:55 +0300 )edit

Accepted Answer

1

answered 2017-12-22 23:10:56 +0300

Pasko
937 ●11 ●26 ●27

updated 2017-12-22 23:17:10 +0300

Hi. I think I found a solution to my own question. :D

Last monday I found some useful information here.

In comments #8, #37 there are suggestions to turn compression off, delete the journal files and restart the daemon..... and so far so good: my journald daemon has been working without problems for the last four days...

[root@Sailfish nemo]# systemctl status systemd-journald
● systemd-journald.service - Journal Service
   Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2017-12-18 15:12:12 CET; 4 days ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 13065 (systemd-journal)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-journald.service
           └─13065 /lib/systemd/systemd-journald

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

I know the versions in Sailfish X and RedHat do not match, but hopefully this bug will be fixed soon.

Best regards.

edit flag offensive delete publish link

[XperiaX] Journalctl randomly stops working [solved] [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by olf
close date 2017-12-23 03:49:06.912607

Comments

1 Answer

Question tools

Stats

Related questions

[XperiaX] Journalctl randomly stops working [solved] [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by olf close date 2017-12-23 03:49:06.912607

Comments

1 Answer

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by olf
close date 2017-12-23 03:49:06.912607