Maybe this shows more detail

top - 12:53:10 up 4 days, 33 min,  1 user,  load average: 0.27, 0.47, 0.48
Tasks: 142 total,   1 running, 141 sleeping,   0 stopped,   0 zombie
Cpu0 : 2.7%us, 0.3%sy, 0.0%ni, 97.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 4.3%us, 1.0%sy, 0.0%ni, 93.6%id, 0.0%wa, 0.0%hi, 1.0%si, 0.0%st
Mem:   8177072k total,  6986228k used,  1190844k free,   350988k buffers
Swap:  6289436k total,        0k used,  6289436k free,  4970784k cached

  PID      USER     PR   NI  VIRT    RES SHR S   %CPU %MEM TIME+  COMMAND
 7785 sipxchan  18   0 2486m 309m  12m S  0.0  3.9  26:17.15 java
 4962 sipxchan  19   0 2358m 289m 9872 S  2.0  3.6  12:15.95 java
 4623 sipxchan  18   0 2333m 154m 9720 S  0.0  1.9   0:05.07 java
 4815 sipxchan  19   0 2357m 133m 9808 S  0.0  1.7   3:09.91 java
 5102 sipxchan  19   0 2332m  89m 9780 S  2.3  1.1  47:29.12 java
 9231 sipxchan  15   0  347m  75m 5616 S  2.3  0.9  20:50.91 sipXproxy
 5033 sipxchan  18   0 2326m  74m  11m S  0.0  0.9   0:02.27 java
 3876 sipxchan  25   0 2320m  60m 9488 S  0.0  0.8   0:02.31 java



On 9/30/2010 12:51 PM, Matthew Kitchin (public/usenet) wrote:
You are doing better (or worse) than me :)

[r...@nshpbx1 ~]# top -b |grep 18 |grep java
 4623 sipxchan  18   0 2333m 154m 9720 S  0.0  1.9   0:05.06 java
 5033 sipxchan  18   0 2326m  74m  11m S  0.0  0.9   0:02.27 java
 7785 sipxchan  18   0 2486m 285m  12m S  0.0  3.6  26:08.46 java


On 9/30/2010 12:31 PM, Michael Scheidell wrote:

old issue, but just to keep it on the forefront: ie: why you need a 64bit build? so you can put in 32GB ram to keep java happy


top -b | grep java
 3323 sipxchan  18   0  190m  26m 6624 S  0.0  2.7   2:07.26 java
 3474 sipxchan  18   0  186m  19m 6512 S  0.0  1.9   0:04.23 java
 3800 sipxchan  18   0  194m  35m 6684 S  0.0  3.6   0:36.79 java
 3822 sipxchan  18   0  193m  30m 8844 S  0.0  3.0   0:05.29 java
 3957 sipxchan  18   0  185m  18m 6508 S  0.0  1.8   0:02.87 java
 5942 sipxchan  18   0  216m  91m 9388 S  0.0  9.1   0:22.40 java
16950 sipxchan  18   0  195m  37m 6736 S  0.0  3.7   1:54.75 java
16966 sipxchan  18   0  224m  51m 8152 S  0.0  5.1   4:17.63 java

that's 1.5GB just for java?


On 8/18/10 9:44 AM, Matthew Kitchin (public/usenet) wrote:
This is exactly what I use successfully.
sipxproc --restart ConfigServer

On 8/18/2010 8:41 AM, Michael Scheidell wrote:
tried:
sipxproc -r ConfigServer
sipxproc -r configserver

both get me:

Usage: /usr/bin/sipxproc parameters

Interface with the sipXpbx watchdog monitored process XMLRPC interface.

  Parameters:
  -h|--help           This help text
-n|--host hostname Remote server, e.g. HA slave (default is localhost)
  -p|--port portnum   Server port (default is 8092)
  -s|--start          Start the specified monitored process
  -k|--stop           Stop the specified monitored process
  -r|--restart        Restart the specified monitored process
  -l|--state          Current state of all monitored processes
-m|--getStatusMessages Display output from the specified service -c|--getConfigVersion Get the configuration version of the specified service -u|--setConfigVersion Set the configuration version of the specified service
  -v|--serviceVersion The service version value to update
  -f|--file           Get the named file
  -d|--delete         Delete the named file
-t|--runConfigtest Run the configtest for the specified service --getConfigtestMessages Return messages from the configtest for the specified service -S|--snapshot Execute snapshot on a local/remote system. Snapshot arguments may be specified after an empty option -- (two minus symbols) e.g. sipxproc --snapshot -- --snapshot_arg_1 x --snapshot_arg_2 y -E|--execStatus Returns the execution status of any of the following commands : snapshot, checkUpdate, checkSwVersion, updateSwVersion
  -C|--checkUpdate      Check for Software Updates
  -V|--checkSwVersion   Check Software Version
  -U|--updateSwVersion  Update Software
  -R|--restartSipXecs   Restart the SipXecs services
  -B|--rebootSystem     Reboot the system


On 8/12/10 3:04 PM, Josh M. Patten wrote:

From the linux shell, run:

Sipxproc --r ConfigServer

This will restart just the config server. It will not cause any calls to drop.


--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
> *| *SECNAP Network Security Corporation

    * Certified SNORT Integrator
    * 2008-9 Hot Company Award Winner, World Executive Alliance
    * Five-Star Partner Program 2009, VARBusiness
    * Best in Email Security,2010: Network Products Guide
    * King of Spam Filters, SC Magazine 2008


------------------------------------------------------------------------

This email has been scanned and certified safe by SpammerTrap®.
For Information please see http://www.secnap.com/products/spammertrap/

------------------------------------------------------------------------


_______________________________________________
sipx-users mailing list
[email protected]
List Archive:http://list.sipfoundry.org/archive/sipx-users/


--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
> *| *SECNAP Network Security Corporation

    * Certified SNORT Integrator
    * 2008-9 Hot Company Award Winner, World Executive Alliance
    * Five-Star Partner Program 2009, VARBusiness
    * Best in Email Security,2010: Network Products Guide
    * King of Spam Filters, SC Magazine 2008


------------------------------------------------------------------------

This email has been scanned and certified safe by SpammerTrap®.
For Information please see http://www.secnap.com/products/spammertrap/

------------------------------------------------------------------------


_______________________________________________
sipx-users mailing list
[email protected]
List Archive:http://list.sipfoundry.org/archive/sipx-users/


_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to