hi,

this is a backtrace of core dump of corosync

(gdb) run
Starting program: /usr/sbin/corosync
warning: linux_test_for_tracefork: failed to kill second child
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6e6250b in __memset_sse2 () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
glibc-2.12-1.107.el6_4.4.x86_64 libibverbs-1.1.6-5.el6.x86_64
librdmacm-1.0.17-0.git4b5c1aa.el6.x86_64 nspr-4.9.5-2.el6_4.x86_64
nss-3.14.3-4.el6_4.x86_64 nss-util-3.14.3-3.el6_4.x86_64
zlib-1.2.3-29.el6.x86_64
(gdb) bt
#0  0x00007ffff6e6250b in __memset_sse2 () from /lib64/libc.so.6
#1  0x00007ffff79a2764 in _logsys_rec_init (fltsize=<value optimized out>)
    at /usr/include/bits/string3.h:85
#2  0x0000000000406389 in logsys_system_init () at main.c:96
#3  0x0000000000410dc6 in __do_global_ctors_aux ()
#4  0x0000000000403c0b in _init ()
#5  0x00007fffffffe7a8 in ?? ()
#6  0x0000000000410d55 in __libc_csu_init ()
#7  0x00007ffff6dfcc70 in __libc_start_main () from /lib64/libc.so.6
#8  0x0000000000404539 in _start ()


Thanks,
Aarti Sawant
NTT DATA OSS Center Pune


On Thu, Sep 19, 2013 at 7:32 PM, Jan Friesse <jfrie...@redhat.com> wrote:

> Aarti,
> can you please try to install debug informations and include backtrace
> from coredump?
>
> Regards,
>   Honza
>
> Aarti Sawant napsal(a):
> > hello,
> >
> > I am trying to setup HA on centos6.4 lxc container.
> > i have install pacemaker and corosync on this container.
> > my settings of /etc/corosync/corosync.conf are as follows
> > # Please read the corosync.conf.5 manual page
> > compatibility: whitetank
> >
> > totem {
> >         version: 2
> >         secauth: off
> >         threads: 0
> >         interface {
> >                ingnumber: 0
> >                bindnetaddr: 192.168.122.66
> >                mcastaddr: 226.94.1.1
> >                mcastport: 5405
> >                ttl: 1
> >        }
> > }
> >
> > logging {
> >        fileline: off
> >        to_stderr: no
> >        to_logfile: yes
> >        to_syslog: no
> >        logfile: /var/log/cluster/corosync.log
> >        debug: off
> >        timestamp: off
> >        logger_subsys {
> >                subsys: AMF
> >                debug: off
> >        }
> > }
> >
> > amf {
> >        mode: disabled
> > }
> >
> > 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# rpm -qa glibc corosync pacemaker
> > glibc-2.12-1.107.el6_4.4.x86_64
> > corosync-1.4.1-15.el6_4.1.x86_64
> > pacemaker-1.1.8-7.el6.x86_64
> >
> > -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]
> >
> >
> > but i am able to start corosync service on host machine(centos6.3)
> > the corosync version on host
> >
> > [root@localhost ~]# rpm -qa corosync pacemaker glibc
> > corosync-1.4.1-15.el6_4.1.x86_64
> > pacemaker-1.1.8-7.el6.x86_64
> > glibc-2.12-1.80.el6.x86_64
> >
> > has anyone faced same problem?
> >
> > Thanks,
> > Aarti Sawant
> > NTTDATA OSS Center Pune
> >
> >
> >
> > _______________________________________________
> > Openais mailing list
> > Openais@lists.linux-foundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/openais
> >
>
>
_______________________________________________
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/openais

Reply via email to