<br><br><div class="gmail_quote">2010/2/23 Harald Stürzebecher <span dir="ltr"><<a href="mailto:haralds@cs.tu-berlin.de">haralds@cs.tu-berlin.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2010/2/22 Samuel Hassine <<a href="mailto:samuel.hassine@gmail.com">samuel.hassine@gmail.com</a>>:<br>
<div class="im">> I'm also looking for a way to monitor gluster nodes.<br>
><br>
> Any solutions ?<br>
><br>
> Le lundi 22 février 2010 à 10:12 +0500, Anton a écrit :<br>
>> Hello!<br>
>><br>
>><br>
>><br>
>> I'm looking for the way to determine the health of the GLUSTER<br>
>> cluster. Is there any way to determine if any of the nodes failed? In<br>
>> the log files it is possible to grep that there is "remotexx:<br>
>> disconnected" - but it is not sutable for monitoring. There should be<br>
>> the simple way to just query the cluster against the .vol file and<br>
>> see, if any node/brick failed to attach and so trigger the alarm. Is<br>
>> there anything like "gluster --reporthealth"?<br>
<br>
</div>Checking if a connection to the GlusterFS TCP server port (6996 IIRC)<br>
is possible might be an indicator for working/failing - at least for<br>
setups that use TCP. I don't know if anything like that is possible<br>
for Infiniband-only setups.<br></blockquote>IPoIB (IP over Infiniband)?<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
IIRC, Nagios can check if a port is open on a remote machine. That<br>
won't find something like disk/filesystem problems on the server, but<br>
it could report crashed GlusterFS server processes and machines that<br>
are not working at all.<br></blockquote><div>nagios can run checks remotely<br> <br><a href="http://www.logix.cz/michal/devel/nagios/">http://www.logix.cz/michal/devel/nagios/</a><br><a href="http://blogs.techrepublic.com.com/opensource/?p=321">http://blogs.techrepublic.com.com/opensource/?p=321</a><br>
<br>so it can check the real status of glusterfsd or whatever we want on remote host<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I know that this simple method won't provide a positive status (=it<br>
works) which would be preferable, but at least it can provide a<br>
negative status (=_something_ failed on _that_ machine) in some cases. </blockquote><div>glusterfsd port can be stolen, check of open port is indirect and unreliable way to check status<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
@<a href="http://gluster.org" target="_blank">gluster.org</a>:<br>
IIRC, some time ago someone requested a syslog feature to debug<br>
problems with GlusterFS as root filesystem for a diskless cluster -<br>
are there any news on that?<br>
Having the clients report problems to a central logging server might<br>
be useful for monitoring.<br></blockquote><div>monitoring of glusterfs daemons from client side is unreliable as monitoring errors can be caused by faults on the client side (I suppose nagios server host(s) to be reliable host)<br>
<br>I insist on remote checks because<br> 1) glusterfsd should abort if non-recoverable error happened, in the case remote check of real status is the most reliable check<br> 2) if glustefsd or any FS-related service continues to work in a non-healthy state after non-recoverable error happened then it can lead to damage and irreversible loss of data. Non-recoverable errors should be investigated and fixed only by system administrator with complete set of system tools at hands.<br>
<br>Regards,<br><br>Alexey.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Regards,<br>
<font color="#888888"><br>
Harald<br>
</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a><br>
<a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br>