Hide Forgot
Glusterd crashes on executing the command >volume gsync stop master slave The core file doesnot contain any stack trace.
PATCH: http://patches.gluster.com/patch/6492 in master (mgmt/glusterd: Use PATH_MAX for pid_file.)
*** Bug 2533 has been marked as a duplicate of this bug. ***
testing 3.2.0 stop fails as - # gluster volume gsync stop :gsyncgit root.compute.amazonaws.com:/mnt/export1 Gsync command failed but glusterd is still running.
(In reply to comment #4) > testing 3.2.0 stop fails as - testing with 3.2.0qa5 stop fails.
(In reply to comment #5) > (In reply to comment #4) > > testing 3.2.0 stop fails as - > testing with 3.2.0qa5 stop fails. tested with 3.2.0qa6 - -- # gluster volume gsync stop :qagit root.compute.amazonaws.com::slave Gsync command failed ----
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > testing 3.2.0 stop fails as - > > testing with 3.2.0qa5 stop fails. > tested with 3.2.0qa6 - > -- > # gluster volume gsync stop :qagit > root.compute.amazonaws.com::slave > > Gsync command failed > ---- with 3.2.0beta1 #gluster volume gsync stop :beta1 root.compute.amazonaws.com::slave Gsync command failed
Now gsync stop does not crash glusterd.