Re: mythbackend service

[Weedy]

On 13 Jul 2014 14:29, "Josu Lazkano" <address@hidden> wrote:
>
> Hello,
>
> I am using monit to strat some services on my server, I have a problem
> with mythbackend, it use to segfault sometimes and it does not start
> automatically:
>
> Jul 11 21:47:59 server  mythbackend[16217]: I Scheduler
> scheduler.cpp:2099 (HandleReschedule) Reschedule requested for MATCH 0
> 2 0 2014-07-11T19:58:28Z EITScanner
> Jul 11 21:47:59 server  mythbackend[16217]: I Scheduler
> scheduler.cpp:2212 (HandleReschedule) Scheduled 1 items in 0.0 = 0.01
> match + 0.00 check + 0.00 place
> Jul 11 21:47:59 server  mythbackend[16217]: C CoreContext
> signalhandling.cpp:305 (handleSignal) Received Segmentation fault:
> Code 1, PID -8, UID -1, Value 0x7f686ee8e6c0
>
> This is the service configuration file:
>
> # cat /etc/monit/conf.d/mythbackend.conf
> check process mythbackend with pidfile /var/run/mythtv/mythbackend.pid
> start program = "/etc/init.d/mythtv-backend start"
> stop program = "/etc/init.d/mythtv-backend stop"
>
> And this is what it says when executing the "start" script:
>
> # /etc/init.d/mythtv-backend start
> mythbackend already running, use restart instead.
>
> If I restart, it works great:
>
> # /etc/init.d/mythtv-backend restart
> Restarting MythTV server: mythbackend No /usr/bin/mythbackend found
> running; none killed.

I always use restart as the start action.

There are a million other tiny ways for the init system to get out of sync with monit. In fact I wrote a wrapper so that stop guaranties a service is stopped and start guaranties a service could start.