[Gluster-devel] Server logging stop and clients can't connect

Melvin Wong melvin.wong at muvee.com
Sun Feb 1 07:43:38 UTC 2009


Hi Anand,
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.
 
melvin

________________________________

From: anand.avati at gmail.com on behalf of Anand Avati
Sent: Sat 1/31/2009 2:24 PM
To: Melvin Wong
Cc: gluster-devel at nongnu.org
Subject: Re: [Gluster-devel] Server logging stop and clients can't connect



On Sat, Jan 31, 2009 at 8:18 AM, Melvin Wong <melvin.wong at muvee.com> wrote:
> Hi,
> I am currently using glusterfs-1.3.11on a production environment and having
> running smoothly for a couple of weeks. However one day the server logging
> suddenly stops and all the clients report "not connected at the moment to
> submit frame type" but the monitoring tools that monitor the port 6996 did
> not register that the port went down. Previously the monitoring tools will
> alert us whenever glusterfs crashes and port not detected without fail. I
> understand I should move to V2.0 but I will like to know if this is a known
> issue so that I can use this reason to propose for an upgrade. Thank you.

What is the process state at this time (you see in ps output of glusterfsd) ?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20090201/d46a0a61/attachment-0003.html>


More information about the Gluster-devel mailing list