[Serusers] Memory leak?

[Jamin W. Collins]

On Tue, May 27, 2003 at 07:34:10PM +0200, Andrei Pelinescu-Onciul wrote:
> On May 27, 2003 at 11:16, Jamin W. Collins <jcollins at asgardsrealm.net> wrote:
> 
> > I'm not sure which log you are referring to.  The server itself has been
> > rebooted by the customer to return functionality.  I found the errors
> > after the fact.
> 
> Look in the log for lines conatining: "qm_status" , "heap size=", 
> "dumping all allocked. fragments:". They should appear before ser
> shutdown.

Nothing like that in the syslog or any other log that I can find.  There
are errors in the logs from SER right up to just prior to the reboot:

May 27 09:41:02 hillcrest /usr/sbin/ser[8258]: process_ins_list(): Error
while deleting from database
May 27 09:41:02 hillcrest ntpd[269]: ntpd exiting on signal 15
May 27 09:41:04 hillcrest kernel: Kernel logging (proc) stopped.
May 27 09:41:04 hillcrest kernel: Kernel log daemon terminating.
May 27 09:41:04 hillcrest exiting on signal 15
May 27 09:41:51 hillcrest syslogd 1.4.1#10: restart.

> > Is the local memory allocated per listening process (as reported by
> > 'ps') or per child process (as configured in ser.cfg) or based on
> > something else?  Just trying to get a grasp on how much the change will
> > effect the memory usage in my environment. 
> 
> per listening process ( total no. of processes = child_no *
>  no_of_listening_addresses + 3).

So, with a child_no of 4 and 1 IP listed for listening, I'm looking at 8
listening processes or ~8 Megs of local memory allocated to SER?

> > Also how much shared memory does SER allocate by default?  Would
> > increasing this number possibly help?
> 
> 32 Mb. In this case it will not help since this is not shared mem. The
> shared mem. runs out (usually :-)) when ser is in statefull mode (tm is
> used for forwarding) and a lot of calls are handled almost
> simultaneously (within sip expire time limits). This also depends on the
> CPU power (if the machine can handle only 100 cps due to cpu limits you
> will never exceed the default 32 Mb). On a dual athlon 2000+ which can
> handle ~4900 cps, 256 Mb are enough (ser -m 256).

The system is a 1.1 Ghz Celeron with 128 Megs and SER's it's only
function.  So, if I'm following correctly, it might be a good idea to
increase the share memory a bit, but the local memory would help more?

-- 
Jamin W. Collins

This is the typical unix way of doing things: you string together lots
of very specific tools to accomplish larger tasks. -- Vineet Kumar