-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very large log files #1544
Comments
root@8da3f4eb72b2:/home/git/gitlab# /etc/cron.daily/logrotate
error: /etc/logrotate.conf:7 unknown group 'syslog' But that's probably not just it. Logrotate needs some different default config, gitlab logs can grow a LOT over 52 weeks... |
Can log rotate be fixed in upcoming release? |
The problem with "unknown group 'syslog'" has already been fixed and merged. Another possible problem is that sidekiq has its own log rotation that conflicts with logrotate. I have solved this by disabling sidekiq rotation, modifying logrotate settings (to rotate based on size) and running logrotate hourly, not daily. |
This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions. |
@drujd do you do the logrotate in the host system or in the container? #1544 (comment) |
we have the same issue, is there any progress with this? |
Hello!
I think, gitlab container takes up a lot of disk space.
root@edc9dbd271eb:/var/log/gitlab# du --max-depth=1 -h 1.5G ./nginx 8.8G ./gitlab 286M ./gitlab-shell 735M ./supervisor 12G .
May be exists cron script for cleaning up old logs?
The text was updated successfully, but these errors were encountered: