Journalctl with high I/O traffic

This forum is for discussion about general software issues.

Journalctl with high I/O traffic

Postby musv » Sat Jul 19, 2014 8:28 am

Good morning,

sometimes after rebooting journalctl is getting crazy. In iotop it's looking like this:
$this->bbcode_second_pass_code('', 'Total DISK READ : 0.00 B/s | Total DISK WRITE : 397.47 K/s
Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 397.47 K/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
1229 be/4 root 0.00 B/s 397.47 K/s 0.00 % 99.82 % systemd-journald')

The logfile says:
$this->bbcode_second_pass_code('', 'Nas login: [ 5034.546736] systemd[1]: Starting Journal Service...
[ 5124.550567] systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
[ 5124.563238] systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
[ 5124.577713] systemd[1]: Unit systemd-journald.service entered failed state.
[ 5124.594537] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 5124.609612] systemd[1]: Stopping Journal Service...
[ 5124.615118] systemd[1]: Starting Journal Service...
[ 5124.623504] systemd[1]: Started Journal Service.
[ 5124.752262] systemd-journald[1083]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 5184.783833] systemd[1]: Starting Journal Service...
[ 5275.029322] systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
[ 5275.056629] systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
[ 5275.080169] systemd[1]: Unit systemd-journald.service entered failed state.
[ 5275.107715] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 5275.138145] systemd[1]: Stopping Journal Service...
[ 5275.151863] systemd[1]: Starting Journal Service...
[ 5275.160077] systemd[1]: Started Journal Service.
[ 5275.262889] systemd-journald[1090]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 5335.283307] systemd[1]: Starting Journal Service...
[ 5425.529899] systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
[ 5425.541980] systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
[ 5425.556006] systemd[1]: Unit systemd-journald.service entered failed state.
[ 5425.572111] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 5425.587048] systemd[1]: Stopping Journal Service...
[ 5425.592080] systemd[1]: Starting Journal Service...
[ 5425.600249] systemd[1]: Started Journal Service.
[ 5425.693312] systemd-journald[1096]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 5485.783880] systemd[1]: Starting Journal Service...
[ 5576.030466] systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
[ 5576.045008] systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
[ 5576.059187] systemd[1]: Unit systemd-journald.service entered failed state.
[ 5576.077496] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 5576.093707] systemd[1]: Stopping Journal Service...
[ 5576.098762] systemd[1]: Starting Journal Service...
[ 5576.107138] systemd[1]: Started Journal Service.
[ 5576.204363] systemd-journald[1191]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 5636.283160] systemd[1]: systemd-journald.service watchdog timeout!
[ 5636.317090] systemd[1]: Starting Journal Service...
[ 5726.530997] systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
[ 5726.545060] systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
[ 5726.559584] systemd[1]: Unit systemd-journald.service entered failed state.
[ 5726.577662] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 5726.592531] systemd[1]: Stopping Journal Service...
[ 5726.598229] systemd[1]: Starting Journal Service...
[ 5726.606441] systemd[1]: Started Journal Service.
[ 5726.684632] systemd-journald[1204]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 5786.783626] systemd[1]: systemd-journald.service watchdog timeout!
[ 5786.798091] systemd[1]: Starting Journal Service...
[ 5877.031538] systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
[ 5877.045453] systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
[ 5877.059039] systemd[1]: Unit systemd-journald.service entered failed state.
[ 5877.076685] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 5877.091444] systemd[1]: Stopping Journal Service...
[ 5877.096562] systemd[1]: Starting Journal Service...
[ 5877.104788] systemd[1]: Started Journal Service.
[ 5877.204453] systemd-journald[1221]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 5937.284150] systemd[1]: systemd-journald.service watchdog timeout!
[ 5937.299058] systemd[1]: Starting Journal Service...
[ 6027.532096] systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
[ 6027.545477] systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
[ 6027.559437] systemd[1]: Unit systemd-journald.service entered failed state.
[ 6027.577116] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 6027.591799] systemd[1]: Stopping Journal Service...
[ 6027.596941] systemd[1]: Starting Journal Service...
[ 6027.605032] systemd[1]: Started Journal Service.
[ 6027.675624] systemd-journald[1229]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 6087.784684] systemd[1]: systemd-journald.service watchdog timeout!
[ 6087.799359] systemd[1]: Starting Journal Service...')

journalctl --verify gives me:
$this->bbcode_second_pass_code('', 'journalctl --verify
PASS: /var/log/journal/e4b5dad211aa4a41920893d218a05e68/user-1000.journal
PASS: /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system@22d6497a83c14ef9a0c00913993b21dd-0000000000000001-00000000003e6846.journal
PASS: /var/log/journal/e4b5dad211aa4a41920893d218a05e68/user-1000@36aa49c231224b66b24d23b461dfccd0-00000000000001c7-0000000000ae4a6a.journal
074a78: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░ 49%
PASS: /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system@0004fe875fe20650-17bd954513c8859c.journal~')

I have already deleted everything in /var/log/journal, but after some minutes journald is restarting its cazyness.
musv
 
Posts: 24
Joined: Thu Sep 12, 2013 9:00 pm

Return to General

Who is online

Users browsing this forum: No registered users and 20 guests