[OpenSIPS-Users] Help!!! Getting ERROR:nathelper:nh_timer: out of memory

[Alex Massover]

Hi!

As far as I understand:
    if (t_was_cancelled()) {
        exit;
    }
in failure route will not help to eliminate
/usr/local/sbin/openser[29869]: ERROR:tm:t_forward_nonack: discarding fwd for a cancelled transaction
/usr/local/sbin/openser[29869]: ERROR:tm:w_t_relay: t_forward_nonack failed

Because it fails in the request route and t_was_cancelled() is not available in the request route.

I have the same "problem" in the scenario:
t_newtran();
perl_exec("very_slow_script");
..[some routing logic]..
t_relay();

If the transaction cancelled during "very_slow_script" I have the errors listed above. Currently I just disregard these errors, because found no way to check if the transaction cancelled before t_relay().

--
Best Regards,
Alex Massover

-----Original Message-----
From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Tuesday, December 09, 2008 11:42 PM
To: Krunal Patel
Cc: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] Help!!! Getting ERROR:nathelper:nh_timer: out of memory

Hi Krunal,

Krunal Patel wrote:
> Hi,
>
> We are having setup like openser+radius+mediaproxy.
> Openser version is 1.2.3. <http://1.2.3./>
>
> When we started to send high volume calls , we get below mentioned
> ERRORs & WARNINGs.
> 1.  /usr/local/sbin/openser[29869]: ERROR:tm:t_forward_nonack:
> discarding fwd for a cancelled transaction
>      /usr/local/sbin/openser[29869]: ERROR:tm:w_t_relay:
> t_forward_nonack failed
>      WARNING: script writer didn't release transaction
This means you are trying to fork a branch from an INVITE that was
already cancelled.

in failure route, do you use something like:
    if (t_was_cancelled()) {
        exit;
    }
(see default opensips cfg script)
>
> 2. WARNING:tm:run_failure_handlers: no UAC or CANCEL support (1, 0)
do not use t_on_failure() for a CANCEL request ;)
>
> 3.  /usr/local/sbin/openser[29870]: ERROR:nathelper:nh_timer: out of
> memory
you have too many contacts registered and nathelper is not able to
retrieve them (for pinging). Solutions:
     1) increase PKG memory - see PKG_MEM_POOL_SIZE in config.h
(recompile is needed)
     2) upgrade to opensips 1.4.3 and use distributed nat pinging
>
> 4.  /usr/local/sbin/openser[29870]: convert_rows: No memory left
> (openser crashed)
>
do you have a core file? a backtrace?

Regards,
Bogdan
>
>
> As we were using default shared memory for openser, we increased
> shared memory to maximum(2GB) to fix out of bound issue.
> We checked openser script for memory leacks using valgrind, but did
> not find any memory leack.
>
> During doing relay of CANCEL,in relay route t_on_failure was added. So
> we removed t_on_failure in relay route for CANCEL.
> So WARNING:tm:run_failure_handlers: no UAC or CANCEL support (1, 0)
> was fixed.
>
> Still we are facing,
> 1. /usr/local/sbin/openser[29869]: ERROR:tm:t_forward_nonack:
> discarding fwd for a cancelled transaction
>     /usr/local/sbin/openser[29869]: ERROR:tm:w_t_relay:
> t_forward_nonack failed
>     WARNING: script writer didn't release transaction
>
> 2.  /usr/local/sbin/openser[29870]: ERROR:nathelper:nh_timer: out of
> memory
>
> 3. ERROR:usrloc:get_all_db_ucontacts: raw_query failed
>
> 4. rc_avpair_gen: received unknown attribute 80 of length 18:
> 0xA40AA6A78F04D67B03C75F8CA233F008
>
> Will increasing private memory will solve all issues?
>
> Thanks in advance!!
>
> --
> Krunal Patel
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



******************************************************************************

 This footnote confirms that this email message has been scanned by Jajah Inc. Mail system for the presence of malicious code, vandals & computer viruses.

******************************************************************************




******************************************************************************
 This footnote confirms that this email message has been scanned by Jajah Inc. Mail system for the presence of malicious code, vandals & computer viruses.
******************************************************************************