date:20180413

Re: [SR-Users] Kamailio 4.2.8 has crashed

2018-04-13 Thread igor.potjevlesch

Hello Henning,

Thank you !!

Regards,

Igor.

-Message d'origine-
De : Henning Westerholt  
Envoyé : vendredi 13 avril 2018 17:43
À : sr-users@lists.kamailio.org
Cc : igor.potjevle...@gmail.com; mico...@gmail.com
Objet : Re: [SR-Users] Kamailio 4.2.8 has crashed

On Friday, 13 April 2018 09:46:48 CEST igor.potjevle...@gmail.com wrote:
> [..]
> I start to analyse the gap to upgrade to the latest 4.3 or 4.4 or 5.1. 
> And I notice that the source code of PDB module has been changed. But, 
> I didn't found a release note for this changing. Do you know where can I
find this?
> [..]

Hello Igor,

you can find the changes with git log or on github (e.g. for 5.1):
https://github.com/kamailio/kamailio/commits/5.1/src/modules/pdb

Best regards,

Henning



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 4.2.8 has crashed

2018-04-13 Thread Henning Westerholt

On Friday, 13 April 2018 09:46:48 CEST igor.potjevle...@gmail.com wrote:
> [..]
> I start to analyse the gap to upgrade to the latest 4.3 or 4.4 or 5.1. And I
> notice that the source code of PDB module has been changed. But, I didn't
> found a release note for this changing. Do you know where can I find this?
> [..]

Hello Igor,

you can find the changes with git log or on github (e.g. for 5.1):
https://github.com/kamailio/kamailio/commits/5.1/src/modules/pdb

Best regards,

Henning


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 4.2.8 has crashed

2018-04-13 Thread igor.potjevlesch

Hello Daniel,

 

I got a new occurrence last night with the following backtrace, looks like
the same:

(gdb) backtrace

#0  0x7f92366761f7 in raise () from /lib64/libc.so.6

#1  0x7f92366778e8 in abort () from /lib64/libc.so.6

#2  0x0061fb2c in qm_free (qm=0x7f91f4eaf000, p=0x7f92110d0300,
file=0x7f9226dd7072 "dialog: dlg_hash.c", func=0x7f9226dd9aeb
<__FUNCTION__.12761> "destroy_dlg", line=381) at mem/q_malloc.c:474

#3  0x7f9226d6fb62 in destroy_dlg (dlg=0x7f920f775598) at dlg_hash.c:381

#4  0x7f9226d75681 in dlg_unref (dlg=0x7f920f775598, cnt=2) at
dlg_hash.c:874

#5  0x7f9226da14d5 in dlg_ontimeout (tl=0x7f920f7755f8) at
dlg_handlers.c:1488

#6  0x7f9226db1e67 in dlg_timer_routine (ticks=8621904, attr=0x0) at
dlg_timer.c:283

#7  0x004af537 in compat_old_handler (ti=137950479,
tl=0x7f91f7ad8cc8, data=0x7f91f7ad8cc8) at timer.c:1011

#8  0x004aff14 in slow_timer_main () at timer.c:1145

#9  0x0052a2af in main_loop () at main.c:1684

#10 0x0052fe71 in main (argc=7, argv=0x7fff51f21418) at main.c:2581

 

I start to analyse the gap to upgrade to the latest 4.3 or 4.4 or 5.1. And I
notice that the source code of PDB module has been changed. But, I didn't
found a release note for this changing. Do you know where can I find this?

 

Regards,

 

Igor.

 

De : igor.potjevle...@gmail.com  
Envoyé : mercredi 11 avril 2018 17:31
À : mico...@gmail.com; 'Kamailio (SER) - Users Mailing List'

Objet : RE: [SR-Users] Kamailio 4.2.8 has crashed

 

Hello Daniel,

 

Ok, thank you for your feedback. mem_safety is available in 4.2?

 

Regards,

 

Igor.

 

De : Daniel-Constantin Mierla 
> 
Envoyé : mercredi 11 avril 2018 16:06
À : Kamailio (SER) - Users Mailing List  >; igor.potjevle...@gmail.com
 
Objet : Re: [SR-Users] Kamailio 4.2.8 has crashed

 

Hello,

the reason of the crash is a double free, but why it happened is not clear
-- if you want to avoid crashing on double free, you can set mem_safety=1 .

4.2 is rather old to start digging into its code with a very limited spare
time. Maybe you can try with a newer version and see if you can reproduce.

Cheers,
Daniel

 

On 11.04.18 14:32, igor.potjevle...@gmail.com
  wrote:

Hello,

 

I had a crash on one Kamailio instance with the following backtrace:

 

