[sr-dev] [ openser-Bugs-2809998 ] pua:pres_process_body: No more memory

SourceForge.net noreply at sourceforge.net
Sun Jun 21 23:29:37 CEST 2009


Bugs item #2809998, was opened at 2009-06-21 21:29
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2809998&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.5.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: pua:pres_process_body: No more memory

Initial Comment:
The mi_pua_publish appears to run out of memory. The syslog is shown below.

Every 10 seconds, the following command is run from the configuration file
exec_msg("/usr/local/etc/kamailio/100avail");
This causes the error message "CRITICAL:exec:ip_addr2a: unknown address family 0" (This bug will be identified in a separate bug report)
The file 100avail is based on the example http://www.kamailio.org/dokuwiki/doku.php/presence:pua-modules#publish_details_from_system 
This configuration has been running for 3-4 days before this problem showed up.

Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: CRITICAL:core:mk_proxy: pkg memory allocation failure 
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2proxy: bad host name in URI <sip:100 at sip.nzvrs.co.nz> 
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2su: failed create a dst proxy 
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:t_uac: no socket found 
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: in t_request tm module function 
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua_mi:mi_pua_publish: sending publish failed 
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:core:init_mi_tree: no more pkg mem 
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:mi_fifo:mi_fifo_server: command (pua_publish) processing failed 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20969]: CRITICAL:exec:ip_addr2a: unknown address family 0 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: CRITICAL:core:mk_proxy: pkg memory allocation failure 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2proxy: bad host name in URI <sip:100 at sip.nzvrs.co.nz> 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2su: failed create a dst proxy 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:t_uac: no socket found 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: in t_request tm module function 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua_mi:mi_pua_publish: sending publish failed 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:core:init_mi_tree: no more pkg mem 
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:mi_fifo:mi_fifo_server: command (pua_publish) processing failed 
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20969]: CRITICAL:exec:ip_addr2a: unknown address family 0 
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:pres_process_body: NO more memory 
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: while processing body 
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: NULL body 
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua_mi:mi_pua_publish: sending publish failed 
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:core:init_mi_tree: no more pkg mem 
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:mi_fifo:mi_fifo_server: command (pua_publish) processing failed 

The workaround I have invoked is to use the uac_req_send(); functions instead of using the fifo.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2809998&group_id=139143



More information about the sr-dev mailing list