[ClusterLabs] corosync service not automatically started

[Václav Mach]

On 10/10/2017 11:40 AM, Valentin Vidic wrote:
> On Tue, Oct 10, 2017 at 11:26:24AM +0200, Václav Mach wrote:
>> # The primary network interface
>> allow-hotplug eth0
>> iface eth0 inet dhcp
>> # This is an autoconfigured IPv6 interface
>> iface eth0 inet6 auto
> 
> allow-hotplug or dhcp could be causing problems.  You can try
> disabling corosync and pacemaker so they don't start on boot
> and start them manually after a few minutes when the network
> is stable.  If it works than you have some kind of a timing
> issue.  You can try using 'auto eth0' or a static IP address
> to see if it helps...
> 

It seems that static network configuration really solved this issue. No 
further modifications of services were necessary.

Thanks for help.

-- 
Václav Mach
CESNET, z.s.p.o.
www.cesnet.cz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3710 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20171010/f6e86c4f/attachment-0002.p7s>