[Pacemaker] [Openais] Linux HA on debian sparc
Steven Dake
sdake at redhat.com
Tue May 31 16:51:06 UTC 2011
Try running paceamaker using the MCP. The plugin mode of pacemaker
never really worked very well because of complexities of posix mmap and
fork. Not having sparc hardware personally, YMMV. We have recently
with corosync 1.3.1 gone through an alignment fixing process for ARM
arches - hope that solves your alignment problems on sparc as well.
Regards
-steve
On 05/31/2011 08:38 AM, william felipe_welter wrote:
> Im trying to setup HA with corosync and pacemaker using the debian
> packages on SPARC Architecture. Using Debian package corosync process
> dies after initializate pacemaker process. I make some tests with ltrace
> and strace and this tools tell me that corosync died because a
> segmentation fault. I try a lot of thing to solve this problem, but
> nothing made corosync works.
>
> My second try is to compile from scratch (using this
> docs:http://www.clusterlabs.org/wiki/Install#From_Source)
> <http://www.clusterlabs.org/wiki/Install#From_Source%29.> . This way
> corosync process startup perfectly! but some process of pacemaker don't
> start.. Analyzing log i see the probably reason:
>
> attrd: [2283]: info: init_ais_connection_once: Connection to our AIS
> plugin (9) failed: Library error (2)
> ....
> stonithd: [2280]: info: init_ais_connection_once: Connection to our AIS
> plugin (9) failed: Library error (2)
> .....
> cib: [2281]: info: init_ais_connection_once: Connection to our AIS
> plugin (9) failed: Library error (2)
> .....
> crmd: [3320]: debug: init_client_ipc_comms_
> nodispatch: Attempting to talk on: /usr/var/run/crm/cib_rw
> crmd: [3320]: debug: init_client_ipc_comms_nodispatch: Could not init
> comms on: /usr/var/run/crm/cib_rw
> crmd: [3320]: debug: cib_native_signon_raw: Connection to command
> channel failed
> crmd: [3320]: debug: init_client_ipc_comms_nodispatch: Attempting to
> talk on: /usr/var/run/crm/cib_callback
> crmd: [3320]: debug: init_client_ipc_comms_nodispatch: Could not init
> comms on: /usr/var/run/crm/cib_callback
> crmd: [3320]: debug: cib_native_signon_raw: Connection to callback
> channel failed
> crmd: [3320]: debug: cib_native_signon_raw: Connection to CIB failed:
> connection failed
> crmd: [3320]: debug: cib_native_signoff: Signing out of the CIB Service
> crmd: [3320]: debug: init_client_ipc_comms_nodispatch: Attempting to
> talk on: /usr/var/run/crm/cib_rw
> crmd: [3320]: debug: init_client_ipc_comms_nodispatch: Could not init
> comms on: /usr/var/run/crm/cib_rw
> crmd: [3320]: debug: cib_native_signon_raw: Connection to command
> channel failed
> crmd: [3320]: debug: init_client_ipc_comms_nodispatch: Attempting to
> talk on: /usr/var/run/crm/cib_callback
> crmd: [3320]: debug: init_client_ipc_comms_nodispatch: Could not init
> comms on: /usr/var/run/crm/cib_callback
> crmd: [3320]: debug: cib_native_signon_raw: Connection to callback
> channel failed
> crmd: [3320]: debug: cib_native_signon_raw: Connection to CIB failed:
> connection failed
> crmd: [3320]: debug: cib_native_signoff: Signing out of the CIB Service
> crmd: [3320]: info: do_cib_control: Could not connect to the CIB
> service: connection failed
> ....
>
>
>
>
>
> My conf:
> # Please read the corosync.conf.5 manual page
> compatibility: whitetank
>
> totem {
> version: 2
> join: 60
> token: 3000
> token_retransmits_before_loss_const: 10
> secauth: off
> threads: 0
> consensus: 8601
> vsftype: none
> threads: 0
> rrp_mode: none
> clear_node_high_bit: yes
> max_messages: 20
> interface {
> ringnumber: 0
> bindnetaddr: 10.10.23.0
> mcastaddr: 226.94.1.1
> mcastport: 5405
> }
> }
>
> logging {
> fileline: off
> to_stderr: no
> to_logfile: yes
> to_syslog: yes
> logfile: /var/log/cluster/corosync.log
> debug: on
> timestamp: on
> logger_subsys {
> subsys: AMF
> debug: on
> }
> }
>
> amf {
> mode: disabled
> }
>
> service {
> # Load the Pacemaker Cluster Resource Manager
> ver: 0
> name: pacemaker
> }
>
> aisexec {
> user: root
> group: root
> }
>
>
> My Question is: why attrd, cib ... can't connect to AIS Plugin? What
> could be the reasons for the connection failed ?
> (Yes, my /dev/shm are tmpfs)
>
>
>
> --
> William Felipe Welter
> ------------------------------
> Consultor em Tecnologias Livres
> william.welter at 4linux.com.br <mailto:william.welter at 4linux.com.br>
> www.4linux.com.br <http://www.4linux.com.br>
>
>
>
> _______________________________________________
> Openais mailing list
> Openais at lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/openais
More information about the Pacemaker
mailing list