Gluster users - Aug 2015 - glusterd doesn't start

On Mon, Aug 10, 2015 at 04:37:19PM +0200, paf1 at email.cz
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150810/fb0866f7/attachment.sig>

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.
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 at email.cz 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150810/1303d864/attachment.html>