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 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 this is a FS bug which has been dealt with, but there's no way around it in 4.0.4 right now.

On Thu, Feb 4, 2010 at 9:58 AM, mkitchin.pub...@gmail.com <mailto:mkitchin.pub...@gmail.com> <mkitchin.pub...@gmail.com <mailto:mkitchin.pub...@gmail.com>> wrote:

    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, 0.0%hi, 1.0%si, 0.0%st Cpu1 : 99.7%us, 0.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
    Mem:   8177104k total,  3057448k used,  5119656k free,   138992k
    buffers
    Swap: 10223608k total,        0k used, 10223608k free,  1730152k
    cached


      PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
     3719 sipxchan  18   0  298m  46m 4888 S 196.7  0.6 273:22.00
    freeswitch
     3915 sipxchan  21   0 1438m 113m 9068 S  1.3  1.4   1:18.14 java

    [r...@nshpbx1 sipxpbx]# ps aux |grep "3719"
    root       790  0.0  0.0  61156   724 pts/0    S+   08:58   0:00
    grep 3719
    500       3719 35.0  0.5 305748 47672 ?        Sl   Feb03 280:04
    /usr/local/freeswitch/bin/freeswitch -conf
    /etc/sipxpbx/freeswitch/conf -db /var/sipxdata/tmp/freeswitch -log
    /var/log/sipxpbx -htdocs /etc/sipxpbx/freeswitch/conf/htdocs -nc
    -nf -nosql




    On 2/3/2010 5:35 PM, mkitchin.pub...@gmail.com
    <mailto:mkitchin.pub...@gmail.com> wrote:
    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
    <mailto:mkitchin.pub...@gmail.com> wrote:
    I rebooted last night to resolve the problem. It just started
    happening again.

    It looks like there was a bug report briefly open about
    something similar:
    http://track.sipfoundry.org/browse/XX-5881

    Any ideas on this one? I will gladly provide any info that would
    help.

Cpu0 : 12.0%us, 1.3%sy, 0.0%ni, 85.4%id, 0.0%wa, 0.0%hi, 1.3%si, 0.0%st Cpu1 : 92.0%us, 0.3%sy, 0.0%ni, 7.6%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
    Mem:   8177104k total,  2425588k used,  5751516k free,   152772k
    buffers
    Swap: 10223608k total,        0k used, 10223608k free,  1017704k
    cached

    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
    13533 sipxchan  18   0  281m  33m 4944 S 99.5  0.4  25:31.50
    freeswitch

    [r...@nshpbx1 sipxpbx]# ps aux |grep "13533"
    500      13533  2.9  0.4 288392 34092 pts/0    Sl   Feb02  26:32
    /usr/local/freeswitch/bin/freeswitch -conf
    /etc/sipxpbx/freeswitch/conf -db /var/sipxdata/tmp/freeswitch
    -log /var/log/sipxpbx -htdocs
    /etc/sipxpbx/freeswitch/conf/htdocs -nc -nf -nosql

    I see others with the same issue:
    http://list.sipfoundry.org/archive/sipx-dev/msg21612.html
    I am not subscribed to the dev list. I don't think I could
    contribute too much. the discussion on this one seems to have
    died off. It would seem to me this is a pretty significant problem.


    On 2/2/2010 12:55 PM, mkitchin.pub...@gmail.com
    <mailto:mkitchin.pub...@gmail.com> wrote:
    I know there is a similar thread about this, but it was a
    little different and I didn't want to hijack it.
    http://list.sipfoundry.org/archive/sipx-users/msg21074.html

    A freeswitch process has started using a large amount of CPU
    on my server. I can't see any obvious reason why.

    Tasks: 151 total,   1 running, 150 sleeping,   0 stopped,   0
    zombie
Cpu0 : 50.2%us, 0.3%sy, 0.0%ni, 48.8%id, 0.0%wa, 0.3%hi, 0.3%si, 0.0%st Cpu1 : 53.0%us, 0.3%sy, 0.0%ni, 46.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 8177104k total, 2887232k used, 5289872k free, 183680k buffers Swap: 10223608k total, 0k used, 10223608k free, 1232760k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
     3811 sipxchan  18   0  296m  49m 4944 S 97.8  0.6   1133:41
    freeswitch
     3591 sipxchan  18   0 1541m 403m  11m S  1.3  5.1  38:52.22 java
     3946 sipxchan  18   0 1418m 197m 9100 S  1.3  2.5  25:33.71 java
     3922 sipxchan  19   0 1379m 196m 9184 S  1.0  2.5   8:33.80 java
    10359 postgres  15   0  121m  13m  10m S  1.0  0.2   2:49.72
    postmaster

    This may provide some details as to what the process is doing:
    [r...@nshpbx1 sipxpbx]# ps aux |grep "freeswitch"
    500       3811 13.9  0.6 303420 50768 ?        Sl   Jan27
    1134:08 /usr/local/freeswitch/bin/freeswitch -conf
    /etc/sipxpbx/freeswitch/conf -db /var/sipxdata/tmp/freeswitch
    -log /var/log/sipxpbx -htdocs
    /etc/sipxpbx/freeswitch/conf/htdocs -nc -nf -nosql

    Local CPU monitoring seems to have died shortly after it
    registered the spike in CPU.
    <removed - picture of sipx SPU stats showing CPU stat
    collection died>

    Remote monitoring is still recording the high CPU utilization:
    <removed - picture of zenoss showing CPU uake went way up and
    stayed up>

    I only have 1 warning entry in freeswitch.log from yesterday,
    and none from today.
    2010-02-01 07:52:10 [WARNING] switch_core_file.c:119
    switch_core_perform_file_open() Sample rate doesn't match

    I only have a few active calls right now, and none active for
    more than an hour.

    Anyone have any idea what might be causing this?

    CentOS 5.4 64 Bit, Sipx 4.0.4, sixbridge, Verizon VOIP, No
    firewall (not needed, private connection), Polycom 450s and
    550s - bootrom 4.2.1, firmware 3.1.3C split.

    Thanks as always,
    Matthew









    _______________________________________________
    sipx-users mailing list sipx-users@list.sipfoundry.org
    <mailto:sipx-users@list.sipfoundry.org>
    List Archive: http://list.sipfoundry.org/archive/sipx-users
    Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
    sipXecs IP PBX -- http://www.sipfoundry.org/




--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net <mailto:tgrazi...@myitdepartment.net>

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.


_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to