5 Dec
2019
5 Dec
'19
10:22 a.m.
Hi Henning,
Just this once on 5.2.5 vers. We had this running on 4.1.5 for many years
and did not see such behavior. Our QA group ran load tests to trigger
pike and could not reproduce this problem.
I guess I'll mark this as one off for now until we run into it again.
On Thu, Dec 5, 2019 at 3:36 AM Henning Westerholt <hw(a)skalatan.de> wrote:
Hello Andrew,
I don’t remember this; pike exists for a long time now and did not see any
big changes recently.
Do you see this problem frequently and/or can reproduce it? If yes,
consider opening a bug report with more details (e.g. logs) on our tracker.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
*From:* sr-users <sr-users-bounces(a)lists.kamailio.org> *On Behalf Of *Andrew
Chen
*Sent:* Wednesday, December 4, 2019 7:07 PM
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
*Subject:* [SR-Users] Pike module never release IP
Hi all,
Have anyone ever experienced pike module not releasing the IP after
"remove_latency" period?
We ran a load test and this is what happened to one of the two paired
nodes and I had to restart kamailio process to release it.
I'm running Kam 5.2.5
Thanks.
--
Andy Chen
Sr. Telephony Lead Engineer
achen@ <achen(a)thinkingphones.com>fuze.com
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
achen@ <achen(a)thinkingphones.com>fuze.com
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*