[OpenSER-Devel] db problems after restart

Bogdan-Andrei Iancu bogdan at voice-system.ro
Thu Apr 3 19:52:27 CEST 2008


Juha,

as the DB connections are TCP connections, if the connection is opened 
before the fork, it will inherited by all the forked child procs. This 
is a typical error if you mishandle a DB connection from mod_init().

Regards,
Bogdan

PS: maybe a better debugging policy will be to notify if the problematic 
openser contains non-public modules - I mean nobody can help/debug if 
you do not have a clear clue about what you try to debug ;)

Juha Heinanen wrote:
> Juha Heinanen writes:
>
>  > after the crash described in previous message, i restarted openser.
>  > after that it happily processed a few registers and invites, but then on
>  > its own (i.e. syslog does not show any incoming requests) it printed to
>  > syslog:
>  > 
>  > Mar 25 21:04:46 test /usr/sbin/openser[17266]:
>  > ERROR:db_mysql:db_mysql_submit_query: driver error on query: Commands
>  > out of sync; you can't run this command now 
>
> it turned out that this was caused by more than one process sharing the
> same database connection.  the culprit was my own local module, but it
> is still not clear to me, how one module can make other modules to use
> its db connection.
>
> thanks to henning, daniel and anca for helping me to debug the problem.
>
> -- juha
>
> _______________________________________________
> Devel mailing list
> Devel at lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/devel
>
>   




More information about the Devel mailing list