On Jun 25, 2004 at 00:30, Jiri Kuthan
<jiri(a)iptel.org> wrote:
Under normal operation, SER can handle
significantly more registrations, by
orders of magnitude. To me, it sounds much more like a result of a memory leak.
Jiri, note that this happens on startup. In fact it runs out of mem.
oh thanks -- I misread. -jiri
when it tries to alloc. a chunk of memory big enough to
hold all the
entries in location. This is not a memory leak and it really happens if
PKG_MEM_POOL_SIZE is 1Mb and you have >6000 entries in location (it
depends of course on your average entry size, but the critical point is
in general between 6000-7000).
Are you using stock SER or some modified SER? In
any case, the way to catch such
leaks is to set a talkative memory log level (memlog=2 in ser.cfg), recompile ser
with memory debugging informaiton (uncomment DBG_QM_MALLOC, comment F_MALLOC
in Makefile.defs and do recompile completely) and watch log output on SER shutdown
for excessive occurent of unallocated memory fragement. I would be very thankful
if you could report your observations back to us.
-jiri
At 12:54 PM 6/24/2004, Andreas Granig wrote:
>Andrei Pelinescu-Onciul wrote:
>>On Jun 21, 2004 at 19:47, Atle Samuelsen <clona(a)cyberhouse.no> wrote:
>>
>>>Some more update.. got the same problem today.. and when it happend, ser
>>>blocked. and I got ALOT of these error messages. Anybody know why ?
>>
>>Ser runs out of "local" memory. The localtions are first loaded in
local
>>(per process memory) and copied and inserted in the usrloc shared memory
>>list. (probably you have a lot of entries)
>>By default ser uses maximum 1Mb of local memory/process. Try to
>>increases it to a bigger value. Change PKG_MEM_POOL_SIZE in config.h and
recompile.
>
>D'oh, same problem again here now (Ser 0.8.12)!
>
>It started with log entries like this:
>
>Jun 24 11:55:54 voip /usr/local/ser/sbin/ser[16801]: ERROR:
build_req_buf_from_sip_req: out of memory
>Jun 24 11:55:54 voip /usr/local/ser/sbin/ser[16801]: ERROR: print_uac_request: no
pkg_mem
>Jun 24 11:55:54 voip /usr/local/ser/sbin/ser[16801]: ERROR: t_forward_nonack: failure
to add branches
This could be a mem. leak (but this is unrelated to the startup
problem).
>
>I thought that maybe a restart could help, but SER didn't come up again,
shouting:
>
>Jun 24 12:01:02 voip /usr/local/ser/sbin/ser[19117]: convert_row(): No memory left
>Jun 24 12:01:02 voip /usr/local/ser/sbin/ser[19117]: convert_rows(): Error while
converting row #6346
>Jun 24 12:01:02 voip /usr/local/ser/sbin/ser[19117]: convert_result(): Error while
converting rows
>Jun 24 12:01:02 voip /usr/local/ser/sbin/ser[19117]: get_result(): Error while
converting result
>Jun 24 12:01:02 voip /usr/local/ser/sbin/ser[19117]: preload_udomain(): Error while
doing db_query
>Jun 24 12:01:02 voip /usr/local/ser/sbin/ser[19117]: register_udomain(): Error while
preloading domain 'location'
>Jun 24 12:01:02 voip /usr/local/ser/sbin/ser[19117]: domain_fixup(): Error while
registering domain
>
>After deleting 100 entries from location it came up again. Hope that the increase of
PKG_MEM_POOL_SIZE to 2MB helps.
>
>So it seems that after about 6300 entries or so in location Ser stops working with
the default configuration!? I'd be interested in how many users do other Ser-Servers
out there serve? Are there similiar problems?
>
>Regards,
>Andy
>
Andrei