Really appreciate your response. I just wanted to close this thread by saying that we were able to figure out the problem.
Since pacemaker was running on other virtual machines except our appliance clearly the problem was our runtime environment. It turns out that our libxml2 library on our appliance was corrupt. It caused huge amount of churn on our side as we had to meet a customer deadline. But the good side was that I took this as an opportunity to gdb pacemaker code. Thanks all -Shravan On Tue, Oct 5, 2010 at 5:01 AM, Andrew Beekhof <and...@beekhof.net> wrote: > On Fri, Oct 1, 2010 at 3:45 PM, Shravan Mishra <shravan.mis...@gmail.com> > wrote: >> Hi, >> >> Just a quick question, who generates the very first cib.xml when >> pacemaker processes are initialized? > > The cib > >> >> Thanks >> Shravan >> >> On Thu, Sep 30, 2010 at 4:22 AM, Andrew Beekhof <and...@beekhof.net> wrote: >>> On Tue, Sep 28, 2010 at 11:47 AM, Andrew Beekhof <and...@beekhof.net> wrote: >>>> On Mon, Sep 27, 2010 at 6:26 AM, Shravan Mishra >>>> <shravan.mis...@gmail.com> wrote: >>>>> Thanks Raoul for the response. >>>>> >>>>> Changing the permission to hacluster:haclient did stop that error. >>>>> >>>>> Now I'm hitting another problem whereby cib is failing to start >>>> >>>> Very strange logs. >>>> Which distribution is this? >>> >>> ^^^^^^^^^^^^^^^^^^^^^^^^ >>> >>>> What does your corosync.conf look like? >>>> >>>> >>>>> ===== >>>>> Sep 27 00:16:29 corosync [pcmk ] info: update_member: Node >>>>> ha2.itactics.com now has process list: >>>>> 00000000000000000000000000110012 (1114130) >>>>> Sep 27 00:16:29 corosync [pcmk ] info: update_member: Node >>>>> ha2.itactics.com now has 1 quorum votes (was 0) >>>>> Sep 27 00:16:29 corosync [pcmk ] info: send_member_notification: >>>>> Sending membership update 100 to 0 children >>>>> Sep 27 00:16:29 corosync [MAIN ] Completed service synchronization, >>>>> ready to provide service. >>>>> Sep 27 00:16:30 corosync [pcmk ] ERROR: pcmk_wait_dispatch: Child >>>>> process cib exited (pid=14889, rc=127) >>>>> Sep 27 00:16:30 corosync [pcmk ] notice: pcmk_wait_dispatch: >>>>> Respawning failed child process: cib >>>>> Sep 27 00:16:30 corosync [pcmk ] info: spawn_child: Forked child >>>>> 14896 for process cib >>>>> crmd[14893]: 2010/09/27_00:16:30 WARN: do_cib_control: Couldn't >>>>> complete CIB registration 1 times... pause and retry >>>>> Sep 27 00:16:31 corosync [pcmk ] ERROR: pcmk_wait_dispatch: Child >>>>> process cib exited (pid=14896, rc=127) >>>>> Sep 27 00:16:31 corosync [pcmk ] notice: pcmk_wait_dispatch: >>>>> Respawning failed child process: cib >>>>> Sep 27 00:16:31 corosync [pcmk ] info: spawn_child: Forked child >>>>> 14901 for process cib >>>>> Sep 27 00:16:32 corosync [pcmk ] ERROR: pcmk_wait_dispatch: Child >>>>> process cib exited (pid=14901, rc=1 >>>>> ====== >>>>> >>>>> >>>>> I have attached the full logs. >>>>> >>>>> We are using corosync 1.2.8 and pacemaker 1.1.3. >>>>> >>>>> >>>>> Thanks. >>>>> Shravan >>>>> >>>>> >>>>> >>>>> On Sat, Sep 25, 2010 at 4:36 AM, Raoul Bhatia [IPAX] <r.bha...@ipax.at> >>>>> wrote: >>>>>> On 24.09.2010 21:41, Shravan Mishra wrote: >>>>>>> >>>>>>> crmd[20612]: 2010/09/24_15:29:57 ERROR: crm_log_init_worker: Cannot >>>>>>> change active directory to /var/lib/heartbeat/cores/hacluster: >>>>>>> Permission denied (13) >>>>>> >>>>>> ls -ald /var/lib/heartbeat/cores/hacluster /var/lib/heartbeat/cores/ >>>>>> /var/lib/heartbeat/ /var/lib/ /var/ >>>>>> >>>>>> is haclient allowed to cd all the way into >>>>>> /var/lib/heartbeat/cores/hacluster ? >>>>>> >>>>>> cheers, >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >>> >> >> _______________________________________________ >> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> > > _______________________________________________ > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > _______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
