Hi,
I have an older installation of Kamailio (3.1.1).
It is configured with
modparam("usrloc", "db_mode", 2)
I tried to change this to
modparam("usrloc", "db_mode", 3)
to not have to restart kamailio when I change the alias table directly from SQL.
But then kamailio shutsdown after about one second with this error:
Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11510]: ERROR: <core> [db.c:408]: invalid version 0 for table trusted found, expected 5 (check table structure and table "version") Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11510]: ERROR: permissions [trusted.c:250]: error during table version check. Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11510]: ERROR: <core> [sr_module.c:832]: init_mod_child(): Error while initializing module permissions (/usr/local/lib/kamailio/modules_k/permissions.so) Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11510]: ERROR: <core> [pt.c:481]: ERROR: fork_tcp_process(): init_child failed for process 28, pid 11510, "tcp receiver child=6" Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11510]: ERROR: <core> [tcp_main.c:4811]: ERROR: tcp_main: fork failed: Success Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11512]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 44 Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11482]: ALERT: <core> [main.c:738]: child process 11510 exited normally, status=255 Mar 26 20:38:55 sip-3-1 /usr/local/sbin/kamailio[11482]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD
I have not made any changes to the permissions/trusted module, so I suspect it is some shared database conection problem.
Is it a known bug in this version? I would prefer not to upgrade the installation and hopes one of you can point me to a patch I can backport.
Hi again,
A small update.
If I raise debug from debug=2 to debug=3 it starts every time.
And once about every 20 times I start kamailio it also runs fine.
On Wed, Mar 27, 2013 at 11:02 AM, Morten Isaksen misak@misak.dk wrote:
Hello,
very likely is related to:
- http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=97f788a3...
You should upgrade to latest in 3.1.x series, nothing needs to be changed in terms of configuration file or database. You install over the latest version in that branch.
Not recommended, but ultimately you can get only the patch. But if you apply the patches for the other fixed issues in the branch, you end up in latest version.
Cheers, Daniel
On 3/27/13 1:07 PM, Morten Isaksen wrote:
On 3/27/13 2:25 PM, Morten Isaksen wrote:
Look at the log in branch 3.1, there might be other related patches to the module done before this one.
Cheers, Daniel
I have tried backport the usrloc and permissions module from 3.1.6 but I get the same error. :(
I have just tried to backport commit d173cc2dab95dba6ededdaa352bf1e2bde1faa0f (srdb1: keep PID per DB connection) and so far it seems to work in the test enviroment.
/Morten
On Wed, Mar 27, 2013 at 2:49 PM, Morten Isaksen misak@misak.dk wrote:
On 4/2/13 11:34 PM, Morten Isaksen wrote:
Yes, that is related to the issue. I know there were a series of fixes at that time, so it is better to just move to latest stable in the series, as it guarantees the compatibility for database structure and configuration file.
Cheers, Daniel