I think your two issues are related: CODE throws this error when there appears to be less than 2GB of free space left on the server.
I have done that (truncated syslog). Now, syslog is 1.6MB!
There are 9.8G free space. After restarting PostgreSQL service, Yunohost server seems to be running normally. The Yunohost apps are only listed after executing Yunohost update.
Unfortunately, I didn’t analyse syslog before I truncated it.
MYADMINPROMPT:~$ sudo systemctl status logrotate.timer
● logrotate.timer - Daily rotation of log files
Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; preset: enab>
Active: active (waiting) since Tue 2025-03-11 12:30:21 CET; 3 months 28 da>
Trigger: Thu 2025-07-10 00:00:00 CEST; 9h left
Triggers: ● logrotate.service
Docs: man:logrotate(8)
man:logrotate.conf(5)
Notice: journal has been rotated since unit was started, output may be incomple>
Strange: the logrotate time seems to be waiting since 2025-03-11, as far as i understand that message.
Output of etc/logrotate.d/rsyslog:
/var/log/syslog
/var/log/mail.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/cron.log
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
/usr/lib/rsyslog/rsyslog-rotate
endscript
}
Thanks very much for this idea.
Nextcloud is the remaining problem. Nextcloud web responds with 504 Gateway timeout, the latest Yunohost log before the disk issue has an Nextcloud-related error.
I’ll do a different thing now and will return soon. Thank you very much for all your help so far!
Everything seems to be ok.
= It has been running since 03/11/2025
Don’t forget to restart rsyslog and monitor it to see what’s filling it.
Done and checked: ok
I will mark this post as solution, since that truncate command freed enough disk space for Yunohost to work properly.
Now, after 2 hours, even Nextcloud seems two run perfectly, even showing inline-documents with Collabora. I will post in the other topic as well.
Now I will have to watch Yunohost’s diagnosis regularly.
Thank you very much @otm33 and @jarod5001 for all your great help!