Re: [Gluster-users] periodical warnings in brick-log after upgrading to gluster 7.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-users] periodical warnings in brick-log after upgrading to gluster 7.1

Amar Tumballi-2


On Sun, Dec 29, 2019 at 9:50 PM Michael Böhm <[hidden email]> wrote:
Hello,

i've finally upgraded our gluster-server to 7.1 (3.8 debian stretch -> gluster-repo 3.12 -> gluster-repo 7.1) and it actually went real smooth. There is just that warning in all brick-logs and every server every 15min i can't really explain myself.

[2019-12-29 05:51:17.807293] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.60:49077 failed (no data available)
[2019-12-29 06:00:47.886369] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.61:49140 failed (no data available)
[2019-12-29 06:06:18.204778] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.60:49077 failed (no data available)
[2019-12-29 06:15:47.317705] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.61:49148 failed (no data available)

.60 and .61 are two servers with bricks for gluster volume "store4". They are not only the gluster-server, they also are clients that mount the gluster volumes. (replicated gluster volume, that hosts kvm images that run locally on the server)

Everything really looks good no other errors or warning - just the lines mentioned above. Is this something i should be worried about or can resolve somehow?

Of course i looked through the web, unfortunately i only really could find one guy that had the same problem but no following messages [1]. And the best explanation i could find was in a bug report [2], so it seems it's not unusual i just don't like ignoring warnings.


Your concern is valid, and if the log level is WARNING, it shouldn't be ignored :-)

I noticed that this is happening when a client disconnects with server (specially, after umount). Was there any periodic umount which is happening? Or a monitoring system which is running, which would do a temporary mount and and check for size etc ?

Regards,
Amar
--


Anyone here that has similiar warning or could explain what i can do about it?


 
________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/441850968

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-users

_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/441850968


NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/441850968

Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel