Le 14 d?cembre 2011 14:54, Marc Muehlfeld < Marc.Muehlfeld at medizinische-genetik.de> a ?crit : > Am 14.12.2011 14:00, schrieb Rapha?l Hoareau: > >> You could also try to use two NICs with specific routes. NIC1 knows the >> >> route to Server1 and NIC2 knows the route to Server2. >> > > Could it be possible that this can't be done or do I miss something? > > Node 1: 192.168.29.14 and 192.168.20.14 > Node 2: 192.168.29.15 and 192.168.20.15 > Each IP is on a separate own NIC in both machines. > > > > Connection over both NICs are fine: > > # traceroute 192.168.20.14 > traceroute to 192.168.20.14 (192.168.20.14), 30 hops max, 60 byte packets > 1 192.168.20.14 (192.168.20.14) 0.162 ms 0.148 ms 0.141 ms > > # traceroute 192.168.29.14 > traceroute to 192.168.29.14 (192.168.29.14), 30 hops max, 60 byte packets > 1 192.168.29.14 (192.168.29.14) 0.189 ms 0.172 ms 0.244 ms > > Could you precise on which host the command is executed ? It will help a lot. (Also available for the output above) > > > But (both nodes on different NICs/Subnets): > > # gluster peer probe 192.168.29.14 > Probe successful > > # gluster volume create test replica 2 transport tcp 192.168.29.14:/mnt/ > 192.168.20.15:/mnt/ > Operation failed on 192.168.29.14 > > > Both nodes with connection over the same NIC/Subnet: > > # gluster peer probe 192.168.20.14 > Probe successful > > # gluster volume create test replica 2 transport tcp 192.168.20.14:/mnt/ > 192.168.20.15:/mnt/ > Creation of volume test has been successful. ... > > It also works if I create the volume over the 192.168.29.0/24 subnet. But > not if I mix them. > > > > > > The log says: > [2011-12-14 14:53:45.253837] I [glusterd-handler.c:448:**glusterd_handle_cluster_lock] > 0-glusterd: Received LOCK from uuid: 4e765edc-9ca6-4404-8757-** > ca170ce938df > [2011-12-14 14:53:45.253888] I [glusterd-utils.c:243:**glusterd_lock] > 0-glusterd: Cluster lock held by 4e765edc-9ca6-4404-8757-**ca170ce938df > [2011-12-14 14:53:45.253938] I [glusterd-handler.c:2651:**glusterd_op_lock_send_resp] > 0-glusterd: Responded, ret: 0 > [2011-12-14 14:53:45.255287] I [glusterd-handler.c:488:**glusterd_req_ctx_create] > 0-glusterd: Received op from uuid: 4e765edc-9ca6-4404-8757-**ca170ce938df > [2011-12-14 14:53:45.256600] E [glusterd-op-sm.c:366:** > glusterd_op_stage_create_**volume] 0-glusterd: cannot resolve brick: > 192.168.20.15:/mnt > It seems that 192.168.29.14 can't resolv 192.168.20.15. Can you show the result of "route -n" executed on the host that produces that log ? > [2011-12-14 14:53:45.256635] E [glusterd-op-sm.c:7370:**glusterd_op_ac_stage_op] > 0-: Validate failed: 1 > [2011-12-14 14:53:45.256681] I [glusterd-handler.c:2743:**glusterd_op_stage_send_resp] > 0-glusterd: Responded to stage, ret: 0 > [2011-12-14 14:53:45.256994] I [glusterd-handler.c:2693:** > glusterd_handle_cluster_**unlock] 0-glusterd: Received UNLOCK from uuid: > 4e765edc-9ca6-4404-8757-**ca170ce938df > [2011-12-14 14:53:45.257049] I [glusterd-handler.c:2671:**glusterd_op_unlock_send_resp] > 0-glusterd: Responded to unlock, ret: 0 > I don't have much time right now, but I'll try to help you a bit more later. Regards, Rapha?l. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20111214/5725589a/attachment.htm>
