[Serusers] receive_msg: no mem for sip_msg

Wed Nov 17 17:34:13 CET 2004

Hi,

I worked all day on this error. Maybe the following information of my ser
could be useful :

[root at localhost sbin]# ser -V
version:  0.8.14 (i386/linux)
flags: STATS:Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, DNS_IP_HACK, SHM_MEM,
SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
@(#) $Id: main.c,v 1.168.4.3 2004/06/28 15:41:21 andrei Exp $
main.c compiled on 12:28:01 Jul 27 2004 with gcc 2.95
[root at localhost sbin]# ser -d -d -d -d
 0(3271) WARNING: could not rev. resolve 10.0.1.99
Listening on
              10.0.1.99 [10.0.1.99]:5060
              127.0.0.1 [127.0.0.1]:5060
Aliases: localhost:5060 10.0.1.99:* mairie-grigny69.fr:*
stateless - initializing
[root at localhost sbin]# Maxfwd module- initializing
 0(3273) mod_init(): Database connection opened successfuly
 0(0) INFO: udp_init: SO_RCVBUF is initially 65535
 0(0) INFO: udp_init: SO_RCVBUF is finally 131070
 0(0) INFO: udp_init: SO_RCVBUF is initially 65535
 0(0) INFO: udp_init: SO_RCVBUF is finally 131070
 9(0) INFO: fifo process starting: 3289
 9(3289) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...
 1(3275) ERROR: receive_msg: no mem for sip_msg
 2(3277) ERROR: receive_msg: no mem for sip_msg
 4(3281) ERROR: receive_msg: no mem for sip_msg
 1(3275) ERROR: receive_msg: no mem for sip_msg

Here, only one of my X-Lite client tried to log in. After those 4 errors,
X-Lite said "logging time-out"...

Thanks for your help (in advance) :-)
  Gwen

> Hi, I am back with my problem...
>
> I installed ser 0.8.14 on another computer (I bought it last week) but I
> still have the same problem :
>   ERROR: receive_msg: no mem for sip_msg
>
> Is it a bug of ser ? Does it come from mysql 4.0.18 ?
>
> Gwen
>
>
>
>>
>> Yes, I have the same problem with db_mode 2
>>
>> I always get these lines :
>> ERROR: receive_msg: no mem for sip_msg
>> DEBUG: probing packet received
>>
>> I will upgrade to 0.8.14...
>>
>> Thank you
>> Gwen
>>
>>> Hi Gwen,
>>>
>>> it will be safer to uninstall first the 0.8.12 version.
>>> out of curiosity, since the problem you reported is quite strange, have
>>> you tried db_mod 2?
>>>
>>> bogdan
>>>
>>> g.billoudet at arwen-tech.fr wrote:
>>>
>>>>Hi,
>>>>
>>>>If I don't use "serctl alias add", I still get the same error
>>>> message...
>>>>I will try to upgrade ser:
>>>>- Should I uninstall ser 0.8.12 and then install 0.8.14
>>>>- Or should I install 0.8.14 directly ?
>>>>
>>>>Thanks
>>>>
>>>>  Gwen
>>>>
>>>>
>>>>
>>>>
>>>>>Try to install 0.8.14.
>>>>>
>>>>>  Jan.
>>>>>
>>>>>On 10-11 14:27, Bogdan-Andrei IANCU wrote:
>>>>>
>>>>>
>>>>>>Hi Gwen,
>>>>>>
>>>>>>try to set back db_mode to 1 or 2 but without adding the aliases via
>>>>>>serctl. I'm trying to figure out if it's a problem in DB part or in
>>>>>> fifo
>>>>>>part of usrloc.
>>>>>>
>>>>>>bogdan
>>>>>>
>>>>>>g.billoudet at arwen-tech.fr wrote:
>>>>>>
>>>>>>
>>>>>>>Hi, thanks for help
>>>>>>>
>>>>>>>I used serctl alias add 1234 sip:gwenael at arwen-tech.fr just after
>>>>>>>
>>>>>>>
>>>>>>starting
>>>>>>
>>>>>>
>>>>>>>ser :
>>>>>>>- When I set modparam("usrloc", "db_mode", 0), ser works fine and I
>>>>>>> can
>>>>>>>have phone calls but I can't use this alias of course...
>>>>>>>- When I ser modparam("usrloc", "db_mode", 1), ser just doesn't work
>>>>>>> at
>>>>>>>all.
>>>>>>>
>>>>>>>My aliases table is empty when I start ser. I am using ser 0.8.12.
>>>>>>>
>>>>>>> Gwen
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>On 10-11 11:41, Bogdan-Andrei IANCU wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Jan Janak wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>On 10-11 10:01, Bogdan-Andrei IANCU wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>my first guess is that use at start-up time you have an
>>>>>>>>>>> intensive
>>>>>>>>>>>private memory consumer which gets into conflict with the SIP
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>messages
>>>>>>
>>>>>>
>>>>>>>>>>>receiver.
>>>>>>>>>>>
>>>>>>>>>>>Judging after the error (in receive loop) I'm sure you have some
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>SIP
>>>>>>
>>>>>>
>>>>>>>>>>>traffic at start-up  - please check with tcpdump or ngrep - it
>>>>>>>>>>> can
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>be
>>>>>>
>>>>>>
>>>>>>>>>a
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>REGISTER, SUBSCRIBE, etc
>>>>>>>>>>>
>>>>>>>>>>>Looking into your script, I would say only usrloc can be the
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>intensive
>>>>>>
>>>>>>
>>>>>>>>>>>private memory consumer - if you have a lot of entries in DB
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>(usrloc
>>>>>>
>>>>>>
>>>>>>>>>and
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>aliases). To check this theory, try to start ser with DB
>>>>>>>>>>> disabled
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>in
>>>>>>
>>>>>>
>>>>>>>>>>>usrloc; set:
>>>>>>>>>>>	modparam("usrloc", "db_mode", 0)
>>>>>>>>>>>
>>>>>>>>>>>please see if you still get the error and also please confirm if
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>you
>>>>>>
>>>>>>
>>>>>>>>>>>have or not sip traffic.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>I don't think this is the problem. usrloc consumes private memory
>>>>>>>>>>before SER forks (and at that stage it does not process SIP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>messages),
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>when re-loading data from the database. It would fail to start if
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>this
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>was the problem, so I think there must be some other memory
>>>>>>>>>> problem.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>I was considering the possibility of memory fragmentation. If
>>>>>>>>> there
>>>>>>>>>
>>>>>>>>>
>>>>>>are
>>>>>>
>>>>>>
>>>>>>>>>a lot of usrloc/aliases records to be loaded, memory can get to
>>>>>>>>>fragmented to be able later to alloced a bigger size chunk.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>Bot tables (aliases, location) are empty:
>>>>>>>>
>>>>>>>> 0(0) preload_udomain(): Table is empty
>>>>>>>> 0(0) fixing /usr/local/lib/ser/modules/sl.so sl_send_reply
>>>>>>>> 0(0) fixing /usr/local/lib/ser/modules/registrar.so lookup
>>>>>>>> 0(0) preload_udomain(): Table is empty
>>>>>>>>
>>>>>>>>   Jan.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: /
Size: 7 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20041117/bbe043b6/attachment.bin>