It seems that pacemakerd 1.1 is trying to connect to unix socket
corosync.ipc but that is not provided by corosync 2.3.3:
connect(4, {sa_family=AF_FILE, path=@"corosync.ipc"}, 110) = -1
ECONNREFUSED (Connection refused)
With the corosync release from the 1.x branch its available:
root@wrk1:/home
On Thu, 2014-03-27 at 23:07 +0100, emmanuel segura wrote:
> where is your config? anyway why your log shows you are using
> 127.0.0.1 as cluster ip?
I'm using localhost only for a local test. No difference when changed to
a vaild network address.
config is:
totem {
version: 2
tok
-Ursprüngliche Nachricht-
Von:emmanuel segura
Gesendet: Do 27.03.2014 23:12
Betreff:Re: [Pacemaker] pacemaker 2.3.3 and corosync 1.1
An: The Pacemaker cluster resource manager ;
> where is your config? anyway why your log shows you are using 127.0.0.1 as
> cluster i
Hi Developers & Users,
I'm trying to use Corosync 2.3.3 in combination with pacemaker 1.1 to build new
packages for Debian but have problems to start pacemaker:
Corosync is up and running:
Mar 27 17:27:52 debianbuild corosync[23019]: [MAIN ] Corosync Cluster Engine
('2.3.3'): started and re
So you want to setup a ping ressource in each subnet. if your active node can
not reach the ping node in one subnet, its an indication, that the node have
lost its connectivity in that network.
Mit freundlichen Grüßen
Stefan Bauer
--
Cubewerk GmbH
Herzog-Otto-Straße 32
83308 Trostberg
08621
If you dont care about the second nics status, why do you even use it redundant?
Stefan
> Am 19.03.2014 um 19:13 schrieb "Aaron Wilson" :
>
> Hello,
>
> This is my first post and I am new to HA clusters. Let me start by thanking
> everyone for their contributions to such a great project.
>
you have to disable all offloading features (rx, tx, tso...)
Mit freundlichen Grüßen
Stefan Bauer
--
Cubewerk GmbH
Herzog-Otto-Straße 32
83308 Trostberg
08621 - 99 60 237
HRB 22195 AG Traunstein
GF Stefan Bauer
Am 14.02.2014 um 09:40 schrieb "Beo Banks" mailto:beo.ba...@goog
that is caused by tcp offloading features in virtual machines network hw.
google for it.
Mit freundlichen Grüßen
Stefan Bauer
--
Cubewerk GmbH
Herzog-Otto-Straße 32
83308 Trostberg
08621 - 99 60 237
HRB 22195 AG Traunstein
GF Stefan Bauer
Am 14.02.2014 um 08:56 schrieb "Beo
-Ursprüngliche Nachricht-
Von:Loick Pelet
> If anyone has an idea to help me, thank you in advance.
You can set a colocation with negative infinite value, means that ressources
will never run on the same host together.
colocation db_not_with_suricata -inf: res_mysql res_suricata
St
-Ursprüngliche Nachricht-
Von:Michael Schwartzkopff
> I doubt that the backup process disturbs your setup. At least not from the
> first view:
I just ran the backup script manually and also let 20 minutse pass by, but
could not trigger the problem.
Stefan
_
-Ursprüngliche Nachricht-
Von:Michael Schwartzkopff
> 16 minutes (!) after the backup your problems start. From the logs you cannot
> see why. First the monitorign of the IP adress and then the MySQL DB fails.
> Perhaps your backup script is still running or you have some other proble
Hi Folks,
we're running a pacemaker/openais cluster for a webserver with databases in an
active/passive setup with 2 nodes on debian 6.0
Unfortunately this is a "closed environment" so we are quite limited in regard
to version updates.
Close to midnight, a backup-script is running - this seems
12 matches
Mail list logo
