On 2/24/2010 3:16 PM, Scott Lawrence wrote:
>
> Open an issue and attach that file.
>
>
Done.
http://track.sipfoundry.org/browse/XX-7751
Thank you!
___
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/arc
On Wed, 2010-02-24 at 14:29 -0600, mkitchin.pub...@gmail.com wrote:
> On 2/24/2010 1:48 PM, Scott Lawrence wrote:
> >
> > I don't think so... seems the identification of the binary isn't quite
> > right.
> >
> > I think that if you do this, it will work:
> >
> > ln /usr/local/freeswitch/bi
On 2/24/2010 1:48 PM, Scott Lawrence wrote:
>
> I don't think so... seems the identification of the binary isn't quite
> right.
>
> I think that if you do this, it will work:
>
> ln /usr/local/freeswitch/bin/freeswitch /usr/bin
>
> and then retry that same sipx-snapshot command.
>
>
Go
On Wed, 2010-02-24 at 13:30 -0600, mkitchin.pub...@gmail.com wrote:
> On 2/24/2010 1:16 PM, Scott Lawrence wrote:
> > sipx-snapshot --core core.11264 --log-start '2010-02-24 18:35' --log-stop
> > '2010-02-24 18:45'
> >
> Done. I don't think it worked though..
> [r...@nshpbx1 sipxpbx]# sipx-sna
On 2/24/2010 1:16 PM, Scott Lawrence wrote:
> sipx-snapshot --core core.11264 --log-start '2010-02-24 18:35' --log-stop
> '2010-02-24 18:45'
>
Done. I don't think it worked though..
[r...@nshpbx1 sipxpbx]# sipx-snapshot --core core.11264 --log-start
'2010-02-24 18:25' --log-stop '2010-02-24 1
On Wed, 2010-02-24 at 12:58 -0600, mkitchin.pub...@gmail.com wrote:
> On 2/5/2010 6:58 PM, Scott Lawrence wrote:
> > Once the problem is detected, log in as root. Find the runaway process
> > pid; check to see if it's the same as the process id in the
> > file /var/run/sipxecs/freeswitch.pid (inte
On 2/5/2010 6:58 PM, Scott Lawrence wrote:
> Once the problem is detected, log in as root. Find the runaway process
> pid; check to see if it's the same as the process id in the
> file /var/run/sipxecs/freeswitch.pid (interesting if not), and then cill
> the process and note the time locally and i
Done, except I still don't know what 'sipXivr and the conference system'
are with respect to the loglevel settings. Freeswitch is Media services,
but you gave different loglevel settings for these 2 and I don't see
anything that corresponds to those names. I'm going to guess that
sipXivr is the
On Fri, 2010-02-05 at 22:24 -0600, mkitchin.pub...@gmail.com wrote:
> I don't see a loglevel setting for Freeswitch, sipXivr, or conference.
> Do they go by other names? Am I looking in the wrong place?
Sorry... Media Services
___
sipx-users mailing lis
I don't see a loglevel setting for Freeswitch, sipXivr, or conference.
Do they go by other names? Am I looking in the wrong place?
On 2/5/2010 6:58 PM, Scott Lawrence wrote:
I would set the logging on DEBUG for Freeswitch, INFO for the proxy,
registrar, sipXivr and the conference system,
On Fri, 2010-02-05 at 16:49 -0600, mkitchin.pub...@gmail.com wrote:
> On 2/5/2010 4:32 PM, Scott Lawrence wrote:
> > Agreed, but so far the only information we could put in an issue is
> > "sometimes freeswitch sucks up the entire cpu". We don't know what
> > configurations those systems have, or
On 2/5/2010 4:32 PM, Scott Lawrence wrote:
> Agreed, but so far the only information we could put in an issue is
> "sometimes freeswitch sucks up the entire cpu". We don't know what
> configurations those systems have, or what event triggers it. As one of
> the people that screens New issues, I c
On Fri, 2010-02-05 at 16:21 -0600, mkitchin.pub...@gmail.com wrote:
> I'm relatively new to sipx, but it would seem to me that there should
> be a sipx bug report opened on this. Am I missing something? Without
> some method of tracking it, does anyone that there is even a change in
> 4.2 that mig
On Fri, 2010-02-05 at 16:45 -0500, Matt White wrote:
> >>> On 2/4/2010 at 10:27 AM, in message
> , Tony Graziano
> wrote:
> > I don't think anything will go down. I think it's a stuck process.
> >
>
> Anybody make any head way with this. This has begun to occur on two
> of our installs. Loggi
I'm relatively new to sipx, but it would seem to me that there should be
a sipx bug report opened on this. Am I missing something? Without some
method of tracking it, does anyone that there is even a change in 4.2
that might fix this? Does the version of Freeswitch change? It isn't
going to be
I had posted some time ago to the dev list with no real replies. After
looking through my FS logs, I see errors marked CRIT which happen
sporadically throughout the day, and when the system boots up. The CRIT
errors on bootup signify a FS config error where some unneeded statements
should have been
On 2/5/2010 3:45 PM, Matt White wrote:
On 2/4/2010 at 10:27 AM, in message
> , Tony Graziano
> wrote:
>
>> I don't think anything will go down. I think it's a stuck process.
>>
>>
> Anybody make any head way with this. This has begun to occur on two of our
> instal
Welcome, you have hell. It's important to note that when you do this any
calls in progress will be lost.
On Fri, Feb 5, 2010 at 4:45 PM, Matt White wrote:
> >>> On 2/4/2010 at 10:27 AM, in message
> , Tony
> Graziano
> wrote:
> > I don't think anything will go down. I think it's a stuck process
>>> On 2/4/2010 at 10:27 AM, in message
, Tony Graziano
wrote:
> I don't think anything will go down. I think it's a stuck process.
>
Anybody make any head way with this. This has begun to occur on two of our
installs. Logging into the GUI and restarting "media services" clears it up
for a
Thanks. I had to kill the process this morning, and all is well now.
Next time it does it, I will start to troubleshoot.
On 2/4/2010 11:51 AM, Eric Varsanyi wrote:
A good way to find out what its burning CPU doing if the logs have no
useful info is to get a stack trace on all threads, several t
A good way to find out what its burning CPU doing if the logs have no useful
info is to get a stack trace on all threads, several times, then just look at
them and see what's going on. Even better is to use 'top's 'H' option to find
out which specific thread ID's are burning cpu and correlate th
I don't think anything will go down. I think it's a stuck process.
On Thu, Feb 4, 2010 at 10:11 AM, mkitchin.pub...@gmail.com <
mkitchin.pub...@gmail.com> wrote:
> If I kill that PID, do I need to restart anything, or should I expect
> anything to go down?
> I can't find anything in the freeswit
If I kill that PID, do I need to restart anything, or should I expect
anything to go down?
I can't find anything in the freeswitch logs.
On 2/4/2010 9:02 AM, Tony Graziano wrote:
You can "kill" the PID and buy a little time. The freeswitch logs
might tell you more. I used a "cpulimit" app I had
You can "kill" the PID and buy a little time. The freeswitch logs might tell
you more. I used a "cpulimit" app I had to compile on the system to limit FS
to a certain percentage, but that's not ideal because there end up being
timing and audio issues as a result.
I feel, and I might be wrong, that
Rebooted last night, and it started up again a little while ago. I'm
already at about 200% processor utilization. This looks like it could be
a disaster for me.
I've take a snapshot of the logs to preserve any evidence that might be
there.
Cpu0 : 98.3%us, 0.7%sy, 0.0%ni, 0.0%id, 0.0%wa,
://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: sipx-users@list.sipfoundry.org
Sent: Wed Feb 03 18:35:39 2010
Subject: Re: [sipx-users] Freeswitch processor usage
After reading a post today that mentioned size limits in posts, I
realized these
After reading a post today that mentioned size limits in posts, I
realized these posts never made it through because it had 2 screenshots.
I have removed the pictures and am resending.
Any help would be greatly appreciated!
On 2/3/2010 12:05 PM, mkitchin.pub...@gmail.com wrote:
I rebooted last
27 matches
Mail list logo
