Hi Daniel,

I compiled the latest 4.1 branch and tested the same INVITE. It works. The loop ends after one loop and all goes well. The password is removed after clearing $rU and the request-uri is correct: sip:sip.custom.com so we are able to change the username part after clearing it.

Great, thank you.

Mit freundlichen Grüßen

Timo Klecker

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Timo Klecker
Gesendet: Mittwoch, 10. Dezember 2014 13:18
An: miconda@gmail.com; 'Kamailio (SER) - Users Mailing List'
Betreff: Re: [SR-Users] Kamailio Crash when modifying username of Request Uri

Hi Daniel,

yes, stock Kamilio Version 4.1.6 downloaded from http://www.kamailio.org/pub/kamailio/4.1.6/ then built into a custom RPM, due to signing and changing of prefix.

Built with:

make prefix=/opt/kamailio group_include="standard mysql" include_modules="mi_fifo kex tmx pv siputils mi_rpc sqlops avpops siptrace snmpstats"

For your question regarding memory usage please see attached top-logfiles. Running with default settings and with –m 256.

If you need anything more, please do not hesitate to ask. I will now try the latest git-version of the 4.1.6 branch.  

Kind regards
Timo Klecker

Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Gesendet: Mittwoch, 10. Dezember 2014 11:33
An: Timo Klecker; 'Kamailio (SER) - Users Mailing List'
Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri

Hello,

you said you saw an increase in memory usage -- was system memory, right? What was the value, did it exceed shared memory size?

Just to be clear, you run stock kamailio, no patches or other modules developed in-house?

Cheers,
Daniel

On 09/12/14 16:36, Timo Klecker wrote:

Hi Daniel,

The child process is terminated by signal 11 (SIGSEGV).

Dec  8 16:41:25  /sbin/kamailio[12000]: ALERT: <core> [main.c:777]: handle_sigs(): child process 12003 exited by a signal 11

Dec  8 16:41:25  /sbin/kamailio[12000]: ALERT: <core> [main.c:780]: handle_sigs(): core was generated

Dec  8 16:41:25  /sbin/kamailio[12000]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD

Maybe not relevant but the process 12003 that is killed has last logged a line to kamailio.log like 6000 lines above the SIGSEGV:

Dec  8 16:40:46 /sbin/kamailio[12003]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI

Have not yet tried the latest branch, will do so tomorrow.

Kind regards

Timo Klecker

Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Gesendet: Dienstag, 9. Dezember 2014 12:46
An: Timo Klecker; 'Kamailio (SER) - Users Mailing List'
Betreff: Re: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri

Hello,

On 08/12/14 16:42, Timo Klecker wrote:

Hi Daniel,

I tried to increase shared memory by setting a parameter in kamctlrc:

STARTOPTIONS="-m 64"

When recreating the crash I counted pv_get_ruri_attr in the logfile just to see if the shared memory changed anything:

> grep pv_get_ruri_attr /var/log/kamailio.log | wc -l

75472 with default settings

75436 with shared memory set to 64

75440 with shared memory set to 256

But in top I saw a massive increase in memory usage.

I don’t know if this is any helpful for you.

It might be that the OS kills the process due to too much memory usage. Can you check again the logs and see what was the signal that killed the process?

Btw, have you tried with latest git branch, after I did the patch for fixing empty username?

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda