[Gluster-devel] Re: client cannot maintain mount of unified AFR
Majied Najjar
majied.najjar at nationalnet.com
Thu Jun 28 15:32:53 UTC 2007
Yes. After I sent this message, I realized that I neglected to upgrade the client. However, after I upgraded the client and updated the config to include the namespace info, the servers kept crashing. Since this was a production machine, I had to downgrade as my "maintenance window" was over. :-)
In an effort to get more data, I set up another instance on a testing server and got somewhat similar results. I have placed my core file from the server crash at http://majied.net/core.txt and my client/server config at http://majied.net/client-server.txt .
Let me know if you need more information.
Thanks,
Majied
On Thu, 28 Jun 2007 18:43:34 +0530
"Anand Avati" <avati at zresearch.com> wrote:
> You would get a 'connection refused' if the server is not running. Can you
> please check if glusterfsd was running at that moment? also please get the
> logs of the glusterfsd which was not running (and if possible, the core
> dump's backtrace)
>
> Also have you upgraded all the servers and clients?
>
> thanks,
> avati
>
>
> 2007/6/27, Majied Najjar <majied.najjar at nationalnet.com>:
> >
> > Also,
> >
> > This happened when the first client in the client config
> > rebooted. Normally, the second client in the afr group would have picked up
> > the slack, but instead I was getting connection refused from the client. I
> > am assuming this is a locking issue?
> >
> > Majied Najjar
>
>
>
> --
> Anand V. Avati
More information about the Gluster-devel
mailing list