Re: [Gluster-users] Debian stable gluster packages
If we are already speaking about stable packages I have a question: is the 3.6 release safe-enough to run in production? Gesendet: Montag, 09. März 2015 um 12:32 Uhr Von: Kaleb S. KEITHLEY kkeit...@redhat.com An: Osborne, Paul (paul.osbo...@canterbury.ac.uk) paul.osbo...@canterbury.ac.uk, gluster-users@gluster.org gluster-users@gluster.org Betreff: Re: [Gluster-users] Debian stable gluster packages On 03/09/2015 08:24 AM, Osborne, Paul (paul.osbo...@canterbury.ac.uk) wrote: Hi, At the moment for my testing I am using version: 3.5.3-1 using the gluster.org 3.5 LATEST repository. Is it safe to assume that there will be continued critical fixes sent out to this version? Or is there another point release (3.6) that I should be using that will knowingly have reasonable long term support? 3.4 will EOL when 3.7 is released. 3.5 will EOL when 4.0 (or 3.8) is released. Updates are made periodically as necessary, as fixes become available. The tracker BZ for 3.5.4 is https://bugzilla.redhat.com/show_bug.cgi?id=1141158. -- Kaleb ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Upgrade from 3.5 to 3.6: issue with socket
Actually I could solve my issue with the mounting of the volume by re-installing Gluster 3.6 from scratch. Before that I tried to update the volfile as I read in a bug but that did not work. So the only last problem which remains is this warning error with the socket as reported. As I did indeed disable NFS on all my volumes (currently only one) I suppose this is why as you suggest Joe. But this is really annoying having a log entry every 3 seconds in gluster's log file. How can I fix or avoid that? I would say this might be a bug? Gesendet: Montag, 09. März 2015 um 04:13 Uhr Von: Joe Julian j...@julianfamily.org An: gluster-users@gluster.org Betreff: Re: [Gluster-users] Upgrade from 3.5 to 3.6: issue with socket I've seen this when the subprocesses running glustershd and nfs were not restarted after the upgrade. I've also seen it if nfs is disabled on all volumes. On 03/08/2015 09:10 PM, Krishnan Parthasarathi wrote: I just upgraded from 3.5.3 to 3.6.2 and have issues mounting my volume on a client. On the server side I found this error message which might be the cause of my issues: Could you describe the issues you are facing? [2015-03-08 13:22:36.383715] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket failed (Invalid argument) Anyony has any idea what that could be ? This log message indicates that there was no (server) process listening on the socket identified by the path, when glusterd tried to connect(3). This happens if the connect(3) happened sooner than the server process starts listening. glusterd will attempt a (re)connect within the next 3 seconds and should successfully establish connection with the server. This wouldn't result in any sort of 'service disruption' in the I/O path. Could you confirm that this log snippet is from glusterd's log file? ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Upgrade from 3.5 to 3.6: issue with socket
As requested I now opened a bug for that issue: https://bugzilla.redhat.com/show_bug.cgi?id=1199936 Thanks for your help. Gesendet: Montag, 09. März 2015 um 09:14 Uhr Von: Krishnan Parthasarathi kpart...@redhat.com An: Uli Zumbuhl uli.zumb...@gmx.ch Cc: gluster-users@gluster.org Betreff: Re: [Gluster-users] Upgrade from 3.5 to 3.6: issue with socket Actually I could solve my issue with the mounting of the volume by re-installing Gluster 3.6 from scratch. Before that I tried to update the volfile as I read in a bug but that did not work. So the only last problem which remains is this warning error with the socket as reported. As I did indeed disable NFS on all my volumes (currently only one) I suppose this is why as you suggest Joe. But this is really annoying having a log entry every 3 seconds in gluster's log file. How can I fix or avoid that? I would say this might be a bug? This is a bug. Could you raise a bug and provide the id in this thread? Meanwhile, I will send out a patch for review on master and release-3.6 branch. Thanks for reporting this issue. Thanks Joe Julian for giving the crucial piece of lead which helped me identify the issue. ~kp Gesendet: Montag, 09. März 2015 um 04:13 Uhr Von: Joe Julian j...@julianfamily.org An: gluster-users@gluster.org Betreff: Re: [Gluster-users] Upgrade from 3.5 to 3.6: issue with socket I've seen this when the subprocesses running glustershd and nfs were not restarted after the upgrade. I've also seen it if nfs is disabled on all volumes. On 03/08/2015 09:10 PM, Krishnan Parthasarathi wrote: I just upgraded from 3.5.3 to 3.6.2 and have issues mounting my volume on a client. On the server side I found this error message which might be the cause of my issues: Could you describe the issues you are facing? [2015-03-08 13:22:36.383715] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket failed (Invalid argument) Anyony has any idea what that could be ? This log message indicates that there was no (server) process listening on the socket identified by the path, when glusterd tried to connect(3). This happens if the connect(3) happened sooner than the server process starts listening. glusterd will attempt a (re)connect within the next 3 seconds and should successfully establish connection with the server. This wouldn't result in any sort of 'service disruption' in the I/O path. Could you confirm that this log snippet is from glusterd's log file? ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Upgrade from 3.5 to 3.6: issue with socket
Hello, I just upgraded from 3.5.3 to 3.6.2 and have issues mounting my volume on a client. On the server side I found this error message which might be the cause of my issues: [2015-03-08 13:22:36.383715] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/6b8f1f2526c6af8a87f1bb611ae5a86f.socket failed (Invalid argument) Anyony has any idea what that could be ? Regards Uli ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
