Thanks for your help Norman - I already have a plugin for running SQL and checking results, so it should be easy enough to adapt it to check the spool table.
Cheers, Chris 2009/12/22 Norman Maurer <[email protected]>: > Hi Chris, > > the plugin was written for my old employer so I don't have access to > it anymore. Anyway, its really simple. Just use mysql to check how > many rows are in the spool table and if more then X are in it return a > WARNING or ERROR. > > select count(*) from spool; > > Bye, > Norman > > > 2009/12/21 Christopher McAtackney <[email protected]>: >> Hi James, >> >> Thanks for your reply. Is your plug-in available anywhere to take a >> look at - or was it for internal use only? >> >> Cheers, >> Chris >> >> 2009/12/21 Norman Maurer <[email protected]>: >>> Hi Christopher, >>> >>> when using James 2.3.x the monitoring options are a bit limited. When >>> using James 2.3.x in the past we used the check_smtp stuff and using a >>> costum nagios plugin script which used sql to check the size of the >>> queue (we used sql for the spool storage). >>> >>> With James 3.x (which is current development version) you could use >>> JMX for most such stuff. >>> >>> Hope this helps, >>> >>> Bye, >>> Norman >>> >>> 2009/12/17 Christopher McAtackney <[email protected]>: >>>> Hi list, >>>> >>>> I am interesting in monitoring Apache James automatically from Nagios >>>> (http://www.nagios.org) and was wondering if I could get a bit of >>>> insight from the list on the best way to do this? >>>> >>>> Firstly, what log files does James write out to? >>>> >>>> Secondly, if, for some reason, James is building up a backlog of >>>> emails, would this be determinable by looking at log file errors? >>>> >>>> Thanks for your help, >>>> Chris >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
