Hi,
as far as I understood from the documentation, the booth-arbitrator is not part
of any cluster-site, and just responsible for communicationg with the other
sites.
However, in my test-setup (2 sites, 1 arbitrator) I figured out that also the
arbitrator tries to run the crm_ticket - command:
2013-02-13T13:59:35.082+01:00 pgnode3 booth-arbitrator[] info: [13611]: info:
command: 'crm_ticket -t Ticket -S owner -v 1' was executed
2013-02-13T13:59:35.131+01:00 pgnode3 booth-arbitrator[] info: [13611]: info:
command: 'crm_ticket -t Ticket -S expires -v 1360760495' was executed
2013-02-13T13:59:35.195+01:00 pgnode3 booth-arbitrator[] info: [13611]: info:
command: 'crm_ticket -t Ticket -S ballot -v 7' was executed
Which fails, as strace shows:
14307 execve("/bin/sh", ["sh", "-c", "crm_ticket -t Ticket -S owner -v"...],
[/* 21 vars */]) = 0
....
14307 write(2, "Could not establish cib_rw conne"..., 64) = 64
...
(which is clear, as I do not have pacemaker installed on the arbitrator-node).
I´m using the latest version from GIT:
commit 55ab027233407fd44850f0c4905b085205d55f64
Author: Xia Li <x...@suse.com>
Date: Thu Jan 10 13:48:20 2013 +0800
This is my booth.conf:
transport="UDP"
port="6666"
arbitrator="192.168.181.103"
site="192.168.181.107"
site="192.168.181.108"
ticket="Ticket;120"
(Same on all nodes), and seems to be OK, the booth-daemon recognizes itself as
arbitrator during startup:
"info: [13611]: info: BOOTH arbitrator daemon started"
After some investigation I think, that in line 394 of ticket.c, some check such
as "if (booth_conf->node[ticket_get_myid()].type != ARBITRATOR)" is missing. Am
I right, or is there some reason for the arbitrator to call store_ticket?
Regards,
Michael
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