Core was generated by `/usr/local/sbin/kamailio -m 704 -M 128 -P
/run/kamailio/kamailio.pid'.

Program terminated with signal 6, Aborted.

#0  0x7f92366761f7 in raise () from /lib64/libc.so.6

Missing separate debuginfos, use: debuginfo-install
bzip2-libs-1.0.6-13.el7.x86_64 elfutils-libelf-0.168-8.el7.x86_64
glibc-2.17-196.el7_4.2.x86_64 keyutils-libs-1.5.8-3.el7.x86_64
krb5-libs-1.15.1-8.el7.x86_64 libacl-2.2.51-12.el7.x86_64
libattr-2.4.46-12.el7.x86_64 libcap-2.22-9.el7.x86_64
libcom_err-1.42.9-10.el7.x86_64 libdb-5.3.21-21.el7_4.x86_64
libgcc-4.8.5-16.el7_4.1.x86_64 libselinux-2.5-11.el7.x86_64
libstdc++-4.8.5-16.el7_4.1.x86_64
lm_sensors-libs-3.4.0-4.20160601gitf9185e5.el7.x86_64
lua-5.1.4-15.el7.x86_64 mariadb-libs-5.5.56-2.el7.x86_64
net-snmp-agent-libs-5.7.2-28.el7_4.1.x86_64
net-snmp-libs-5.7.2-28.el7_4.1.x86_64 nspr-4.13.1-1.0.el7_3.x86_64
nss-3.28.4-15.el7_4.x86_64 nss-softokn-freebl-3.28.3-8.el7_4.x86_64
nss-util-3.28.4-3.el7.x86_64 openssl-libs-1.0.2k-8.el7.x86_64
pcre-8.32-17.el7.x86_64 perl-libs-5.16.3-292.el7.x86_64
popt-1.13-16.el7.x86_64 rpm-libs-4.11.3-25.el7.x86_64
tcp_wrappers-libs-7.6-77.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64
zlib-1.2.7-17.el7.x86_64

(gdb) backtrace

#0  0x7f92366761f7 in raise () from /lib64/libc.so.6

#1  0x7f92366778e8 in abort () from /lib64/libc.so.6

#2  0x0061fb2c in qm_free (qm=0x7f91f4eaf000, p=0x7f92110d0300,
file=0x7f9226dd7072 "dialog: dlg_hash.c", func=0x7f9226dd9aeb
<__FUNCTION__.12761> "destroy_dlg", line=381) at mem/q_malloc.c:474

#3  0x7f9226d6fb62 in destroy_dlg (dlg=0x7f920f775598) at dlg_hash.c:381

#4  0x7f9226d75681 in dlg_unref (dlg=0x7f920f775598, cnt=2) at
dlg_hash.c:874

#5  0x7f9226da14d5 in dlg_ontimeout (tl=0x7f920f7755f8) at
dlg_handlers.c:1488

#6  0x7f9226db1e67 in dlg_timer_routine (ticks=8621904, attr=0x0) at
dlg_timer.c:283

#7  0x004af537 in compat_old_handler (ti=137950479,
tl=0x7f91f7ad8cc8, data=0x7f91f7ad8cc8) at timer.c:1011

#8  0x004aff14 in slow_timer_main () at timer.c:1145

#9  0x0052a2af in main_loop () at main.c:1684

#10 0x0052fe71 in main (argc=7, argv=0x7fff51f21418) at main.c:2581

(gdb)

 

Is there enough information to understand the reason of the crash?

 

Regards,

 

Igor.





___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org

Re: [SR-Users] Problem with resuming suspended transacation

2018-04-13 Thread Kjeld Flarup

You are suspending in [6039] and resuming in [6092], does these two
processes share memory?

  Kjeld

2018-04-12 11:52 GMT+02:00 Arik Halperin :

> Hello,
>
>
>
> I’m trying to resume a suspended transaction, but keep getting this error:
>
>
>
> WARNING: tm [t_suspend.c:193]: t_continue(): transaction is not suspended
> [20608:1256194941]
>
> WARNING: tmx [tmx_mod.c:686]: w_t_continue(): resuming the processing of
> transaction [20608:1256194941] failed
>
> WARNING: tm [t_lookup.c:1483]: t_unref(): script writer didn't release
> transaction
>
>
>
>
>
> I’m implementing push handling, in INVITE I do the following:
>
>
>
> route[INVITE] {
>
>   *if (!lookup("location"))*
>
>   {
>
>
>
>send_reply("100", "Trying");
>
> record_route();
>
> *route(SUSPEND);*
>
>   }
>
>   else
>
>   {
>
>  # NAT detection
>
>  route(NATMANAGE);
>
>  if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY");
>
> record_route();
>
>  t_relay();
>
>  ts_store();
>
>  $sht(vtp=>stored::$rU) = 1;
>
> }
>
> route(SENDPUSH);
>
> }
>
>
>
> # suspend the transaction
>
> route[SUSPEND] {
>
>
>
> *if(!t_suspend()) *//Transaction is suspended!
>
> {
>
>   exit;
>
> }
>
> $sht(vtp=>join::$rU) = "" + $T(id_index) + ":" +$T(id_label);
>
> }
>
>
>
> In Register I call the PUSHJOIN route:
>
>
>
> # append branches or resume the transaction
>
> route[PUSHJOIN] {
>
> $var(hjoin) = 0;
>
> lock("$tU");
>
> $var(hjoin) = $sht(vtp=>join::$tU);
>
> $var(hstored) = $sht(vtp=>stored::$tU);
>
> $sht(vtp=>join::$tU) = $null;
>
> unlock("$tU");
>
> if ($var(hjoin)==0)
>
> {
>
> if ($var(hstored))
>
> ts_append("location", "$tu");
>
> return;
>
> }
>
> $var(id_index) = $(var(hjoin){s.select,0,:}{s.int});
>
> $var(id_label) = $(var(hjoin){s.select,1,:}{s.int});
>
> ($var(hjoin))\n");
>
> * t_continue("$var(id_index)", "$var(id_label)", "INVRESUME");*
>
> }
>
>
>
>
>
> For some reason I keep getting:
>
>
>
> Apr 12 12:37:11 kamprod /usr/local/sbin/kamailio[6039]: ERROR:

Re: [SR-Users] Kamailio + tls

2018-04-13 Thread Do Quang Trung

1/ I built openssl-1.0.2n with engine supported.
2/ in file tls_domain.c i modified C code in function static int
set_cipher_list(tls_domain_t* d)
cipher_list="GOST-GOST89MAC" and rebuild kamailio
i config kamailio support tls with self-signed as in help url:
https://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates
3/ start kamailio and error as follow
 0(15353) ERROR: tls [tls_domain.c:652]: set_cipher_list(): TLSs:
Failure to set SSL context cipher list "GOST-GOST89MAC"
 0(15353) ERROR:  [core/sr_module.c:942]: init_mod_child(): error
while initializing module tls (/usr/local/lib64/kamailio/modules/tls.so)
(idx: 0 rank: -127 desc: [main])
Plz help!

On Thu, Apr 12, 2018 at 1:18 PM, Henning Westerholt  wrote:

> On Wednesday, 11 April 2018 13:49:35 CEST Do Quang Trung wrote:
> > Plz help me.
> > I want config kamailio 5.1 support tls using gost89 cipher to protect
> data.
>
> Hello,
>
> could you share a bit more details:
>
> - what have you already done
> - have you already tried to configure it
> - what is the exact issue that you are facing?
>
> Best regards,
>
> Henning
>

-- 
Full Name:Do Quang Trung
Mobile: +84916067763
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Problem with resuming suspended transacation

2018-04-13 Thread Arik Halperin

Hello,

I’m trying to resume a suspended transaction, but keep getting this error:

WARNING: tm [t_suspend.c:193]: t_continue(): transaction is not suspended 
[20608:1256194941]
WARNING: tmx [tmx_mod.c:686]: w_t_continue(): resuming the processing of 
transaction [20608:1256194941] failed
WARNING: tm [t_lookup.c:1483]: t_unref(): script writer didn't release 
transaction


I’m implementing push handling, in INVITE I do the following:

route[INVITE] {
  if (!lookup("location"))
  {

   send_reply("100", "Trying");
record_route();
route(SUSPEND);
  }
  else
  {
 # NAT detection
 route(NATMANAGE);
 if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY");
record_route();
 t_relay();
 ts_store();
 $sht(vtp=>stored::$rU) = 1;
}
route(SENDPUSH);
}

# suspend the transaction
route[SUSPEND] {

if(!t_suspend()) //Transaction is suspended!
{
  exit;
}
$sht(vtp=>join::$rU) = "" + $T(id_index) + ":" +$T(id_label);
}

In Register I call the PUSHJOIN route:

# append branches or resume the transaction
route[PUSHJOIN] {
$var(hjoin) = 0;
lock("$tU");
$var(hjoin) = $sht(vtp=>join::$tU);
$var(hstored) = $sht(vtp=>stored::$tU);
$sht(vtp=>join::$tU) = $null;
unlock("$tU");
if ($var(hjoin)==0)
{
if ($var(hstored))
ts_append("location", "$tu");
return;
}
$var(id_index) = $(var(hjoin){s.select,0,:}{s.int});
$var(id_label) = $(var(hjoin){s.select,1,:}{s.int});
($var(hjoin))\n");
 t_continue("$var(id_index)", "$var(id_label)", "INVRESUME");
}


For some reason I keep getting:

Apr 12 12:37:11 kamprod /usr/local/sbin/kamailio[6039]: ERROR:

Re: [SR-Users] Kamailio 4.2.8 has crashed

Re: [SR-Users] Kamailio 4.2.8 has crashed

Re: [SR-Users] Kamailio 4.2.8 has crashed

Re: [SR-Users] Problem with resuming suspended transacation

Re: [SR-Users] Kamailio + tls

[SR-Users] Problem with resuming suspended transacation

6 matches

Site Navigation

Mail list logo

Footer information