Hi,
maybe this has been discussed before and maybe I'm not too good in
reading mailinglists, but anyhow.
If you have two OpenSER proxies storing to the same
location table.
I see in my logs: WARNING:usrloc:dbrow2info: non-local socket @of other server:5060 ...ignoring,
I have a probleme with my DB when i register some UA.
This is crucial?
If this is not crucial, might this message be supressed in some way?
Thanks,
On Thursday 27 November 2008, ALAEDDINE abbech wrote:
If you have two OpenSER proxies storing to the same location table.
I see in my logs: WARNING:usrloc:dbrow2info: non-local socket @of other server:5060 ...ignoring,
Hi ALAEDDINE,
i think you get this warning every time if you register from a different machine then the proxy that finally reads the entry back.
I have a probleme with my DB when i register some UA.
Do you've another problem, or is this the only issue you observed?
This is crucial? If this is not crucial, might this message be supressed in some way?
I don't think its critical, you can just increase the log level to supress this warning, or edit the code and modify the log level of this warning message (this is what we did).
Cheers,
Henning
i have an other problem, when i look the users online in the first server(openserctl online) i show many users register in the other server.
--- En date de : Jeu 27.11.08, Henning Westerholt henning.westerholt@1und1.de a écrit : De: Henning Westerholt henning.westerholt@1und1.de Objet: Re: [Kamailio-Users] WARNING dbrow2info: non-local socket À: users@lists.kamailio.org, alasupcom@yahoo.fr Date: Jeudi 27 Novembre 2008, 12h50
On Thursday 27 November 2008, ALAEDDINE abbech wrote:
If you have two OpenSER proxies storing to the same location table.
I see in my logs: WARNING:usrloc:dbrow2info: non-local socket @of other server:5060 ...ignoring,
Hi ALAEDDINE,
i think you get this warning every time if you register from a different machine then the proxy that finally reads the entry back.
I have a probleme with my DB when i register some UA.
Do you've another problem, or is this the only issue you observed?
This is crucial? If this is not crucial, might this message be supressed in some way?
I don't think its critical, you can just increase the log level to supress this warning, or edit the code and modify the log level of this warning message (this is what we did).
Cheers,
Henning
On Thursday 27 November 2008, ALAEDDINE abbech wrote:
i have an other problem, when i look the users online in the first server(openserctl online) i show many users register in the other server. [..]
Hi ALAEDDINE,
well, what else do you expect if you let use both OpenSERs use the same DB?
Cheers,
Henning