CAcert System Admins discussion list

["Christopher Hoth [CAcert.org]" <christopher AT cacert.org>]

Hi Markus,

but internally we can open access to a testdb - I didn´t see a problem
with it..
Or we use a php script / c-program which open a port with informations.
Or a http based status ;)



Regards,
Christopher

-------- Original Message  --------
Subject: Re: Requirments - monitoring
From: Markus Warg 
<markus AT quarkus.de>
To: 
cacert-sysadm AT lists.cacert.org
Date: Mon Aug 17 2009 12:12:26 GMT+0200 (CEST)

> for DB monitoring, you could simply set up shell or perl or php cli
> scripts that perform the checks you want and put them into inetd/xinetd
> config (with IP access list). You don't neet to open up mysql to the net.
> Other solution would be nagios nrpe with local check scripts.
> 
> regards,
> 
> Markus
> 
> 
> Daniel Black schrieb:
>> On Wednesday 05 August 2009 05:45:11 Bas van den Dikkenberg wrote:
>>> Hi all,
>>>
>>> I am going to setup the new monitoring system but have acoppel of 
>>> question.
>>>
>>> 1.       What system and services do want to monitor?
>> email / lists/ blog / wiki - the port connectivity and functionality like 
>> seeing if port 143 is really IMAP
>>
>> as some of these are database backend access could be opened up to verify 
>> the 
>> structure and maybe stats based on queries - how many email aliases are 
>> there, 
>> how many users, how many list subscribers.
>>
>>> 2.       Who needs to be notifed when there is problem? A mailing list?
>> there was a plan to do a DR list of non-cacert emails. Perhaps sending it 
>> to 
>> there. For the more critical service breakdowns an irc notification - 
>> freenode 
>> and cacert?
>>> 3.       Access to the webinterface is this public or sysadmin only ?
>> If its status information only I'm pretty happy for this to be public. RSS 
>> as 
>> a minor thought of distributing notification.
>>