AW: AW: [Serusers] No mem for sip_msg

Peter Herre nospam at inconsult.at
Thu Aug 26 00:07:59 CEST 2004


Hi Jiri,

enclosed find the requested files:
a new ser log file with the ser.cfg file.

I set the parameter "fork=no".
I could not set "fork==1" or "fork=1" as requested.

The result is that ser cannot correctly start,
i.e. "sertctl start" hangs at the following log file
position ("serctl start" does not come back to the
command line):

2(9767) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...

After pressing CTRL-C ser shuts down and frees memory.

This effect only happens with "fork=no".
With "fork=yes" I receive one ser process starting all
the required child processes.


Best regards,
Peter

-----Ursprungliche Nachricht-----
Von: Jiri Kuthan [mailto:jiri at iptel.org]
Gesendet: Mittwoch, 25. August 2004 19:37
An: Peter Herre; serusers at lists.iptel.org
Betreff: Re: AW: [Serusers] No mem for sip_msg


Unfortunately I have no idea what the cause can be (at least not
yet). It is very surprising that one of very first pkg_malloc
called fails. Perhaps an error in the database or the database
reader that causes some insane huge memory waste?

What is the logs in the case that SER does not start with
fork==1?

If that does not give us any clues, you will have to recompile
in memory debugging mode, set debugging level high and we will
then have to review what happens during allocations.

Thanks for reporting.

-jiri

At 02:56 PM 8/25/2004, Peter Herre wrote:
>Hi Jiri,
>
>thank you for your quick reply.
>
>The mentioned error occurs after each single SIP message,
>even right after starting ser.
>
>There is no load on the SIP server, there is just one SIP
>user who wants to log on SER by sending the appropriate
>request.
>
>This request works fine with my SER, as long as I leave
>database access disabled. As soon as I enable database
>access, the mentioned error occurs.
>
>More detailed information follows:
>
>operating system:
>=================
>Linux voip 2.6.5-7.104-default #1 Wed Jul 28 16:42:13 UTC 2004
>i686 athlon i386 GNU/Linux
>
>ser distribution:
>=================
>ser-0.8.14_src.tar.gz
>
>modified config.h file:
>
>/*used only if PKG_MALLOC is defined*/
>#define PKG_MEM_POOL_SIZE 10240*1024
>
>/*used if SH_MEM is defined*/
>#define SHM_MEM_SIZE 64
>
>ser build:
>==========
>version:  0.8.14 (i386/linux)
>flags: STATS:Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, DNS_IP_HACK, SHM_MEM,
>SHM_MM
>AP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
>ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
>MAX_URI_SI
>ZE 1024, BUF_SIZE 65535
>@(#) $Id: main.c,v 1.168.4.3 2004/06/28 15:41:21 andrei Exp $
>main.c compiled on 23:59:48 Aug 24 2004 with gcc 3.3
>
>ser config file:
>================
>see enclosed ser.cfg
>
>ser log file at loglevel 8:
>===========================
>see enclosed ser.log
>
>However, it is worth mentioning that my ser cannot be started if the
ser.cfg
>parameter "fork" is set to "no": The ser process starts and immediately
>after
>the start it closes itself at that point where usually the child processes
>are started in a "fork=yes" scenario.
>
>
>Best regards,
>Peter
>
>
>
>-----Ursprungliche Nachricht-----
>Von: Jiri Kuthan [mailto:jiri at iptel.org]
>Gesendet: Mittwoch, 25. August 2004 14:28
>An: Peter Herre; serusers at lists.iptel.org
>Betreff: Re: [Serusers] No mem for sip_msg
>
>
>At 11:57 AM 8/25/2004, Peter Herre wrote:
>>Dear ser users,
>>
>>I have a similar problem like Joseph Rork:
>>
>>I have ser 0.8.14 with mysql 4.0.
>>
>>Without DB access, ser handles all SIP requests.
>>With enabled DB access, I receive the following
>>error message when a SIP request comes in:
>>
>>receive_msg: no mem for sip_msg
>
>How much time and traffic does it take for this error to occur?
>
>BTW: there are guidelines for complete problem reporting at
>http://www.iptel.org/ser/problems/
>
>-jiri
>
>
>>As posted in September 2003, I increased both
>>the shared memory to 64 MB and PKG_MEM_POOL_SIZE
>>to 10240*1024, but the error remained.
>>
>>Beside this, I also added 256 MB physical RAM.
>>
>>Do have any other ideas what I could change?
>>
>>Best regards,
>>Peter
>>
>>
>>_______________________________________________
>>Serusers mailing list
>>serusers at lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>
>--
>Jiri Kuthan            http://iptel.org/~jiri/
>
>

--
Jiri Kuthan            http://iptel.org/~jiri/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ser.log
Type: application/octet-stream
Size: 34359 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20040826/c75b2f98/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ser.cfg
Type: application/octet-stream
Size: 3525 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20040826/c75b2f98/attachment-0001.obj>


More information about the sr-users mailing list