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

[timabbott]

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.

[lacrimal]

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]

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]

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]

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