Re: [ClusterLabs] corosync service not automatically started

2017-10-11 Thread Václav Mach
On 10/11/2017 09:00 AM, Ferenc Wágner wrote: Václav Mach writes: allow-hotplug eth0 iface eth0 inet dhcp Try replacing allow-hotplug with auto. Ifupdown simply runs ifup -a before network-online.target, which excludes allow-hotplug interfaces. That means allow-hotplug interfaces are not

Re: [ClusterLabs] corosync service not automatically started

2017-10-10 Thread 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

Re: [ClusterLabs] corosync service not automatically started

2017-10-10 Thread Václav Mach
On 10/10/2017 11:04 AM, Valentin Vidic wrote: On Tue, Oct 10, 2017 at 10:35:17AM +0200, Václav Mach wrote: Oct 10 10:27:05 r1nren.et.cesnet.cz corosync[709]: [QB] Denied connection, is not ready (709-1337-18) Oct 10 10:27:06 r1nren.et.cesnet.cz corosync[709]: [QB] Denied connection

[ClusterLabs] corosync service not automatically started

2017-10-10 Thread Václav Mach
eduroam_ping (systemd:eduroam_ping): Started r2nren.et.cesnet.cz mailto (ocf::heartbeat:MailTo):Started r2nren.et.cesnet.cz What could be the problem I encountered? Thanks for help. Regards, Vaclav -- Václav Mach CESNET, z.s.p.o.

[ClusterLabs] strange cluster state

2017-09-29 Thread Václav Mach
urces should run on same node and all the resources should be started in the defined order. The output above does not match that. I'm not totally sure if the attached logs were created when this problem occured, but I think they should. Thanks for help. Regards, Vaclav -- Václav Mach CESNE