[Freeswitch-users] LUKE: I'm hit, but not bad - thread failure
devel at omninet.eu
Fri Jan 11 10:22:07 MSK 2013
I faced a very similar (if not the same) situation a few weeks ago.
I had exactly the same behavior with the stable branch, but with the CPU
very very low. This is on CentOS (with a lot of cores and memory)
I went back to version 89e163a100 (November 11th, 2012) and the problem was
A few days ago I updated to master git 40cbc5c0e5 (January 4th, 2013) and
the problem doesn't exist anymore.
For me, it looks like there was something limiting the number of responses
from FS to the clients. (New configuration for ODBC was already done!)
I would try to upgrade to latest git.
From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Peter
Sent: Friday, January 11, 2013 8:40 AM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] LUKE: I'm hit, but not bad - thread failure
Please report to JIRA.
11 jan 2013 kl. 02:43 skrev "Tim St. Pierre"
<fs-list at communicatefreely.net>:
> Okay, so I have a bit more detail, and my first post hasn't posted yet.
> FreeSWITCH Version 1.3.13b+git~20121230T190855Z~8859eb0b23 (git 8859eb0
> FreeBSD 8.3-RELEASE
> I start getting thread_failures several times per second. It was so many
entries that the
> logs started turning over at about 10 minute intervals.
> A few minutes later, I get the above quotes from Star Wars.
> After an hour and a half of no phone service, someone finds my pager
number and I take a look.
> Our alarms didn't go off, because Freeswitch would still respond to
sockets, and it was
> still acknowledging SIP messages to a certain degree.
> fs_cli times out.
> Freeswitch is using 96% CPU and around 900MB of RAM. Earlier today, it
was 500MB, but I
> have seen it higher than that before. I have never seen it use more than
10% CPU on our
> little dual core Xeon machine. I probably should get more cores, but it
has never gone
> past 10% CPU usage.
> So I kill -9 Freeswitch, wait a few seconds, and start it up again.
Everything comes back
> after the phones re-register, but I would really like to know why, and how
to prevent it
> from happening again.
> This isn't an especially high call volume night, and I looked through the
logs - it
> started just after a new session was created for an outgoing call.
Nothing unusual about
> it. For a while after, I could still see SIP registrations in the logs,
but there weren't
> any SIP registrations in the database. The process to delete the expired
ones seems to
> have been working, but not the process to update them.
> This is essentially a forensic investigation at this point, but I wouldn't
> suggestions as to what I should watch out for.
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> Official FreeSWITCH Sites
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
Professional FreeSWITCH Consulting Services:
consulting at freeswitch.org
Official FreeSWITCH Sites
FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org
Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users