[Users] troubles with usrloc module: db_mode=3 (DB only)

Bogdan-Andrei Iancu bogdan at voice-system.ro
Thu Jun 8 12:37:43 CEST 2006


Hi Christian,

getting a backtrace will be very, very helpful. be sure the you are 
using exactly the same binaries as the ones generating the core file.

Also, could you describe the scenario leading to the crash? also set 
debug=9 and the log will be very useful.

regards,
bogdan

Christian Schlatter wrote:

> Hi all,
>
> Running openser (CVS HEAD) with usrloc:db_mode=3 causes it to crash 
> repeatedly after 15 secs or so. The core dump does not say much except
>
> (gdb) bt
> #0  0x00b2b392 in ?? ()
> #1  0x08131468 in mem_pool ()
> #2  0xbfff8b54 in ?? ()
> #3  0xbfff8b54 in ?? ()
> #4  0x00000008 in ?? ()
> #5  0x00b3adbf in ?? ()
> #6  0x00000007 in ?? ()
> #7  0x00b3a88c in ?? ()
> #8  0x00000006 in ?? ()
> #9  0x00b3adcd in ?? ()
> #10 0x00000005 in ?? ()
> #11 0x00b3adae in ?? ()
> #12 0xb576a560 in ?? ()
> #13 0x00000007 in ?? ()
> #14 0x00b39c59 in ?? ()
> #15 0x00000005 in ?? ()
> #16 0x00b3adae in ?? ()
> #17 0x00000001 in ?? ()
> #18 0x00000001 in ?? ()
> #19 0x00000000 in ?? ()
>
>
> The openser log looks like:
>
> ERROR: receive_fd: EOF on 16
> child process 18101 exited by a signal 11
> core was generated
>
>
> I also don't see any mysql errors. The last mysql query issued by 
> openser before dying is always
>
> Query  delete from location where expires<'2006-06-05 16:03:17'
> (only the timestamp changes)
>
> Deleting all location table entries before starting up openser does 
> not help either. Is there something special I have to consider when 
> running openser in DB-only mode?
>
> Thanks for any help,
> Christian
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Users mailing list
>Users at openser.org
>http://openser.org/cgi-bin/mailman/listinfo/users
>  
>





More information about the sr-users mailing list