<HTML dir=ltr><HEAD><TITLE>Re: [Gluster-devel] Server logging stop and clients can't connect</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText33635 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi Anand,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>The ps output show that the process is still running although it is not working correctly. The glusterfs process is still holding on to the port 6996.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>melvin</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> anand.avati@gmail.com on behalf of Anand Avati<BR><B>Sent:</B> Sat 1/31/2009 2:24 PM<BR><B>To:</B> Melvin Wong<BR><B>Cc:</B> gluster-devel@nongnu.org<BR><B>Subject:</B> Re: [Gluster-devel] Server logging stop and clients can't connect<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>On Sat, Jan 31, 2009 at 8:18 AM, Melvin Wong <melvin.wong@muvee.com> wrote:<BR>> Hi,<BR>> I am currently using glusterfs-1.3.11on a production environment and having<BR>> running smoothly for a couple of weeks. However one day the server logging<BR>> suddenly stops and all the clients report "not connected at the moment to<BR>> submit frame type" but the monitoring tools that monitor the port 6996 did<BR>> not register that the port went down. Previously the monitoring tools will<BR>> alert us whenever glusterfs crashes and port not detected without fail. I<BR>> understand I should move to V2.0 but I will like to know if this is a known<BR>> issue so that I can use this reason to propose for an upgrade. Thank you.<BR><BR>What is the process state at this time (you see in ps output of glusterfsd) ?<BR><BR></FONT></P></DIV></BODY></HTML>