Hi, yet one note - the error is logged also when monit starts for the first time (this is minor bug, we'll fix) ... the error can be ignored, monit works normally even if the state wasn't read.
Regards, Martin On Feb 4, 2013, at 9:40 PM, Martin Pala <mart...@tildeslash.com> wrote: > Hi Sergey, > > the magic is used to differentiate old state file format (which started with > number of services) from the new extensible state file format (starts with 0, > which is the "magic" - older monit versions will always start with number > > 0). > > It seems that the user's statefile is probably empty, hence the error is > returned. > > The solution is simple: > > 1.) stop monit > 2.) remove the state file: rm -f /var/lib/monit/state > 3.) start monit (will create new state file) > > Regards, > Martin > > > > On Feb 4, 2013, at 8:05 PM, Sergey B Kirpichev <skirpic...@gmail.com> wrote: > >> At the first startup of monit (just installed) users see: >> [EDT Jun 24 21:26:20] error : State file '/var/lib/monit/state': Unable to >> read magic >> >> Example: >> https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1017327 >> >> That's normal? Is there any way to prevent this "confusing" message >> for this case? >> >> _______________________________________________ >> monit-dev mailing list >> monit-dev@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/monit-dev > _______________________________________________ monit-dev mailing list monit-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/monit-dev
