This could happen when u start a new glusterd session while an older one(glusterd) is already running. On 07/05/2013 05:36 AM, Marcus Bointon wrote: > On 3 Jul 2013, at 16:55, Marcus Bointon <marcus at synchromedia.co.uk> wrote: > >> [2013-07-03 14:24:08.350429] I [glusterfsd.c:1666:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.3.0 >> [2013-07-03 14:24:08.350592] E [glusterfsd.c:1296:glusterfs_pidfile_setup] 0-glusterfsd: pidfile /var/run/glusterd.pid lock error (Resource temporarily unavailable) > I just noticed something: those errors are from glusterfsd about a glusterd pid file. Is there some clash going on where one daemon is trying to use the other's pid file? > > Marcus > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users
