I have been having issues with my server and so came across this feature.

I followed the above steps but I got some of these problems:

etc/monit/monitrc:75: Error: syntax error ‘From: monit@$HOST’
/etc/monit/monitrc:76: Error: syntax error ‘Subject: monit alert -- $EVENT $SERVICE # subject’

DO i need to change those $ variables to something specific? If so what, am nnot sure what to have here.

Also I attempted to connect to the web interfacet using my ip range and the port but can’t get access. I dont thing I have a firewall step up, or if I do i don’t know how to find out.

Alot of questions here, would be great i any one could help.

Thanks

set httpd port 2812 and localhost
=> set httpd port 2812

thanks

The reason is that i hawe a nother prosess that hawe somting like the web “Monit Service Manager” running …..

and it do not hawe a pid file when it starts … linux somtimes kills tis prosess and then the web servise stops to ..

Hope you understand the qestion …. how do i configure monit to test a servese like its one “Monit Service Manager”

I hop someon ansers

The only problem I have is when I try to activate the mysql and apache2 services, it gives me a syntax error if I just copy/paste that excerpt from your base conf file.

/etc/monit/monitrc:213: Error: syntax error ‘=’

I now its probably me, but it would be great if you could give me some info on this.

Thanks a lot!

Thanks for the tutorial about monit. I found it very useful and immediately applicable.

I’ve been experiencing random crashing of the mythtv-backend process on Ubuntu Feisty, mostly related to race conditions that upset the backend process. When the backend dies, it is not automatically restarted, resulting in lost scheduled recordings and a poor wife acceptance factor (WAF). Rather than spend the time trying to isolate and debug the crashing (since it happens so seldom), I decided to monitor the backend process to maintain its unattended operation.

Using the instructions above, I installed monit to perform the monitoring function. This is the clause for mythtv that appears in the /etc/monit/monitrc:


# Monitoring MythTV Service
check process mythtv with pidfile /var/run/mythtv/mythbackend.pid
start program = "/etc/init.d/mythtv-backend restart"
stop program = "/etc/init.d/mythtv-backend stop"
if failed port 6544 protocol http then restart
if 5 restarts within 5 cycles then timeout
group server


Rather than check the port the backend listens on, I’m monitoring the port the status reports on. This way, the mythtv backend status log does not fill up with unsuccessful connection error messages.

The mythtv-backend init script that comes with Ubuntu Feisty checks for the existence of a PID file during the start process. This added some complication to the monit clause because a backend crash would leave an orphaned PID file and the init script would not restart properly. Using the restart parameter on the command line for the “start program” fixed the complication.

In addition to monitoring mythtv-backend, I’ve added ssh (for ensured access to the box) and mysql (to ensure that the backend’s repository is also available) as per the above instructions.