[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gluster-devel] Problem - Transport endpoint is not connected
From: |
Daniel Maher |
Subject: |
Re: [Gluster-devel] Problem - Transport endpoint is not connected |
Date: |
Wed, 16 Apr 2008 10:39:54 +0200 |
On Tue, 15 Apr 2008 23:16:53 -0700 (PDT) B P <address@hidden>
wrote:
> 2008-04-16 07:10:56 D [spec.y:152:section_option] libglusterfs/parser:
> Option:client:transport-timeout:3 2008-04-16 07:10:56 D
> 2008-04-16 07:11:00 E [fuse-bridge.c:1976:fuse_statfs_cbk]
> glusterfs-fuse: 4: ERR => -1 (107)
So your timeout is set to 3 seconds, and you started the client at
07:10:56 (thus, but 07:11:00, it times out).
> 2008-04-16 07:11:16 D [spec.y:115:new_section] libglusterfs/parser:
> New node for 'brick' 2008-04-16 07:11:16 D [spec.y:132:section_type]
> libglusterfs/parser: Type:brick:storage/posix
But you didn't start your server process until 07:11:16, 16 seconds
(and roughly 5 "timeout periods") later. Have you tried starting the
server process first, then the client after ?
Is the adress of PC2indeed "10.20.1.19" ? Does this machine have a
firewall running on it ?
--
Daniel Maher <dma AT witbe.net>