On 2017-01-09 15:54:40 +0300, Sergey B Kirpichev wrote: > On Mon, Jan 09, 2017 at 01:32:59PM +0100, Vincent Lefevre wrote: > > > Can you check permissions on events dir & file? > > > > root@zira:/home/vinc17# ls -l /var/lib/monit > > total 12 > > drwx------ 2 root root 4096 2017-01-06 18:16:28 events > > -rw-r--r-- 1 root root 32 2015-07-07 13:17:34 id > > -rw------- 1 root root 768 2017-01-09 13:21:03 state > > root@zira:/home/vinc17# ls -l /var/lib/monit/events > > total 0 > > -rw-r--r-- 1 root root 0 2015-07-25 17:15:17 1437837317_12a1a40 > > -rw-r--r-- 1 root root 0 2016-12-23 10:51:02 1482486662_5640726e2fa0 > > > > > If possible, please check new sid's version. > > > > Same problem: > > First file seems to be too old. Second - too (but not too much). What > if you clean up these files?
The error messages no longer occur (without needing to restart monit). If the problem was that some files were too old, then monit should have done some clean up. BTW, shouldn't they be under /run? > > > This shouldn't be. Monit must be stopped first by init script (and > > > started last, by the way). That's - package default. > > > > Apparently not: there are lots of services stopped before monit. > > Are you using sysvinit and standard init-file for monit? It looks > like sysvinit-core - pruned on your system. I'm using systemd, as said in "System Information" in my bug report, and I haven't changed the init files. But systemd provides LSB compatibility. -- 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)
