[Gluster-devel] glusterfsd service not able to start on RHEL 6.6

Atin Mukherjee amukherj at redhat.com
Sat Apr 8 07:00:32 UTC 2017


A glusterfsd service indicates a brick process or other gluster services
like self heal, quota and is *implicitly* started by glusterd when a
gluster volume is created and started.

On Wed, 5 Apr 2017 at 20:31, Manohar Mikkili <mikkilimanohar at gmail.com>
wrote:

> Hi,
>
> [root at uc-esm2 ammapp]# /sbin/service glusterfsd start
> [root at uc-esm2 ammapp]# echo $?
> 6
>
> Although, the "glusterd" service is running....
>
> from the /var/log/glusterfs/etc-glusterfs-glusterd.vol.log:
>
>
> +------------------------------------------------------------------------------+
> [2017-04-05 11:48:24.541044] W [glusterfsd.c:1194:cleanup_and_exit] (-->
> 0-: received signum (15), shutting down
> [2017-04-05 11:48:46.014942] I [MSGID: 100030] [glusterfsd.c:2018:main]
> 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.6.5
> (args: /usr/sbin/glusterd --pid-file=/var/run/glusterd.pid)
> [2017-04-05 11:48:46.018338] I [glusterd.c:1214:init] 0-management:
> Maximum allowed open file descriptors set to 65536
> [2017-04-05 11:48:46.018372] I [glusterd.c:1259:init] 0-management: Using
> /var/lib/glusterd as working directory
> [2017-04-05 11:48:46.022043] E [rpc-transport.c:266:rpc_transport_load]
> 0-rpc-transport: /usr/lib64/glusterfs/3.6.5/rpc-transport/rdma.so: cannot
> open shared object file: No such file or directory
> [2017-04-05 11:48:46.022058] W [rpc-transport.c:270:rpc_transport_load]
> 0-rpc-transport: volume 'rdma.management': transport-type 'rdma' is not
> valid or not found on this machine
> [2017-04-05 11:48:46.022068] W [rpcsvc.c:1524:rpcsvc_transport_create]
> 0-rpc-service: cannot create listener, initing the transport failed
> [2017-04-05 11:48:46.023406] I
> [glusterd.c:413:glusterd_check_gsync_present] 0-glusterd: geo-replication
> module not installed in the system
> [2017-04-05 11:48:46.023488] E [store.c:432:gf_store_handle_retrieve] 0-:
> Path corresponding to /var/lib/glusterd/glusterd.info, returned error:
> (No such file or directory)
> [2017-04-05 11:48:46.023506] E [store.c:432:gf_store_handle_retrieve] 0-:
> Path corresponding to /var/lib/glusterd/glusterd.info, returned error:
> (No such file or directory)
> [2017-04-05 11:48:46.023515] I
> [glusterd-store.c:2063:glusterd_restore_op_version] 0-management: Detected
> new install. Setting op-version to maximum : 30603
> [2017-04-05 11:48:46.023593] I
> [glusterd-store.c:3497:glusterd_store_retrieve_missed_snaps_list]
> 0-management: No missed snaps list.
> Final graph:
>
> +------------------------------------------------------------------------------+
>   1: volume management
>   2:     type mgmt/glusterd
>   3:     option rpc-auth.auth-glusterfs on
>   4:     option rpc-auth.auth-unix on
>   5:     option rpc-auth.auth-null on
>   6:     option transport.socket.listen-backlog 128
>   7:     option ping-timeout 30
>   8:     option transport.socket.read-fail-log off
>   9:     option transport.socket.keepalive-interval 2
>  10:     option transport.socket.keepalive-time 10
>  11:     option transport-type rdma
>  12:     option working-directory /var/lib/glusterd
>  13: end-volume
>  14:
>
> +------------------------------------------------------------------------------+
>
> please advise, appreciate your help on this.
>
>
> thanks,
> Manohar.
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel

-- 
- Atin (atinm)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170408/655edeb3/attachment.html>


More information about the Gluster-devel mailing list