You can ignore this as well. After stopping a nfs or self-heal (nodesvc) daemon process, we attempt to cleanup any socket files if they were left behind. When a nodesvc process stops cleanly, it will cleanup the socket file by itself, and there is no file for glusterd to remove, so glusterd logs this message.
~kaushal
On Fri, Jan 9, 2015 at 10:47 AM, Ravishankar N <ravishankar@xxxxxxxxxx> wrote:
On 01/09/2015 10:39 AM, Tamizhanban K wrote:
> Hi Ravi,
>
> Thanks for your immediate reply. Can you please help with Error 2 as well ... I can see the file is present in the mentioned directory, but cannot understand why it is reporting an error indicating
> Resource temporarily unavailable.
>
Not sure about the second one Tamizh. Perhaps someone working on glusterd can help.
> _Error 2_
> _
> _
> [2015-01-08 18:38:59.379218] E [glusterd-utils.c:3801:glusterd_nodesvc_unlink_socket_file] 0-management: Failed to remove /var/run/b5c81a20be385645b1333701bde3393e.socket error: Resource temporarily
> unavailable
>
> On Fri, Jan 9, 2015 at 6:32 AM, Ravishankar N <ravishankar@xxxxxxxxxx <mailto:ravishankar@xxxxxxxxxx>> wrote:
>
> On 01/09/2015 12:11 AM, Tamizhanban K wrote:
> > _Error 1_
> > _
> > _
> > [2015-01-08 18:24:30.493275] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-0
> >
> >
>
>
> This one's a false error, you can ignore it safely. The fix (http://review.gluster.org/7314) is present in glusterfs 3.6.
>
> -Ravi
>
>
>
>
> --
> Regards,
> Tamizhanban K
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
