What type of hardware are you using: Raspberry Pi 3, 4+
What YunoHost version are you running: 12.0.11
How are you able to access your server: The webadmin
SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no
Describe your issue
Hello.
Sometimes, my YNH instance becomes rather slow. This happens periodically, and a little inconsistently. Sometimes it is my fault. However, when using HTOP, I noticed an unusual behavior:
Journalctl uses 100% of my disk for several minutes at a time.
for no real reason. Right now, It’s using 100% of my disk at 266MB/s because I wanted to open the services window to view filebrowser’s status. It’s been running for at least 2 minutes. That means this has read 32 GB+ of something. I do not think that I have 32GB of logs. And it’s still running. That’s another 16GB as I wrote that sentence. I have witnessed this run for up to 10 minutes before (<–this is a dubious claim. I am strictly going off of feeling here. at least 5. Longer than 3.). Not always related to filebrowser. Why? Is there a solution? I fear it will wear out my SSD. This seems to happen when I attempt to view a service through the webadmin, but usually it only does it for 20 seconds at most (including most journalctls for filebrowser). Why does it take so long sometimes? I do not have enough information. Do I have 80+ GB of logs to delete?
Share relevant logs or error messages
can I journalctl journalctl? sudo journalctl -u systemd-journald
?
-- Boot d447e2a31b2a4166a568e0b39ec639b7 --
Feb 12 15:01:46 host.domain.com systemd-journald[161]: Journal started
Feb 12 15:01:46 host.domain.com systemd-journald[161]: Runtime Journal (/run/log/journal/ce84254c98d941b78d2b5207990fca98) is 8.0M, max 75.8M, 67.8M free.
Feb 12 15:01:46 host.domain.com systemd-journald[161]: Time spent on flushing to /var/log/journal/ce84254c98d941b78d2b5207990fca98 is 47.721ms for 386 entries.
Feb 12 15:01:46 host.domain.com systemd-journald[161]: System Journal (/var/log/journal/ce84254c98d941b78d2b5207990fca98) is 3.9G, max 4.0G, 77.3M free.
Feb 12 15:01:47 host.domain.com systemd-journald[161]: Received client request to flush runtime journal.
Feb 15 08:52:27 host.domain.com systemd-journald[161]: Data hash table of /var/log/journal/ce84254c98d941b78d2b5207990fca98/system.journal has a fill level at 75.0 (174763 of 233016 items, 134217728 file size, 767 bytes per hash table item), suggesting rotation.
Feb 15 08:52:27 host.domain.com systemd-journald[161]: /var/log/journal/ce84254c98d941b78d2b5207990fca98/system.journal: Journal header limits reached or header out-of-date, rotating.
Feb 24 13:05:53 host.domain.com systemd-journald[598014]: File /var/log/journal/ce84254c98d941b78d2b5207990fca98/system.journal corrupted or uncleanly shut down, renaming and replacing.
Feb 24 13:05:53 host.domain.com systemd-journald[598014]: Journal started
Feb 24 13:05:53 host.domain.com systemd-journald[598014]: System Journal (/var/log/journal/ce84254c98d941b78d2b5207990fca98) is 3.9G, max 4.0G, 77.4M free.
Feb 24 13:05:38 host.domain.com systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
Feb 24 13:05:38 host.domain.com systemd[1]: systemd-journald.service: Killing process 161 (systemd-journal) with signal SIGABRT.
Feb 24 13:28:59 host.domain.com systemd-journald[598372]: File /var/log/journal/ce84254c98d941b78d2b5207990fca98/system.journal corrupted or uncleanly shut down, renaming and replacing.
Feb 24 13:28:59 host.domain.com systemd-journald[598372]: Journal started
Feb 24 13:28:59 host.domain.com systemd-journald[598372]: System Journal (/var/log/journal/ce84254c98d941b78d2b5207990fca98) is 3.9G, max 4.0G, 69.4M free.
Feb 24 13:28:56 host.domain.com systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
Feb 24 13:28:56 host.domain.com systemd[1]: systemd-journald.service: Killing process 598014 (systemd-journal) with signal SIGABRT.
Feb 24 14:32:11 host.domain.com systemd-journald[600283]: File /var/log/journal/ce84254c98d941b78d2b5207990fca98/system.journal corrupted or uncleanly shut down, renaming and replacing.
Feb 24 14:32:11 host.domain.com systemd-journald[600283]: Journal started
Feb 24 14:32:11 host.domain.com systemd-journald[600283]: System Journal (/var/log/journal/ce84254c98d941b78d2b5207990fca98) is 3.9G, max 4.0G, 61.4M free.
Feb 24 14:23:23 host.domain.com systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
Feb 24 14:23:23 host.domain.com systemd[1]: systemd-journald.service: Killing process 598372 (systemd-journal) with signal SIGABRT.
Feb 24 15:06:22 host.domain.com systemd-journald[600283]: Forwarding to syslog missed 11 messages.
Feb 24 15:06:32 host.domain.com systemd-journald[600283]: Forwarding to syslog missed 449 messages.
Feb 24 15:08:14 host.domain.com systemd-journald[600283]: Forwarding to syslog missed 9 messages.
Feb 24 15:09:08 host.domain.com systemd-journald[600283]: Forwarding to syslog missed 47990 messages.
Feb 24 15:19:48 host.domain.com systemd-journald[601521]: File /var/log/journal/ce84254c98d941b78d2b5207990fca98/system.journal corrupted or uncleanly shut down, renaming and replacing.
Feb 24 15:27:21 host.domain.com systemd-journald[601629]: File /var/log/journal/ce84254c98d941b78d2b5207990fca98/system.journal corrupted or uncleanly shut down, renaming and replacing.
Feb 24 15:27:21 host.domain.com systemd-journald[601629]: Journal started
Feb 24 15:27:21 host.domain.com systemd-journald[601629]: System Journal (/var/log/journal/ce84254c98d941b78d2b5207990fca98) is 3.9G, max 4.0G, 29.3M free.
Feb 24 15:17:19 host.domain.com systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
Feb 24 15:17:20 host.domain.com systemd[1]: systemd-journald.service: Killing process 600283 (systemd-journal) with signal SIGABRT.