> On 23 Mar 2016, at 11:51, Yvan Calas <[log in to unmask]> wrote:
>
>
>> On 23 Mar 2016, at 11:11, Fabrice Jammes <[log in to unmask]> wrote:
>>
>> I'd like to add a Qserv related probe:
>>
>> 1. Check that correct ports are open on all nodes:
>>
>> on master (for now ccqserv100, ccqserv 125): 2131 4040 5012 1094
>>
>> on all other ccqserv{nnn}: 5012 1094
>
> Ok I guess that you want to check that a process is listening on each of these ports, right?
>
>>
>>
>> 2. Add a probe to check that Qserv container is running on all nodes might also be usefull:
>>
>> docker inspect --format='{{ .State.Running }}' qserv
>
> Ok.
All the nagios probes described above are now deployed on ccqserv{100..149}.
>
>> Could you please gave us the Nagios URL?
>
> Unfortunately, our nagios homepage is accessible from our internal network only. I will check with our nagios service managers what could be done for you (e.g. email notifications).
Could you please give me a list of email addresses corresponding to the persons interested in receiving email notifications when the status of a probe change?
BTW, Nagios is currently reporting a problem on ccqserv125 (port 4040) and ccqserv142 (port 1094).
Yvan
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
|