Re: socket failed errors in logs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 02/11/2015 08:08 AM, Craig Yoshioka wrote:
> Every 3 seconds my Gluster peers print a socket error to their logs:
> 
> [2015-02-11 02:34:51.538651] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/8ec925040908cb66670cb4304e0c0538.socket failed (Invalid argument)
> [2015-02-11 02:34:54.538965] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/8ec925040908cb66670cb4304e0c0538.socket failed (Invalid argument)
> [2015-02-11 02:34:57.539321] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/8ec925040908cb66670cb4304e0c0538.socket failed (Invalid argument)
> 
> Everything seems to be running fine though…
> 
> Any thoughts?
Check which process is this socket file mapped to? If that process is
not running (for eg - nfs server) then you may end up seeing this log.

~Atin
> 
> Thanks,
> -Craig
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-users
> 

-- 
~Atin
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users





[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux