Bret,
try:
ps aux --forest | grep opensips
that will show you parent and child processes in tree diagram and if any
opensips master process is actually responsible for so many of them.
I agree that it is probably being spawned many times with a cron job, loop
in the init script or a service like
On Wed, 2011-05-04 at 07:30 -0700, Dave Singer wrote:
Bret,
try:
ps aux --forest | grep opensips
that will show you parent and child processes in tree diagram and if
any opensips master process is actually responsible for so many of
them.
I agree that it is probably being spawned many
I am seeing an ever increasing number of processes in opensips (from
under 10 at launch to over 1000 after a few hours). How can
I tell where those processes are (apparently) blocking and not exiting
like they should?
--
Trixter aka Bret McDanel
website: http://www.0xdecafbad.com
pgp key:
Hello,
This is strange. You could do
scripts/opensipsctl fifo ps
and paste the name of the repeating processes here. You could also choose one
of the pids of those stuck processes and attach via gdb :
gdb path-to-opensips-binary pid
and also reply with a backtrace.
Regards,
Bret
You can get a little more information on those processes with:
opensipsctl ps
The output of that command would likely be useful in troubleshooting
-Brett
But 1000 sounds like way too many
On Apr 30, 2011, at 5:53 AM, Bret McDanel trix...@0xdecafbad.com wrote:
I am seeing an ever increasing
On 30 April 2011 19:22, Bret McDanel trix...@0xdecafbad.com wrote:
gdb it is, the fifo ps command returns the same data despite the fact
that my process table continues to fill and those processes wont die
without a sigkill. I was trying to avoid that because I was thinking it
was a simple
On Sat, 2011-04-30 at 19:37 +0100, Stanisław Pitucha wrote:
You mean that fifo ps returns a low number of processes? How are you
starting up opensips? What kind of scripts / process management are
you using?
I would guess that something you use to start up opensips is not
working as you
