Why I am getting “0-management: readv on /var/run/” messages in vol log file ?

1 Reply

Today while working on Cu issue I found that below messages were coming continuously in vol.log file.

[2015-02-11 12:10:08.574421] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/fcc8c003f45e9ea3ce0caef63d4f7dff.socket failed (Invalid argument)
[2015-02-11 12:10:11.578722] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/fcc8c003f45e9ea3ce0caef63d4f7dff.socket failed (Invalid argument)
[2015-02-11 12:10:14.583767] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/fcc8c003f45e9ea3ce0caef63d4f7dff.socket failed (Invalid argument)

I checked with “ss -x” didn’t find any problem with socket.

After doing google for few minutes I found that bugs are already opened for it. This will probably get fixed in future version of RHS  3.0.4

As workaround we can follow these steps to get rid of these messages. These messages were coming at interval of 3s.

1) Open the /etc/init.d/glusterd file and search for LOG_LEVEL parameter.

Before Change :

LOG_LEVEL=''

After Change it should look like :

LOG_LEVEL='ERROR'

2) Restart the glusterd service.

/etc/init.d/glusterd restart

This should start reporting after that.

Note : We are stopping logging of all warning messages. This is your choice whether to live with them or not 🙂

1 thought on “Why I am getting “0-management: readv on /var/run/” messages in vol log file ?”

  1. Sokratis Galiatsis

    Well, the problem seems to be related to nfs daemons not started correctly.
    In CentOS for example after enabling/start the following services and restarting glusterd service on all glusterfs server the problem went away.

    chkconfig rpcbind on && service rpcbind restart
    chkconfig rpcgssd on && service rpcgssd restart
    chkconfig nfslock on && service nfslock restart

    Check it.

    Reply ↓

Leave a comment