On Tue, May 19, 2009 at 2:45 PM, Steinhauer Juergen <[email protected]> wrote: > Hi! > > I hope that's what you meant with stack trace:
yep. thats a very strange place to crash. can you try printing the values of lpc and *node please? but generally speaking, the config doesn't make sense. symmetrical was a short-term hack that wont do what you think it will. what was the reason for you wanting to use it? > > (gdb) bt > #0 0x00a3f70b in pe_find_node_id (nodes=0x82cad00, > id=0x82c7418 "04057199-76a0-4fe6-8963-c3fe931b0dfe") at status.c:294 > #1 0x00a656bd in node_list_update (list1=0x82c25b0, list2=0x82cad00, > factor=1) > at native.c:704 > #2 0x00a675f3 in native_merge_weights (rsc=0x82ea240, > rhs=0x82bfbc0 "ips, nodes=0x82c25b0, factor=1, allow_rollback=1) > at native.c:136 > #3 0x00a67b92 in group_merge_weights (rsc=0x82f1de0, > rhs=0x82f29b0 "app1", nodes=0x82c25b0, factor=1, allow_rollback=1) > at group.c:393 > #4 0x00a67093 in native_color (rsc=0x82ea240, data_set=0xbfd8acc4) > at native.c:195 > #5 0x00a66fb7 in native_color (rsc=0x82f2b28, data_set=0xbfd8acc4) > at native.c:183 > #6 0x00a692b0 in group_color (rsc=0x82f1de0, data_set=0xbfd8acc4) > at group.c:61 > #7 0x00a5a727 in stage5 (data_set=0xbfd8acc4) at allocate.c:590 > #8 0x00a59ae8 in do_calculations (data_set=0xbfd8acc4, > xml_input=0x82ab9a8, > now=0x0) at pengine.c:276 > #9 0x00a59fb9 in process_pe_message (msg=0x82a6688, xml_data=0x82ab9a8, > sender=0x8247dc0) at pengine.c:112 > #10 0x009e9a31 in subsystem_msg_dispatch (sender=0x8247dc0, > user_data=0x8048810) at ipc.c:309 > ---Type <return> to continue, or q <return> to quit--- > #11 0x00784896 in G_CH_dispatch_int (source=0x8247f30, callback=0, > user_data=0x0) at GSource.c:625 > #12 0x007f91a2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 > #13 0x007fc196 in ?? () from /lib/libglib-2.0.so.0 > #14 0x007fc557 in g_main_loop_run () from /lib/libglib-2.0.so.0 > #15 0x08048afe in pe_init () > #16 0x08048d20 in main () > > > Andrew Beekhof schrieb: >>> the pengine crashes with signal 11. >> >> stack trace? >> > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
