On 06/04/2015 02:11 PM, Pranith Kumar Karampuri wrote: > hi Atin, > Could you help with this please: > http://build.gluster.org/job/rackspace-regression-2GB-triggered/10096/consoleFull I see glusterd failed to start test 6 with the following reason: [2015-06-04 04:23:34.669874] E [MSGID: 100018 [glusterfsd.c:1929:glusterfs_pidfile_update] 0-glusterfsd: pidfile /d/backends/2/glusterd.pid lock failed [Resource temporarily unavailable] This indicates that lock has been already acquired which means at the earlier cleanup_and_exit () it was not invoked due to some reason because I don't see glusterd logging "shutting down" in the kill_glusterd 2. I am trying to reproduce it and will keep you posted. ~Atin > > > Pranith -- ~Atin _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
