Closed pyro-code01 closed 2 years ago
Hi, Thank You for the issue. I'll fix this behavior in next release.
Hi! Sorry for the late but I just release v3.1.11 that solves this issue. Bye. Andrea
@andreapollastri Is that possible to use logrotate package (https://logtail.com/tutorials/how-to-manage-log-files-with-logrotate-on-ubuntu-20-04)
Hi,
I am running cipi v2, the issue maybe still persist in v3, the access.log logfile is huge, i have a busy adserver hosted there and the logfile itself is around 17GB.
Can you please check if you have this issue too, since this bug could fill up hdd space on less linux experienced users and cause system problems.
Edit: the logfile is owned by root group and www-data user, your install disables ssh root by default, so we cant delete the file using current home user access and also cipi user too. Only way is to log in with root recovery console on digital ocean, this could be problem on other providers.
Suggestion: I think serverpilot chunks the logfiles when they reach certain size and then deletes the oldest files when they are > n files.
Regards