Re: [SR-Users] crash in version 4.0

Hello, is is 4.0.0 or some later version in the series? There were some fixes, iirc, at least to cloning of values used for acc via transaction callbacks, but many other can be there. Cheers, Daniel On 19/12/15 05:46, Juha Heinanen wrote: > core dump occurred in kamailio version 4.0. does

[SR-Users] crash in version 4.0

core dump occurred in kamailio version 4.0. does anyone remember if a bug causing such a crash would possibly have been fixed in some later kamailio version? -- juha -- Dec 17 17:16:59 node5 /usr/sbin/sip-proxy[21089]:

Re: [SR-Users] crash on using http_query when response is 200

Please post this on the issue tracker. I also get crashes, but they’re not like this. /Olle > On 07 Dec 2015, at 15:54, Jayesh Nambiar wrote: > > Hi, > I'm using http_query to send a post request on a https URL. The weird part is > it crashes with segmentation fault

[SR-Users] crash on using http_query when response is 200

Hi, I'm using http_query to send a post request on a https URL. The weird part is it crashes with segmentation fault when the response from the server is 200. If the response was a 500, it works and continues processing. Here's the function: http_query("https://notify.abcd.com/onnet/call;,

Re: [SR-Users] crash on using http_query when response is 200

Hello Olle, I made a note on your but tracker issue, because the new curl module doesn't seem to have some fixed done to utils module in august/september -- those patches look like fixing what you are facing. Have you seen it? Cheers, Daniel On 07/12/15 16:06, Olle E. Johansson wrote: > Please

Re: [SR-Users] crash on using the $expires variable

So someone planning to patch it? Just asking? Thanks, - Jayesh On Thu, Nov 26, 2015 at 6:48 PM Sergey Okhapkin wrote: > Confirmed, I'm getting crash too. > > On Thursday 26 November 2015 13:05:57 Jayesh Nambiar wrote: > > Hi, > > I am trying to extract out the

Re: [SR-Users] crash on using the $expires variable

Pushed a fix for it in master and 4.3 branches. It is recommended to open an issue on tracker, because is usually easier to spot the open bugs there than on mailing list, especially after a period of traveling. Cheers, Daniel On 27/11/15 14:31, Jayesh Nambiar wrote: > So someone planning to

Re: [SR-Users] crash on using the $expires variable

Will keep that in mind for the future. Thanks a lot. - Jayesh On Fri, Nov 27, 2015 at 7:10 PM Daniel-Constantin Mierla wrote: > Pushed a fix for it in master and 4.3 branches. It is recommended to open > an issue on tracker, because is usually easier to spot the open bugs

[SR-Users] crash on using the $expires variable

Hi, I am trying to extract out the expires value from the incoming REGISTER request. It might be present in the Contact header or as a separate Expires header and hence I planned to use the $expires(max) PV to get this. But kamailio just crashes as soon as I use the variable. Here's when it

Re: [SR-Users] crash on using the $expires variable

Confirmed, I'm getting crash too. On Thursday 26 November 2015 13:05:57 Jayesh Nambiar wrote: > Hi, > I am trying to extract out the expires value from the incoming REGISTER > request. It might be present in the Contact header or as a separate Expires > header and hence I planned to use the

Re: [SR-Users] Crash kamailio 4.3.1

Federico, I have tried to apply your commit on the branch 4.3 (just the modifications on t_append_branch.c) The result is not very good (failure route not called, 408 timeout not send...) Have you a patch for the 4.3 branch ? Regards thibault 2015-09-28 11:45 GMT+02:00 Thibault Gueslin

Re: [SR-Users] Crash kamailio 4.3.1

Hi, I've finally managed to understand what was causing the crash. I've submitted a pull request with a proposal for a fix ( https://github.com/kamailio/kamailio/pull/346). Let's wait Daniel thoughts about it :) Regards, Federico On Sun, Sep 20, 2015 at 4:17 PM, Federico Cabiddu <

Re: [SR-Users] Crash kamailio 4.3.1

Federico, This is good news! I will try it as soon as possible Regards thibault 2015-09-28 9:25 GMT+02:00 Federico Cabiddu : > Hi, > I've finally managed to understand what was causing the crash. > I've submitted a pull request with a proposal for a fix ( >

Re: [SR-Users] Crash kamailio 4.3.1

Hi Thibault, there is no need for special decline handling when using tsilo, so the default basic should work with the modifications you've done. I tested your scenario with this config and I haven't been able to get the crash. Could you please perform a test with debug level 3 and send me the

Re: [SR-Users] Crash kamailio 4.3.1

Hi Thibault, I tried again to reproduce the issue but with no luck. Are you doing something "special" in the failure route after calling t_is_canceled? Regards, Federico On Wed, Sep 16, 2015 at 7:33 PM, Thibault Gueslin < thibault.gues...@gmail.com> wrote: > Hello Federico, > > You are right.

Re: [SR-Users] Crash kamailio 4.3.1

Hi Federico, Thank you to keep looking at this. I have sent you all my changes to default config. So there is nothing done after t_is_canceled (no voice mail, ...) I have just enabled WITH_NAT & WITH_NATSIPPING. I am sure if it is related but do you do special tricks for DECLINE (when enabling

Re: [SR-Users] Crash kamailio 4.3.1

Hi Thibault, I'm not sure I understand the scenario of your crash. Is the branch rejecting the call a branch added with ts_append? What are you doing upon receiving the 603 (supposing that's how the application is rejecting the call)? Are you appending other branches? In the bt it looks like the

Re: [SR-Users] Crash kamailio 4.3.1

Hello Federico, You are right. The first line comes from the other core dump (which is related to normal sig handling on crash). In my scenario, I have only 2 SIP client: one caller and one callee I am starting the callee after call is initiated then kill the callee, then relaunch the callee.

Re: [SR-Users] Crash kamailio 4.3.1

Hi Thibault, I have not been able to get the crash reproducing the scenario you described. Could you try the last 4.3.x code? Are you still seeing the crash? Regards, Federico On Fri, Sep 11, 2015 at 11:34 PM, Thibault Gueslin < thibault.gues...@gmail.com> wrote: > Hi Federico, > > I will try

Re: [SR-Users] Crash kamailio 4.3.1

Hello Federico, I have built from 4.3 branch. I got a crash again... However it seems different than previous one: Issue seems located in tm module. It appears if the remote denied the incoming call, then quit application . thibault Core was generated by `sbin/kamailio -f

Re: [SR-Users] Crash kamailio 4.3.1

Hi Federico, didn't get the time to write a more detailed report, but my quick look at the tsilo code revealed two potential issues: - the ts transaction structure is cloned in shared memory to be passed as parameter to a tm callback. The clone is stil linked to the list with prev and next. In

Re: [SR-Users] Crash kamailio 4.3.1

Hi Federico, I will try last code in 4.3.x branch. The scenario is very easy: I am calling a SIP client (running on a mobile) First the client is stopped. Then launch the app. As expected, the calll is presented after it has registered. Then kill the application (before answering), then

Re: [SR-Users] Crash kamailio 4.3.1

Hi Daniel, thank you for having a look. Regard your remarks: 1) when the cloned transaction structure is passed to ts_onreply, we take the pointer to its urecord and from this last one we take the transaction list. So, the transaction list should still be coherent. We could have a problem if the

Re: [SR-Users] Crash kamailio 4.3.1

I have done again the trace and obtained 2 core dumps: Here is the second: Core was generated by `kamailio -f /etc/kamailio/kamailio.cfg -w /tmp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0264 in ?? () (gdb) bt full #0 0x0264 in ?? () No

Re: [SR-Users] Crash kamailio 4.3.1

Hello, can you install the kamailio-dbg package to get access to debugging sysmbols? Once that package is installed, get the backtrace again and send it here. Cheers, Daniel On 10/09/15 10:55, Thibault Gueslin wrote: > I have done again the trace and obtained 2 core dumps: > > Here is the

Re: [SR-Users] Crash kamailio 4.3.1

Do you have msrp enabled in configuration file? Send the output from gdb for next commands: frame 0 info locals p *msg p *ruri p *ptr p *_r Cheers, Daniel On 10/09/15 14:07, Thibault Gueslin wrote: > > [Thread debugging using libthread_db enabled] > > Using host libthread_db library

Re: [SR-Users] Crash kamailio 4.3.1

On 10/09/15 14:36, Thibault Gueslin wrote: > > > 2015-09-10 14:25 GMT+02:00 Daniel-Constantin Mierla >: > > Do you have msrp enabled in configuration file > > > I don't think so The last frames of backtrace indicates code related to msrp, but

Re: [SR-Users] Crash kamailio 4.3.1

2015-09-10 14:25 GMT+02:00 Daniel-Constantin Mierla : > Do you have msrp enabled in configuration file > I don't think so > Send the output from gdb for next commands: > > frame 0 > #0 ts_append (msg=0x7f883bfd5490, ruri=0x7fff65fbfe30, table=0x7f883bf7e390 "location") at

Re: [SR-Users] Crash kamailio 4.3.1

[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.'. Program terminated with signal SIGSEGV, Segmentation fault. #0

Re: [SR-Users] Crash kamailio 4.3.1

Hi Thibault, have you tried last tsilo code from 4.3.x branch? Recently there has been a fix ( https://github.com/kamailio/kamailio/commit/6ce6803d57dabe287d7d6fa859e93c1df402d821) for an issue that may be related to yours. I'll keep investigating to see if I can spot something else. In the

Re: [SR-Users] Crash kamailio 4.3.1

Hello, do you get other error messages in syslog before the one "CRITICAL: ..."? It is hard to say it is from something already known or new. Right now there is an open issue for saving dialog variables in database that was not yet sorted out. Another one related to tm and memory manager,

[SR-Users] Crash kamailio 4.3.1

After upgrading to kamailio 4.3.1 and modifying the config, I get this crash very often: ... CRITICAL: [pass_fd.c:275]: receive_fd(): EOF on 21 ALERT: [main.c:728]: handle_sigs(): child process 9341 exited by a signal 11 ALERT: [main.c:731]: handle_sigs(): core was not generated INFO:

Re: [SR-Users] Crash kamailio 4.3.1

It seems related to tsilo module and tm module: #0 0x7f6a7c8978f5 in lock_entry () from /usr/lib/x86_64-linux-gnu/kamailio/modules/tsilo.so #0 0x7f6a7c8978f5 in lock_entry () from /usr/lib/x86_64-linux-gnu/kamailio/modules/tsilo.so (gdb) bt full #0 0x7f6a7c8978f5 in lock_entry

Re: [SR-Users] Crash kamailio 4.3.1

This is during shut down clean up. Have you stopped kamailio manually? If not, aave you got more than one core file? If not, enable one core file per process. Cheers, Daniel On 09/09/15 17:03, Thibault Gueslin wrote: > > It seems related to tsilo module and tm module: > > > #0

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hi Daniel, I will see if I can grow my balls big enough to upgrade :-) Thanks for your help and time. Regards, Kristian. On Wednesday 14 January 2015 14:58:22 Daniel-Constantin Mierla wrote: Hello, ok, so it is from the pid. At this moment I don't see any reason in that part of code to

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hello, the operation done by that code is practically a sql query, fetching the result and packing it for nathelper usage. It is no race between it and handling any sip packet, no shared memory accessed. Do you get only one corefile? From the backtrace it looks like row pointer is not ok, can

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hello, the string_val field look ok. But p variable which is assigned that value a line before the reported crash is not, as reported by bt full: p = 0xcfcdffaf Address 0xcfcdffaf out of bounds Do you have enabled core files per process/pid? I still wonder if it is a overwritten core.

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hi Daniel, # kamailio -V version: kamailio 3.1.1 (x86_64/linux) c274ce flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hello, ok, so it is from the pid. At this moment I don't see any reason in that part of code to crash, unless hardware problems. Maybe you can at least upgrade to latest version in 3.1.x series, to rule out the side effects of the bugs found in 3.1 branch at that time. It should be same config

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hi Daniel, (gdb) p *row $1 = {values = 0x9bd2b8, n = 13} Regards, Kristian. On Wednesday 14 January 2015 10:01:41 Daniel-Constantin Mierla wrote: Hello, the operation done by that code is practically a sql query, fetching the result and packing it for nathelper usage. It is no race

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hi Daniel, Sorry. Forgot to answer your question. I am quite sure, I only got one core file. Regards, Kristian Høgh Uni-tel On Wednesday 14 January 2015 10:01:41 Daniel-Constantin Mierla wrote: Hello, the operation done by that code is practically a sql query, fetching the result and

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hello, get also: p *row-values p i Cheers, Daniel On 14/01/15 10:50, Kristian F. Høgh wrote: Hi Daniel, (gdb) p *row $1 = {values = 0x9bd2b8, n = 13} Regards, Kristian. On Wednesday 14 January 2015 10:01:41 Daniel-Constantin Mierla wrote: Hello, the operation done by that code is

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

Hi Daniel, (gdb) p *row-values $1 = {type = DB1_STRING, nul = 0, free = 0, val = {int_val = 58055112, ll_val = 58055112, double_val = 2.8683036404665902e-316, time_val = 58055112, string_val = 0x375d9c8 sip:44221xxx@192.168.1.157:37612;rinstance=8c613319a30caff6;transport=TCP, str_val = {

Re: [SR-Users] Crash in usrloc, get_all_db_ucontacts

On 14/01/15 14:21, Kristian F. Høgh wrote: Hi Daniel, # kamailio -V version: kamailio 3.1.1 (x86_64/linux) c274ce flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX,

Re: [SR-Users] Crash Kamailio 4.1.4

\) - Users Mailing List' Objet : Re: [SR-Users] Crash Kamailio 4.1.4 Hello, you can browse the git repository online and get from there the patch or diff: - http://git.sip-router.org/cgi-bin/gitweb.cgi?p=kamailio;a=history;f=modules/acc;hb=HEAD Or on github: - https://github.com/kamailio

Re: [SR-Users] Crash Kamailio 4.1.4

2014 09:00 *À :* Igor Potjevlesch *Cc :* 'Kamailio \(SER\) - Users Mailing List' *Objet :* Re: [SR-Users] Crash Kamailio 4.1.4 Hello, I pushed a fix to kamailio master branch that should solve it -- last commits to acc module. If you can give it a try and report results, would be appreciated

Re: [SR-Users] Crash Kamailio 4.1.4

Potjevlesch Cc : 'Kamailio \(SER\) - Users Mailing List' Objet : Re: [SR-Users] Crash Kamailio 4.1.4 Hello, I pushed a fix to kamailio master branch that should solve it -- last commits to acc module. If you can give it a try and report results, would be appreciated. Cheers, Daniel On 03/10

Re: [SR-Users] Crash Kamailio 4.1.4

October. I can wait until this date. Regards, Igor. *De :*Igor Potjevlesch [mailto:igor.potjevle...@gmail.com] *Envoyé :* jeudi 2 octobre 2014 18:43 *À :* mico...@gmail.com *Cc :* 'Kamailio \(SER\) - Users Mailing List' *Objet :* RE: [SR-Users] Crash Kamailio 4.1.4 Hello, Thank you for your time

Re: [SR-Users] Crash Kamailio 4.1.4

: RE: [SR-Users] Crash Kamailio 4.1.4 Hello, Thank you for your time on this issue. I understand that I can define “db_extra” like: modparam(acc, db_extra, src_user=$fU;username=$Au;src_domain=$fd;src_ip=$si;src_pai=$avp(s:pai); dst_ouser=$tU;dst_user=$rU;dst_domain=$rd

Re: [SR-Users] Crash Kamailio 4.1.4

(REQINIT); […] } I can put this fix while waiting for 4.2. Regards, Igor. De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] Envoyé : jeudi 2 octobre 2014 10:17 À : Igor Potjevlesch Cc : 'Kamailio \(SER\) - Users Mailing List' Objet : Re: [SR-Users] Crash Kamailio 4.1.4

Re: [SR-Users] Crash Kamailio 4.1.4

: [SR-Users] Crash Kamailio 4.1.4 Hello, so it is still related to PAI header -- I will have more time to look at it by end of the week. Cheers, Daniel On 23/09/14 19:16, Igor Potjevlesch wrote: Hello Daniel, Patching has been done in the same time than the upgrade to 4.1.5. A new crash

Re: [SR-Users] Crash Kamailio 4.1.4

Potjevlesch Cc : 'Kamailio \(SER\) - Users Mailing List' Objet : Re: [SR-Users] Crash Kamailio 4.1.4 Hello, it is not in my plans for 4.1.5, because I didn't get any feedback on testing and its results, whether it fixes or not the issue. Cheers, Daniel On 06/08/14 16:07, Igor Potjevlesch wrote

Re: [SR-Users] Crash Kamailio 4.1.5

(SER) - Users Mailing List' Objet : Re: [SR-Users] Crash Kamailio 4.1.5 Hello, the value to insert in db is invalid, now to see what was supposed to be there. Can you send the parameters you set for acc module? Cheers, Daniel On 17/09/14 19:48, Igor Potjevlesch wrote: Hello, (gdb) frame

Re: [SR-Users] Crash Kamailio 4.1.5

...@lists.sip-router.org] De la part de Daniel-Constantin Mierla Envoyé : mardi 16 septembre 2014 17:44 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Crash Kamailio 4.1.5 Hello, can you get the output in gdb for: frame 2 p *_v Cheers, Daniel On 16/09/14 17:34, Igor

Re: [SR-Users] Crash Kamailio 4.1.5

(SER) - Users Mailing List *Objet :* Re: [SR-Users] Crash Kamailio 4.1.5 Hello, can you get the output in gdb for: frame 2 p *_v Cheers, Daniel On 16/09/14 17:34, Igor Potjevlesch wrote: Hello, A crash just occurred. I use the patch for the PAI issue. I had a look to the core dump

[SR-Users] Crash Kamailio 4.1.5

Hello, A crash just occurred. I use the patch for the PAI issue. I had a look to the core dump and it looks to be another issue: (gdb) bt full #0 0x0030f2230f30 in escape_string_for_mysql () from /usr/lib64/mysql/libmysqlclient.so.16 No symbol table info available. #1

Re: [SR-Users] Crash Kamailio 4.1.5

Hello, can you get the output in gdb for: frame 2 p *_v Cheers, Daniel On 16/09/14 17:34, Igor Potjevlesch wrote: Hello, A crash just occurred. I use the patch for the PAI issue. I had a look to the core dump and it looks to be another issue: (gdb) bt full #0 0x0030f2230f30 in

Re: [SR-Users] Crash Kamailio 4.1.4

Hello Daniel, Thank you for this exhaustive feedback. Do you include the patch to 4.1.5? Regards, Igor. De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] Envoyé : lundi 4 août 2014 16:24 À : Igor Potjevlesch Cc : Kamailio \(SER\) - Users Mailing List Objet : Re: [SR-Users

Re: [SR-Users] Crash Kamailio 4.1.4

? Regards, Igor. *De :*Daniel-Constantin Mierla [mailto:mico...@gmail.com] *Envoyé :* lundi 4 août 2014 16:24 *À :* Igor Potjevlesch *Cc :* Kamailio \(SER\) - Users Mailing List *Objet :* Re: [SR-Users] Crash Kamailio 4.1.4 Hello, the problem was that a structure in shared memory (the request cloned

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, the problem was that a structure in shared memory (the request cloned in tm) could have been used in parallel by different kamailio processes. If there were two processes at the same time, parsing PAI resulted in setting the header pointer to a private memory. The other process could

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, To try on a lab, i need to understand the behaviour of your patch. How your patch avoid segmentation fault? I can't download the patch with your link, i can only see the diff. can you send me the patch again? Regards, Igor 2014-07-18 0:06 GMT+02:00 Daniel-Constantin Mierla

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, I don't understand the patch you sent me. Is it for the PAI problem? Regards, Igor 2014-07-07 12:40 GMT+02:00 Igor Potjevlesch igor.potjevle...@gmail.com: Hello, Can you explain the modification and the impact on our plateform? Is it for the pai problem? Do you have explanation

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, On 17/07/14 18:41, Igor Potjevlesch wrote: Hello, When this patch will be add in a new release? I can't try without validation of new release. when is scheduled the next release? you were the only one reporting this issue. The patch will be backported if you can test and confirm

[SR-Users] crash after 100 trying on NOTIFY

Hi, We've had the following crash. Kamailio 4.0.4 Client sends SUBSCRIBE, kamailio answers 202. Kamailio sends NOTIFY, client answers 100 trying. fr_timer is 5000. The client doesn't send 200 OK, so kamailio generates 408. Any suggestions? Regards, Kristian Høgh (gdb) bt #0

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, Can you explain the modification and the impact on our plateform? Is it for the pai problem? Do you have explanation for the km_val.c problem wich cause crash for Kamailio too? Regards, Igor 2014-07-01 16:40 GMT+02:00 Daniel-Constantin Mierla mico...@gmail.com: Hello, can you

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, can you give it a try with the patch from next commit? - http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=da9d56be28e050dd0cb4aed50efcbda043a3e5cf If all goes fine while testing, I will backport. Cheers, Daniel On 26/06/14 12:58, Igor Potjevlesch wrote: Hello,

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, We updated this morning Kamailio in 4.1.4 with your patch. Kamailio crashed again this afternoon. here an extract from /var/log/messages : Jun 25 13:49:01 /usr/local/sbin/kamailio[20259]: WARNING: script: time=[Wed Jun 25 13:49:01 2014] call id=[f4653f6fe909d3118f86009033290024@A.B.C.D]

Re: [SR-Users] Crash Kamailio 4.1.4

Hello, can you give the output of: frame 6 print hdr print *hdr frame 4 print *pid_b Also, it would be good to have full trace for other details: bt full Cheers, Daniel On 25/06/14 14:49, Igor Potjevlesch wrote: Hello, We updated this morning Kamailio in 4.1.4 with your patch. [...] --

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, We don't use $ai in xlog nor in other process. only in ACC. parameters for ACC are : modparam(acc, db_flag, FLT_ACC) modparam(acc, db_missed_flag, 3) modparam(acc, db_url, DBURLWO) modparam(acc, db_extra, src_user=$fU;username=$Au;src_domain=$fd;src_ip=$si;src_pai=$ai;

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, if you get a record for 180 response, then you have also the early_media parameter set for acc module, isn't it? In the morning I pushed a patch that should fix this issue. Use latest release 4.1.4 and see if works fine. Report the results to know that it is gone or not. Cheers,

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, we didn't set the early media parameter . its '0' by default, isn't it? regards, Igor 2014-06-12 17:03 GMT+02:00 Daniel-Constantin Mierla mico...@gmail.com: Hello, if you get a record for 180 response, then you have also the early_media parameter set for acc module, isn't it?

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, in the same frame 5, can yo get: p *t-uas.request-pai p *((p_id_body_t*)(t-uas.request-pai-parsed)) Cheers, Daniel On 10/06/14 18:35, Igor Potjevlesch wrote: Hello, Here is the results : _ _ (gdb) frame 5 #5 0x7f6a687e9b43 in acc_onreply (t=0x7f6a60d16ff8, req=0x7f6a60cd2c10,

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, This is the result, always for frame 5 : (gdb) p *t-uas.request-pai $1 = {type = HDR_PAI_T, name = { s = 0x7f6a60cd34b8 P-Asserted-Identity: \0987654321\sip:0987654321@A.B.C.D\r\nContact: sip:0987654321@A.B.C.D:5060\r\nAllow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE,

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, at least I narrowed it down a bit. It is empty also in the clone stored in transaction, so it happens either during cloning or before. I will have to check these parts. Cheers, Daniel On 11/06/14 17:00, Igor Potjevlesch wrote: Hello, This is the result, always for frame 5 : (gdb)

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, cloning to shm for tm seems ok. Can you tell where you access P-Asserted-Identity header, via variables? Does it happen in request_route, failure_route or branch_route? Can you print from gdb, any frame: p mem_block p shm_block I want to see if parsed filed point to shm or pkg

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, We do not access to the P-asserted-identity in our configuration but we added the field PAI in the db base ACC ( for INVITE, ACK and BYE) . I dont know if it's in request_route, failure_route or branch_route . This is the print : (gdb) p mem_block $3 = (struct qm_block *) 0x7f6a6bef1010

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, so you don't print $ai in xlog() statements nor use it in any assignments or other functions besides acc parameter? Cheers, Daniel On 11/06/14 19:19, Igor Potjevlesch wrote: Hello, We do not access to the P-asserted-identity in our configuration but we added the field PAI in the db

Re: [SR-Users] Crash Kamailio 4.1.3

Few more things... Are you recording 1xx events? Can you check to see if there is another record in acc table for the same call? You can search by call-id 3781-4b1-572014182635-OGNAJ-1-A.B.C.D Eventually, send also the parameters you set for acc module. Cheers, Daniel On 11/06/14 19:25,

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello, I'm not using tel2uri(). I tested it again and I can't reproduced it with the last commit in 4.1 branch. With version 4.1.3 it reproduces always. The problem seems to be present after more than one mysql query thus I thought it could be related with that commit. I try it at

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello, On 10/06/14 12:47, Andrés Souto wrote: Hello, I'm not using tel2uri(). I tested it again and I can't reproduced it with the last commit in 4.1 branch. With version 4.1.3 it reproduces always. The problem seems to be present after more than one mysql query thus I thought it could be

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

I don't know the Kamailio internals but after that commit this crash does not occur... Yeah, I'm think the log is complete but it contains more than one execution. I updated the file to a new log. Now it only contains one executions from initialization until it crashes. The message is still not

Re: [SR-Users] Crash Kamailio 4.1.3

schedule to include the patch in 4.1.4? Do you need more information? Regards, Igor. De : Daniel-Constantin Mierla [mailto: mailto:mico...@gmail.com mico...@gmail.com] Envoyé : vendredi 30 mai 2014 18:02 À : Igor Potjevlesch; Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Crash

Re: [SR-Users] Crash Kamailio 4.1.3

the patch in 4.1.4? Do you need more information? Regards, Igor. *De :*Daniel-Constantin Mierla [mailto:mico...@gmail.com mailto:mico...@gmail.com] *Envoyé :* vendredi 30 mai 2014 18:02 *À :* Igor Potjevlesch; Kamailio (SER) - Users Mailing List *Objet :* Re: [SR-Users] Crash Kamailio 4.1.3 Hello

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello, do you still have the core file for inspection? Can the issue be reproduced? Cheers, Daniel On 29/05/14 12:18, Andrés Souto wrote: Hello, Kamailio crashes with this message: May 29 12:03:45 kamfree-manager kamailio[8705]: : core [mem/q_malloc.c:159]: qm_debug_frag(): BUG: qm_*: prev.

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello, yes, I'm still have the core file. The issue reproduces always with this configuration. 2014-06-09 18:08 GMT+02:00 Daniel-Constantin Mierla mico...@gmail.com: Hello, do you still have the core file for inspection? Can the issue be reproduced? Cheers, Daniel On 29/05/14 12:18,

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello again, I have tested right now if it still reproduces with the current last branch 4.1 git version and it seems to work. Tomorrow I'll do more testing but probably it is already fixed by 94ebfb5d5973ed59de84ca0e0c87052b4c80f9de. 2014-06-09 20:46 GMT+02:00 Andrés Souto

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello, if you can reproduce it, set: memdbg=1 memlog=1 in kamailio.cfg and run again. Then send me all the messages from syslog file related to this execution. Cheers, Daniel On 09/06/14 20:46, Andrés Souto wrote: Hello, yes, I'm still have the core file. The issue reproduces always with

Re: [SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello, the only patch that could fix such situation lately was in tel2uri() function, are you using it? In the backtrace I didn't see a tel uri. Cheers, Daniel On 09/06/14 20:57, Andrés Souto wrote: Hello again, I have tested right now if it still reproduces with the current last branch

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, The crash happen once. it can't be reproduced. The pai seems good, why it cannot be parsed? Regards, Igor. 2014-05-29 17:11 GMT+02:00 Daniel-Constantin Mierla mico...@gmail.com: Hello, for the moment I added a safety check to prevent crash in such situation: -

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, On 30/05/14 17:41, Igor Potjevlesch wrote: Hello, The crash happen once. it can't be reproduced. The pai seems good, why it cannot be parsed? apparently it was parsed, but then the content got reset. The sip_msg_t for request is accessed via a callback inside acc module when the

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, I missed somehow the message with the pai parsed content. I will look over it later today. Cheers, Daniel On 28/05/14 18:45, Igor Potjevlesch wrote: Hello, Do you any ideas about the reason of this issue? Is it caused by the last call? Do you have enough information with the PAI?

[SR-Users] Crash Kamailio 4.1 (qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten)

Hello, Kamailio crashes with this message: May 29 12:03:45 kamfree-manager kamailio[8705]: : core [mem/q_malloc.c:159]: qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten(c0c0c000, abcdefed)[0x7ff5a5031a98:0x7ff5a5031ac8]! May 29 12:03:45 kamfree-manager kamailio[8697]: ALERT: core

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, for the moment I added a safety check to prevent crash in such situation: - http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e633ca6b7e748a77825d3208e86bf9bce18944a5 I need to investigate more to discover why the parsed field has null content. Does the crash

[SR-Users] Crash Kamailio 4.1.3

hello, Kamailio 4.1.3 crashed today, with an segmentation fault error : kernel: kamailio[2406]: segfault at 18 ip 00495792 sp 7fff3d9d2d80 error 4 in kamailio[40+275000] Here is the result of BT : #0 0x00495792 in pv_get_strval (msg=0x7fad2cf8a530, param=0x7fad3858c288,

Re: [SR-Users] Crash Kamailio 4.1.3

Hello, can you give the output in gdb for: set print elements 2000 p *msg Cheers, Daniel On 28/05/14 11:48, Igor Potjevlesch wrote: hello, Kamailio 4.1.3 crashed today, with an segmentation fault error : kernel: kamailio[2406]: segfault at 18 ip 00495792 sp 7fff3d9d2d80 error

Re: [SR-Users] Crash Kamailio 4.1.3

Hello Daniel, Here is the result of p *msg : $3 = {id = 128120, pid = 2414, tval = {tv_sec = 1401265832, tv_usec = 5951}, fwd_send_flags = {f = 0 '\000', blst_imask = 0 '\000'}, rpl_send_flags = {f = 0 '\000', blst_imask = 0 '\000'}, first_line = {type = 1, len = 48, u = {request = {method =

Re: [SR-Users] Crash on REGISTER

part de* Pedro Niño *Envoyé :* mercredi 2 avril 2014 02:47 *À :* Kamailio (SER) - Users Mailing List *Objet :* Re: [SR-Users] Crash on REGISTER Looks like its crashing because a special character trying to be parsed, maybe a character used for password? Not sure, but try to use simple

Re: [SR-Users] Crash on REGISTER

Hello, Do you receive my emails? And on the list? Regards, Igor. De : Igor Potjevlesch [mailto:igor.potjevle...@gmail.com] Envoyé : lundi 31 mars 2014 18:34 À : mico...@gmail.com; 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Crash on REGISTER Hello

Re: [SR-Users] Crash on REGISTER

optimized out) at main.c:2566 Regards, Igor. *De :* Igor Potjevlesch [mailto:igor.potjevle...@gmail.com] *Envoyé :* samedi 29 mars 2014 14:28 *À :* mico...@gmail.com; 'Kamailio (SER) - Users Mailing List' *Objet :* RE: [SR-Users] Crash on REGISTER Hello Daniel, Thank you for your

Re: [SR-Users] Crash on REGISTER

' Objet : RE: [SR-Users] Crash on REGISTER Hello Daniel, Looks that GDB works after all. Here is the result of a BT: #0 0x0030f2230f30 in escape_string_for_mysql () from /usr/lib64/mysql/libmysqlclient.so.16 #1 0x0030f22269c1 in mysql_real_escape_string () from /usr/lib64/mysql

  1   2   >