[Pacemaker] corosync service start giving segmentation fault on centos
Aarti Sawant
aartipsawant10 at gmail.com
Fri Sep 20 01:01:28 EDT 2013
when i try to install corosync i get seg fault error
when i am trying to start corosync i get error of segfault
-bash-4.1# service corosync start
Starting Corosync Cluster Engine (corosync): /etc/init.d/corosync: line 85:
610 Segmentation fault (core dumped) $prog > /dev/null 2>&1
[FAILED]
-bash-4.1# tail /var/log/messages
Sep 19 08:09:40 test1 kernel: imklog 5.8.10, log source = /proc/kmsg
started.
Sep 19 08:09:40 test1 rsyslogd: [origin software="rsyslogd"
swVersion="5.8.10" x-pid="327" x-info="http://www.rsyslog.com"] start
Sep 19 08:09:40 test1 rpc.statd[361]: Version 1.2.3 starting
Sep 19 08:09:40 test1 sm-notify[362]: Version 1.2.3 starting
Sep 19 08:16:12 test1 kernel: corosync[5858]: segfault at 0 ip
00007f8b7192e50b sp 00007fffcc9938a8 error 6 in libc-2.12.so
[7f8b718aa000+18a000]
Sep 19 08:46:11 test1 kernel: imklog 5.8.10, log source = /proc/kmsg
started.
Sep 19 08:46:11 test1 rsyslogd: [origin software="rsyslogd"
swVersion="5.8.10" x-pid="325" x-info="http://www.rsyslog.com"] start
Sep 19 08:46:11 test1 rpc.statd[359]: Version 1.2.3 starting
Sep 19 08:46:11 test1 sm-notify[360]: Version 1.2.3 starting
Sep 19 08:46:20 test1 kernel: corosync[6907]: segfault at 0 ip
00007fca0b65050b sp 00007fff65aa4588 error 6 in libc-2.12.so
[7fca0b5cc000+18a000]
On Fri, Sep 20, 2013 at 5:24 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>
> On 19/09/2013, at 11:07 PM, Aarti Sawant <aartipsawant10 at gmail.com> wrote:
>
> > hello,
> >
> > i am running corosync plugin and not using cman.
>
> then contrary to what digimer said, you do need to start corosync yourself.
>
> >
> >
> > On Thu, Sep 19, 2013 at 4:22 PM, Andrew Beekhof <andrew at beekhof.net>
> wrote:
> >
> > On 19/09/2013, at 8:17 PM, Aarti Sawant <aartipsawant10 at gmail.com>
> wrote:
> >
> > > hello,
> > >
> > > pacemaker starts but it corosync service is not started
> >
> > Are you using cman (cluster.conf) or the corosync plugin (corosync.conf)
> > Pacemaker only starts corosync if cman (which is a particular way of
> running corosync) is being used.
> >
> >
> > > below is a output of service pacemaker start
> > > pa -ax command to check the processe on lxc container
> > >
> > >
> > > -bash-4.1# service pacemaker start
> > > Starting Pacemaker Cluster Manager: [ OK ]
> > > -bash-4.1# ps -ax
> > > Warning: bad syntax, perhaps a bogus '-'? See
> /usr/share/doc/procps-3.2.8/FAQ
> > > PID TTY STAT TIME COMMAND
> > > 1 ? Ss 0:00 /sbin/init
> > > 71 ? S<s 0:00 /sbin/udevd -d
> > > 201 ? Ss 0:00 login -- root
> > > 202 pts/0 Ss 0:00 -bash
> > > 666 ? Ss 0:00 /sbin/dhclient -1 -q -lf
> /var/lib/dhclient/dhclient-e
> > > 1417 pts/0 S 0:00 pacemakerd
> > > 1423 pts/0 R+ 0:00 ps -ax
> > >
> > >
> > > Thanks ,
> > > Aarti Sawant
> > > NTTDATA OSS Center Oune
> > >
> > >
> > > On Thu, Sep 19, 2013 at 12:40 PM, Digimer <lists at alteeve.ca> wrote:
> > > On 18/09/13 23:59, Aarti Sawant wrote:
> > > > Hello,
> > > > i am using corosync - corosync-1.4.1-15.el6_4.1.x86_64
> > > > i am using crmsh +pacemaker+corosync
> > > > my pacemaker service starts but when i try to start corosync i get
> > > > segmentation fault error.
> > > > Thanks for replying.
> > > >
> > > > Thanks,
> > > > Aarti Sawant,
> > > > NTTDATA OSS Center Pune
> > > >
> > >
> > > Pacemaker starts corosync, you don't need to start corosync yourself.
> > >
> > > --
> > > 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?
> > >
> > > _______________________________________________
> > > Pacemaker mailing list: Pacemaker at 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
> >
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at 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
> >
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at 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
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130920/11a9062d/attachment-0003.html>
More information about the Pacemaker
mailing list