I found the solution to my problem (was suggested in this ml yesterday).
/etc/logrotate.d/sogo contained a post-rotate script which tried to
restart sogo via its own init-script. This restart made sogo crash
(well, not really a crash, as it shutdown gracefully, but not the
expected outcome of a
Hi!
I found the solution to my problem (was suggested in this ml yesterday).
[SNIP]
expected. But removing the post-rotate-part will fix the problem of sogo
being offline after a log-rotate occurred.
Just posting it here for documentary reasons.
Yes, i can remove it but i want understand
Thanks for your reply.
Actually it is shutdown 3 hours later, which is strange, because there
should be no cron-script running at that time. However your comment made
me check cron.daily again. Apparently a script got auto-generated on
install there. It contains the following:
#!/bin/sh
Hi Michael,
SOGo will restart after its log files have been rotated (via logrotate).
As you can see it's being relaunched right after being shutdown.
Your problem is that 3 minutes later it is shut down again. But there is
no way for us to know why without looking at your system. It's most
