Gluster users - Aug 2015 - Why is it not possible to mount a replicated gluster volume with one Gluster server?

I am running 2 glusterd (3.7.3) on individual machines connected by private
network. It apears that I can only mount the (replicated) bricks if both
deamons are up, otherwise it failes. However, failover works - once they
are running.

As I am pretty new to glusterfs, there might be some misconfiguration or
misunderstanding of functionality. So I am hoping to find some help or
hints here which guide me the path.

Trying to mount the brick on the same physical server with deamon running
on this server but not on the other server:

@node2:~$ sudo mount -t glusterfs gs2:/volume1 /data/nfs
Mount failed. Please check the log file for more details.

The coresponding llog entry:

E [socket.c:2332:socket_connect_finish] 0-management: connection to
10.0.0.120:24007 failed (Connection refused)
I [MSGID: 106004] [glusterd-handler.c:5051:__glusterd_peer_rpc_notify]
0-management: Peer <db1> (<41a553e8-918b-4ce4-be48-057a269b0579>),
in
state <Peer in Cluster>, has disconnected from glusterd.
W [socket.c:923:__socket_keepalive] 0-socket: failed to set
TCP_USER_TIMEOUT -1000 on socket 12, Invalid argument
E [socket.c:3019:socket_connect] 0-management: Failed to set
keep-alive: Invalid argument

The last two errors keep on comming every three seconds inside the log!

This is the volume info:

Volume Name: volume1
Type: Replicate
Volume ID: 92d9adb8-756b-4138-87a8-23237d21688f
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: gs1:/data/gluster/brick
Brick2: gs2:/data/gluster/brick
Options Reconfigured:
performance.readdir-ahead: on
performance.cache-size: 256MB
server.allow-insecure: on
performance.io-thread-count: 16
performance.client-io-threads: on

Once both deamons are up and running everythign works perfectly I can mount
and unmount as much as I want and there are no problems.

Thank you in advance for any help on this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150831/733a248c/attachment.html>

On 08/31/2015 12:53 PM, Merlin Morgenstern wrote:
>
> Trying to mount the brick on the same physical server with deamon 
> running on this server but not on the other server:
>
> |@node2:~$ sudo mount -t glusterfs gs2:/volume1 /data/nfs Mount failed. 
> Please check the log file for more details. |
For mount to succeed the glusterd must be up on the node that you 
specify as the volfile-server; gs2 in this case. You can use -o 
backupvolfile-server=gs1 as a fallback.
-Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150831/ef6ae7b6/attachment.html>