Hi all,
Well we have a current problem at a customers site, where James 2.3 rc3 is just stopping to deliver mail. No Logging, what so ever. So far, we have no clue what the problem is. After we restart James everything is working fine. We have the exact same Directory per rsync on another server, and it runs there smoothly. So what would be really really coll, at least for us ;) Would be to be able to monitor James with Nagios. What I would like to be able is to check if - James SMTP Port is active and accepting connections - James POP3 Port is active and accepting connections - James IMAP Port is active and accepting connections - The timestamp of last queue run IIRC there will be a possibility to monitor the performance of James in the future through JMX. Maybe this could be made available by JMX also, then one could write a nagios plugin which does JMX lookups. (Not too hard) Kind regards Juergen Hoffmann -----Ursprüngliche Nachricht----- Von: robert burrell donkin [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 17. November 2006 14:39 An: James Developers List Betreff: Re: JAMES status? On 11/17/06, Bernd Fondermann <[EMAIL PROTECTED]> wrote: > robert burrell donkin wrote: > > i run james on linux. a status feature would be useful (as many other > > linux services provide) to me. if this already exists, then please > > jump in. > > what stati would you expect to be returned? dunno :-) open to suggestions > something like the following? > > STARTING > RUNNING -or- RUNNING +pop3 +smtp -nntp -imap4 > STOPPING sounds about right (RUNNING +pop3 +smtp -nntp -imap4 would be good) > AFAIK, we are not tracking these states yet. and also cannot say if > James is not running at all ;-) probably able to use the container to provide this information (but not sure how right now) anyone with avalon-foo care to jump in (before i start digging)...? > > any ideas about the best way to implement this? > > > > i was wondering about extending remotemanager so that it's more > > scriptable. it'd be useful to be able to connect with user and > > password and the command to be executed. perhaps then status could be > > implemented as a command. > > yeah, probably the best way. opinions on syntax anyone? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !EXCUBATOR:1,455dbb8353073197299516! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
