Hi Dave,
Here is the patch - I hope it will provide you with some clues on your
problem.
Regards,
Bogdan
Dave Singer wrote:
Thanks for the reply.
I would also lean to the DB as the problem but I have also experienced
it with about the same frequency when not using any database modules
and
Thanks for the reply.
I would also lean to the DB as the problem but I have also experienced it
with about the same frequency when not using any database modules and low or
now calls.
So if you could point me to the patch you refereed to I would appreciate it.
I'll then run it through a scripted p
Hi Dave,
At sthutdown, opensips modules are mainly doing memory cleanup (dialog,
transactions, caches, etc) or data flush to DB (dialogs, usrloc, etc).
As memory cleanup is predictable as time and not resource consuming, I
would say it is something related to DB flush - some DB ops that take
r
Hi Dave,
Your email did go through - if you do not receive any auto-reply , is
ok. You can also check the mailing list achive
(http://lists.opensips.org/pipermail/users/).
About getting an answer - you have to understand that this is a free
project and also the help you get is for free, so the
If this goes through to everyone on the list just ignore the paragraph below
and look at the meat of the problem below it in the forward.
This is/was my first post so I'm not sure exactly sure how things work. It
has been a few days and I haven't seen it come out among the other emails
from the li
Sometimes when I'm do a restart on opensips (using init.d script, with some
customization to handle this problem) opensips takes quite a bit of time,
like 30 - 50 seconds to stop. Other times it is very quick. I'm using 1.6.2
and 1.6.3.
The servers are fairly busy, less then 200 calls per sec, with
