You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Christopher McAtackney <cr...@gmail.com> on 2010/01/04 11:44:02 UTC

Re: Monitoring Apache James

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 <no...@googlemail.com>:
> 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 <cr...@gmail.com>:
>> 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 <no...@googlemail.com>:
>>> 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 <cr...@gmail.com>:
>>>> 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: server-user-unsubscribe@james.apache.org
>>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org