Hello Bogdan,
Possible it releated to issue
https://github.com/OpenSIPS/opensips/issues/1443
We use PgSQL too.
volga629
On Thu, Aug 16, 2018 at 1:12 AM, volga...@networklab.ca wrote:
Hello Bogdan,
I was monitoring and trasfered config to dev machine where 0 load or
connection and it look
Hello Bogdan,
I was monitoring and trasfered config to dev machine where 0 load or
connection and it look like some sort of mini crash, but I can't tell
100%.
Here are log, the first line mean INVITE 200 OK reply then all those
messages start showing up and 200 OK never reach end point.
Aug
Hi Volga,
The logs report a serious heavy execution of certain timer routines in
OpenSIPS, like the presence cleanup takes more than 191 secsmost
probably due long lasting DB queries ??? or because of heavy load in
OpenSIPS that leads to starvation in handling the timer jobs - what is
Hello Bogdan,
I checked database connection and it looks normal ping less then sec to
database.
I monitored load on database nodes and didn't notcied any extra load on
them.
Right now I see 2 types of messages on all cluster nodes.
Jun 30 22:56:45 aitossbc01 /usr/sbin/opensips[20245]:
Hi Volga,
How large is the presentity data set in your system ? I'm asking as the
routine that seems to be slow queries the presentity table in order to
get the expired presentities - this is done with or without clustering.
Still, in clustering, all the nodes are doing this query, putting
Hi Slava,
What is the presence clustering configuration you have here ? also, what
is the DB setup in regards to the cluster ?
Also, did you start getting those errors only after enabling the
clustering support? have you run an opensips individual presence node to
see if you still get them
