The lock service is under development and not yet complete. We are targeting May 15th with high confidence for the 1.0 releases of corosync and openais with this feature usable in production.
regards -steve On Thu, 2009-04-02 at 13:02 +0200, Dietmar Maurer wrote: > This time I stopped the clvm-openais daemon, which causes a SIGABRT in > the coroync binaries: > > in lck.c, line 1741 > > assert (resource_lock != NULL); > > I think it not good to terminate one of the most important services in > the system that way. > > Any idea what is wrong? > > - Dietmar > > > --------------------------------------- > Apr 2 6:40:01 [LCK ] LIB request: saLckResourceOpen V_pves1-1 > Apr 2 6:40:01 [LCK ] EXEC request: saLckResourceOpen V_pves1-1 > [New Thread 0xb183b8d0 (LWP 4410)] > Apr 2 6:40:01 [LCK ] LIB request: saLckResourceLock V_pves1-1 > Apr 2 6:40:01 [LCK ] EXEC request: saLckResourceLock V_pves1-1 > Apr 2 6:40:01 [LCK ] [DEBUG]: lock_id=25 addr=0x92d6588 > corosync: lck.c:1867: message_handler_req_exec_lck_resourceunlock: > Assertion `resource_lock != ((void *)0)' failed. > > Program received signal SIGABRT, Aborted. > [Switching to Thread 0xb7d756b0 (LWP 2593)] > 0xb7f37416 in __kernel_vsyscall () > (gdb) > (gdb) bt > #0 0xb7f37416 in __kernel_vsyscall () > #1 0xb7da2640 in raise () from /lib/i686/cmov/libc.so.6 > #2 0xb7da4018 in abort () from /lib/i686/cmov/libc.so.6 > #3 0xb7d9b5be in __assert_fail () from /lib/i686/cmov/libc.so.6 > #4 0xb70a2225 in message_handler_req_exec_lck_resourceunlock () from > /usr/lib/lcrso/service_lck.lcrso > #5 0x00000005 in ?? () > #6 0xb70a49b8 in ?? () from /usr/lib/lcrso/service_lck.lcrso > #7 0xbfa495d8 in ?? () > #8 0x00000000 in ?? () > > > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
