Václav Mach writes:
> 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
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
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 waited for before corosync
is
Ken Gaillot napsal(a):
On Tue, 2017-10-10 at 12:24 +0200, Václav Mach wrote:
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
Václav Mach napsal(a):
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
On Tue, 2017-10-10 at 12:24 +0200, Václav Mach wrote:
> 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
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.
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
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
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, is not ready (709-1337-18)
> Oct 10
Hello,
I'm working on a two node cluster. The nodes are r1nren (r1) and r2nren
(r2). There are some resources at the moment, but I think it's not
important for this problem.
Both nodes are virtual servers running on vmware. Both nodes are running
debian strech, I'm using corosync and
11 matches
Mail list logo