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? > [...] > [CET Jan 2 07:32:58] error : Queued event file: unable to read event size > -- end of file > [CET Jan 2 07:32:58] error : Queued event file: unable to read event size > -- end of file > [CET Jan 2 07:32:58] error : 'eth0' link down > [CET Jan 2 07:34:58] error : Queued event file: unable to read event size > -- end of file > [CET Jan 2 07:34:58] error : Queued event file: unable to read event size > -- end of file > [CET Jan 2 07:34:58] error : 'eth0' link down > [CET Jan 2 07:35:07] info : Awakened by the SIGHUP signal > Reinitializing Monit - Control file '/etc/monit/monitrc' > > while /var/log/monit.log starts with: > > [CET Jan 10 10:29:40] info : Starting Monit 5.20.0 daemon > [CET Jan 10 10:29:40] info : 'zira' Monit 5.20.0 started What happens with logfile if you do manual restart of the monit? stop and start? If you do reload?
