[Pacemaker] corosync service start giving segmentation fault on centos
Digimer
lists at alteeve.ca
Thu Sep 19 06:41:53 UTC 2013
On 18/09/13 22:58, Aarti Sawant wrote:
> hello,
>
> I am new to HA, i am trying to create HA on centos 6.4 LXC container
> I have install pacemaker corosync on container and trying to create a
> cluster.
> contents of /etc/corosync/corosync.conf
>
> compatibility: whitetank
>
> totem {
> version: 2
> secauth: off
> threads: 0
> interface {
> ringnumber: 0
> bindnetaddr: 172.26.126.65
> mcastaddr: 226.94.1.1
> mcastport: 5405
> ttl: 1
> }
> }
>
> logging {
> fileline: off
> to_stderr: no
> to_logfile: yes
> to_syslog: yes
> logfile: /var/log/cluster/corosync.log
> debug: off
> timestamp: on
> logger_subsys {
> subsys: AMF
> debug: off
> }
> }
>
> amf {
> mode: disabled
> }
>
>
> And now i am trying to start the corosync service
> i am getting error
> -bash-4.1# service corosync start
> Starting Corosync Cluster Engine (corosync): /etc/init.d/corosync: line
> 85: 1378 Segmentation fault (core dumped) $prog > /dev/null 2>&1
> [FAILED]
>
> Have anyone got same error?
> i think problem is in corosync binary so i remove corosync and installed
> it again still facing same error.
> i even tried staring corosync on centos6 lxc container, i am facing same
> error.
>
> Thanks,
> Aarti Sawant
> NTTDATA OSS Center Pune.
What kind of cluster are you trying to build? I've not used LXC, but
corosync + pacemaker can be managed by pcs and corosync + cman +
rgmanager can be managed with luci. In either case, you shouldn't need
to configure corosync directly.
All this said, corosync shouldn't segfault. What version are you using?
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
More information about the Pacemaker
mailing list