You are not logged in.
Pages: 1
My arch linux is too slow and I found the following messages in my /proc/kmsg:
<30>[1029011.126824] systemd[1]: Started Journal Service.
<28>[1029551.895711] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating.
<28>[1029567.037146] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
<29>[1029567.037561] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1029567.037593] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
<30>[1029567.038313] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1029567.038534] systemd[1]: Stopped Journal Service.
<30>[1029567.039614] systemd[1]: Starting Journal Service...
<29>[1029594.566248] systemd-coredump[13418]: Detected coredump of the journal daemon or PID 1, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.bd01ca5aea7b48c898098994445ea272.13291.1498064017000000.lz4.
<28>[1029657.135903] systemd[1]: systemd-journald.service: Start operation timed out. Terminating.
<28>[1029747.377461] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing.
<29>[1029747.377578] systemd[1]: systemd-journald.service: Killing process 13421 (systemd-journal) with signal SIGKILL.
<30>[1029749.079570] systemd[1]: Started Session c79 of user caio.
<28>[1029837.619057] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode.
<27>[1029837.619234] systemd[1]: Failed to start Journal Service.
<29>[1029837.619319] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1029837.619326] systemd[1]: systemd-journald.service: Failed with result 'timeout'.
<30>[1029837.619605] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1029837.619846] systemd[1]: Stopped Journal Service.
<30>[1029837.620472] systemd[1]: Starting Journal Service...
<28>[1029927.860669] systemd[1]: systemd-journald.service: Start operation timed out. Terminating.
<46>[1029967.413433] systemd-journald[13505]: Received SIGTERM from PID 1 (systemd).
<27>[1029981.896622] systemd[1]: Failed to start Journal Service.
<29>[1029981.896712] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1029981.896720] systemd[1]: systemd-journald.service: Failed with result 'timeout'.
<30>[1029981.897218] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1029981.897298] systemd[1]: Stopped Journal Service.
<30>[1029981.898218] systemd[1]: Starting Journal Service...
<30>[1029982.081753] systemd[1]: Started Journal Service.
<28>[1031692.196463] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating.
<28>[1031782.438065] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing.
<29>[1031782.438175] systemd[1]: systemd-journald.service: Killing process 13528 (systemd-journal) with signal SIGKILL.
<28>[1031872.679641] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring.
<28>[1031962.921235] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing.
<29>[1031962.921343] systemd[1]: systemd-journald.service: Killing process 13528 (systemd-journal) with signal SIGKILL.
<28>[1032053.162848] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode.
<29>[1032053.163041] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1032053.163050] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
<30>[1032053.163222] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1032053.163478] systemd[1]: Stopped Journal Service.
<30>[1032053.164239] systemd[1]: Starting Journal Service...
<28>[1032143.404457] systemd[1]: systemd-journald.service: Start operation timed out. Terminating.
<28>[1032233.646045] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing.
<29>[1032233.646196] systemd[1]: systemd-journald.service: Killing process 13923 (systemd-journal) with signal SIGKILL.
<29>[1032233.646253] systemd[1]: systemd-journald.service: Killing process 13528 (systemd-journal) with signal SIGKILL.
<28>[1032323.887667] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode.
<27>[1032323.887850] systemd[1]: Failed to start Journal Service.
<29>[1032323.887943] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1032323.887953] systemd[1]: systemd-journald.service: Failed with result 'timeout'.
<30>[1032323.888490] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1032323.888761] systemd[1]: Stopped Journal Service.
<30>[1032323.889563] systemd[1]: Starting Journal Service...
<28>[1032373.234565] systemd-coredump[13968]: Failed to get EXE, ignoring: No such process
<30>[1032373.237832] systemd[1]: Started Process Core Dump (PID 13968/UID 0).
<44>[1032373.314273] systemd-journald[13960]: File /var/log/journal/5bdee296b74e4558ac66ad91bfa45eed/system.journal corrupted or uncleanly shut down, renaming and replacing.
<30>[1032373.539280] systemd[1]: Started Journal Service.
<28>[1032833.901500] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
<29>[1032833.901851] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1032833.901873] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
<30>[1032833.902347] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1032833.902492] systemd[1]: Stopped Journal Service.
<30>[1032833.903535] systemd[1]: Starting Journal Service...
<29>[1032834.029677] systemd-coredump[14081]: Detected coredump of the journal daemon or PID 1, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.bd01ca5aea7b48c898098994445ea272.13960.1498067285000000.lz4.
<44>[1032834.095823] systemd-journald[14083]: File /var/log/journal/5bdee296b74e4558ac66ad91bfa45eed/system.journal corrupted or uncleanly shut down, renaming and replacing.
<30>[1032834.408230] systemd[1]: Started Journal Service.
<28>[1034274.456086] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating.
<28>[1034364.697701] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing.
<29>[1034364.697812] systemd[1]: systemd-journald.service: Killing process 14083 (systemd-journal) with signal SIGKILL.
<28>[1034454.939294] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring.
<28>[1034545.180885] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing.
<29>[1034545.180993] systemd[1]: systemd-journald.service: Killing process 14083 (systemd-journal) with signal SIGKILL.
<28>[1034628.150663] systemd[1]: systemd-journald.service: Main process exited, code=killed, status=9/KILL
<29>[1034628.150941] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1034628.150948] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
<30>[1034628.151260] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1034628.151342] systemd[1]: Stopped Journal Service.
<28>[1034628.151349] systemd-coredump[14402]: Failed to get COMM, falling back to the command line: No such process
<28>[1034628.151368] systemd-coredump[14402]: Failed to get EXE, ignoring: No such process
<30>[1034628.152218] systemd[1]: Starting Journal Service...
<30>[1034628.153726] systemd[1]: Started Process Core Dump (PID 14402/UID 0).
<44>[1034637.972082] systemd-journald[14405]: File /var/log/journal/5bdee296b74e4558ac66ad91bfa45eed/system.journal corrupted or uncleanly shut down, renaming and replacing.
<30>[1034641.550728] systemd[1]: Started Journal Service.
<28>[1035787.153434] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
<29>[1035787.153780] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1035787.153804] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
<30>[1035787.154263] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1035787.154461] systemd[1]: Stopped Journal Service.
<30>[1035787.155321] systemd[1]: Starting Journal Service...
<29>[1035787.276112] systemd-coredump[14595]: Detected coredump of the journal daemon or PID 1, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.bd01ca5aea7b48c898098994445ea272.14405.1498070238000000.lz4.
<44>[1035787.414642] systemd-journald[14598]: File /var/log/journal/5bdee296b74e4558ac66ad91bfa45eed/system.journal corrupted or uncleanly shut down, renaming and replacing.
<30>[1035789.092966] systemd[1]: Started Journal Service.
<28>[1036329.014881] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating.
<28>[1036419.256499] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing.
<29>[1036419.256604] systemd[1]: systemd-journald.service: Killing process 14598 (systemd-journal) with signal SIGKILL.
<28>[1036509.498098] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring.
<28>[1036599.739685] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing.
<29>[1036599.739800] systemd[1]: systemd-journald.service: Killing process 14598 (systemd-journal) with signal SIGKILL.
<28>[1036689.981278] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode.
<29>[1036689.981450] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1036689.981458] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
<30>[1036689.981587] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1036689.981772] systemd[1]: Stopped Journal Service.
<30>[1036689.982414] systemd[1]: Starting Journal Service...
<28>[1036780.222865] systemd[1]: systemd-journald.service: Start operation timed out. Terminating.
<28>[1036870.464532] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing.
<29>[1036870.464661] systemd[1]: systemd-journald.service: Killing process 14787 (systemd-journal) with signal SIGKILL.
<29>[1036870.464699] systemd[1]: systemd-journald.service: Killing process 14598 (systemd-journal) with signal SIGKILL.
<28>[1036960.706069] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode.
<27>[1036960.706250] systemd[1]: Failed to start Journal Service.
<29>[1036960.706328] systemd[1]: systemd-journald.service: Unit entered failed state.
<28>[1036960.706335] systemd[1]: systemd-journald.service: Failed with result 'timeout'.
<30>[1036960.706615] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
<30>[1036960.706786] systemd[1]: Stopped Journal Service.
<30>[1036960.707438] systemd[1]: Starting Journal Service...
<28>[1036993.890619] systemd-coredump[14824]: Failed to get COMM, falling back to the command line: No such process
<28>[1036993.890631] systemd-coredump[14824]: Failed to get EXE, ignoring: No such process
<30>[1036993.893059] systemd[1]: Started Process Core Dump (PID 14824/UID 0).
<44>[1036997.591307] systemd-journald[14816]: File /var/log/journal/5bdee296b74e4558ac66ad91bfa45eed/system.journal corrupted or uncleanly shut down, renaming and replacing.
<30>[1036997.938711] systemd[1]: Started Journal Service.
<28>[1038132.347011] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating.
<28>[1038222.588616] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing.
<29>[1038222.588734] systemd[1]: systemd-journald.service: Killing process 14816 (systemd-journal) with signal SIGKILL.Here comes the computer info. Hope someone can provide any information. Thanks!
Intel(R) Xeon(R) CPU E5-2640 v2 @ 2.00GHz
256 GB RAM Memory
Personalities : [raid1]
md4 : active raid1 sdb5[1] sda5[0]
4591610176 blocks super 1.2 [2/2] [UU]
bitmap: 0/35 pages [0KB], 65536KB chunk
md3 : active raid1 sdb4[1] sda4[0]
2147352576 blocks super 1.2 [2/2] [UU]
bitmap: 7/16 pages [28KB], 65536KB chunk
md2 : active raid1 sdb3[1] sda3[0]
1047552 blocks super 1.2 [2/2] [UU]
md1 : active raid1 sdb2[1] sda2[0]
1073610752 blocks super 1.2 [2/2] [UU]
bitmap: 1/8 pages [4KB], 65536KB chunk
unused devices: <none>Last edited by mellorf (2017-06-21 20:02:57)
Offline
I suppose I found out what was happening. I had a Java application producing lots of exceptions per second, making my system quite slow. Now I canceled such exceptions once they are not necessary for my application. I found out that journalctl is now stable :-)
Makes sense?
Offline
Pages: 1