Re: [Gluster-users] [External] Re: Geo Replication / Error: bash: gluster: command not found
Hi,
i resolved this specifying the command= directive in the ssh public keys:
command="/usr/libexec/glusterfs/gsyncd" ssh-rsa B3
and
command="tar ${SSH_ORIGINAL_COMMAND#* }" ssh-rsa B...
On Tue, Nov 27, 2018 at 10:15 PM m0rbidini wrote:
> Hi everyone.
>
> I'm having the same problem in almost the same scenario.
>
> It only started after I upgraded to v4.1.5
>
> Output from the first node of the master volume:
>
> [root@glusterfs-node1 ~]# gluster volume geo-replication gv0
> geouser@glusterfs-node3::gv0 create push-pem
> gluster command on geouser@glusterfs-node3 failed. Error: bash: gluster:
> command not found
> geo-replication command failed
>
> [root@glusterfs-node1 ~]# cat /etc/redhat-release
> CentOS Linux release 7.5.1804 (Core)
>
> [root@glusterfs-node1 ~]# rpm -qa | grep glu
> glusterfs-libs-4.1.5-1.el7.x86_64
> glusterfs-fuse-4.1.5-1.el7.x86_64
> centos-release-gluster41-1.0-3.el7.centos.noarch
> glusterfs-4.1.5-1.el7.x86_64
> glusterfs-cli-4.1.5-1.el7.x86_64
> glusterfs-client-xlators-4.1.5-1.el7.x86_64
> glusterfs-server-4.1.5-1.el7.x86_64
> glusterfs-geo-replication-4.1.5-1.el7.x86_64
> glusterfs-api-4.1.5-1.el7.x86_64
> python2-gluster-4.1.5-1.el7.x86_64
>
> Output from the first node of the slave volume:
>
> [root@glusterfs-node3 ~]# cat /etc/redhat-release
> CentOS Linux release 7.5.1804 (Core)
>
> [root@glusterfs-node3 ~]# rpm -qa | grep glu
> glusterfs-libs-4.1.5-1.el7.x86_64
> glusterfs-client-xlators-4.1.5-1.el7.x86_64
> glusterfs-fuse-4.1.5-1.el7.x86_64
> glusterfs-server-4.1.5-1.el7.x86_64
> glusterfs-geo-replication-4.1.5-1.el7.x86_64
> centos-release-gluster41-1.0-3.el7.centos.noarch
> glusterfs-4.1.5-1.el7.x86_64
> glusterfs-api-4.1.5-1.el7.x86_64
> glusterfs-cli-4.1.5-1.el7.x86_64
> python2-gluster-4.1.5-1.el7.x86_64
>
>
> > Hi all,
> >
> > I encounter a problem to set up my geo replication session in glusterfs
> > 4.1.5 on centos 7.5.1804.
> >
> > After I give the
> > gluster volume geo-replication mastervol geoaccount at servere::slavevol
> > create push-pem
> >
> > I see the following
> >
> > gluster command on geoaccount at servere failed. Error: bash: gluster:
> command
> > not found
> > geo-replication command failed
> >
> > Do you know where is the problem?
> >
> > Thanks in advance!
> >
> > BR
> > -- next part --
> > An HTML attachment was scrubbed...
> > URL: <
> http://lists.gluster.org/pipermail/gluster-users/attachments/20181115/7449ed9c/attachment.html
> >
> >
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
--
Davide Obbi
System Administrator
Booking.com B.V.
Vijzelstraat 66-80 Amsterdam 1017HL Netherlands
Direct +31207031558
[image: Booking.com]
Re: [Gluster-users] Geo Replication / Error: bash: gluster: command not found
Hi everyone. I'm having the same problem in almost the same scenario. It only started after I upgraded to v4.1.5 Output from the first node of the master volume: [root@glusterfs-node1 ~]# gluster volume geo-replication gv0 geouser@glusterfs-node3::gv0 create push-pem gluster command on geouser@glusterfs-node3 failed. Error: bash: gluster: command not found geo-replication command failed [root@glusterfs-node1 ~]# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core) [root@glusterfs-node1 ~]# rpm -qa | grep glu glusterfs-libs-4.1.5-1.el7.x86_64 glusterfs-fuse-4.1.5-1.el7.x86_64 centos-release-gluster41-1.0-3.el7.centos.noarch glusterfs-4.1.5-1.el7.x86_64 glusterfs-cli-4.1.5-1.el7.x86_64 glusterfs-client-xlators-4.1.5-1.el7.x86_64 glusterfs-server-4.1.5-1.el7.x86_64 glusterfs-geo-replication-4.1.5-1.el7.x86_64 glusterfs-api-4.1.5-1.el7.x86_64 python2-gluster-4.1.5-1.el7.x86_64 Output from the first node of the slave volume: [root@glusterfs-node3 ~]# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core) [root@glusterfs-node3 ~]# rpm -qa | grep glu glusterfs-libs-4.1.5-1.el7.x86_64 glusterfs-client-xlators-4.1.5-1.el7.x86_64 glusterfs-fuse-4.1.5-1.el7.x86_64 glusterfs-server-4.1.5-1.el7.x86_64 glusterfs-geo-replication-4.1.5-1.el7.x86_64 centos-release-gluster41-1.0-3.el7.centos.noarch glusterfs-4.1.5-1.el7.x86_64 glusterfs-api-4.1.5-1.el7.x86_64 glusterfs-cli-4.1.5-1.el7.x86_64 python2-gluster-4.1.5-1.el7.x86_64 > Hi all, > > I encounter a problem to set up my geo replication session in glusterfs > 4.1.5 on centos 7.5.1804. > > After I give the > gluster volume geo-replication mastervol geoaccount at servere::slavevol > create push-pem > > I see the following > > gluster command on geoaccount at servere failed. Error: bash: gluster: command > not found > geo-replication command failed > > Do you know where is the problem? > > Thanks in advance! > > BR > -- next part -- > An HTML attachment was scrubbed... > URL: < http://lists.gluster.org/pipermail/gluster-users/attachments/20181115/7449ed9c/attachment.html > > ___ Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Shared Storage is unmount after stopping glusterd
Hello Rafi, a few days ago I had the scenario described below. Here are the log entries. As you can see glusterd was stopped at 15:22:48. The same time FUSE of shared_storage was stopped. It seems to be nearly the same error message. You can also see that I restarted glusterd manually but FUSE of shared_storage was not restarted *#-> /var/log/glusterfs/glusterd.log[2018-11-21 15:22:37.406032] I [MSGID: 106487] [glusterd-handler.c:1486:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list reqThe message "I [MSGID: 106488] [glusterd-handler.c:1549:__glusterd_handle_cli_get_volume] 0-management: Received get vol req" repeated 7 times between [2018-11-21 15:21:45.377310] and [2018-11-21 15:22:39.382300][2018-11-21 15:22:48.623951] W [glusterfsd.c:1514:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7559) [0x7fb1e5f11559] -->/usr/sbin/glusterd(glusterfs_sigwaiter+0xfd) [0x561c3626340d] -->/usr/sbin/glusterd(cleanup_and_exit+0x5a) [0x561c362631fa] ) 0-: received signum (15), shutting down[2018-11-21 15:22:53.491120] I [MSGID: 100030] [glusterfsd.c:2741:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 4.1.5 (args: /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO)[2018-11-21 15:22:53.494326] I [MSGID: 106478] [glusterd.c:1423:init] 0-management: Maximum allowed open file descriptors set to 65536[2018-11-21 15:22:53.494372] I [MSGID: 106479] [glusterd.c:1481:init] 0-management: Using /var/lib/glusterd as working directory[2018-11-21 15:22:53.494393] I [MSGID: 106479] [glusterd.c:1486:init] 0-management: Using /var/run/gluster as pid file working directory[2018-11-21 15:22:53.496564] I [socket.c:4477:socket_init] 0-socket.management: SSL support on the I/O path is ENABLED[2018-11-21 15:22:53.496598] I [socket.c:4480:socket_init] 0-socket.management: SSL support for glusterd is ENABLED[2018-11-21 15:22:53.496607] I [socket.c:4497:socket_init] 0-socket.management: using private polling thread[2018-11-21 15:22:53.496615] I [socket.c:4507:socket_init] 0-socket.management: using certificate depth 1[2018-11-21 15:22:53.496891] E [socket.c:4554:socket_init] 0-socket.management: failed to open /etc/ssl/dhparam.pem, DH ciphers are disabled[2018-11-21 15:22:53.499933] W [MSGID: 103071] [rdma.c:4629:__gf_rdma_ctx_create] 0-rpc-transport/rdma: rdma_cm event channel creation failed [No such device][2018-11-21 15:22:53.499970] W [MSGID: 103055] [rdma.c:4938:init] 0-rdma.management: Failed to initialize IB Device[2018-11-21 15:22:53.499983] W [rpc-transport.c:351:rpc_transport_load] 0-rpc-transport: 'rdma' initialization failed[2018-11-21 15:22:53.500148] W [rpcsvc.c:1781:rpcsvc_create_listener] 0-rpc-service: cannot create listener, initing the transport failed[2018-11-21 15:22:53.500174] E [MSGID: 106244] [glusterd.c:1764:init] 0-management: creation of 1 listeners failed, continuing with succeeded transport[2018-11-21 15:22:53.500361] I [socket.c:4480:socket_init] 0-socket.management: SSL support for glusterd is ENABLED[2018-11-21 15:22:53.500373] I [socket.c:4507:socket_init] 0-socket.management: using certificate depth 1[2018-11-21 15:22:53.500615] E [socket.c:4554:socket_init] 0-socket.management: failed to open /etc/ssl/dhparam.pem, DH ciphers are disabled[2018-11-21 15:22:55.353929] I [MSGID: 106513] [glusterd-store.c:2240:glusterd_restore_op_version] 0-glusterd: retrieved op-version: 40100[2018-11-21 15:22:55.423433] I [MSGID: 106544] [glusterd.c:158:glusterd_uuid_init] 0-management: retrieved UUID: 7e7fd30a-94c9-4c21-9c4b-3817508ef121[2018-11-21 15:22:55.429214] I [MSGID: 106498] [glusterd-handler.c:3614:glusterd_friend_add_from_peerinfo] 0-management: connect returned 0[2018-11-21 15:22:55.429317] I [MSGID: 106498] [glusterd-handler.c:3614:glusterd_friend_add_from_peerinfo] 0-management: connect returned 0[2018-11-21 15:22:55.429379] W [MSGID: 106061] [glusterd-handler.c:3408:glusterd_transport_inet_options_build] 0-glusterd: Failed to get tcp-user-timeout[2018-11-21 15:22:55.429443] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600[2018-11-21 15:22:55.429623] I [socket.c:4477:socket_init] 0-management: SSL support on the I/O path is ENABLED[2018-11-21 15:22:55.429635] I [socket.c:4480:socket_init] 0-management: SSL support for glusterd is ENABLED[2018-11-21 15:22:55.429643] I [socket.c:4497:socket_init] 0-management: using private polling thread[2018-11-21 15:22:55.429650] I [socket.c:4507:socket_init] 0-management: using certificate depth 1[2018-11-21 15:22:55.429914] E [socket.c:4554:socket_init] 0-management: failed to open /etc/ssl/dhparam.pem, DH ciphers are disabled[2018-11-21 15:22:55.431676] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600[2018-11-21
