En/na Anand Avati ha escrit:
During several days i didn't pay attention to the gluster logs, as
everything worked fine. However, today i decided i was moving a file sized
500MB and the mount point got stale, i couln't access the data from that
particular client. The gluster itself didn't seem to be affected, nodes
didn't report any problem at all in the log files and other clients kept the
mount point without any problem.
Then i decided to have a look at the log files:
*************
2009-01-30 11:00:41 W [client-protocol.c:332:client_protocol_xfer] espai1:
not connected at the moment to submit frame type(1) op(15)
2009-01-30 11:00:41 E [client-protocol.c:3891:client_statfs_cbk] espai1: no
proper reply from server, returning ENOTCONN
2009-01-30 11:00:41 E [tcp-client.c:190:tcp_connect] espai5: non-blocking
connect() returned: 111 (Connection refused)
2009-01-30 11:00:43 W [client-protocol.c:332:client_protocol_xfer] espai2:
not connected at the moment to submit frame type(1) op(15)
2009-01-30 11:00:43 E [client-protocol.c:3891:client_statfs_cbk] espai2: no
proper reply from server, returning ENOTCONN
2009-01-30 11:00:43 E [tcp-client.c:190:tcp_connect] espai6: non-blocking
connect() returned: 111 (Connection refused)
*************
A connection refused error is got when a daemon is not running, or if
there is a packet filter resetting connections. If GlusterFS daemon is
running and other clients are able to access normally, please make
sure there is no packet filtering of some sort happening. You can try
flushing all firewall rules if there were any. Based on the
description you give, it seems to be an issue outside GlusterFS
Avati
Hi,
thanks for the explanation about the origin of the error message.
Well... it doesn't look like there is a problem with the network on
which glusterfs runs, it would have appeared in the rrd graphs i'm
keeping for net traffic, but i'll carry a whole test to see if there's
the slightest problem which could generate this message.
Thanks.
