Scott Merrill
2014-Dec-01 20:25 UTC
[Gluster-users] readv on socket failed (invalid argument)
What causes these errors? [2014-12-01 20:22:04.661974] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed (Invalid argument) [2014-12-01 20:22:07.662292] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed (Invalid argument) [2014-12-01 20:22:10.662612] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed (Invalid argument) [2014-12-01 20:22:13.662965] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed (Invalid argument) [2014-12-01 20:22:16.663287] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed (Invalid argument) [2014-12-01 20:22:19.663602] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed (Invalid argument) [2014-12-01 20:22:22.663946] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/ We're getting a lot of these in our logs ever since upgrading to 3.6.1. Is it related to my previous report of stale locks? http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019621.html Or are these two independent problems? Thanks, Scott
Krishnan Parthasarathi
2014-Dec-02 05:48 UTC
[Gluster-users] readv on socket failed (invalid argument)
Scott, Could you check if there a process is listening on the unix domain socket /var/run/3714f2b1aabf9be7087fc323824b74dd.socket? ss -x | grep /var/run/3714f2b1aabf9be7087fc323824b74dd.socket ~kp ----- Original Message -----> What causes these errors? > > [2014-12-01 20:22:04.661974] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed > (Invalid argument) > [2014-12-01 20:22:07.662292] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed > (Invalid argument) > [2014-12-01 20:22:10.662612] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed > (Invalid argument) > [2014-12-01 20:22:13.662965] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed > (Invalid argument) > [2014-12-01 20:22:16.663287] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed > (Invalid argument) > [2014-12-01 20:22:19.663602] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/3714f2b1aabf9be7087fc323824b74dd.socket failed > (Invalid argument) > [2014-12-01 20:22:22.663946] W [socket.c:611:__socket_rwv] 0-management: > readv on /var/run/ > > We're getting a lot of these in our logs ever since upgrading to 3.6.1. > > Is it related to my previous report of stale locks? > http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019621.html > > Or are these two independent problems? > > Thanks, > Scott > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users >