Ok, so turns out it was to do with file permissions, there was no folder /root/home/ creating the folder fixed the issue, any help regarding using mod_vlc to stream out, I can't use mod_shout as I don't want to transcode.
Send FreeSWITCH-users mailing list submissions to
freeswitch-users@lists.freeswitch.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
or, via email, send a message with subject or body 'help' to
freeswitch-users-request@lists.freeswitch.org
You can reach the person managing the list at
freeswitch-users-owner@lists.freeswitch.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of FreeSWITCH-users digest..."
Today's Topics:
1. LUKE: I'm hit, but not bad - thread failure (Tim St. Pierre)
2. Re: LUKE: I'm hit, but not bad - thread failure (Tim St. Pierre)
3. Re: mod_conference auto-record issue (Seven Du)
4. PHP ESL timeout? (Tim St. Pierre)
5. Re: LUKE: I'm hit, but not bad - thread failure (Peter Olsson)
6. Re: LUKE: I'm hit, but not bad - thread failure (Anestis Mavro)
---------- Forwarded message ----------
From: "Tim St. Pierre" <fs-list@communicatefreely.net>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Cc:
Date: Thu, 10 Jan 2013 20:37:48 -0500
Subject: [Freeswitch-users] LUKE: I'm hit, but not bad - thread failure
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 2012-12-30 19:08:55Z
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 mind some suggestions as to what I should watch out for.
-Tim
---------- Forwarded message ----------
From: "Tim St. Pierre" <fs-list@communicatefreely.net>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Cc:
Date: Thu, 10 Jan 2013 20:44:49 -0500
Subject: Re: [Freeswitch-users] LUKE: I'm hit, but not bad - thread failure
Thought this might be helpful -
switch_core_session.c:1655 Thread Failure!
That's the actual error with the line of code.
Tim St. Pierre wrote:
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 2012-12-30 19:08:55Z
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 mind some suggestions as to what I should watch out for.
-Tim
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
---------- Forwarded message ----------
From: Seven Du <dujinfang@gmail.com>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Cc:
Date: Fri, 11 Jan 2013 09:46:12 +0800
Subject: Re: [Freeswitch-users] mod_conference auto-record issue
maybe check if you have the /root/home dir and is writable by the user running FreeSWITCH?On Friday, January 11, 2013 at 9:26 AM, Usama Zaidi wrote:
Hi,
Following in my conference profile:
<profile name="intPreConf" description="InterPre Phone Conference">
<!--param name="auto-record" value="#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128,deinterlace}: rtp{mux=ts,dst=192.168.1.8,port=5004,sdp=sap://,name=\"TestStream\"}" /-->Regards.
<param name="auto-record" value="/root/home/test.wav"/>
<param name="rate" value="8000"/>
<param name="member-flags" value="dist-dtmf"/>
<param name="energy-level" value="300"/>
<param name="caller-controls" value=""/>
</profile>
I'm having issues with auto-record, I keep getting these messages on the console:
2013-01-11 06:19:27.082662 [ERR] mod_conference.c:3884 Error Opening File [/root/home/test.wav]
2013-01-11 06:19:27.082662 [ERR] switch_core_timer.c:117 Timer is not properly configured.
And if I keep it running for a while, FS segfaults. I was trying recording to a stream initially, but then to narrow down the issue I tried recording to a file and got the same error. Please advise.
--
I'd love to change the world, but they wont gimme the source code to it_________________________________________________________________________Professional FreeSWITCH Consulting Services:FreeSWITCH-powered IP PBX: The CudaTel Communication ServerOfficial FreeSWITCH SitesFreeSWITCH-users mailing list
---------- Forwarded message ----------
From: "Tim St. Pierre" <fs-list@communicatefreely.net>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Cc:
Date: Thu, 10 Jan 2013 20:54:03 -0500
Subject: [Freeswitch-users] PHP ESL timeout?
Hello,
I currently have a testing system that opens an ESL connection to freeswitch to launch test calls, and also to make sure the switch is actually running as it should be.
If the switch is up, it works. If the switch is totally down, it works. If the switch is partially up, it doesn't work.
If the switch is up, but not really responsive, I am able to create a connection, but when I issue an API call, it sits there forever and doesn't return anything. If the API execute timed out and the script continued to execute, it would check the response, see that it is not what it should be, and alert the right people.
Anyone know this library that can help?
-Tim
---------- Forwarded message ----------
From: Peter Olsson <peter.olsson@visionutveckling.se>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Cc:
Date: Fri, 11 Jan 2013 06:40:29 +0000
Subject: Re: [Freeswitch-users] LUKE: I'm hit, but not bad - thread failure
Please report to JIRA.
/Peter
11 jan 2013 kl. 02:43 skrev "Tim St. Pierre" <fs-list@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 2012-12-30 19:08:55Z
> 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 mind some
> suggestions as to what I should watch out for.
>
> -Tim
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting@freeswitch.org
> http://www.freeswitchsolutions.com
>
> FreeSWITCH-powered IP PBX: The CudaTel Communication Server
> http://www.cudatel.com
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
> !DSPAM:50ef69f032762133211294!
>
---------- Forwarded message ----------
From: "Anestis Mavro" <devel@omninet.eu>
To: "'FreeSWITCH Users Help'" <freeswitch-users@lists.freeswitch.org>
Cc:
Date: Fri, 11 Jan 2013 09:22:07 +0200
Subject: Re: [Freeswitch-users] LUKE: I'm hit, but not bad - thread failure
Hello Peter,
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
gone.
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.
Good luck
-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Peter
Olsson
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.
/Peter
11 jan 2013 kl. 02:43 skrev "Tim St. Pierre"
<fs-list@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
2012-12-30 19:08:55Z
> 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
mind some
> suggestions as to what I should watch out for.
>
> -Tim
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting@freeswitch.org
> http://www.freeswitchsolutions.com
>
> FreeSWITCH-powered IP PBX: The CudaTel Communication Server
> http://www.cudatel.com
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
> !DSPAM:50ef69f032762133211294!
>
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org