Re: [monit] Calling monit -g groupname from cron/logrotate. Need to suppress informational messages.

[Martin Pala]

Which monit version it is?


On Oct 9, 2008, at 1:23 AM, Brian Gupta wrote:

> When we issue "monit -g mongrel restart all" from crontab many times
> we see the following messages:
>
> /etc/cron.daily/logrotate:
> monit: Cannot connect to the monit daemon. Did you start it with  
> http support?
> monit: Cannot connect to the monit daemon. Did you start it with  
> http support?
> monit: Cannot connect to the monit daemon. Did you start it with  
> http support?
> monit: Cannot connect to the monit daemon. Did you start it with  
> http support?
>
> It seems that the monit command will keep trying to reconnect to the
> monit server, until the command completes. Because we see these
> messages frequesntly we get alot of email from cron/logrotate. (Which
> I have to dig through to make sure nothing bad really did happen).
>
> We really only want to know if monit completely fails to issue the
> restart command.
>
> Any advice here? (Is was thinking maybe the differnt conditions have
> different return codes which I could trap, or monit might spit certain
> messaages to standard out vs standard err.)
>
> Thanks,
> Brian
>
> --
> - Brian Gupta
>
> http://opensolaris.org/os/project/nycosug/
>
> http://www.genunix.org/wiki/index.php/OpenSolaris_New_User_FAQ
>
> New York City user groups calendar:
> http://www.google.com/calendar/embed?src=nycusergroups%40brandorr.com&ctz=America/New_York
>
>
> --
> To unsubscribe:
> http://lists.nongnu.org/mailman/listinfo/monit-general