WARNING: <core> [db_id.c:281]: identical DB URLs, but different DB connection pid [30123/30107]
Any idea what does it mean? Where does it come from? Do I have to change my config? How?
WARNING: <core> [db_id.c:281]: identical DB URLs, but different DB connection pid [30123/30107]
Thanks Klaus
On Friday 04 March 2011, Klaus Darilion wrote:
Any idea what does it mean? Where does it come from? Do I have to change my config? How?
WARNING: <core> [db_id.c:281]: identical DB URLs, but different DB connection pid [30123/30107]
Hi Klaus,
its related to this change:
commit f138cce2c0968872f26538983e06a128a1b41344 Author: Daniel-Constantin Mierla miconda@gmail.com Date: Wed Dec 1 23:30:34 2010 +0100
srdb1: keep PID per DB connection
- print warning when PID mismatches - it is cross-process shared DB connection - initial patch by Robert Verspuy
By searching for Robert you should be able to find the initial discussion of this problem, i guess.
Cheers,
Henning
On Friday 04 March 2011, Henning Westerholt wrote:
By searching for Robert you should be able to find the initial discussion of this problem, i guess.
[sr-dev] invalid type (3) or nul (0) version columns for trusted (kamailio 3.1 latest from git)
This was it.
Henning
Op 04-03-11 15:43, Henning Westerholt schreef:
On Friday 04 March 2011, Henning Westerholt wrote:
By searching for Robert you should be able to find the initial discussion of this problem, i guess.
[sr-dev] invalid type (3) or nul (0) version columns for trusted (kamailio 3.1 latest from git)
See the thread here: http://lists.sip-router.org/pipermail/sr-dev/2010-October/009545.html
With kind regards, Robert Verspuy
Hi Robert!
Am 04.03.2011 15:49, schrieb Robert Verspuy:
Op 04-03-11 15:43, Henning Westerholt schreef:
On Friday 04 March 2011, Henning Westerholt wrote:
By searching for Robert you should be able to find the initial discussion of this problem, i guess.
[sr-dev] invalid type (3) or nul (0) version columns for trusted (kamailio 3.1 latest from git)
See the thread here: http://lists.sip-router.org/pipermail/sr-dev/2010-October/009545.html
So, when it is fixed, why printing a WARNING? Is it something I have to be aware of? I use mysql with 3 modules doing DB lookups. I get this warning 3 times.
Since ever usually most modules use the same db_url. So I am confused.
If there isn't a problem anymore we should change the WARNING to an DBG.
regards Klaus
Op 04-03-11 16:05, Klaus Darilion schreef:
Hi Robert!
See the thread here: http://lists.sip-router.org/pipermail/sr-dev/2010-October/009545.html
So, when it is fixed, why printing a WARNING? Is it something I have to be aware of? I use mysql with 3 modules doing DB lookups. I get this warning 3 times.
Since ever usually most modules use the same db_url. So I am confused.
If there isn't a problem anymore we should change the WARNING to an DBG.
You really have to ask that to Daniel-Constantin Mierla. See his answer on my patch on http://lists.sip-router.org/pipermail/sr-dev/2010-November/009866.html
So I guess the warning means the module is doing some kind of incorrect DB initialization ?? I don't know what the correct way is, I'm not a openser / kamailio developer. I just started using Kamailio in september 2010, found an issue, and made a patch.
With kind regards, Robert Verspuy
regards Klaus
Klaus Darilion writes:
So, when it is fixed, why printing a WARNING? Is it something I have to be aware of? I use mysql with 3 modules doing DB lookups. I get this warning 3 times.
Since ever usually most modules use the same db_url. So I am confused.
If there isn't a problem anymore we should change the WARNING to an DBG.
i agree with klaus. if a module does not use db correctly, it needs to be fixed. otherwise, please change log level to debug.
-- juha
On 3/4/11 8:59 PM, Juha Heinanen wrote:
Klaus Darilion writes:
So, when it is fixed, why printing a WARNING? Is it something I have to be aware of? I use mysql with 3 modules doing DB lookups. I get this warning 3 times.
Since ever usually most modules use the same db_url. So I am confused.
If there isn't a problem anymore we should change the WARNING to an DBG.
i agree with klaus. if a module does not use db correctly, it needs to be fixed. otherwise, please change log level to debug.
I will change that. The warning is fully harmless, but I let it for a while just to be sure is all fine. The update done could have caused kamailio not to start if some module would do some extra internal checks over the existence of db connection -- the warning would give a clear indication about what could be the issue in such case.
Cheers, Daniel
-
Daniel-Constantin Mierla -
Henning Westerholt -
Juha Heinanen -
Klaus Darilion -
Robert Verspuy