Re: glusterd doesn't start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 08/12/2015 09:24 PM, paf1@xxxxxxxx wrote:
> Hello,
> some logs after reboot :
> 
> # systemctl status glusterd
> glusterd.service - GlusterFS, a clustered file-system server
>    Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled)
>    Active: failed (Result: exit-code) since St 2015-08-12 16:34:22 CEST;
> 2min 6s ago
>   Process: 1355 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid
> (code=exited, status=1/FAILURE)
> 
> srp 12 16:34:20 2hp2.algocloud.net systemd[1]: Starting GlusterFS, a
> clustered file-system server...
> srp 12 16:34:22 2hp2.algocloud.net systemd[1]: glusterd.service: control
> process exited, code=exited status=1
> srp 12 16:34:22 2hp2.algocloud.net systemd[1]: Failed to start
> GlusterFS, a clustered file-system server.
> srp 12 16:34:22 2hp2.algocloud.net systemd[1]: Unit glusterd.service
> entered failed state.
> 
> 
> but I'm not shure about loga are relevant  my problem - these record are
> visible after glusterd restart only.
This log is not relevant as I believe these are the log entries after
glusterd was manually started. Is it possible for you to share the
entire log file such that I can have a look?
> 
> # tail  etc-glusterfs-glusterd.vol.log
> 
> [2015-08-12 15:50:14.461796] I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req
> [2015-08-12 15:50:15.631170] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> The message "I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req" repeated 4 times between [2015-08-12
> 15:50:14.461796] and [2015-08-12 15:50:14.468411]
> [2015-08-12 15:50:15.631198] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> [2015-08-12 15:50:18.631606] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> [2015-08-12 15:50:18.631649] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> [2015-08-12 15:50:19.623528] I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req
> [2015-08-12 15:50:21.632061] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> The message "I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req" repeated 4 times between [2015-08-12
> 15:50:19.623528] and [2015-08-12 15:50:19.629977]
> [2015-08-12 15:50:21.632123] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> [2015-08-12 15:50:24.632445] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> [2015-08-12 15:50:24.632473] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> [2015-08-12 15:50:24.785810] I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req
> [2015-08-12 15:50:26.467729] E
> [glusterd-op-sm.c:252:glusterd_get_txn_opinfo]
> (-->/usr/lib64/glusterfs/3.7.3/xlator/mgmt/glusterd.so(glusterd_big_locked_handler+0x30)
> [0x7f42e8cf7970]
> -->/usr/lib64/glusterfs/3.7.3/xlator/mgmt/glusterd.so(__glusterd_handle_stage_op+0x1be)
> [0x7f42e8cf95ee]
> -->/usr/lib64/glusterfs/3.7.3/xlator/mgmt/glusterd.so(glusterd_get_txn_opinfo+0x147)
> [0x7f42e8d0a6e7] ) 0-management: Unable to get transaction opinfo for
> transaction ID : c58a4d2e-ea09-4e52-b5dd-4d6b2e2e6fe7
> [2015-08-12 15:50:27.632975] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> The message "I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req" repeated 4 times between [2015-08-12
> 15:50:24.785810] and [2015-08-12 15:50:24.792359]
> [2015-08-12 15:50:27.633017] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> [2015-08-12 15:50:29.946007] I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req
> [2015-08-12 15:50:30.633401] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> The message "I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req" repeated 4 times between [2015-08-12
> 15:50:29.946007] and [2015-08-12 15:50:29.952434]
> [2015-08-12 15:50:30.633446] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> [2015-08-12 15:50:33.633749] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> [2015-08-12 15:50:33.633870] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> [2015-08-12 15:50:35.105927] I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req
> [2015-08-12 15:50:36.634267] W [socket.c:642:__socket_rwv] 0-nfs: readv
> on /var/run/gluster/8fda87786925db271d1df3db3858bfde.socket failed
> (Invalid argument)
> The message "I [MSGID: 106488]
> [glusterd-handler.c:1463:__glusterd_handle_cli_get_volume] 0-glusterd:
> Received get vol req" repeated 4 times between [2015-08-12
> 15:50:35.105927] and [2015-08-12 15:50:35.112442]
> [2015-08-12 15:50:36.634318] I [MSGID: 106006]
> [glusterd-svc-mgmt.c:319:glusterd_svc_common_rpc_notify] 0-management:
> nfs has disconnected from glusterd.
> 
> regs.
> Pa.
> 
> 
> On 11.8.2015 06:21, Atin Mukherjee wrote:
>>
>> On 08/11/2015 02:45 AM, paf1@xxxxxxxx wrote:
>>> After reboot /  reset server we have no  new records in gluster logs (
>>> /var/log/glusterfs ) - any and glusterd doesn't start automaticaly
>>>
>>> # systemctl status glusterd
>>> glusterd.service - GlusterFS, a clustered file-system server
>>>     Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled)
>>>     Active: failed (Result: exit-code) since Po 2015-08-10 21:12:15
>>> CEST;
>>> 2min 23s ago
>>>    Process: 1346 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid
>>> (code=exited, status=1/FAILURE)
>>>
>>> srp 10 21:12:12 2hp2.algocloud.net systemd[1]: Starting GlusterFS, a
>>> clustered file-system server...
>>> srp 10 21:12:15 2hp2.algocloud.net systemd[1]: glusterd.service: control
>>> process exited, code=exited status=1
>>> srp 10 21:12:15 2hp2.algocloud.net systemd[1]: Failed to start
>>> GlusterFS, a clustered file-system server.
>> This indicates that an attempt was made to start glusterd service which
>> means there has to be some logs in /var/log/glusterfs/etc-*glusterd*.log
>> file. Please check the same and find out the error logs, that would give
>> us the hint of the problem.
>>> srp 10 21:12:15 2hp2.algocloud.net systemd[1]: Unit glusterd.service
>>> entered failed state.
>>>
>>> Pa.
>>>
>>> On 10.8.2015 18:21, Niels de Vos wrote:
>>>> On Mon, Aug 10, 2015 at 04:37:19PM +0200, paf1@xxxxxxxx wrote:
>>>>> Hello everybody,
>>>>> I've got long time issue with my glusterd daemon.
>>>>>
>>>>> I'm using Centos 7.1 with last updates and gluster packages from
>>>>> 3.7.3-1
>>>>> version on hypervizor servers.
>>>>> glusterfs-3.7.3-1.el7.x86_64
>>>>> glusterfs-cli-3.7.3-1.el7.x86_64
>>>>> glusterfs-geo-replication-3.7.3-1.el7.x86_64
>>>>> glusterfs-libs-3.7.3-1.el7.x86_64
>>>>> glusterfs-api-3.7.3-1.el7.x86_64
>>>>> vdsm-gluster-4.16.20-0.el7.centos.noarch
>>>>> glusterfs-fuse-3.7.3-1.el7.x86_64
>>>>> glusterfs-client-xlators-3.7.3-1.el7.x86_64
>>>>> glusterfs-server-3.7.3-1.el7.x86_64
>>>>> glusterfs-rdma-3.7.3-1.el7.x86_64
>>>>>
>>>>> After rebooting hypervizor, glusterd doesn't start  automaticaly, then
>>>>> restart manualy him. This problem goes over several last versions.
>>>>>
>>>>> Any idea how to fix this ??
>>>> Please check with "systemctl status glusterd" if the service is
>>>> enabled.
>>>> You can enable the service with "systemctl enable glusterd" and after
>>>> that it should automatically get started upon boot.
>>>>
>>>> HTH,
>>>> Niels
>>>
>>>
>>>
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users@xxxxxxxxxxx
>>> http://www.gluster.org/mailman/listinfo/gluster-users
>>>
> 
> 

-- 
~Atin
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux