Closed xmgz closed 9 months ago
Hi!
Its a bug with how YunoHost generates logrotate config files I opened an issue here some time ago: https://github.com/YunoHost/issues/issues/2242 It's a "core" bug, not a package bug, so I'll not fix it in the GTS package
For now you can fix this using those two commands:
chmod 644 /etc/logrotate.d/gotosocial__2
logrotate -v /etc/logrotate.d/gotosocial__2
The first one fixes the wrong permissions while the second one processes the log file to rotate it immediately
In fact only the first one is needed, as your system should rotates the log automatically in the future
oh! thank you.
@xmgz the patch is now released in the yunohost 11.2.6 :)
TL;DR
gts log file is almost 1Gb in size, is this normal? Can it be mitigated manually setting more restrictive values in the config? does it need to be that big? Thank you.
I've not edited or changed default settings neither for gts nor yunohost
Issue
as I have very small VPS (debian 11, x64, ynh 11.2.5, gts 0.12.1) so I check space available from time to time and I noticed what I consider a very big logfile for gotosocial, and is also true compared to other services:
gotosocial__2 is about 2/3 of total size :/ That catched my eye.
Reading gotosocial's logrotate config:
in
/var/www/gotosocial__2/config.yaml
we havelog-level: "info"
, would this log level cause such a big file?So, any thoughts would be appreciated, thank you.