Skip to content
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

Figure out why log rotation for server/error logs do not work in docker-zulip #263

Open
timabbott opened this issue Jul 7, 2020 · 4 comments · May be fixed by #473
Open

Figure out why log rotation for server/error logs do not work in docker-zulip #263

timabbott opened this issue Jul 7, 2020 · 4 comments · May be fixed by #473

Comments

@timabbott
Copy link
Member

As reported in #250 (comment), some users appear to have error log files that are far larger than the limits configured in our supervisord configuration.

@timabbott timabbott added the bug label Jul 7, 2020
@lacrimal
Copy link

lacrimal commented Mar 25, 2021

Hi, Tim - can you update is it fixed ?
Found that server.log has logrotate configuration in /etc/logrotate.d
but it is not rotating this way, also supervisord looks like forgetting about this file giving it extremely grow.

Can I simply map volume to main system and logrotate it from there using script from /etc/logrotate.d ?

@timabbott
Copy link
Member Author

I'm not aware of us changing anything that might fix this.

That mount approach might work for you. That said, I think it'd be better to just debug why log rotation is not working properly as it does in a non-Docker Zulip server and fix the bug for everyone.

@flam22
Copy link

flam22 commented Jan 24, 2024

I just ran into this same issue. Having a look around in the container it seems there are a few issues here:

  • logrotate is not installed in the container.
  • When installed, logrotate refuses to run because the smokescreen log file is referenced twice (/etc/logrotate.d/zulip and /etc/logrotate.d/smokescreen).
  • After running logrotate it did not free up any disk space.
    This could be expected as the container is saving the log files on an overlay filesystem. It is probably best to use the mount approach anyway.

savaliyabhargav added a commit to savaliyabhargav/docker-zulip that referenced this issue Nov 14, 2024
@savaliyabhargav
Copy link

hii , @timabbott i am trying to fix this issue can you please review my pr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants