On 2017-01-10 18:36:22 +0300, Sergey B Kirpichev wrote: > On Tue, Jan 10, 2017 at 04:08:03PM +0100, Vincent Lefevre wrote: > > I've noticed that the latest version of monit has overwritten > > its log file (/var/log/monit.log). /var/log/monit.log.1 ends > > on January 2 with: > > How logging system configured? journald?
Yes, the default with systemd + persistent logging. > What happens with logfile if you do manual restart of the monit? stop > and start? If you do reload? No problems in all these cases: # service monit restart # service monit stop # service monit start # service monit reload However... # apt install --reinstall monit [...] Preparing to unpack .../monit_1%3a5.20.0-5_amd64.deb ... Unpacking monit (1:5.20.0-5) over (1:5.20.0-5) ... Setting up monit (1:5.20.0-5) ... Processing triggers for systemd (232-8) ... Processing triggers for man-db (2.7.6.1-2) ... ====== How can you help? (doc: https://wiki.debian.org/how-can-i-help ) ====== ----- Show old opportunities as well as new ones: how-can-i-help --old ----- root@zira:/home/vinc17# cat /var/log/monit.log [CET Jan 10 17:26:45] info : Starting Monit 5.20.0 daemon [CET Jan 10 17:26:45] info : 'zira' Monit 5.20.0 started The log file has been overwritten! Something wrong in the postinst script? Could this be: install -o root -g adm -m 0640 /dev/null /var/log/monit.log -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
