[mythtv-users] Trouble with monit
Harry Devine
lifter89 at comcast.net
Sun May 11 02:37:54 UTC 2008
Nick Morrott wrote:
> On 11/05/2008, Harry Devine <lifter89 at comcast.net> wrote:
>
>> Nick Morrott wrote:
>> > On 11/05/2008, Harry Devine <lifter89 at comcast.net> wrote:
>> >
>> >> Nick Morrott wrote:
>> >> > On 10/05/2008, Harry Devine <lifter89 at comcast.net> wrote:
>> >> >
>> >> >> I restarted the backend
>> >> >> fine, but the monit process won't start. I start it and it says it
>> >> >> started, but when I immediately check it with "service monit status" it
>> >> >> says it's dead with subsys locked.
>> >> >>
>> >> >
>> >> > This is usually due to a service's stale pidfile which was left behind
>> >> > when the process aborted. Check /var/run/ for monit's pidfile, delete
>> >> > it, and then restart the monit service.
>> >> >
>> >> >
>> >>
>> >> I looked but there's no pidfile (I looked for monit.pid). It still says
>> >> "monit dead but subsys locked" after I start it and check its status.
>> >> Could it be under another pidfile name?
>> >>
>> >
>> > Check for (and delete) /var/lock/subsys/monit.
>> >
>> >
>>
>> No good. I found it, deleted it, and as soon as I start the service, it
>> immediately dies. Maybe I have to re-install it? It just won't run at
>> all for some reason.
>>
>
> That should mean there are no problems with stale pid/lock files, and
> that the cause is more likely monit aborting at startup to a
> missing/bad config file.
>
> Have you updated the /etc/rc.d/init.d/monit file to use your local
> config file, rather than a default (such as /etc/monit.conf on a FC7
> box I just checked) set in that file? It could simply be that the
> config file is empty, resulting in monit aborting.
>
>
That was it. My /etc/rc.d/init.d/monit file was set to use
/etc/monit.conf as its config file, but everything in that file was
commented out. I read the monit docs when I installed it and it said
that it would look at ~/.monitrc if the monit.conf file wasn't there. I
had my myth specific settings in .monitrc so I thought it would be OK
(and it was for a little bit). Anyway, I modified the monit service
script to use /root/.monitrc and it started fine now.
Thanks for all the help, Nick!
Harry
More information about the mythtv-users
mailing list