[Gluster-users] Transport endpoint

Robin, Robin robinr at muohio.edu
Mon Dec 17 15:58:19 UTC 2012


Joe, there's nothing around the time stamp.

On the client, /var/log/glusterfs/mnt-gluster-RedhawkShared.log:
[2012-12-13 17:25:21.014040] I [fuse-bridge.c:3376:fuse_init]
0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.13
kernel 7.10
[2012-12-13 17:25:21.014823] I
0-RedhawkShared-replicate-0: added root inode
[2012-12-15 03:21:37.566345] I [glusterfsd.c:1666:main]
0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.3.0
[2012-12-15 03:21:37.687280] I [io-cache.c:1549:check_cache_size_ok]
0-RedhawkShared-quick-read: Max cache size is 25133539328
[2012-12-15 03:21:37.692566] I [io-cache.c:1549:check_cache_size_ok]
0-RedhawkShared-io-cache: Max cache size is 25133539328
[2012-12-15 03:21:37.694761] I [client.c:2142:notify]
0-RedhawkShared-client-0: parent translators are ready, attempting connect
on transport
[2012-12-15 03:21:37.698557] I [client.c:2142:notify]
0-RedhawkShared-client-1: parent translators are ready, attempting connect
on transport

There's nothing on 2012-12-15, other than the fact that at 03:21 AM, I
manually remount the gluster partition again.

John, I've not filed a bug yet.

Let me do another test on the Gluster protocol.

I'm running keepalived for an NFS floating IP. That could be my
work-around for now.

The downside of using NFS is the fact that I need to use an additional
software like keepalived. What are the other downsides ?


On 12/17/12 10:29 AM, "Joe Julian" <joe at julianfamily.org> wrote:

>On 12/17/2012 06:56 AM, Robin, Robin wrote:
>> Hi,
>> I've got Gluster error: Transport endpoint not connected.
>> It came up twice after trying to rsync 2 TB filesystem over; it
>> reached about 1.8 TB and got the error.
>> Logs on the server side (on reverse time order):
>> [2012-12-15 00:53:24.747934] I
>> [server-helpers.c:629:server_connection_destroy]
>> 0-RedhawkShared-server: destroyed connection of
>> [2012-12-15 00:53:24.743459] I [server-helpers.c:474:do_fd_cleanup]
>> 0-RedhawkShared-server: fd cleanup on
>> [2012-12-15 00:53:24.743430] I
>> [server-helpers.c:330:do_lock_table_cleanup] 0-RedhawkShared-server:
>> finodelk released on
>> [2012-12-15 00:53:24.743400] I
>> [server-helpers.c:741:server_connection_put] 0-RedhawkShared-server:
>> Shutting down connection
>> [2012-12-15 00:53:24.743368] I [server.c:685:server_rpc_notify]
>> 0-RedhawkShared-server: disconnecting connectionfrom
>> [2012-12-15 00:53:24.740055] W [socket.c:195:__socket_rwv]
>> 0-tcp.RedhawkShared-server: readv failed (Connection reset by peer)
>> I can't find relevant logs on the client side.
>> From the logs, can we judge for sure that this is a network reset
>> problem ?
>When you say, "I can't find relevant logs on the client side," do you
>mean that you can't find the log, or that there's nothing in there from
>around the same timestamp? The client log will be in /var/log/glusterfs
>and will be named based on the mountpoint.
>Gluster-users mailing list
>Gluster-users at gluster.org

More information about the Gluster-users mailing list