Re: [SR-Users] Need help analyze crash
Thanks for the suggestion. We have an AMI image with just libssl1.1 and will test with that. On Thu, Jun 3, 2021 at 10:12 AM Daniel-Constantin Mierla wrote: > Well, probably a misunderstanding: the issue was observed on OSes having > the two libssl 1.0 & 1.1 versions, but it does not mean (it was not proved) > that the problem was created by having the two version were installed at > the same time. I would rather think it was more that libssl1.1 was not very > mature at that moment when OSes shipped both of them. > > If I would make a suggestion, that would be to use an OS version that > comes only with one of them by default. Think like: when libssl1.0 was > completely removed from an OS, the libssl1.1 was more tested/stable. > > Cheers, > Daniel > On 03.06.21 15:58, Andrew Chen wrote: > > No blaming here. :). Just looking for answers. > > After chatting with my peers on options around this, we are going to > remove libssl1.0 and just have libssl1.1 running. > > Thanks again for you input. > > On Thu, Jun 3, 2021 at 9:48 AM Daniel-Constantin Mierla > wrote: > >> Again, not to be blamed later: I am not sure you face the same kind of >> issue like reported in the past. I was looking at it from the perspective >> that db_mysql and carrierroute modules were not touched that much in the >> 5.4.x series recently. >> >> The libssl did a lot of internal/api changes between 1.0 and 1.1, so for >> a few past years many libs and apps (including kamailio) faced some >> "strange" crashes/behaviours. Now seems stabilized and, at least on debian >> 10, there were no related open issues recently. In the future we may need >> to make --atexit=no the default (maybe needs to be set even on latest >> ubuntu 20.04), it's the last I remember that surfaced and it appeared after >> a minor version upgrade of libssl1.1, iirc. >> >> Cheers, >> Daniel >> On 03.06.21 15:31, Andrew Chen wrote: >> >> Thanks Daniel. >> It sounds like upgrading to a newer Ubuntu seems like the cleanest way of >> resolving this issue. >> >> On Thu, Jun 3, 2021 at 8:58 AM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> Hello, >>> >>> it is not related to kamailio tls being compiled with libssl1.1. The >>> issues were observed on the systems having both libssl1.0 (which was >>> somehow the default choice) and libssl1.1. I got the chance to test a bit >>> and it was still crashing even I compiled manually with libssl1.1. I didn't >>> dig much in the external libraries given that upgrading OS seemed to fix >>> it. There is a mod param for db_mysql that you can try to play with: >>> opt_ssl_mode - I don't recall solving much for mysql servers requiring tls. >>> >>> Otherwise, on a different direction: if you can get mariadb client >>> library, you can try to compile kamailio against it (the db_mysql module) >>> -- if the MySQL server is on a remote system, it should work. >>> >>> I can't confirm it is same issue, but if you upgraded in kamailio 5.4.x >>> series, there were no changes to carrierroute or db_mysql to >>> >>> As a side note, for newer operating systems and newer libssl, it may >>> also require to set --atexit cli parameter for kamailio. >>> >>> Cheers, >>> Daniel >>> On 03.06.21 14:42, Andrew Chen wrote: >>> >>> Hi Daniel, >>> >>> I just confirmed mysql is compiled using libssl.so.1.1. >>> >>> As for the other kamailio packages, I only see two that are installed >>> where both are depends on libssl1.1 >>> >>> kamailio-tls-modules:amd64 >>> >>> *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libcurl4 (>= 7.16.2), >>> libssl1.1 (>= 1.1.0) >>> >>> >>> >>> kamailio-websocket-modules:amd64 >>> >>> *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libssl1.1 (>= 1.1.0), >>> libunistring2 (>= 0.9.7) >>> >>> So in my case here there shouldn't be any conflict with mysql client >>> libssl version? >>> >>> Thanks. >>> >>> >>> On Thu, Jun 3, 2021 at 3:10 AM Daniel-Constantin Mierla < >>> mico...@gmail.com> wrote: >>> >>>> Hello, >>>> >>>> I think the relevant here are the client library. I asked about mysql >>>> vs mariadb because some distro had (meta-)packages named mysql but >>>> installing mariadb. Debian at some point switched to something like >>>>
Re: [SR-Users] Need help analyze crash
No blaming here. :). Just looking for answers. After chatting with my peers on options around this, we are going to remove libssl1.0 and just have libssl1.1 running. Thanks again for you input. On Thu, Jun 3, 2021 at 9:48 AM Daniel-Constantin Mierla wrote: > Again, not to be blamed later: I am not sure you face the same kind of > issue like reported in the past. I was looking at it from the perspective > that db_mysql and carrierroute modules were not touched that much in the > 5.4.x series recently. > > The libssl did a lot of internal/api changes between 1.0 and 1.1, so for a > few past years many libs and apps (including kamailio) faced some "strange" > crashes/behaviours. Now seems stabilized and, at least on debian 10, there > were no related open issues recently. In the future we may need to make > --atexit=no the default (maybe needs to be set even on latest ubuntu > 20.04), it's the last I remember that surfaced and it appeared after a > minor version upgrade of libssl1.1, iirc. > > Cheers, > Daniel > On 03.06.21 15:31, Andrew Chen wrote: > > Thanks Daniel. > It sounds like upgrading to a newer Ubuntu seems like the cleanest way of > resolving this issue. > > On Thu, Jun 3, 2021 at 8:58 AM Daniel-Constantin Mierla > wrote: > >> Hello, >> >> it is not related to kamailio tls being compiled with libssl1.1. The >> issues were observed on the systems having both libssl1.0 (which was >> somehow the default choice) and libssl1.1. I got the chance to test a bit >> and it was still crashing even I compiled manually with libssl1.1. I didn't >> dig much in the external libraries given that upgrading OS seemed to fix >> it. There is a mod param for db_mysql that you can try to play with: >> opt_ssl_mode - I don't recall solving much for mysql servers requiring tls. >> >> Otherwise, on a different direction: if you can get mariadb client >> library, you can try to compile kamailio against it (the db_mysql module) >> -- if the MySQL server is on a remote system, it should work. >> >> I can't confirm it is same issue, but if you upgraded in kamailio 5.4.x >> series, there were no changes to carrierroute or db_mysql to >> >> As a side note, for newer operating systems and newer libssl, it may also >> require to set --atexit cli parameter for kamailio. >> >> Cheers, >> Daniel >> On 03.06.21 14:42, Andrew Chen wrote: >> >> Hi Daniel, >> >> I just confirmed mysql is compiled using libssl.so.1.1. >> >> As for the other kamailio packages, I only see two that are installed >> where both are depends on libssl1.1 >> >> kamailio-tls-modules:amd64 >> >> *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libcurl4 (>= 7.16.2), >> libssl1.1 (>= 1.1.0) >> >> >> >> kamailio-websocket-modules:amd64 >> >> *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libssl1.1 (>= 1.1.0), >> libunistring2 (>= 0.9.7) >> >> So in my case here there shouldn't be any conflict with mysql client >> libssl version? >> >> Thanks. >> >> >> On Thu, Jun 3, 2021 at 3:10 AM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> Hello, >>> >>> I think the relevant here are the client library. I asked about mysql vs >>> mariadb because some distro had (meta-)packages named mysql but installing >>> mariadb. Debian at some point switched to something like >>> default-mysql-client... >>> >>> Based on backtrace, the crashes would prevent kamailio to start, as >>> carrierroute_db_open() is used in mod_init/child_init callbacks. >>> >>> A variant you could try is the use of mysql-proxy to bridge from a local >>> unix socket to remote mysql, so kamailio connects to mysql server via >>> local unix socket and by that won't use libssl. >>> >>> First you can check with ldd if mysql client libraries are compiled >>> against libssl1.1 and the libssl1.0 is also used for other packages. >>> >>> Cheers, >>> Daniel >>> On 02.06.21 21:56, Andrew Chen wrote: >>> >>> Hi Daniel, >>> So our DB is in rds and this is what I can gather: >>> >>> +-+--+ >>> >>> | Variable_name | Value| >>> >>> +-+--+ >>> >>> | innodb_version | 5.6.34 | >>> >>> | protocol_version| 10 |
Re: [SR-Users] Need help analyze crash
Thanks Daniel. It sounds like upgrading to a newer Ubuntu seems like the cleanest way of resolving this issue. On Thu, Jun 3, 2021 at 8:58 AM Daniel-Constantin Mierla wrote: > Hello, > > it is not related to kamailio tls being compiled with libssl1.1. The > issues were observed on the systems having both libssl1.0 (which was > somehow the default choice) and libssl1.1. I got the chance to test a bit > and it was still crashing even I compiled manually with libssl1.1. I didn't > dig much in the external libraries given that upgrading OS seemed to fix > it. There is a mod param for db_mysql that you can try to play with: > opt_ssl_mode - I don't recall solving much for mysql servers requiring tls. > > Otherwise, on a different direction: if you can get mariadb client > library, you can try to compile kamailio against it (the db_mysql module) > -- if the MySQL server is on a remote system, it should work. > > I can't confirm it is same issue, but if you upgraded in kamailio 5.4.x > series, there were no changes to carrierroute or db_mysql to > > As a side note, for newer operating systems and newer libssl, it may also > require to set --atexit cli parameter for kamailio. > > Cheers, > Daniel > On 03.06.21 14:42, Andrew Chen wrote: > > Hi Daniel, > > I just confirmed mysql is compiled using libssl.so.1.1. > > As for the other kamailio packages, I only see two that are installed > where both are depends on libssl1.1 > > kamailio-tls-modules:amd64 > > *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libcurl4 (>= 7.16.2), > libssl1.1 (>= 1.1.0) > > > > kamailio-websocket-modules:amd64 > > *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libssl1.1 (>= 1.1.0), > libunistring2 (>= 0.9.7) > > So in my case here there shouldn't be any conflict with mysql client > libssl version? > > Thanks. > > > On Thu, Jun 3, 2021 at 3:10 AM Daniel-Constantin Mierla > wrote: > >> Hello, >> >> I think the relevant here are the client library. I asked about mysql vs >> mariadb because some distro had (meta-)packages named mysql but installing >> mariadb. Debian at some point switched to something like >> default-mysql-client... >> >> Based on backtrace, the crashes would prevent kamailio to start, as >> carrierroute_db_open() is used in mod_init/child_init callbacks. >> >> A variant you could try is the use of mysql-proxy to bridge from a local >> unix socket to remote mysql, so kamailio connects to mysql server via >> local unix socket and by that won't use libssl. >> >> First you can check with ldd if mysql client libraries are compiled >> against libssl1.1 and the libssl1.0 is also used for other packages. >> >> Cheers, >> Daniel >> On 02.06.21 21:56, Andrew Chen wrote: >> >> Hi Daniel, >> So our DB is in rds and this is what I can gather: >> >> +-+--+ >> >> | Variable_name | Value| >> >> +-+--+ >> >> | innodb_version | 5.6.34 | >> >> | protocol_version| 10 | >> >> | slave_type_conversions | | >> >> | version | 5.6.34-log | >> >> | version_comment | MySQL Community Server (GPL) | >> >> | version_compile_machine | x86_64 | >> >> | version_compile_os | Linux| >> >> +-+--+ >> >> >> The mysql server/client library we received from my apt-cache madison >> output earlier. >> >> >> I don't know if upgrading to 20.04 is an option. >> >> >> Given this said, what are the symptoms of these crashes? I'm guessing >> one of them is a brief disconnect from the DB for >> dialplan/dispatcher/carrierroute lookup? >> >> >> Thanks. >> >> On Wed, Jun 2, 2021 at 3:38 PM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> Hello, >>> >>> did you upgrade the Kamailio only or also mysql server/client library? >>> Is it Oracle's MySQL or MariaDB? >>> >>> A while ago, there were a few reports of problems with mysql-client >>> (Oracle) library on Ubuntu 16.04 and 18.04, which typically happened after >>> upgrades of the library, as I understood, the upgrade brought in a >>> dependency on libssl 1.1, while libssl1.0 was used by most of the o
Re: [SR-Users] Need help analyze crash
Hi Daniel, I just confirmed mysql is compiled using libssl.so.1.1. As for the other kamailio packages, I only see two that are installed where both are depends on libssl1.1 kamailio-tls-modules:amd64 *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libcurl4 (>= 7.16.2), libssl1.1 (>= 1.1.0) kamailio-websocket-modules:amd64 *Depends*: kamailio (= 5.4.5), libc6 (>= 2.14), libssl1.1 (>= 1.1.0), libunistring2 (>= 0.9.7) So in my case here there shouldn't be any conflict with mysql client libssl version? Thanks. On Thu, Jun 3, 2021 at 3:10 AM Daniel-Constantin Mierla wrote: > Hello, > > I think the relevant here are the client library. I asked about mysql vs > mariadb because some distro had (meta-)packages named mysql but installing > mariadb. Debian at some point switched to something like > default-mysql-client... > > Based on backtrace, the crashes would prevent kamailio to start, as > carrierroute_db_open() is used in mod_init/child_init callbacks. > > A variant you could try is the use of mysql-proxy to bridge from a local > unix socket to remote mysql, so kamailio connects to mysql server via > local unix socket and by that won't use libssl. > > First you can check with ldd if mysql client libraries are compiled > against libssl1.1 and the libssl1.0 is also used for other packages. > > Cheers, > Daniel > On 02.06.21 21:56, Andrew Chen wrote: > > Hi Daniel, > So our DB is in rds and this is what I can gather: > > +-+--+ > > | Variable_name | Value| > > +-+--+ > > | innodb_version | 5.6.34 | > > | protocol_version| 10 | > > | slave_type_conversions | | > > | version | 5.6.34-log | > > | version_comment | MySQL Community Server (GPL) | > > | version_compile_machine | x86_64 | > > | version_compile_os | Linux| > > +-+--+ > > > The mysql server/client library we received from my apt-cache madison > output earlier. > > > I don't know if upgrading to 20.04 is an option. > > > Given this said, what are the symptoms of these crashes? I'm guessing one > of them is a brief disconnect from the DB for > dialplan/dispatcher/carrierroute lookup? > > > Thanks. > > On Wed, Jun 2, 2021 at 3:38 PM Daniel-Constantin Mierla > wrote: > >> Hello, >> >> did you upgrade the Kamailio only or also mysql server/client library? Is >> it Oracle's MySQL or MariaDB? >> >> A while ago, there were a few reports of problems with mysql-client >> (Oracle) library on Ubuntu 16.04 and 18.04, which typically happened after >> upgrades of the library, as I understood, the upgrade brought in a >> dependency on libssl 1.1, while libssl1.0 was used by most of the other >> packages, resulting in mixed deployments. Upgrading to 20.04 seemed to >> solve it, as it came with libssl1.1 only. >> >> Cheers, >> Daniel >> On 02.06.21 20:51, Andrew Chen wrote: >> >> Hi all, >> >> Today I upgraded Kamailio to 5.4.5 and a random crash was just reported >> in our crash monitoring script. Below is the output of the crash: >> >> #3 0x7fa149ebe58d in ?? () from >> /usr/lib/x86_64-linux-gnu/kamailio/modules/tls.so >> >> #4 0x7fa14989e277 in ERR_clear_error () from >> /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 >> >> #5 0x7fa149933d81 in X509_STORE_set_default_paths () from >> /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 >> >> #6 0x7fa10310d374 in ?? () from >> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 >> >> #7 0x7fa10310d9f3 in ?? () from >> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 >> >> #8 0x7fa1030e0427 in mysql_real_connect () from >> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 >> >> #9 0x7fa10368428c in db_mysql_new_connection () from >> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so >> >> #10 0x7fa1501f96dc in db_do_init2 () from >> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 >> >> #11 0x7fa1501f83f9 in db_do_init () from >> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 >> >> #12 0x7fa103689710 in db_mysql_init () from >> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so >> >> #13 0x7fa15062d35f in carrierroute_db_open () from >> /usr/lib/x86_64-linux-gnu/kamailio/modules/
Re: [SR-Users] Need help analyze crash
Hi Daniel, So our DB is in rds and this is what I can gather: +-+--+ | Variable_name | Value| +-+--+ | innodb_version | 5.6.34 | | protocol_version| 10 | | slave_type_conversions | | | version | 5.6.34-log | | version_comment | MySQL Community Server (GPL) | | version_compile_machine | x86_64 | | version_compile_os | Linux| +-+--+ The mysql server/client library we received from my apt-cache madison output earlier. I don't know if upgrading to 20.04 is an option. Given this said, what are the symptoms of these crashes? I'm guessing one of them is a brief disconnect from the DB for dialplan/dispatcher/carrierroute lookup? Thanks. On Wed, Jun 2, 2021 at 3:38 PM Daniel-Constantin Mierla wrote: > Hello, > > did you upgrade the Kamailio only or also mysql server/client library? Is > it Oracle's MySQL or MariaDB? > > A while ago, there were a few reports of problems with mysql-client > (Oracle) library on Ubuntu 16.04 and 18.04, which typically happened after > upgrades of the library, as I understood, the upgrade brought in a > dependency on libssl 1.1, while libssl1.0 was used by most of the other > packages, resulting in mixed deployments. Upgrading to 20.04 seemed to > solve it, as it came with libssl1.1 only. > > Cheers, > Daniel > On 02.06.21 20:51, Andrew Chen wrote: > > Hi all, > > Today I upgraded Kamailio to 5.4.5 and a random crash was just reported in > our crash monitoring script. Below is the output of the crash: > > #3 0x7fa149ebe58d in ?? () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/tls.so > > #4 0x7fa14989e277 in ERR_clear_error () from > /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 > > #5 0x7fa149933d81 in X509_STORE_set_default_paths () from > /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 > > #6 0x7fa10310d374 in ?? () from > /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 > > #7 0x7fa10310d9f3 in ?? () from > /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 > > #8 0x7fa1030e0427 in mysql_real_connect () from > /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 > > #9 0x7fa10368428c in db_mysql_new_connection () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so > > #10 0x7fa1501f96dc in db_do_init2 () from > /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 > > #11 0x7fa1501f83f9 in db_do_init () from > /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 > > #12 0x7fa103689710 in db_mysql_init () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so > > #13 0x7fa15062d35f in carrierroute_db_open () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so > > #14 0x7fa1506719c6 in ?? () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so > > > Is this crash due to libcrypto or mysql client? > Currently I have the following mysql client installed on the kamailio > instance: > > ii lib*mysql*client20:amd64 5.7.34-0ubuntu0.18.04.1 > amd64MySQL database client library > > ii *mysql*-client 5.7.34-0ubuntu0.18.04.1 > all MySQL database client (metapackage depending on the > latest version) > > ii *mysql*-client-5.7 5.7.34-0ubuntu0.18.04.1 > amd64MySQL database client binaries > > ii *mysql*-client-core-5.75.7.34-0ubuntu0.18.04.1 > amd64MySQL database core client binaries > > ii *mysql*-common 5.8+1.0.4 > all MySQL database common files, e.g. /etc/*mysql*/my.cnf > > root@ashintgtpsg51:/var/lib/cores # apt-cache madison mysql-client > > mysql-client | 5.7.34-0ubuntu0.18.04.1 | > http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 > Packages > > mysql-client | 5.7.34-0ubuntu0.18.04.1 | http://security.ubuntu.com/ubuntu > bionic-security/main amd64 Packages > > mysql-client | 5.7.21-1ubuntu1 | > http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > root@ashintgtpsg51:/var/lib/cores # > > > Any suggestions would be greatly appreciated. > Thanks in advance. > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby n
[SR-Users] Need help analyze crash
Hi all, Today I upgraded Kamailio to 5.4.5 and a random crash was just reported in our crash monitoring script. Below is the output of the crash: #3 0x7fa149ebe58d in ?? () from /usr/lib/x86_64-linux-gnu/kamailio/modules/tls.so #4 0x7fa14989e277 in ERR_clear_error () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #5 0x7fa149933d81 in X509_STORE_set_default_paths () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #6 0x7fa10310d374 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #7 0x7fa10310d9f3 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #8 0x7fa1030e0427 in mysql_real_connect () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #9 0x7fa10368428c in db_mysql_new_connection () from /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so #10 0x7fa1501f96dc in db_do_init2 () from /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 #11 0x7fa1501f83f9 in db_do_init () from /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1 #12 0x7fa103689710 in db_mysql_init () from /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so #13 0x7fa15062d35f in carrierroute_db_open () from /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so #14 0x7fa1506719c6 in ?? () from /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so Is this crash due to libcrypto or mysql client? Currently I have the following mysql client installed on the kamailio instance: ii lib*mysql*client20:amd64 5.7.34-0ubuntu0.18.04.1 amd64MySQL database client library ii *mysql*-client 5.7.34-0ubuntu0.18.04.1 all MySQL database client (metapackage depending on the latest version) ii *mysql*-client-5.7 5.7.34-0ubuntu0.18.04.1 amd64MySQL database client binaries ii *mysql*-client-core-5.75.7.34-0ubuntu0.18.04.1 amd64MySQL database core client binaries ii *mysql*-common 5.8+1.0.4 all MySQL database common files, e.g. /etc/*mysql*/my.cnf root@ashintgtpsg51:/var/lib/cores # apt-cache madison mysql-client mysql-client | 5.7.34-0ubuntu0.18.04.1 | http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages mysql-client | 5.7.34-0ubuntu0.18.04.1 | http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages mysql-client | 5.7.21-1ubuntu1 | http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@ashintgtpsg51:/var/lib/cores # Any suggestions would be greatly appreciated. Thanks in advance. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 5.4 dependency package question
Ok I'll try those steps. Thanks. On Wed, May 19, 2021 at 10:46 AM Daniel-Constantin Mierla wrote: > Maybe switch to hard copy as instructed by Victor Seva and use > dpkg-buildpackage directly: > > On the root of the kamailio repository: > > cp -r pkg/kamailio/deb/bionic debian > dpkg-buildpackage -rfakeroot -tc -uc -us > On 19.05.21 16:38, Daniel-Constantin Mierla wrote: > > Hello, > > is quite strange that you get those dependency requirements. I do not have > a bionic, I do it for buster and they are not required. > > Searching for gcj-jdk on specs dirs results in: > > ag gcj-jdk pkg/kamailio/deb/ > pkg/kamailio/deb/debian/backports/bionic > 21:# No app_java due lack of gcj-jdk > 22:sed -i -e '/gcj-jdk/d' -e '/^Package: kamailio-java-modules/,/^$/d' \ > > pkg/kamailio/deb/debian/backports/sid > 21:# No app_java due lack of gcj-jdk > 22:sed -i -e '/gcj-jdk/d' -e '/^Package: kamailio-java-modules/,/^$/d' \ > > pkg/kamailio/deb/debian/backports/bullseye > 21:# No app_java due lack of gcj-jdk > 22:sed -i -e '/gcj-jdk/d' -e '/^Package: kamailio-java-modules/,/^$/d' \ > > pkg/kamailio/deb/debian/backports/focal > 21:# No app_java due lack of gcj-jdk > 22:sed -i -e '/gcj-jdk/d' -e '/^Package: kamailio-java-modules/,/^$/d' \ > > pkg/kamailio/deb/debian/control > 17: gcj-jdk, > > pkg/kamailio/deb/debian/backports/buster > 21:# No app_java due lack of gcj-jdk > 22:sed -i -e '/gcj-jdk/d' -e '/^Package: kamailio-java-modules/,/^$/d' \ > > pkg/kamailio/deb/precise/control > 15: gcj-jdk, > > pkg/kamailio/deb/stretch/control > 17: gcj-jdk, > > pkg/kamailio/deb/wheezy/control > 15: gcj-jdk, > > pkg/kamailio/deb/jessie/control > 16: gcj-jdk, > > pkg/kamailio/deb/xenial/control > 16: gcj-jdk, > > pkg/kamailio/deb/trusty/control > 15: gcj-jdk, > > So it is not in pkg/kamailio/deb/bionic/control (also not in the folder > for buster), you should not get it if debian symlink is pointing correctly. > I do the steps: > > ln -s pkg/kamailio/deb/buster debian > make deb > > every time I do a public kamailio release to be sure packages build fine > (independent of deb.kamailio.org portal) and no java/jdk is requested as > dependency. Can you try to run manually on a VM or docker with bionic? > > Cheers, > Daniel > On 19.05.21 16:16, Andrew Chen wrote: > > Hi Henning, > > Thanks for the response. > > From what I can see, I am not seeing that module. Below is my > INCLUDE_MODULES list: > > INCLUDE_MODULES="exec rtpengine topoh carrierroute statsd dialplan kex tm > tmx sl rr pv maxfwd usrloc textops sdpops siputils xlog sanity ctl acc > dispatcher cfgutils permissions domain presence presence_xml nathelper > dialog tls htable pike db_mysql userblacklist sqlops websocket xhttp > siptrace tcpops jsonrpcs rtimer" > > --Andy > > On Wed, May 19, 2021 at 8:08 AM Henning Westerholt wrote: > >> Hi Andrew, >> >> >> >> just remove the app_java module which introduce this dependency if you do >> not use it. >> >> >> >> Cheers, >> >> >> >> Henning >> >> >> >> -- >> >> Henning Westerholt – https://skalatan.de/blog/ >> >> Kamailio services – https://gilawa.com >> >> >> >> *From:* sr-users *On Behalf Of *Andrew >> Chen >> *Sent:* Wednesday, May 19, 2021 1:59 PM >> *To:* Daniel-Constantin Mierla >> *Cc:* Kamailio (SER) - Users Mailing List >> *Subject:* Re: [SR-Users] 5.4 dependency package question >> >> >> >> Hi guys, >> >> >> >> Does anyone have any updates on this? >> >> >> >> More so, can this package dependency be ignored if I am not using Java >> for Kamailio configuration? >> >> >> >> Thanks >> >> --Andy >> >> >> >> On Mon, May 17, 2021 at 1:56 PM Andrew Chen wrote: >> >> Yes. My Jenkins job runs the symlink step everytime: >> >> >> >> sudo ln -s pkg/kamailio/deb/bionic debian >> >> ## Create debian package >> sudo make deb >> >> >> >> I do this in the main kamailio install directory. >> >> >> >> On Mon, May 17, 2021 at 1:09 PM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >> Is it debian symlink pointing to the right folder in pkg/kamailio/deb/ >> for you distribution? As I said, it gets deleted and running 'make deb' >> again with (re-)create the symlink to the 'debian' folder. In other words, >> create symlink always before running 'make deb'. >> >> Cheers, >> Da
Re: [SR-Users] 5.4 dependency package question
Hi Henning, Thanks for the response. >From what I can see, I am not seeing that module. Below is my INCLUDE_MODULES list: INCLUDE_MODULES="exec rtpengine topoh carrierroute statsd dialplan kex tm tmx sl rr pv maxfwd usrloc textops sdpops siputils xlog sanity ctl acc dispatcher cfgutils permissions domain presence presence_xml nathelper dialog tls htable pike db_mysql userblacklist sqlops websocket xhttp siptrace tcpops jsonrpcs rtimer" --Andy On Wed, May 19, 2021 at 8:08 AM Henning Westerholt wrote: > Hi Andrew, > > > > just remove the app_java module which introduce this dependency if you do > not use it. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* sr-users *On Behalf Of *Andrew > Chen > *Sent:* Wednesday, May 19, 2021 1:59 PM > *To:* Daniel-Constantin Mierla > *Cc:* Kamailio (SER) - Users Mailing List > *Subject:* Re: [SR-Users] 5.4 dependency package question > > > > Hi guys, > > > > Does anyone have any updates on this? > > > > More so, can this package dependency be ignored if I am not using Java for > Kamailio configuration? > > > > Thanks > > --Andy > > > > On Mon, May 17, 2021 at 1:56 PM Andrew Chen wrote: > > Yes. My Jenkins job runs the symlink step everytime: > > > > sudo ln -s pkg/kamailio/deb/bionic debian > > ## Create debian package > sudo make deb > > > > I do this in the main kamailio install directory. > > > > On Mon, May 17, 2021 at 1:09 PM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > > Is it debian symlink pointing to the right folder in pkg/kamailio/deb/ for > you distribution? As I said, it gets deleted and running 'make deb' again > with (re-)create the symlink to the 'debian' folder. In other words, create > symlink always before running 'make deb'. > > Cheers, > Daniel > > On 17.05.21 17:44, Andrew Chen wrote: > > So after looking at the build logs, it seems I'm still facing these > dependency errors: > > > > The following packages have unmet dependencies: > > gcj-jdk : Depends: libgcj-common (>= 1:6.4-3ubuntu1) but it is not > installable > >Depends: gcj-jre (>= 4:6.4.0-3ubuntu1) but it is not installable > >Depends: gcj-6-jdk (>= 6.4.0-1~) but it is not installable > > The following packages have unmet dependencies: > > libval-dev : Depends: libval15 (= 2.2-4) but it is not installable > > How important are these libraries and which module uses them? > > > > On Mon, May 17, 2021 at 11:34 AM Andrew Chen wrote: > > Hey guys. The linking of the directory worked! Thanks again for your > help. > > > > On Mon, May 17, 2021 at 7:59 AM Andrew Chen wrote: > > Thanks guys! I will try these out today. > > > > On Mon, May 17, 2021 at 5:08 AM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > > > On 17.05.21 09:49, Victor Seva wrote: > > On 5/14/21 2:09 PM, Andrew Chen wrote: > >> Hi Daniel, > >> > >> Yes. These are the steps I took: > >> > >> ## git clone kamailio repository > >> cd $INSTALLDIR > >> sudo git clone https://github.com/kamailio/kamailio > >> <https://github.com/kamailio/kamailio> kamailio > >> cd kamailio > >> sudo git checkout 5.4 > >> > >> ## Make config files with included modules list > >> sudo make include_modules="$INCLUDE_MODULES" cfg > >> > >> ## Compile Kamailio > >> sudo make mode=debug > >> > >> cd pkg/kamailio/deb > >> > >> ## Create debian package > >> sudo dpkg-buildpackage > >> > >> > >> Hi Victor, > >> > >> Yes, this is the version of Ubuntu we are using: > >> > >> debhttp://deb.kamailio.org/kamailio54 > >> <http://deb.kamailio.org/kamailio54> bionic main > >> deb-srchttp://deb.kamailio.org/kamailio54 > >> <http://deb.kamailio.org/kamailio54> bionic main > > > > If you're using bionic, then use bionic directory at pkg/kamailio/deb > > as your debian dir. > > > > On the root of the kamailio repository: > > # cp -r pkg/kamailio/deb/bionic debian > > # dpkg-buildpackage -rfakeroot -tc -uc -us > > For what it worth, we have also a target in the Makefile for building > debs, next is what I typically use to test debs building before a release: > > ln -s pkg/kamailio/deb/bionic debian > make deb > > Note that debian syml
Re: [SR-Users] 5.4 dependency package question
Hi guys, Does anyone have any updates on this? More so, can this package dependency be ignored if I am not using Java for Kamailio configuration? Thanks --Andy On Mon, May 17, 2021 at 1:56 PM Andrew Chen wrote: > Yes. My Jenkins job runs the symlink step everytime: > > sudo ln -s pkg/kamailio/deb/bionic debian > > ## Create debian package > sudo make deb > > I do this in the main kamailio install directory. > > On Mon, May 17, 2021 at 1:09 PM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> Is it debian symlink pointing to the right folder in pkg/kamailio/deb/ >> for you distribution? As I said, it gets deleted and running 'make deb' >> again with (re-)create the symlink to the 'debian' folder. In other words, >> create symlink always before running 'make deb'. >> >> Cheers, >> Daniel >> On 17.05.21 17:44, Andrew Chen wrote: >> >> So after looking at the build logs, it seems I'm still facing these >> dependency errors: >> >> The following packages have unmet dependencies: >> gcj-jdk : Depends: libgcj-common (>= 1:6.4-3ubuntu1) but it is not >> installable >>Depends: gcj-jre (>= 4:6.4.0-3ubuntu1) but it is not installable >>Depends: gcj-6-jdk (>= 6.4.0-1~) but it is not installable >> >> The following packages have unmet dependencies: >> libval-dev : Depends: libval15 (= 2.2-4) but it is not installable >> >> How important are these libraries and which module uses them? >> >> >> On Mon, May 17, 2021 at 11:34 AM Andrew Chen wrote: >> >>> Hey guys. The linking of the directory worked! Thanks again for your >>> help. >>> >>> On Mon, May 17, 2021 at 7:59 AM Andrew Chen wrote: >>> >>>> Thanks guys! I will try these out today. >>>> >>>> On Mon, May 17, 2021 at 5:08 AM Daniel-Constantin Mierla < >>>> mico...@gmail.com> wrote: >>>> >>>>> >>>>> On 17.05.21 09:49, Victor Seva wrote: >>>>> > On 5/14/21 2:09 PM, Andrew Chen wrote: >>>>> >> Hi Daniel, >>>>> >> >>>>> >> Yes. These are the steps I took: >>>>> >> >>>>> >> ## git clone kamailio repository >>>>> >> cd $INSTALLDIR >>>>> >> sudo git clone https://github.com/kamailio/kamailio >>>>> >> <https://github.com/kamailio/kamailio> kamailio >>>>> >> cd kamailio >>>>> >> sudo git checkout 5.4 >>>>> >> >>>>> >> ## Make config files with included modules list >>>>> >> sudo make include_modules="$INCLUDE_MODULES" cfg >>>>> >> >>>>> >> ## Compile Kamailio >>>>> >> sudo make mode=debug >>>>> >> >>>>> >> cd pkg/kamailio/deb >>>>> >> >>>>> >> ## Create debian package >>>>> >> sudo dpkg-buildpackage >>>>> >> >>>>> >> >>>>> >> Hi Victor, >>>>> >> >>>>> >> Yes, this is the version of Ubuntu we are using: >>>>> >> >>>>> >> debhttp://deb.kamailio.org/kamailio54 >>>>> >> <http://deb.kamailio.org/kamailio54> bionic main >>>>> >> deb-srchttp://deb.kamailio.org/kamailio54 >>>>> >> <http://deb.kamailio.org/kamailio54> bionic main >>>>> > >>>>> > If you're using bionic, then use bionic directory at pkg/kamailio/deb >>>>> > as your debian dir. >>>>> > >>>>> > On the root of the kamailio repository: >>>>> > # cp -r pkg/kamailio/deb/bionic debian >>>>> > # dpkg-buildpackage -rfakeroot -tc -uc -us >>>>> >>>>> For what it worth, we have also a target in the Makefile for building >>>>> debs, next is what I typically use to test debs building before a >>>>> release: >>>>> >>>>> ln -s pkg/kamailio/deb/bionic debian >>>>> make deb >>>>> >>>>> Note that debian symlink is deleted after 'make deb' completes or >>>>> fails, >>>>> so needs to be recreated if the command has to be run again. >>>>> >>>>> Cheers, >>>>> Daniel >>>>> >>>>> -- >>>>> Dan
Re: [SR-Users] 5.4 dependency package question
Yes. My Jenkins job runs the symlink step everytime: sudo ln -s pkg/kamailio/deb/bionic debian ## Create debian package sudo make deb I do this in the main kamailio install directory. On Mon, May 17, 2021 at 1:09 PM Daniel-Constantin Mierla wrote: > Is it debian symlink pointing to the right folder in pkg/kamailio/deb/ for > you distribution? As I said, it gets deleted and running 'make deb' again > with (re-)create the symlink to the 'debian' folder. In other words, create > symlink always before running 'make deb'. > > Cheers, > Daniel > On 17.05.21 17:44, Andrew Chen wrote: > > So after looking at the build logs, it seems I'm still facing these > dependency errors: > > The following packages have unmet dependencies: > gcj-jdk : Depends: libgcj-common (>= 1:6.4-3ubuntu1) but it is not > installable >Depends: gcj-jre (>= 4:6.4.0-3ubuntu1) but it is not installable >Depends: gcj-6-jdk (>= 6.4.0-1~) but it is not installable > > The following packages have unmet dependencies: > libval-dev : Depends: libval15 (= 2.2-4) but it is not installable > > How important are these libraries and which module uses them? > > > On Mon, May 17, 2021 at 11:34 AM Andrew Chen wrote: > >> Hey guys. The linking of the directory worked! Thanks again for your >> help. >> >> On Mon, May 17, 2021 at 7:59 AM Andrew Chen wrote: >> >>> Thanks guys! I will try these out today. >>> >>> On Mon, May 17, 2021 at 5:08 AM Daniel-Constantin Mierla < >>> mico...@gmail.com> wrote: >>> >>>> >>>> On 17.05.21 09:49, Victor Seva wrote: >>>> > On 5/14/21 2:09 PM, Andrew Chen wrote: >>>> >> Hi Daniel, >>>> >> >>>> >> Yes. These are the steps I took: >>>> >> >>>> >> ## git clone kamailio repository >>>> >> cd $INSTALLDIR >>>> >> sudo git clone https://github.com/kamailio/kamailio >>>> >> <https://github.com/kamailio/kamailio> kamailio >>>> >> cd kamailio >>>> >> sudo git checkout 5.4 >>>> >> >>>> >> ## Make config files with included modules list >>>> >> sudo make include_modules="$INCLUDE_MODULES" cfg >>>> >> >>>> >> ## Compile Kamailio >>>> >> sudo make mode=debug >>>> >> >>>> >> cd pkg/kamailio/deb >>>> >> >>>> >> ## Create debian package >>>> >> sudo dpkg-buildpackage >>>> >> >>>> >> >>>> >> Hi Victor, >>>> >> >>>> >> Yes, this is the version of Ubuntu we are using: >>>> >> >>>> >> debhttp://deb.kamailio.org/kamailio54 >>>> >> <http://deb.kamailio.org/kamailio54> bionic main >>>> >> deb-srchttp://deb.kamailio.org/kamailio54 >>>> >> <http://deb.kamailio.org/kamailio54> bionic main >>>> > >>>> > If you're using bionic, then use bionic directory at pkg/kamailio/deb >>>> > as your debian dir. >>>> > >>>> > On the root of the kamailio repository: >>>> > # cp -r pkg/kamailio/deb/bionic debian >>>> > # dpkg-buildpackage -rfakeroot -tc -uc -us >>>> >>>> For what it worth, we have also a target in the Makefile for building >>>> debs, next is what I typically use to test debs building before a >>>> release: >>>> >>>> ln -s pkg/kamailio/deb/bionic debian >>>> make deb >>>> >>>> Note that debian symlink is deleted after 'make deb' completes or fails, >>>> so needs to be recreated if the command has to be run again. >>>> >>>> Cheers, >>>> Daniel >>>> >>>> -- >>>> Daniel-Constantin Mierla -- www.asipto.com >>>> www.twitter.com/miconda -- www.linkedin.com/in/miconda >>>> Kamailio Advanced Training - Online >>>> May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) >>>> * https://www.asipto.com/sw/kamailio-advanced-training-online/ >>>> >>>> >>>> __ >>>> Kamailio - Users Mailing List - Non Commercial Discussions >>>> * sr-users@lists.kamailio.org >>>> Important: keep the mailing list in the recipients, do not reply only >>>> to the send
Re: [SR-Users] 5.4 dependency package question
So after looking at the build logs, it seems I'm still facing these dependency errors: The following packages have unmet dependencies: gcj-jdk : Depends: libgcj-common (>= 1:6.4-3ubuntu1) but it is not installable Depends: gcj-jre (>= 4:6.4.0-3ubuntu1) but it is not installable Depends: gcj-6-jdk (>= 6.4.0-1~) but it is not installable The following packages have unmet dependencies: libval-dev : Depends: libval15 (= 2.2-4) but it is not installable How important are these libraries and which module uses them? On Mon, May 17, 2021 at 11:34 AM Andrew Chen wrote: > Hey guys. The linking of the directory worked! Thanks again for your > help. > > On Mon, May 17, 2021 at 7:59 AM Andrew Chen wrote: > >> Thanks guys! I will try these out today. >> >> On Mon, May 17, 2021 at 5:08 AM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> >>> On 17.05.21 09:49, Victor Seva wrote: >>> > On 5/14/21 2:09 PM, Andrew Chen wrote: >>> >> Hi Daniel, >>> >> >>> >> Yes. These are the steps I took: >>> >> >>> >> ## git clone kamailio repository >>> >> cd $INSTALLDIR >>> >> sudo git clone https://github.com/kamailio/kamailio >>> >> <https://github.com/kamailio/kamailio> kamailio >>> >> cd kamailio >>> >> sudo git checkout 5.4 >>> >> >>> >> ## Make config files with included modules list >>> >> sudo make include_modules="$INCLUDE_MODULES" cfg >>> >> >>> >> ## Compile Kamailio >>> >> sudo make mode=debug >>> >> >>> >> cd pkg/kamailio/deb >>> >> >>> >> ## Create debian package >>> >> sudo dpkg-buildpackage >>> >> >>> >> >>> >> Hi Victor, >>> >> >>> >> Yes, this is the version of Ubuntu we are using: >>> >> >>> >> debhttp://deb.kamailio.org/kamailio54 >>> >> <http://deb.kamailio.org/kamailio54> bionic main >>> >> deb-srchttp://deb.kamailio.org/kamailio54 >>> >> <http://deb.kamailio.org/kamailio54> bionic main >>> > >>> > If you're using bionic, then use bionic directory at pkg/kamailio/deb >>> > as your debian dir. >>> > >>> > On the root of the kamailio repository: >>> > # cp -r pkg/kamailio/deb/bionic debian >>> > # dpkg-buildpackage -rfakeroot -tc -uc -us >>> >>> For what it worth, we have also a target in the Makefile for building >>> debs, next is what I typically use to test debs building before a >>> release: >>> >>> ln -s pkg/kamailio/deb/bionic debian >>> make deb >>> >>> Note that debian symlink is deleted after 'make deb' completes or fails, >>> so needs to be recreated if the command has to be run again. >>> >>> Cheers, >>> Daniel >>> >>> -- >>> Daniel-Constantin Mierla -- www.asipto.com >>> www.twitter.com/miconda -- www.linkedin.com/in/miconda >>> Kamailio Advanced Training - Online >>> May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) >>> * https://www.asipto.com/sw/kamailio-advanced-training-online/ >>> >>> >>> __ >>> Kamailio - Users Mailing List - Non Commercial Discussions >>> * sr-users@lists.kamailio.org >>> Important: keep the mailing list in the recipients, do not reply only to >>> the sender! >>> Edit mailing list options or unsubscribe: >>> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >> >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> 415 516 5535 (M) >> achen@ fuze.com >> >> > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 5.4 dependency package question
Hey guys. The linking of the directory worked! Thanks again for your help. On Mon, May 17, 2021 at 7:59 AM Andrew Chen wrote: > Thanks guys! I will try these out today. > > On Mon, May 17, 2021 at 5:08 AM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> >> On 17.05.21 09:49, Victor Seva wrote: >> > On 5/14/21 2:09 PM, Andrew Chen wrote: >> >> Hi Daniel, >> >> >> >> Yes. These are the steps I took: >> >> >> >> ## git clone kamailio repository >> >> cd $INSTALLDIR >> >> sudo git clone https://github.com/kamailio/kamailio >> >> <https://github.com/kamailio/kamailio> kamailio >> >> cd kamailio >> >> sudo git checkout 5.4 >> >> >> >> ## Make config files with included modules list >> >> sudo make include_modules="$INCLUDE_MODULES" cfg >> >> >> >> ## Compile Kamailio >> >> sudo make mode=debug >> >> >> >> cd pkg/kamailio/deb >> >> >> >> ## Create debian package >> >> sudo dpkg-buildpackage >> >> >> >> >> >> Hi Victor, >> >> >> >> Yes, this is the version of Ubuntu we are using: >> >> >> >> debhttp://deb.kamailio.org/kamailio54 >> >> <http://deb.kamailio.org/kamailio54> bionic main >> >> deb-srchttp://deb.kamailio.org/kamailio54 >> >> <http://deb.kamailio.org/kamailio54> bionic main >> > >> > If you're using bionic, then use bionic directory at pkg/kamailio/deb >> > as your debian dir. >> > >> > On the root of the kamailio repository: >> > # cp -r pkg/kamailio/deb/bionic debian >> > # dpkg-buildpackage -rfakeroot -tc -uc -us >> >> For what it worth, we have also a target in the Makefile for building >> debs, next is what I typically use to test debs building before a release: >> >> ln -s pkg/kamailio/deb/bionic debian >> make deb >> >> Note that debian symlink is deleted after 'make deb' completes or fails, >> so needs to be recreated if the command has to be run again. >> >> Cheers, >> Daniel >> >> -- >> Daniel-Constantin Mierla -- www.asipto.com >> www.twitter.com/miconda -- www.linkedin.com/in/miconda >> Kamailio Advanced Training - Online >> May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) >> * https://www.asipto.com/sw/kamailio-advanced-training-online/ >> >> >> __ >> Kamailio - Users Mailing List - Non Commercial Discussions >> * sr-users@lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to >> the sender! >> Edit mailing list options or unsubscribe: >> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 5.4 dependency package question
Thanks guys! I will try these out today. On Mon, May 17, 2021 at 5:08 AM Daniel-Constantin Mierla wrote: > > On 17.05.21 09:49, Victor Seva wrote: > > On 5/14/21 2:09 PM, Andrew Chen wrote: > >> Hi Daniel, > >> > >> Yes. These are the steps I took: > >> > >> ## git clone kamailio repository > >> cd $INSTALLDIR > >> sudo git clone https://github.com/kamailio/kamailio > >> <https://github.com/kamailio/kamailio> kamailio > >> cd kamailio > >> sudo git checkout 5.4 > >> > >> ## Make config files with included modules list > >> sudo make include_modules="$INCLUDE_MODULES" cfg > >> > >> ## Compile Kamailio > >> sudo make mode=debug > >> > >> cd pkg/kamailio/deb > >> > >> ## Create debian package > >> sudo dpkg-buildpackage > >> > >> > >> Hi Victor, > >> > >> Yes, this is the version of Ubuntu we are using: > >> > >> debhttp://deb.kamailio.org/kamailio54 > >> <http://deb.kamailio.org/kamailio54> bionic main > >> deb-srchttp://deb.kamailio.org/kamailio54 > >> <http://deb.kamailio.org/kamailio54> bionic main > > > > If you're using bionic, then use bionic directory at pkg/kamailio/deb > > as your debian dir. > > > > On the root of the kamailio repository: > > # cp -r pkg/kamailio/deb/bionic debian > > # dpkg-buildpackage -rfakeroot -tc -uc -us > > For what it worth, we have also a target in the Makefile for building > debs, next is what I typically use to test debs building before a release: > > ln -s pkg/kamailio/deb/bionic debian > make deb > > Note that debian symlink is deleted after 'make deb' completes or fails, > so needs to be recreated if the command has to be run again. > > Cheers, > Daniel > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - Online > May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) > * https://www.asipto.com/sw/kamailio-advanced-training-online/ > > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 5.4 dependency package question
Hi Daniel, Yes. These are the steps I took: ## git clone kamailio repository cd $INSTALLDIR sudo git clone https://github.com/kamailio/kamailio kamailio cd kamailio sudo git checkout 5.4 ## Make config files with included modules list sudo make include_modules="$INCLUDE_MODULES" cfg ## Compile Kamailio sudo make mode=debug cd pkg/kamailio/deb ## Create debian package sudo dpkg-buildpackage Hi Victor, Yes, this is the version of Ubuntu we are using: deb http://deb.kamailio.org/kamailio54 bionic main deb-src http://deb.kamailio.org/kamailio54 bionic main On Fri, May 14, 2021 at 7:03 AM Victor Seva < linuxman...@torreviejawireless.org> wrote: > Hi, > > you have some official Ubuntu versions supported [0] > > [0] http://deb.kamailio.org/#dev54 > > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 5.4 dependency package question
The other option was to apply the "-d" to the dpkg-buildpackage binary to ignore the dependencies..but I don't know what are the repercussions in doing this. Again, please advise. :) On Thu, May 13, 2021 at 3:56 PM Andrew Chen wrote: > Btw, I manually downloaded the gcj-jdk deb package ( > gcj-jdk_6.4.0-3ubuntu1_amd64.deb) from Ubuntu main page and still I get > this error: > > The following packages have unmet dependencies: > gcj-jdk : Depends: libgcj-common (>= 1:6.4-3ubuntu1) but it is not > installable >Depends: gcj-jre (>= 4:6.4.0-3ubuntu1) but it is not installable >Depends: gcj-6-jdk (>= 6.4.0-1~) but it is not installable > > > I also did the same for libval-dev (libval-dev_2.2-4_amd64.deb) and got this: > > > The following packages have unmet dependencies: > > libval-dev : Depends: libval15 (= 2.2-4) but it is not installable > > E: Unable to correct problems, you have held broken packages. > > > As for libxmlrpc-c3-dev, there is a "libxmlrpc-core-c3-dev" package. Is that > the same thing? If not, does anyone know where I can get my hands on > libxmlrpc-c3-dev.deb? > > > On Thu, May 13, 2021 at 2:26 PM Andrew Chen wrote: > >> Hi guys, >> >> I'm trying to build a deb file of kamailio 5.4 and when doing >> dpkg-buidpackage it gave a bunch of dependency warnings. >> >> I was able to take care a good number of them until I ran into this: >> >> *dpkg-checkbuilddeps: **error*: Unmet build dependencies: gcj-jdk >> libval-dev libxmlrpc-c3-dev >> >> >> None of these packages are in the "apt-cache search" output. >> >> >> Below is a list of modules currently loaded in 5.2.5 and want to use them >> again: >> >> >> INCLUDE_MODULES="exec rtpengine topoh carrierroute statsd dialplan kex tm >> tmx sl rr pv maxfwd usrloc textops sdpops siputils xlog sanity ctl acc >> dispatcher cfgutils permissions domain presence presence_xml nathelper >> dialog tls htable pike db_mysql userblacklist sqlops websocket xhttp >> siptrace tcpops jsonrpcs rtimer" >> >> >> Thanks >> >> >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> 415 516 5535 (M) >> achen@ fuze.com >> >> > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 5.4 dependency package question
Btw, I manually downloaded the gcj-jdk deb package ( gcj-jdk_6.4.0-3ubuntu1_amd64.deb) from Ubuntu main page and still I get this error: The following packages have unmet dependencies: gcj-jdk : Depends: libgcj-common (>= 1:6.4-3ubuntu1) but it is not installable Depends: gcj-jre (>= 4:6.4.0-3ubuntu1) but it is not installable Depends: gcj-6-jdk (>= 6.4.0-1~) but it is not installable I also did the same for libval-dev (libval-dev_2.2-4_amd64.deb) and got this: The following packages have unmet dependencies: libval-dev : Depends: libval15 (= 2.2-4) but it is not installable E: Unable to correct problems, you have held broken packages. As for libxmlrpc-c3-dev, there is a "libxmlrpc-core-c3-dev" package. Is that the same thing? If not, does anyone know where I can get my hands on libxmlrpc-c3-dev.deb? On Thu, May 13, 2021 at 2:26 PM Andrew Chen wrote: > Hi guys, > > I'm trying to build a deb file of kamailio 5.4 and when doing > dpkg-buidpackage it gave a bunch of dependency warnings. > > I was able to take care a good number of them until I ran into this: > > *dpkg-checkbuilddeps: **error*: Unmet build dependencies: gcj-jdk > libval-dev libxmlrpc-c3-dev > > > None of these packages are in the "apt-cache search" output. > > > Below is a list of modules currently loaded in 5.2.5 and want to use them > again: > > > INCLUDE_MODULES="exec rtpengine topoh carrierroute statsd dialplan kex tm > tmx sl rr pv maxfwd usrloc textops sdpops siputils xlog sanity ctl acc > dispatcher cfgutils permissions domain presence presence_xml nathelper > dialog tls htable pike db_mysql userblacklist sqlops websocket xhttp > siptrace tcpops jsonrpcs rtimer" > > > Thanks > > > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] 5.4 dependency package question
Hi guys, I'm trying to build a deb file of kamailio 5.4 and when doing dpkg-buidpackage it gave a bunch of dependency warnings. I was able to take care a good number of them until I ran into this: *dpkg-checkbuilddeps: **error*: Unmet build dependencies: gcj-jdk libval-dev libxmlrpc-c3-dev None of these packages are in the "apt-cache search" output. Below is a list of modules currently loaded in 5.2.5 and want to use them again: INCLUDE_MODULES="exec rtpengine topoh carrierroute statsd dialplan kex tm tmx sl rr pv maxfwd usrloc textops sdpops siputils xlog sanity ctl acc dispatcher cfgutils permissions domain presence presence_xml nathelper dialog tls htable pike db_mysql userblacklist sqlops websocket xhttp siptrace tcpops jsonrpcs rtimer" Thanks -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamcmd dlg.end_dlg not working in shell script
Hi Bastian,
Oh wow. nice catch. It's so nice to have a second set of eyes to spot
something as trivial as this. Really appreciate it.
--Andy
On Tue, Mar 16, 2021 at 1:08 PM Andrew Chen wrote:
>
>
> On Tue, Mar 16, 2021 at 12:52 PM Bastian Triller <
> bastian.tril...@gmail.com> wrote:
>
>> With the logs in your first post and your shell function in a later post,
>> it seems your variables aren't only containing id and entry, but h_entry:
>> 123 and h_id 567.
>>
>> On Tue, Mar 16, 2021, 17:31 David Villasmil <
>> david.villasmil.w...@gmail.com> wrote:
>>
>>> Maybe the user executing from cron?
>>>
>>> On Tue, 16 Mar 2021 at 16:16, Andrew Chen wrote:
>>>
>>>> Now what's really interesting is that I echo'd the command I was going
>>>> to execute:
>>>>
>>>> 2021-03-16T15:49:02.291485+00:00 ashmainkama51 /scripts/
>>>> *get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02
>>>> UTC 2021 executing kamcmd dlg.end_dlg h_entry: 401 h_id: 11452
>>>>
>>>>
>>>> and this is exact copy of the kamcmd in the script but for some reason
>>>> kamcmd returned invalid parameters:
>>>>
>>>>
>>>> 2021-03-16T15:49:02.299040+00:00 ashmainkama51 /scripts/
>>>> *get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02
>>>> UTC 2021 status=error: 500 - Invalid parameters
>>>>
>>>>
>>>> I don't get it.
>>>>
>>>> On Tue, Mar 16, 2021 at 11:49 AM Andrew Chen wrote:
>>>>
>>>>> Hi Llie
>>>>> sure.
>>>>>
>>>>> loadmodule "*ctl*.so"
>>>>>
>>>>> #modparam("*ctl*", "binrpc", "tcp:*:2046")
>>>>>
>>>>> #modparam("*ctl*", "binrpc_max_body_size", 20)
>>>>>
>>>>> #modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>>>>>
>>>>> modparam("*ctl*", "binrpc", "unix:/var/run/kamailio/kamailio_*ctl*")
>>>>>
>>>>> modparam("*ctl*", "binrpc", "tcp:*:2046")
>>>>>
>>>>> modparam("*ctl*", "binrpc_max_body_size", 20)
>>>>>
>>>>> modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>>>>>
>>>>>
>>>>> So the script is actually kicked off by another script that is
>>>>> executed by a cronjob
>>>>>
>>>>>
>>>>> Been doing more troubleshooting and I'm starting to think this is some
>>>>> cron issue but can't really isolate the issue to that 100%. Need more
>>>>> testing data to confirm.
>>>>>
>>>>> On Tue, Mar 16, 2021 at 9:27 AM Ilie Soltanici
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Can you post here parameters for the ctl module and what is the user
>>>>>> you're running the script?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, 15 Mar 2021 at 21:04, Andrew Chen wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Coming back to this. Any other suggestions here?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Wed, Mar 10, 2021 at 9:24 AM Andrew Chen wrote:
>>>>>>>
>>>>>>>> So the strange thing is that I use kamcmd to get the list of users
>>>>>>>> and that works. Are there special permissions needed to delete them?
>>>>>>>>
>>>>>>>> On Wed, Mar 10, 2021 at 4:38 AM Ilie Soltanici <
>>>>>>>> iliusha...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> Sorry, there is actually no need for the callid argument, I mixed
>>>>>>>>> it up with another command.
>>>>>>>>> As Daniel recommended try to check the permissions. Which user the
>>>>>>>>> script is running with and what are the permission for
>>>>>>>>> /
Re: [SR-Users] kamcmd dlg.end_dlg not working in shell script
On Tue, Mar 16, 2021 at 12:52 PM Bastian Triller
wrote:
> With the logs in your first post and your shell function in a later post,
> it seems your variables aren't only containing id and entry, but h_entry:
> 123 and h_id 567.
>
> On Tue, Mar 16, 2021, 17:31 David Villasmil <
> david.villasmil.w...@gmail.com> wrote:
>
>> Maybe the user executing from cron?
>>
>> On Tue, 16 Mar 2021 at 16:16, Andrew Chen wrote:
>>
>>> Now what's really interesting is that I echo'd the command I was going
>>> to execute:
>>>
>>> 2021-03-16T15:49:02.291485+00:00 ashmainkama51 /scripts/
>>> *get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02
>>> UTC 2021 executing kamcmd dlg.end_dlg h_entry: 401 h_id: 11452
>>>
>>>
>>> and this is exact copy of the kamcmd in the script but for some reason
>>> kamcmd returned invalid parameters:
>>>
>>>
>>> 2021-03-16T15:49:02.299040+00:00 ashmainkama51 /scripts/
>>> *get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02
>>> UTC 2021 status=error: 500 - Invalid parameters
>>>
>>>
>>> I don't get it.
>>>
>>> On Tue, Mar 16, 2021 at 11:49 AM Andrew Chen wrote:
>>>
>>>> Hi Llie
>>>> sure.
>>>>
>>>> loadmodule "*ctl*.so"
>>>>
>>>> #modparam("*ctl*", "binrpc", "tcp:*:2046")
>>>>
>>>> #modparam("*ctl*", "binrpc_max_body_size", 20)
>>>>
>>>> #modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>>>>
>>>> modparam("*ctl*", "binrpc", "unix:/var/run/kamailio/kamailio_*ctl*")
>>>>
>>>> modparam("*ctl*", "binrpc", "tcp:*:2046")
>>>>
>>>> modparam("*ctl*", "binrpc_max_body_size", 20)
>>>>
>>>> modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>>>>
>>>>
>>>> So the script is actually kicked off by another script that is executed
>>>> by a cronjob
>>>>
>>>>
>>>> Been doing more troubleshooting and I'm starting to think this is some
>>>> cron issue but can't really isolate the issue to that 100%. Need more
>>>> testing data to confirm.
>>>>
>>>> On Tue, Mar 16, 2021 at 9:27 AM Ilie Soltanici
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Can you post here parameters for the ctl module and what is the user
>>>>> you're running the script?
>>>>>
>>>>> Regards,
>>>>>
>>>>>
>>>>>
>>>>> On Mon, 15 Mar 2021 at 21:04, Andrew Chen wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Coming back to this. Any other suggestions here?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Wed, Mar 10, 2021 at 9:24 AM Andrew Chen wrote:
>>>>>>
>>>>>>> So the strange thing is that I use kamcmd to get the list of users
>>>>>>> and that works. Are there special permissions needed to delete them?
>>>>>>>
>>>>>>> On Wed, Mar 10, 2021 at 4:38 AM Ilie Soltanici
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> Sorry, there is actually no need for the callid argument, I mixed
>>>>>>>> it up with another command.
>>>>>>>> As Daniel recommended try to check the permissions. Which user the
>>>>>>>> script is running with and what are the permission for
>>>>>>>> /var/run/kamailio/
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> On Wed, 10 Mar 2021 at 09:26, Ilie Soltanici
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> kamcmd dlg.end_dlg $h_entry $h_id
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I think you are missing the callid parameter when calling kamcmd
>>>>>>>>> command:
>>>>>>>>>
Re: [SR-Users] kamcmd dlg.end_dlg not working in shell script
So I would expect some other error if it's a user permission issue. Plus
just a reminder that kamcmd works when gathering caller info to get the h_
params.
On Tue, Mar 16, 2021 at 12:36 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> Maybe the user executing from cron?
>
> On Tue, 16 Mar 2021 at 16:16, Andrew Chen wrote:
>
>> Now what's really interesting is that I echo'd the command I was going to
>> execute:
>>
>> 2021-03-16T15:49:02.291485+00:00 ashmainkama51 /scripts/
>> *get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02
>> UTC 2021 executing kamcmd dlg.end_dlg h_entry: 401 h_id: 11452
>>
>>
>> and this is exact copy of the kamcmd in the script but for some reason
>> kamcmd returned invalid parameters:
>>
>>
>> 2021-03-16T15:49:02.299040+00:00 ashmainkama51 /scripts/
>> *get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02
>> UTC 2021 status=error: 500 - Invalid parameters
>>
>>
>> I don't get it.
>>
>> On Tue, Mar 16, 2021 at 11:49 AM Andrew Chen wrote:
>>
>>> Hi Llie
>>> sure.
>>>
>>> loadmodule "*ctl*.so"
>>>
>>> #modparam("*ctl*", "binrpc", "tcp:*:2046")
>>>
>>> #modparam("*ctl*", "binrpc_max_body_size", 20)
>>>
>>> #modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>>>
>>> modparam("*ctl*", "binrpc", "unix:/var/run/kamailio/kamailio_*ctl*")
>>>
>>> modparam("*ctl*", "binrpc", "tcp:*:2046")
>>>
>>> modparam("*ctl*", "binrpc_max_body_size", 20)
>>>
>>> modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>>>
>>>
>>> So the script is actually kicked off by another script that is executed
>>> by a cronjob
>>>
>>>
>>> Been doing more troubleshooting and I'm starting to think this is some
>>> cron issue but can't really isolate the issue to that 100%. Need more
>>> testing data to confirm.
>>>
>>> On Tue, Mar 16, 2021 at 9:27 AM Ilie Soltanici
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Can you post here parameters for the ctl module and what is the user
>>>> you're running the script?
>>>>
>>>> Regards,
>>>>
>>>>
>>>>
>>>> On Mon, 15 Mar 2021 at 21:04, Andrew Chen wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Coming back to this. Any other suggestions here?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Mar 10, 2021 at 9:24 AM Andrew Chen wrote:
>>>>>
>>>>>> So the strange thing is that I use kamcmd to get the list of users
>>>>>> and that works. Are there special permissions needed to delete them?
>>>>>>
>>>>>> On Wed, Mar 10, 2021 at 4:38 AM Ilie Soltanici
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> Sorry, there is actually no need for the callid argument, I mixed it
>>>>>>> up with another command.
>>>>>>> As Daniel recommended try to check the permissions. Which user the
>>>>>>> script is running with and what are the permission for
>>>>>>> /var/run/kamailio/
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> On Wed, 10 Mar 2021 at 09:26, Ilie Soltanici
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> kamcmd dlg.end_dlg $h_entry $h_id
>>>>>>>>>
>>>>>>>>
>>>>>>>> I think you are missing the callid parameter when calling kamcmd
>>>>>>>> command:
>>>>>>>> Try kamcmd dlg.end_dlg $h_entry $h_id $SIPCallID
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> On Tue, 9 Mar 2021 at 13:03, Andrew Chen wrote:
>>>>>>>>
>>>>>>>>> Thanks guys.
>>>>>>>>> Here is the whole function I created:
>>>>>>>>>
>>>>>>>>> function FollowUpAction
>>>&
Re: [SR-Users] kamcmd dlg.end_dlg not working in shell script
Now what's really interesting is that I echo'd the command I was going to
execute:
2021-03-16T15:49:02.291485+00:00 ashmainkama51 /scripts/
*get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02 UTC
2021 executing kamcmd dlg.end_dlg h_entry: 401 h_id: 11452
and this is exact copy of the kamcmd in the script but for some reason
kamcmd returned invalid parameters:
2021-03-16T15:49:02.299040+00:00 ashmainkama51 /scripts/
*get-call-from-hepic*.sh - *get-call-from-hepic*: Tue Mar 16 15:49:02 UTC
2021 status=error: 500 - Invalid parameters
I don't get it.
On Tue, Mar 16, 2021 at 11:49 AM Andrew Chen wrote:
> Hi Llie
> sure.
>
> loadmodule "*ctl*.so"
>
> #modparam("*ctl*", "binrpc", "tcp:*:2046")
>
> #modparam("*ctl*", "binrpc_max_body_size", 20)
>
> #modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>
> modparam("*ctl*", "binrpc", "unix:/var/run/kamailio/kamailio_*ctl*")
>
> modparam("*ctl*", "binrpc", "tcp:*:2046")
>
> modparam("*ctl*", "binrpc_max_body_size", 20)
>
> modparam("*ctl*", "binrpc_struct_max_body_size", 3)
>
>
> So the script is actually kicked off by another script that is executed by
> a cronjob
>
>
> Been doing more troubleshooting and I'm starting to think this is some
> cron issue but can't really isolate the issue to that 100%. Need more
> testing data to confirm.
>
> On Tue, Mar 16, 2021 at 9:27 AM Ilie Soltanici
> wrote:
>
>> Hi,
>>
>> Can you post here parameters for the ctl module and what is the user
>> you're running the script?
>>
>> Regards,
>>
>>
>>
>> On Mon, 15 Mar 2021 at 21:04, Andrew Chen wrote:
>>
>>> Hi All,
>>>
>>> Coming back to this. Any other suggestions here?
>>>
>>> Thanks
>>>
>>> On Wed, Mar 10, 2021 at 9:24 AM Andrew Chen wrote:
>>>
>>>> So the strange thing is that I use kamcmd to get the list of users and
>>>> that works. Are there special permissions needed to delete them?
>>>>
>>>> On Wed, Mar 10, 2021 at 4:38 AM Ilie Soltanici
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Sorry, there is actually no need for the callid argument, I mixed it
>>>>> up with another command.
>>>>> As Daniel recommended try to check the permissions. Which user the
>>>>> script is running with and what are the permission for /var/run/kamailio/
>>>>>
>>>>> Regards,
>>>>>
>>>>> On Wed, 10 Mar 2021 at 09:26, Ilie Soltanici
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> kamcmd dlg.end_dlg $h_entry $h_id
>>>>>>>
>>>>>>
>>>>>> I think you are missing the callid parameter when calling kamcmd
>>>>>> command:
>>>>>> Try kamcmd dlg.end_dlg $h_entry $h_id $SIPCallID
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> On Tue, 9 Mar 2021 at 13:03, Andrew Chen wrote:
>>>>>>
>>>>>>> Thanks guys.
>>>>>>> Here is the whole function I created:
>>>>>>>
>>>>>>> function FollowUpAction
>>>>>>>
>>>>>>> {
>>>>>>>
>>>>>>> SIPCallID=$1
>>>>>>>
>>>>>>>
>>>>>>> if [ $callStatus -ge 7 ] && [ $callStatus -le 15 ]; then
>>>>>>>
>>>>>>> GetDialogID $SIPCallID
>>>>>>>
>>>>>>> log "$(date) Found active dialog on completed call. Delete
>>>>>>> call using $h_entry $h_id on SIP Call-ID $SIPCallID" >>
>>>>>>> deleted-calls-list.txt
>>>>>>>
>>>>>>> kamcmd dlg.end_dlg $h_entry $h_id
>>>>>>>
>>>>>>> fi
>>>>>>>
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Mar 9, 2021 at 6:53 AM David Villasmil <
>>>>>>> david.villasmil.w...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Specially if you don’t show the script source.
>>>>>>>>
>>>>&
Re: [SR-Users] kamcmd dlg.end_dlg not working in shell script
Hi Llie
sure.
loadmodule "*ctl*.so"
#modparam("*ctl*", "binrpc", "tcp:*:2046")
#modparam("*ctl*", "binrpc_max_body_size", 20)
#modparam("*ctl*", "binrpc_struct_max_body_size", 3)
modparam("*ctl*", "binrpc", "unix:/var/run/kamailio/kamailio_*ctl*")
modparam("*ctl*", "binrpc", "tcp:*:2046")
modparam("*ctl*", "binrpc_max_body_size", 20)
modparam("*ctl*", "binrpc_struct_max_body_size", 3)
So the script is actually kicked off by another script that is executed by
a cronjob
Been doing more troubleshooting and I'm starting to think this is some cron
issue but can't really isolate the issue to that 100%. Need more testing
data to confirm.
On Tue, Mar 16, 2021 at 9:27 AM Ilie Soltanici wrote:
> Hi,
>
> Can you post here parameters for the ctl module and what is the user
> you're running the script?
>
> Regards,
>
>
>
> On Mon, 15 Mar 2021 at 21:04, Andrew Chen wrote:
>
>> Hi All,
>>
>> Coming back to this. Any other suggestions here?
>>
>> Thanks
>>
>> On Wed, Mar 10, 2021 at 9:24 AM Andrew Chen wrote:
>>
>>> So the strange thing is that I use kamcmd to get the list of users and
>>> that works. Are there special permissions needed to delete them?
>>>
>>> On Wed, Mar 10, 2021 at 4:38 AM Ilie Soltanici
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> Sorry, there is actually no need for the callid argument, I mixed it up
>>>> with another command.
>>>> As Daniel recommended try to check the permissions. Which user the
>>>> script is running with and what are the permission for /var/run/kamailio/
>>>>
>>>> Regards,
>>>>
>>>> On Wed, 10 Mar 2021 at 09:26, Ilie Soltanici
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> kamcmd dlg.end_dlg $h_entry $h_id
>>>>>>
>>>>>
>>>>> I think you are missing the callid parameter when calling kamcmd
>>>>> command:
>>>>> Try kamcmd dlg.end_dlg $h_entry $h_id $SIPCallID
>>>>>
>>>>> Regards,
>>>>>
>>>>> On Tue, 9 Mar 2021 at 13:03, Andrew Chen wrote:
>>>>>
>>>>>> Thanks guys.
>>>>>> Here is the whole function I created:
>>>>>>
>>>>>> function FollowUpAction
>>>>>>
>>>>>> {
>>>>>>
>>>>>> SIPCallID=$1
>>>>>>
>>>>>>
>>>>>> if [ $callStatus -ge 7 ] && [ $callStatus -le 15 ]; then
>>>>>>
>>>>>> GetDialogID $SIPCallID
>>>>>>
>>>>>> log "$(date) Found active dialog on completed call. Delete call
>>>>>> using $h_entry $h_id on SIP Call-ID $SIPCallID" >> deleted-calls-list.txt
>>>>>>
>>>>>> kamcmd dlg.end_dlg $h_entry $h_id
>>>>>>
>>>>>> fi
>>>>>>
>>>>>> }
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Mar 9, 2021 at 6:53 AM David Villasmil <
>>>>>> david.villasmil.w...@gmail.com> wrote:
>>>>>>
>>>>>>> Specially if you don’t show the script source.
>>>>>>>
>>>>>>> On Tue, 9 Mar 2021 at 08:51, Daniel-Constantin Mierla <
>>>>>>> mico...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> it is hard to say why your shell script does not work, when the
>>>>>>>> command runs ok in the terminal. Maybe missing/empty parameters, or
>>>>>>>> insufficient access rights, ...
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Daniel
>>>>>>>> On 08.03.21 20:23, Andrew Chen wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I have a script that cleans up hanging dialog and for some reason,
>>>>>>>> executing 'kamcmd dlg.end_dlg' does not seem to work. Below I log
>>>>>>>> events
>>>>>>>> of stuck calls and as you can see it just keeps logging the
Re: [SR-Users] kamcmd dlg.end_dlg not working in shell script
So the strange thing is that I use kamcmd to get the list of users and that
works. Are there special permissions needed to delete them?
On Wed, Mar 10, 2021 at 4:38 AM Ilie Soltanici wrote:
> Hello,
>
> Sorry, there is actually no need for the callid argument, I mixed it up
> with another command.
> As Daniel recommended try to check the permissions. Which user the script
> is running with and what are the permission for /var/run/kamailio/
>
> Regards,
>
> On Wed, 10 Mar 2021 at 09:26, Ilie Soltanici wrote:
>
>> Hello,
>>
>> kamcmd dlg.end_dlg $h_entry $h_id
>>>
>>
>> I think you are missing the callid parameter when calling kamcmd command:
>> Try kamcmd dlg.end_dlg $h_entry $h_id $SIPCallID
>>
>> Regards,
>>
>> On Tue, 9 Mar 2021 at 13:03, Andrew Chen wrote:
>>
>>> Thanks guys.
>>> Here is the whole function I created:
>>>
>>> function FollowUpAction
>>>
>>> {
>>>
>>> SIPCallID=$1
>>>
>>>
>>> if [ $callStatus -ge 7 ] && [ $callStatus -le 15 ]; then
>>>
>>> GetDialogID $SIPCallID
>>>
>>> log "$(date) Found active dialog on completed call. Delete call
>>> using $h_entry $h_id on SIP Call-ID $SIPCallID" >> deleted-calls-list.txt
>>>
>>> kamcmd dlg.end_dlg $h_entry $h_id
>>>
>>> fi
>>>
>>> }
>>>
>>>
>>>
>>> On Tue, Mar 9, 2021 at 6:53 AM David Villasmil <
>>> david.villasmil.w...@gmail.com> wrote:
>>>
>>>> Specially if you don’t show the script source.
>>>>
>>>> On Tue, 9 Mar 2021 at 08:51, Daniel-Constantin Mierla <
>>>> mico...@gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> it is hard to say why your shell script does not work, when the
>>>>> command runs ok in the terminal. Maybe missing/empty parameters, or
>>>>> insufficient access rights, ...
>>>>>
>>>>> Cheers,
>>>>> Daniel
>>>>> On 08.03.21 20:23, Andrew Chen wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I have a script that cleans up hanging dialog and for some reason,
>>>>> executing 'kamcmd dlg.end_dlg' does not seem to work. Below I log events
>>>>> of stuck calls and as you can see it just keeps logging the same call
>>>>> until
>>>>> I manually run the kamcmd either in bash shell prompt or in kamcmd cli:
>>>>>
>>>>> 2021-03-08T19:00:04.347807+00:00 sjointgkama51
>>>>> /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:00:04
>>>>> UTC 2021 Found active dialog on completed call. Delete call using h_entry:
>>>>> 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul
>>>>>
>>>>> 2021-03-08T19:01:02.531822+00:00 sjointgkama51
>>>>> /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:01:02
>>>>> UTC 2021 Found active dialog on completed call. Delete call using h_entry:
>>>>> 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul
>>>>>
>>>>> 2021-03-08T19:02:02.689823+00:00 sjointgkama51
>>>>> /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:02:02
>>>>> UTC 2021 Found active dialog on completed call. Delete call using h_entry:
>>>>> 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul
>>>>>
>>>>> 2021-03-08T19:03:02.044960+00:00 sjointgkama51
>>>>> /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:03:02
>>>>> UTC 2021 Found active dialog on completed call. Delete call using h_entry:
>>>>> 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul
>>>>>
>>>>> 2021-03-08T19:04:02.436588+00:00 sjointgkama51
>>>>> /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:04:02
>>>>> UTC 2021 Found active dialog on completed call. Delete call using h_entry:
>>>>> 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul
>>>>>
>>>>> 2021-03-08T19:05:02.685572+00:00 sjointgkama51
>>>>> /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:05:02
>>>>> UTC 2021 Found active dialog on completed call. Delete call using h_entry:
>>>>> 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul
>>>>>
[SR-Users] kamcmd dlg.end_dlg not working in shell script
Hi all, I have a script that cleans up hanging dialog and for some reason, executing 'kamcmd dlg.end_dlg' does not seem to work. Below I log events of stuck calls and as you can see it just keeps logging the same call until I manually run the kamcmd either in bash shell prompt or in kamcmd cli: 2021-03-08T19:00:04.347807+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:00:04 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:01:02.531822+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:01:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:02:02.689823+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:02:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:03:02.044960+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:03:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:04:02.436588+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:04:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:05:02.685572+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:05:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:06:02.775561+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:06:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:07:01.867021+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:07:01 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:08:01.888512+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:08:01 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:09:02.146887+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:09:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:10:02.649627+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:10:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:11:01.904948+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:11:01 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:12:01.932267+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:12:01 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:13:02.428128+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:13:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:14:02.617683+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:14:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:15:01.863099+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:15:01 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:16:01.650299+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:16:01 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:17:02.338576+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:17:02 UTC 2021 Found active dialog on completed call. Delete call using h_entry: 1333 *h_id*: 11225 on SIP Call-ID 7j5r1msitcvg9siohoul 2021-03-08T19:18:01.743163+00:00 sjointgkama51 /scripts/get-call-from-hepic.sh - get-call-from-hepic: Mon Mar 8 19:18:01 UTC 2021 Found active dialog on completed
[SR-Users] logging rd/wr queue usage?
Hi all, I was wondering if there's a way to log rd/wr queue usage when processing a new incoming message? I am currently running 5.2.5 but couldn't find any variables in core cookbook or psudovar page. Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] websocket rd buffer size limit?
So what engineering is stating is we may need to support up to 65k. The video feature to support more video pods will produce large SDP's. So I got a random MESSAGE to Kamailio to work with TCP 5060 with 70k content length but when using websocket, it's limited to 64k. On Wed, Jan 27, 2021 at 5:57 AM Daniel-Constantin Mierla wrote: > Out of curiosity, how large do you expect the sip messages to be? Event > with webrtc sdp, I haven't seen sip messages getting closer to 64kB... > > Cheers, > Daniel > On 26.01.21 22:01, Andrew Chen wrote: > > Ok thanks. I also forgot to mention these are websocket SIP calls to the > Kamailio. > > I also ran into a thread after googling is to update the following in > tls_server.c > > #define TLS_RD_MBUF_SZ 65536 > #define TLS_WR_MBUF_SZ 65536 > > I will try both options. > > Thanks again! > > On Tue, Jan 26, 2021 at 1:15 PM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> Hello, >> >> this seems to be related to the SIP message max size, not to the tcp >> buffer size. >> >> You have to recompile kamailio after changing BUF_SIZE in the >> src/core/config.h. >> >> Cheers, >> Daniel >> On 26.01.21 18:43, Andrew Chen wrote: >> >> Hey group, >> >> I was wondering if there is a way to control the websocket buffer size to >> support large SIP messages. I received the following error when sending >> content-length of 65000 >> >> 2021-01-26T17:32:19.251408+00:00 sjomainkama50 kamailio[31871]: >> 109(32008) WARNING: websocket [*ws_frame.c*:482]: >> decode_and_validate_ws_frame(): message is too long for our buffer size >> (65535 / 66151) >> >> >> I am assuming this is controlled by the tcp_rd_buf params which I have >> set to 131k: >> >> >> *tcp_*rd_buf_size=131072 >> >> >> and this is my tcp_wr_buf params: >> >> *tcp_*wq_blk_size=131072 >> >> *tcp_*conn_wq_max=131072 >> >> >> >> Please advise. >> >> >> Thanks. >> >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> achen@ fuze.com >> >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> >> ___ >> Kamailio (SER) - Users Mailing >> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> -- >> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- >> www.linkedin.com/in/miconda >> Funding: https://www.paypal.me/dcmierla >> >> > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- > www.linkedin.com/in/miconda > Funding: https://www.paypal.me/dcmierla > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] websocket rd buffer size limit?
Ok thanks. I also forgot to mention these are websocket SIP calls to the Kamailio. I also ran into a thread after googling is to update the following in tls_server.c #define TLS_RD_MBUF_SZ 65536 #define TLS_WR_MBUF_SZ 65536 I will try both options. Thanks again! On Tue, Jan 26, 2021 at 1:15 PM Daniel-Constantin Mierla wrote: > Hello, > > this seems to be related to the SIP message max size, not to the tcp > buffer size. > > You have to recompile kamailio after changing BUF_SIZE in the > src/core/config.h. > > Cheers, > Daniel > On 26.01.21 18:43, Andrew Chen wrote: > > Hey group, > > I was wondering if there is a way to control the websocket buffer size to > support large SIP messages. I received the following error when sending > content-length of 65000 > > 2021-01-26T17:32:19.251408+00:00 sjomainkama50 kamailio[31871]: 109(32008) > WARNING: websocket [*ws_frame.c*:482]: decode_and_validate_ws_frame(): > message is too long for our buffer size (65535 / 66151) > > > I am assuming this is controlled by the tcp_rd_buf params which I have > set to 131k: > > > *tcp_*rd_buf_size=131072 > > > and this is my tcp_wr_buf params: > > *tcp_*wq_blk_size=131072 > > *tcp_*conn_wq_max=131072 > > > > Please advise. > > > Thanks. > > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > ___ > Kamailio (SER) - Users Mailing > Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- > www.linkedin.com/in/miconda > Funding: https://www.paypal.me/dcmierla > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] websocket rd buffer size limit?
Hey group, I was wondering if there is a way to control the websocket buffer size to support large SIP messages. I received the following error when sending content-length of 65000 2021-01-26T17:32:19.251408+00:00 sjomainkama50 kamailio[31871]: 109(32008) WARNING: websocket [*ws_frame.c*:482]: decode_and_validate_ws_frame(): message is too long for our buffer size (65535 / 66151) I am assuming this is controlled by the tcp_rd_buf params which I have set to 131k: *tcp_*rd_buf_size=131072 and this is my tcp_wr_buf params: *tcp_*wq_blk_size=131072 *tcp_*conn_wq_max=131072 Please advise. Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
Ok..that's interesting to know. Thanks for your input Richard. This helps a lot. On Fri, Dec 4, 2020 at 2:18 PM Richard Fuchs wrote: > On 04/12/2020 14.04, Andrew Chen wrote: > > Sure...I understand ICE has its own setup workflow than SIP but it's > > also important that rtpengine uses the rtp path that's negotiated in > > the SIP or else it can cause confusion (to those who don't understand > > ICE very well like me). > > There is no RTP path negotiated through SIP. There is only a number of > possible paths, which are compiled from the list of candidates that each > side advertises. ICE then checks which paths work, and then finally > chooses the one with the highest priority. > > The only way to have a single media path that is negotiated through SIP > is if you don't use ICE. > > Cheers > > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
Sure...I understand ICE has its own setup workflow than SIP but it's also important that rtpengine uses the rtp path that's negotiated in the SIP or else it can cause confusion (to those who don't understand ICE very well like me). On Fri, Dec 4, 2020 at 1:47 PM Richard Fuchs wrote: > On 04/12/2020 13.36, Andrew Chen wrote: > > Hmm..that's interesting. You would guess that the rtpengine binary > > process shouldn't start connecting ICE candidates once the SIP part is > > fully negotiated, which should trigger the rtpengine module on the > > Kamailio to tell rtpengine binary.."ok..you can start associating now..." > > Not really. Why would you think that? ICE and SIP are really largely > unrelated, and ICE processing starts as soon as possible so that media > can flow as soon as possible. Any delay in ICE processing leads to > delays in establishing the call or the media flows. (Trickle ICE exists > partly for that reason.) In particular early media would break if ICE > had to wait for SIP to finish. > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
Hmm..that's interesting. You would guess that the rtpengine binary process shouldn't start connecting ICE candidates once the SIP part is fully negotiated, which should trigger the rtpengine module on the Kamailio to tell rtpengine binary.."ok..you can start associating now..." On Fri, Dec 4, 2020 at 1:30 PM Richard Fuchs wrote: > On 04/12/2020 13.10, Andrew Chen wrote: > > So from a SIP point of view, the 200 OK should of sent the final > > negotiation of SDP once the client ACK's it right? > > The requirement to send an updated offer once ICE has completed with the > final negotiated candidates existed in the original ICE RFC, but I > believe it has been removed in the newer ICE RFC (I'm not 100% sure > about that though). For rtpengine that requirement certainly doesn't > exist and it's happy to negotiate and conclude ICE without a final > updated offer. Also rtpengine itself cannot trigger such an updated > offer since it's not directly in the SIP path, so that would have to be > left up to the clients. So in short, a single offer/answer exchange is > enough to get ICE started and it can complete negotiation out of band > without further signalling. > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
So from a SIP point of view, the 200 OK should of sent the final negotiation of SDP once the client ACK's it right? On Fri, Dec 4, 2020 at 11:49 AM Richard Fuchs wrote: > On 04/12/2020 11.39, Andrew Chen wrote: > > oh...that's the IPv6 address of the STUN server, not the ipv6 of the > > rtpengine instance. > > Ok. From rtpengine's point of view, this is one of the client's IP > addresses. The ICE candidate in the SDP is the client telling rtpengine: > This is one of my own addresses (`typ host`) and I can receive media > here. It is also listed (by the client who has sent the SDP) as the > highest priority candidate, and this is why it's (presumably) negotiated > as the candidate to use. This is why rtpengine is sending media there. > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
oh...that's the IPv6 address of the STUN server, not the ipv6 of the rtpengine instance. On Fri, Dec 4, 2020 at 11:38 AM Richard Fuchs wrote: > On 04/12/2020 11.31, Andrew Chen wrote: > > If that's the case then I don't know why this line doesn't show the > > ipv6 address of the client: > > > > Dec 3 18:05:47 ashmainrtpe42 rtpengine[8505]: DEBUG: > > [ep1sbnkk9tikhg4kpmot]: Forward to sink endpoint: > > 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71:59827 (RTP seq 25423 TS 0) > > It doesn't? > > 2020-12-03T18:05:46.456030+00:00 ashmainkama51 kamailio[22147]: > a=candidate:3373280875 1 udp 2122262783 > 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 59827 typ host generation 0 > network-id 2 network-cost 10 > > What is this then? > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
If that's the case then I don't know why this line doesn't show the ipv6 address of the client: Dec 3 18:05:47 ashmainrtpe42 rtpengine[8505]: DEBUG: [ep1sbnkk9tikhg4kpmot]: Forward to sink endpoint: 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71:59827 (RTP seq 25423 TS 0) On Fri, Dec 4, 2020 at 11:25 AM Richard Fuchs wrote: > On 04/12/2020 10.39, Andrew Chen wrote: > > So my next question would be: > > > > My 200 OK back to the client should have rtpengine as the only ICE > > candidate. Shouldn't it use that one instead? > > Yes it should. And it probably does. > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
So my next question would be: My 200 OK back to the client should have rtpengine as the only ICE candidate. Shouldn't it use that one instead? On Fri, Dec 4, 2020 at 10:18 AM Richard Fuchs wrote: > On 04/12/2020 09.40, Andrew Chen wrote: > > Hey Richard, > > > > So that's what I thought too until I saw this in rtpengine logs for > > one of my test calls: > > > > Dec 3 18:05:47 ashmainrtpe42 rtpengine[8505]: DEBUG: > > [ep1sbnkk9tikhg4kpmot]: Forward to sink endpoint: > > 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71:59827 (RTP seq 25423 TS 0) > > > > unless I misunderstood what this line means. > > I think you did. It means rtpengine has received a media packet from one > side and has forwarded it to the other side. Of course it's one of the > ICE candidates from the SDP because that's where the peer said it wants > to receive the media from rtpengine. > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
Hey Richard, So that's what I thought too until I saw this in rtpengine logs for one of my test calls: Dec 3 18:05:47 ashmainrtpe42 rtpengine[8505]: DEBUG: [ep1sbnkk9tikhg4kpmot]: Forward to sink endpoint: 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71:59827 (RTP seq 25423 TS 0) unless I misunderstood what this line means. On Fri, Dec 4, 2020 at 9:34 AM Richard Fuchs wrote: > On 04/12/2020 09.24, Andrew Chen wrote: > > Hey Richard, > > > > So it is true rtpengine is handling rtp between kamailio and receiver > > (freeswitch). I'm trying to understand if there is a way to not > > forward rtp to any of the ICE candidates in the original INVITE > > request from the client side. In other words, have the client rtp > > forward directly to the rtpengine and not any of the STUN servers (or > > ICE candidates). i honestly thought putting ICE=force in the > > rtpengine_answer would help in this case...but I don't see this part > > working. > > But that is what's happening, isn't it? What other media would rtpengine > be sending to the client if not the media received from the other > client? So your A client is sending to rtpengine, and rtpengine is > forwarding that to B, while your B client is also sending to rtpengine, > which then forwards it to A. Where do you not see that working? > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
Hey Richard, So it is true rtpengine is handling rtp between kamailio and receiver (freeswitch). I'm trying to understand if there is a way to not forward rtp to any of the ICE candidates in the original INVITE request from the client side. In other words, have the client rtp forward directly to the rtpengine and not any of the STUN servers (or ICE candidates). i honestly thought putting ICE=force in the rtpengine_answer would help in this case...but I don't see this part working. On Fri, Dec 4, 2020 at 9:20 AM Richard Fuchs wrote: > On 04/12/2020 09.11, Andrew Chen wrote: > > So for Yuriy's comment: > > > > I did issue ICE=force parameter but, as you can see my paste, it's > > still sending RTP sequence packets to the ICE candidate, which is not > > what I want to do. > > > > Richard, > > > > So our current setup is this: > > > > SIP > > client -> kamailio -> freeswitch > > RTP > > client -> freeswitch > > > > What I want to accomplish is this: > > > > SIP > > client -> kamailio -> freeswitch > > RTP (bypass ICE) > > client -> rtpengine -> freeswitch > > I still don't understand. What does "bypass ICE" mean? > > If you see rtpengine forwarding media packets as per the log you posted, > what makes you think that media is not going through rtpengine? > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
Actually Yuriy's..sorry...I see what you are saying.
So my question should be, this means I don't have a choice but to use the
ICE candidate between client and kamailio?
On Fri, Dec 4, 2020 at 9:11 AM Andrew Chen wrote:
> So for Yuriy's comment:
>
> I did issue ICE=force parameter but, as you can see my paste, it's still
> sending RTP sequence packets to the ICE candidate, which is not what I want
> to do.
>
> Richard,
>
> So our current setup is this:
>
> SIP
> client -> kamailio -> freeswitch
> RTP
> client -> freeswitch
>
> What I want to accomplish is this:
>
> SIP
> client -> kamailio -> freeswitch
> RTP (bypass ICE)
> client -> rtpengine -> freeswitch
>
>
>
> On Fri, Dec 4, 2020 at 3:34 AM Yuriy Gorlichenko
> wrote:
>
>> Hello
>> 2020-12-03T18:05:46.456106+00:00 ashmainkama51 kamailio[22147]:
>> a=candidate:2274611867 1 tcp 1518283007
>> 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 9 typ host tcptype active generation
>> 0 network-id 2 network-cost 10
>> is a local candidate sent in the offer from the client
>> ICE=force just says rtpengine: "when you will resend this offer to the
>> receiver, remove all candidates sent by sender and put yourself as the only
>> candidate"
>> But rtpengine still has to follow the ICE check for the received
>> candidates as in that case rtpengine is the receiver and it can't just not
>> check local candidates. That is why you facing this behaviour from the
>> rtpengine, which is totally correct.
>>
>> In other terms
>> Sender ---> rtpengine :rtpengine must follow ice procedure
>> and check availability of these local candidates to establish connection
>> between Sender and rtpengine
>> rtpengine -> Receiver: rtpengine pretends to be a Sender for
>> the ICE agent of the receiver. but in this term, RTPengine will be the only
>> candidate for this part of the call, so this part is establishing a
>> connection between rtpengine and Receiver
>>
>> чт, 3 дек. 2020 г. в 23:40, Richard Fuchs :
>>
>>> On 03/12/2020 13.39, Andrew Chen wrote:
>>> > Hi all,
>>> >
>>> > I was wondering if someone can help me understand how the ICE
>>> > parameter works in the rtpengine module works.
>>> >
>>> > So basically our client does an ICE candidate lookup and grabs a list
>>> > of them and applies it to the INVITE that gets sent to the Kamailio.
>>> > The list looks like this:
>>> >
>>> > 2020-12-03T18:05:46.456030+00:00 ashmainkama51 kamailio[22147]:
>>> > a=candidate:3373280875 1 udp 2122262783
>>> > 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 59827 typ host generation 0
>>> > network-id 2 network-cost 10
>>> > 2020-12-03T18:05:46.456057+00:00 ashmainkama51 kamailio[22147]:
>>> > a=candidate:3040609428 1 udp 2122197247
>>> > 2001:8a0:78fc:7000:d979:bf75:dbc0:69f 59828 typ host generation 0
>>> > network-id 3 network-cost 10
>>> > 2020-12-03T18:05:46.456081+00:00 ashmainkama51 kamailio[22147]:
>>> > a=candidate:1681997092 1 udp 2122129151 192.168.1.66 59829 typ host
>>> > generation 0 network-id 1 network-cost 10
>>> > 2020-12-03T18:05:46.456106+00:00 ashmainkama51 kamailio[22147]:
>>> > a=candidate:2274611867 1 tcp 1518283007
>>> > 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 9 typ host tcptype active
>>> > generation 0 network-id 2 network-cost 10
>>> > 2020-12-03T18:05:46.456131+00:00 ashmainkama51 kamailio[22147]:
>>> > a=candidate:4223662180 1 tcp 1518217471
>>> > 2001:8a0:78fc:7000:d979:bf75:dbc0:69f 9 typ host tcptype active
>>> > generation 0 network-id 3 network-cost 10
>>> > 2020-12-03T18:05:46.456155+00:00 ashmainkama51 kamailio[22147]:
>>> > a=candidate:717406676 1 tcp 1518149375 192.168.1.66 9 typ host tcptype
>>> > active generation 0 network-id 1 network-cost 10
>>> > 2020-12-03T18:05:46.456180+00:00 ashmainkama51 kamailio[22147]:
>>> > a=candidate:2130547417 1 udp 8199935 206.81.191.27 61165 typ relay
>>> > raddr 85.247.0.121 rport 53091 generation 0 network-id 1 network-cost
>>> 10
>>> >
>>> >
>>> > In the rtpengine_offer, I have this:
>>> >
>>> > rtpengine_offer("ICE=force DTLS=passive replace-session-connection
>>> > replace-origin external internal");
>>> >
>>> > What i am trying to do is to tell the freeswitch endpoint to use
>>> > rtpengine as ICE candidate a
Re: [SR-Users] question regarding rtpengine and ICE candidate selection
So for Yuriy's comment:
I did issue ICE=force parameter but, as you can see my paste, it's still
sending RTP sequence packets to the ICE candidate, which is not what I want
to do.
Richard,
So our current setup is this:
SIP
client -> kamailio -> freeswitch
RTP
client -> freeswitch
What I want to accomplish is this:
SIP
client -> kamailio -> freeswitch
RTP (bypass ICE)
client -> rtpengine -> freeswitch
On Fri, Dec 4, 2020 at 3:34 AM Yuriy Gorlichenko
wrote:
> Hello
> 2020-12-03T18:05:46.456106+00:00 ashmainkama51 kamailio[22147]:
> a=candidate:2274611867 1 tcp 1518283007
> 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 9 typ host tcptype active generation
> 0 network-id 2 network-cost 10
> is a local candidate sent in the offer from the client
> ICE=force just says rtpengine: "when you will resend this offer to the
> receiver, remove all candidates sent by sender and put yourself as the only
> candidate"
> But rtpengine still has to follow the ICE check for the received
> candidates as in that case rtpengine is the receiver and it can't just not
> check local candidates. That is why you facing this behaviour from the
> rtpengine, which is totally correct.
>
> In other terms
> Sender ---> rtpengine :rtpengine must follow ice procedure and
> check availability of these local candidates to establish connection
> between Sender and rtpengine
> rtpengine -> Receiver: rtpengine pretends to be a Sender for
> the ICE agent of the receiver. but in this term, RTPengine will be the only
> candidate for this part of the call, so this part is establishing a
> connection between rtpengine and Receiver
>
> чт, 3 дек. 2020 г. в 23:40, Richard Fuchs :
>
>> On 03/12/2020 13.39, Andrew Chen wrote:
>> > Hi all,
>> >
>> > I was wondering if someone can help me understand how the ICE
>> > parameter works in the rtpengine module works.
>> >
>> > So basically our client does an ICE candidate lookup and grabs a list
>> > of them and applies it to the INVITE that gets sent to the Kamailio.
>> > The list looks like this:
>> >
>> > 2020-12-03T18:05:46.456030+00:00 ashmainkama51 kamailio[22147]:
>> > a=candidate:3373280875 1 udp 2122262783
>> > 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 59827 typ host generation 0
>> > network-id 2 network-cost 10
>> > 2020-12-03T18:05:46.456057+00:00 ashmainkama51 kamailio[22147]:
>> > a=candidate:3040609428 1 udp 2122197247
>> > 2001:8a0:78fc:7000:d979:bf75:dbc0:69f 59828 typ host generation 0
>> > network-id 3 network-cost 10
>> > 2020-12-03T18:05:46.456081+00:00 ashmainkama51 kamailio[22147]:
>> > a=candidate:1681997092 1 udp 2122129151 192.168.1.66 59829 typ host
>> > generation 0 network-id 1 network-cost 10
>> > 2020-12-03T18:05:46.456106+00:00 ashmainkama51 kamailio[22147]:
>> > a=candidate:2274611867 1 tcp 1518283007
>> > 2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 9 typ host tcptype active
>> > generation 0 network-id 2 network-cost 10
>> > 2020-12-03T18:05:46.456131+00:00 ashmainkama51 kamailio[22147]:
>> > a=candidate:4223662180 1 tcp 1518217471
>> > 2001:8a0:78fc:7000:d979:bf75:dbc0:69f 9 typ host tcptype active
>> > generation 0 network-id 3 network-cost 10
>> > 2020-12-03T18:05:46.456155+00:00 ashmainkama51 kamailio[22147]:
>> > a=candidate:717406676 1 tcp 1518149375 192.168.1.66 9 typ host tcptype
>> > active generation 0 network-id 1 network-cost 10
>> > 2020-12-03T18:05:46.456180+00:00 ashmainkama51 kamailio[22147]:
>> > a=candidate:2130547417 1 udp 8199935 206.81.191.27 61165 typ relay
>> > raddr 85.247.0.121 rport 53091 generation 0 network-id 1 network-cost 10
>> >
>> >
>> > In the rtpengine_offer, I have this:
>> >
>> > rtpengine_offer("ICE=force DTLS=passive replace-session-connection
>> > replace-origin external internal");
>> >
>> > What i am trying to do is to tell the freeswitch endpoint to use
>> > rtpengine as ICE candidate and I see in the SDP this is happening:
>> >
>> > a=candidate:6296910676 1 udp 659136 206.81.191.52 52766 typ host
>> > generation 0
>> >
>> > Btw..206.81.191.52 is a separate AWS instance running rtpengine binary.
>> >
>> > On the rtpengine_answer, I tell the remote client side the same
>> > thing..use rtpengine as your ICE candidate:
>> >
>> > rtpengine_answer("ICE=force DTLS=passive replace-session-connection
>> > replace-origin internal external");
>> >
>> > and this is snippet from 200 OK:
>>
[SR-Users] question regarding rtpengine and ICE candidate selection
Hi all,
I was wondering if someone can help me understand how the ICE parameter
works in the rtpengine module works.
So basically our client does an ICE candidate lookup and grabs a list of
them and applies it to the INVITE that gets sent to the Kamailio. The list
looks like this:
2020-12-03T18:05:46.456030+00:00 ashmainkama51 kamailio[22147]:
a=candidate:3373280875 1 udp 2122262783
2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 59827 typ host generation 0
network-id 2 network-cost 10
2020-12-03T18:05:46.456057+00:00 ashmainkama51 kamailio[22147]:
a=candidate:3040609428 1 udp 2122197247
2001:8a0:78fc:7000:d979:bf75:dbc0:69f 59828 typ host generation 0
network-id 3 network-cost 10
2020-12-03T18:05:46.456081+00:00 ashmainkama51 kamailio[22147]:
a=candidate:1681997092 1 udp 2122129151 192.168.1.66 59829 typ host
generation 0 network-id 1 network-cost 10
2020-12-03T18:05:46.456106+00:00 ashmainkama51 kamailio[22147]:
a=candidate:2274611867 1 tcp 1518283007
2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 9 typ host tcptype active generation
0 network-id 2 network-cost 10
2020-12-03T18:05:46.456131+00:00 ashmainkama51 kamailio[22147]:
a=candidate:4223662180 1 tcp 1518217471
2001:8a0:78fc:7000:d979:bf75:dbc0:69f 9 typ host tcptype active generation
0 network-id 3 network-cost 10
2020-12-03T18:05:46.456155+00:00 ashmainkama51 kamailio[22147]:
a=candidate:717406676 1 tcp 1518149375 192.168.1.66 9 typ host tcptype
active generation 0 network-id 1 network-cost 10
2020-12-03T18:05:46.456180+00:00 ashmainkama51 kamailio[22147]:
a=candidate:2130547417 1 udp 8199935 206.81.191.27 61165 typ relay raddr
85.247.0.121 rport 53091 generation 0 network-id 1 network-cost 10
In the rtpengine_offer, I have this:
rtpengine_offer("ICE=force DTLS=passive replace-session-connection
replace-origin external internal");
What i am trying to do is to tell the freeswitch endpoint to use rtpengine
as ICE candidate and I see in the SDP this is happening:
a=candidate:6296910676 1 udp 659136 206.81.191.52 52766 typ host generation
0
Btw..206.81.191.52 is a separate AWS instance running rtpengine binary.
On the rtpengine_answer, I tell the remote client side the same thing..use
rtpengine as your ICE candidate:
rtpengine_answer("ICE=force DTLS=passive replace-session-connection
replace-origin internal external");
and this is snippet from 200 OK:
a=candidate:6296910676 1 udp 659136 206.81.191.52 52766 typ host generation
0
Question:
Why does the rtpengine logs still show that it's trying to use
2001:8a0:78fc:7000:e1d7:e93:3c50:ee71 as RTP candidate in this scenario?
Dec 3 18:05:47 ashmainrtpe42 rtpengine[8505]: DEBUG:
[ep1sbnkk9tikhg4kpmot]: Forward to sink endpoint:
2001:8a0:78fc:7000:e1d7:e93:3c50:ee71:59827 (RTP seq 25423 TS 0)
I thought ICE=force will handle such adjustments so that all rtp is handled
by the rtpengine to our client and bypass the STUN server?
Thanks.
--
Andy Chen
Sr. Telephony Lead Engineer
achen@ fuze.com
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio 5.2.5 - Need help with rtpengine error
Thanks Alex for your quick reply. I did as you mentioned and looked at the initial INVITE section. This is the only error I can find in regards to rtpengine: Oct 15 15:02:10 ashprodkama52 kamailio[8028]: 83(8139) DEBUG: rtpengine [rtpengine.c:2914]: select_rtpp_node_old(): rtpengine hash table lookup failed to find node for calllen=20 callid=16pgtn7s4pdk9l42gcmf viabranch= Is this what you were referring to? On Thu, Oct 15, 2020 at 11:57 AM Alex Balashov wrote: > This sounds like the offer command for the invite never made it to > RTPEngine, so it was never engaged and does not know what’s up 200 OK > answer is for. In other words, look further back in the history of this > call. > > — > Sent from mobile, with due apologies for brevity and errors. > > On Oct 15, 2020, at 11:49 AM, Andrew Chen wrote: > > > Hi all, > > Today I saw the following errors reported by rtpengine module: > > Oct 15 15:02:10 ashprodkama52 kamailio[8028]: 30(8086) DEBUG: rtpengine > [rtpengine.c:2453]: rtpp_function_call(): proxy reply: > d6:result5:error12:error-reason15:Unknown call-ide > Oct 15 15:02:10 ashprodkama52 kamailio[8028]: 30(8086) ERROR: rtpengine > [rtpengine.c:2474]: rtpp_function_call(): proxy replied with error: Unknown > call-id > > This was on the 200 OK response back from our Freeswitch. > > Any idea what would cause this? > > Thanks. > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Kamailio 5.2.5 - Need help with rtpengine error
Hi all, Today I saw the following errors reported by rtpengine module: Oct 15 15:02:10 ashprodkama52 kamailio[8028]: 30(8086) DEBUG: rtpengine [rtpengine.c:2453]: rtpp_function_call(): proxy reply: d6:result5:error12:error-reason15:Unknown call-ide Oct 15 15:02:10 ashprodkama52 kamailio[8028]: 30(8086) ERROR: rtpengine [rtpengine.c:2474]: rtpp_function_call(): proxy replied with error: Unknown call-id This was on the 200 OK response back from our Freeswitch. Any idea what would cause this? Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPENGINE question
Hmm...interesting. Is there logging which states the fallback is issued? If so, can someone share? Thanks. On Mon, Sep 14, 2020 at 1:28 PM Richard Fuchs wrote: > On 14/09/2020 13.14, Andrew Chen wrote: > > Btw Richard Fuchs, to follow up on your comment, we have a load > > generator running sipp which is non-SRTP traffic. > > As for the fallback, how does that work exactly? We tried the > > following today and it seems to have helped: > > > > - Removed "--table" startup param in systems file > > - Uncommented "no-fallback = false" in rtpengine.conf > > - Set "table=-1" in rtpengine.conf > > > > Is there anything else I'm missing that controls the fallback? > > Userspace fallback is always available, even if `no-fallback` is set > (which is relevant during startup only). If a packet is not handled by > the kernel module for whatever reason, it's always automatically passed > on to the daemon to be handled (except when explicitly instructed to > drop a packet, e.g. through `strict-source`). In this sense, you get the > same behaviour as if `table = -1` is used. > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPENGINE question
Sergey Safarov, Thanks for the response but we're not a CentOS house. Just Ubuntu.18.04. One other question. Is Daniel's suggestion the only way to get around kernel forwarding with our current setup? Will there be support for it in the future without disabling module signature check? On Mon, Sep 14, 2020 at 1:14 PM Andrew Chen wrote: > Btw Richard Fuchs, to follow up on your comment, we have a load > generator running sipp which is non-SRTP traffic. > As for the fallback, how does that work exactly? We tried the following > today and it seems to have helped: > > - Removed "--table" startup param in systems file > - Uncommented "no-fallback = false" in rtpengine.conf > - Set "table=-1" in rtpengine.conf > > Is there anything else I'm missing that controls the fallback? > > On Sat, Sep 12, 2020 at 1:32 AM Sergey Safarov > wrote: > >> I have testes build on 5.7 kernel on CentOS 8 (custom rpm package) >> >> You will find commit here >> https://github.com/sipwise/rtpengine/issues/975 >> >> Sergey >> >> On Fri, Sep 11, 2020 at 10:53 PM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> Related to tainted kernel, I faced the same issue when I deployed >>> rtpengine on a Suse Enterprise many months ago, so I do not really remember >>> the exact steps, but there is a way to disable the check of signed kernel >>> modules (iirc, these are only the ones coming from the kernel source tree, >>> so if you need to load any external kernel module, you have to disable this >>> option). >>> >>> Quick check on the net, it may have to do with module.sig_enforce option >>> for kernel loading. >>> >>> Cheers, >>> Daniel >>> On 11.09.20 21:31, Andrew Chen wrote: >>> >>> Sorry let me clarify this line here: >>> >>> "...at the time, I was running an older version 8.0.x so I recompiled >>> all the ngcp packages under this kernel and completed the installation >>> without issues.." >>> >>> 8.0.x is the older ngcp version. I recompiled version 9.0.1.0 under that >>> new kernel version 5.3.0-1035-aws #37-Ubuntu >>> >>> >>> On Fri, Sep 11, 2020 at 3:29 PM Andrew Chen wrote: >>> >>>> Thanks Alex. >>>> >>>> So it turns out my rtpengine stopped working after our latest kernel >>>> upgrade to: >>>> >>>> Linux sjomainrtpe30 5.3.0-1035-aws #37-Ubuntu SMP Sun Sep 6 01:17:09 >>>> UTC 2020 x86_64 x86_64 x86_64 GNU/Linux >>>> >>>> at the time, I was running an older version 8.0.x so I recompiled all >>>> the ngcp packages under this kernel and completed the installation without >>>> issues. >>>> >>>> As soon as we started making test calls, I received 0 audio from those >>>> test endpoints. Looking at the rtpengine logs, I see several messages >>>> that's quite concerning: >>>> >>>> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434623] xt_RTPENGINE: >>>> loading out-of-tree module taints kernel. >>>> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434670] xt_RTPENGINE: >>>> module verification failed: signature and/or required key missing - >>>> tainting kernel >>>> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434938] Registering >>>> xt_RTPENGINE module - version 9.0.1.0+0~mr9.0.1.0 >>>> >>>> and >>>> >>>> Sep 11 18:49:50 sjomainrtpe30 rtpengine[1030]: WARNING: >>>> [2-7859@2600:1f1c:4ff:3e01:f64d:2f67:c0fa:c931 >>>> port 5]: No support for kernel packet forwarding available (decryption >>>> cipher or HMAC not supported by kernel module) >>>> >>>> which I assume is due to the first error I pasted. >>>> >>>> So I tried >>>> >>>> - rebooting the system which maybe the module wasn't loaded properly. >>>> - I reran modprobe to make sure the module is installed >>>> - I ran some dkms command to see if any error pop up due to the kernel >>>> version I'm running and I see no errors: >>>> >>>> dkms status >>>> falco, 0.20.0+d77080a, 5.3.0-1032-aws, x86_64: installed >>>> falco, 0.20.0+d77080a, 5.3.0-1035-aws, x86_64: installed >>>> ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1032-aws, x86_64: installed >>>> ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1035-aws, x86_64: installed >>>> >>>>
Re: [SR-Users] RTPENGINE question
Btw Richard Fuchs, to follow up on your comment, we have a load generator running sipp which is non-SRTP traffic. As for the fallback, how does that work exactly? We tried the following today and it seems to have helped: - Removed "--table" startup param in systems file - Uncommented "no-fallback = false" in rtpengine.conf - Set "table=-1" in rtpengine.conf Is there anything else I'm missing that controls the fallback? On Sat, Sep 12, 2020 at 1:32 AM Sergey Safarov wrote: > I have testes build on 5.7 kernel on CentOS 8 (custom rpm package) > > You will find commit here > https://github.com/sipwise/rtpengine/issues/975 > > Sergey > > On Fri, Sep 11, 2020 at 10:53 PM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> Related to tainted kernel, I faced the same issue when I deployed >> rtpengine on a Suse Enterprise many months ago, so I do not really remember >> the exact steps, but there is a way to disable the check of signed kernel >> modules (iirc, these are only the ones coming from the kernel source tree, >> so if you need to load any external kernel module, you have to disable this >> option). >> >> Quick check on the net, it may have to do with module.sig_enforce option >> for kernel loading. >> >> Cheers, >> Daniel >> On 11.09.20 21:31, Andrew Chen wrote: >> >> Sorry let me clarify this line here: >> >> "...at the time, I was running an older version 8.0.x so I recompiled all >> the ngcp packages under this kernel and completed the installation without >> issues.." >> >> 8.0.x is the older ngcp version. I recompiled version 9.0.1.0 under that >> new kernel version 5.3.0-1035-aws #37-Ubuntu >> >> >> On Fri, Sep 11, 2020 at 3:29 PM Andrew Chen wrote: >> >>> Thanks Alex. >>> >>> So it turns out my rtpengine stopped working after our latest kernel >>> upgrade to: >>> >>> Linux sjomainrtpe30 5.3.0-1035-aws #37-Ubuntu SMP Sun Sep 6 01:17:09 UTC >>> 2020 x86_64 x86_64 x86_64 GNU/Linux >>> >>> at the time, I was running an older version 8.0.x so I recompiled all >>> the ngcp packages under this kernel and completed the installation without >>> issues. >>> >>> As soon as we started making test calls, I received 0 audio from those >>> test endpoints. Looking at the rtpengine logs, I see several messages >>> that's quite concerning: >>> >>> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434623] xt_RTPENGINE: >>> loading out-of-tree module taints kernel. >>> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434670] xt_RTPENGINE: >>> module verification failed: signature and/or required key missing - >>> tainting kernel >>> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434938] Registering >>> xt_RTPENGINE module - version 9.0.1.0+0~mr9.0.1.0 >>> >>> and >>> >>> Sep 11 18:49:50 sjomainrtpe30 rtpengine[1030]: WARNING: >>> [2-7859@2600:1f1c:4ff:3e01:f64d:2f67:c0fa:c931 >>> port 5]: No support for kernel packet forwarding available (decryption >>> cipher or HMAC not supported by kernel module) >>> >>> which I assume is due to the first error I pasted. >>> >>> So I tried >>> >>> - rebooting the system which maybe the module wasn't loaded properly. >>> - I reran modprobe to make sure the module is installed >>> - I ran some dkms command to see if any error pop up due to the kernel >>> version I'm running and I see no errors: >>> >>> dkms status >>> falco, 0.20.0+d77080a, 5.3.0-1032-aws, x86_64: installed >>> falco, 0.20.0+d77080a, 5.3.0-1035-aws, x86_64: installed >>> ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1032-aws, x86_64: installed >>> ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1035-aws, x86_64: installed >>> >>> So I'm running out of options. >>> >>> Any advice? >>> >>> >>> On Fri, Sep 11, 2020 at 3:17 PM Alex Balashov >>> wrote: >>> >>>> There is an RTPEngine mailing list, I believe, but RTPEngine questions >>>> are often posed here given its close association with Kamailio. What's >>>> going on? >>>> >>>> On 9/11/20 2:57 PM, Andrew Chen wrote: >>>> > Hey guys, >>>> > >>>> > Is this the right place to ask about rtpengine (ngcp) related issues >>>> > with kernel packet forwarding? >>>> > >>>> > Thanks. >>>> > >>>> >
Re: [SR-Users] RTPENGINE question
Thanks Daniel. Let me look at that option. On Fri, Sep 11, 2020 at 3:52 PM Daniel-Constantin Mierla wrote: > Related to tainted kernel, I faced the same issue when I deployed > rtpengine on a Suse Enterprise many months ago, so I do not really remember > the exact steps, but there is a way to disable the check of signed kernel > modules (iirc, these are only the ones coming from the kernel source tree, > so if you need to load any external kernel module, you have to disable this > option). > > Quick check on the net, it may have to do with module.sig_enforce option > for kernel loading. > > Cheers, > Daniel > On 11.09.20 21:31, Andrew Chen wrote: > > Sorry let me clarify this line here: > > "...at the time, I was running an older version 8.0.x so I recompiled all > the ngcp packages under this kernel and completed the installation without > issues.." > > 8.0.x is the older ngcp version. I recompiled version 9.0.1.0 under that > new kernel version 5.3.0-1035-aws #37-Ubuntu > > > On Fri, Sep 11, 2020 at 3:29 PM Andrew Chen wrote: > >> Thanks Alex. >> >> So it turns out my rtpengine stopped working after our latest kernel >> upgrade to: >> >> Linux sjomainrtpe30 5.3.0-1035-aws #37-Ubuntu SMP Sun Sep 6 01:17:09 UTC >> 2020 x86_64 x86_64 x86_64 GNU/Linux >> >> at the time, I was running an older version 8.0.x so I recompiled all the >> ngcp packages under this kernel and completed the installation without >> issues. >> >> As soon as we started making test calls, I received 0 audio from those >> test endpoints. Looking at the rtpengine logs, I see several messages >> that's quite concerning: >> >> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434623] xt_RTPENGINE: >> loading out-of-tree module taints kernel. >> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434670] xt_RTPENGINE: module >> verification failed: signature and/or required key missing - tainting kernel >> Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434938] Registering >> xt_RTPENGINE module - version 9.0.1.0+0~mr9.0.1.0 >> >> and >> >> Sep 11 18:49:50 sjomainrtpe30 rtpengine[1030]: WARNING: >> [2-7859@2600:1f1c:4ff:3e01:f64d:2f67:c0fa:c931 >> port 5]: No support for kernel packet forwarding available (decryption >> cipher or HMAC not supported by kernel module) >> >> which I assume is due to the first error I pasted. >> >> So I tried >> >> - rebooting the system which maybe the module wasn't loaded properly. >> - I reran modprobe to make sure the module is installed >> - I ran some dkms command to see if any error pop up due to the kernel >> version I'm running and I see no errors: >> >> dkms status >> falco, 0.20.0+d77080a, 5.3.0-1032-aws, x86_64: installed >> falco, 0.20.0+d77080a, 5.3.0-1035-aws, x86_64: installed >> ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1032-aws, x86_64: installed >> ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1035-aws, x86_64: installed >> >> So I'm running out of options. >> >> Any advice? >> >> >> On Fri, Sep 11, 2020 at 3:17 PM Alex Balashov >> wrote: >> >>> There is an RTPEngine mailing list, I believe, but RTPEngine questions >>> are often posed here given its close association with Kamailio. What's >>> going on? >>> >>> On 9/11/20 2:57 PM, Andrew Chen wrote: >>> > Hey guys, >>> > >>> > Is this the right place to ask about rtpengine (ngcp) related issues >>> > with kernel packet forwarding? >>> > >>> > Thanks. >>> > >>> > -- >>> > Andy Chen >>> > Sr. Telephony Lead Engineer >>> > achen@ <mailto:ac...@thinkingphones.com>fuze.com <http://fuze.com> >>> > >>> > >>> > >>> > *Confidentiality Notice: The information contained in this e-mail and >>> any >>> > attachments may be confidential. If you are not an intended recipient, >>> you >>> > are hereby notified that any dissemination, distribution or copying of >>> this >>> > e-mail is strictly prohibited. If you have received this e-mail in >>> error, >>> > please notify the sender and permanently delete the e-mail and any >>> > attachments immediately. You should not retain, copy or use this >>> e-mail or >>> > any attachment for any purpose, nor disclose all or any part of the >>> > contents to any other person. Thank you.* >>> > >>> >
Re: [SR-Users] RTPENGINE question
Sorry let me clarify this line here: "...at the time, I was running an older version 8.0.x so I recompiled all the ngcp packages under this kernel and completed the installation without issues.." 8.0.x is the older ngcp version. I recompiled version 9.0.1.0 under that new kernel version 5.3.0-1035-aws #37-Ubuntu On Fri, Sep 11, 2020 at 3:29 PM Andrew Chen wrote: > Thanks Alex. > > So it turns out my rtpengine stopped working after our latest kernel > upgrade to: > > Linux sjomainrtpe30 5.3.0-1035-aws #37-Ubuntu SMP Sun Sep 6 01:17:09 UTC > 2020 x86_64 x86_64 x86_64 GNU/Linux > > at the time, I was running an older version 8.0.x so I recompiled all the > ngcp packages under this kernel and completed the installation without > issues. > > As soon as we started making test calls, I received 0 audio from those > test endpoints. Looking at the rtpengine logs, I see several messages > that's quite concerning: > > Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434623] xt_RTPENGINE: loading > out-of-tree module taints kernel. > Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434670] xt_RTPENGINE: module > verification failed: signature and/or required key missing - tainting kernel > Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434938] Registering > xt_RTPENGINE module - version 9.0.1.0+0~mr9.0.1.0 > > and > > Sep 11 18:49:50 sjomainrtpe30 rtpengine[1030]: WARNING: > [2-7859@2600:1f1c:4ff:3e01:f64d:2f67:c0fa:c931 > port 5]: No support for kernel packet forwarding available (decryption > cipher or HMAC not supported by kernel module) > > which I assume is due to the first error I pasted. > > So I tried > > - rebooting the system which maybe the module wasn't loaded properly. > - I reran modprobe to make sure the module is installed > - I ran some dkms command to see if any error pop up due to the kernel > version I'm running and I see no errors: > > dkms status > falco, 0.20.0+d77080a, 5.3.0-1032-aws, x86_64: installed > falco, 0.20.0+d77080a, 5.3.0-1035-aws, x86_64: installed > ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1032-aws, x86_64: installed > ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1035-aws, x86_64: installed > > So I'm running out of options. > > Any advice? > > > On Fri, Sep 11, 2020 at 3:17 PM Alex Balashov > wrote: > >> There is an RTPEngine mailing list, I believe, but RTPEngine questions >> are often posed here given its close association with Kamailio. What's >> going on? >> >> On 9/11/20 2:57 PM, Andrew Chen wrote: >> > Hey guys, >> > >> > Is this the right place to ask about rtpengine (ngcp) related issues >> > with kernel packet forwarding? >> > >> > Thanks. >> > >> > -- >> > Andy Chen >> > Sr. Telephony Lead Engineer >> > achen@ <mailto:ac...@thinkingphones.com>fuze.com <http://fuze.com> >> > >> > >> > >> > *Confidentiality Notice: The information contained in this e-mail and >> any >> > attachments may be confidential. If you are not an intended recipient, >> you >> > are hereby notified that any dissemination, distribution or copying of >> this >> > e-mail is strictly prohibited. If you have received this e-mail in >> error, >> > please notify the sender and permanently delete the e-mail and any >> > attachments immediately. You should not retain, copy or use this e-mail >> or >> > any attachment for any purpose, nor disclose all or any part of the >> > contents to any other person. Thank you.* >> > >> > ___ >> > Kamailio (SER) - Users Mailing List >> > sr-users@lists.kamailio.org >> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > >> >> -- >> Alex Balashov | Principal | Evariste Systems LLC >> >> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) >> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >> >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPENGINE question
Thanks Alex. So it turns out my rtpengine stopped working after our latest kernel upgrade to: Linux sjomainrtpe30 5.3.0-1035-aws #37-Ubuntu SMP Sun Sep 6 01:17:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux at the time, I was running an older version 8.0.x so I recompiled all the ngcp packages under this kernel and completed the installation without issues. As soon as we started making test calls, I received 0 audio from those test endpoints. Looking at the rtpengine logs, I see several messages that's quite concerning: Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434623] xt_RTPENGINE: loading out-of-tree module taints kernel. Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434670] xt_RTPENGINE: module verification failed: signature and/or required key missing - tainting kernel Sep 11 18:43:41 sjomainrtpe30 kernel: [ 13.434938] Registering xt_RTPENGINE module - version 9.0.1.0+0~mr9.0.1.0 and Sep 11 18:49:50 sjomainrtpe30 rtpengine[1030]: WARNING: [2-7859@2600:1f1c:4ff:3e01:f64d:2f67:c0fa:c931 port 5]: No support for kernel packet forwarding available (decryption cipher or HMAC not supported by kernel module) which I assume is due to the first error I pasted. So I tried - rebooting the system which maybe the module wasn't loaded properly. - I reran modprobe to make sure the module is installed - I ran some dkms command to see if any error pop up due to the kernel version I'm running and I see no errors: dkms status falco, 0.20.0+d77080a, 5.3.0-1032-aws, x86_64: installed falco, 0.20.0+d77080a, 5.3.0-1035-aws, x86_64: installed ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1032-aws, x86_64: installed ngcp-rtpengine, 9.0.1.0+0~mr9.0.1.0, 5.3.0-1035-aws, x86_64: installed So I'm running out of options. Any advice? On Fri, Sep 11, 2020 at 3:17 PM Alex Balashov wrote: > There is an RTPEngine mailing list, I believe, but RTPEngine questions > are often posed here given its close association with Kamailio. What's > going on? > > On 9/11/20 2:57 PM, Andrew Chen wrote: > > Hey guys, > > > > Is this the right place to ask about rtpengine (ngcp) related issues > > with kernel packet forwarding? > > > > Thanks. > > > > -- > > Andy Chen > > Sr. Telephony Lead Engineer > > achen@ <mailto:ac...@thinkingphones.com>fuze.com <http://fuze.com> > > > > > > > > *Confidentiality Notice: The information contained in this e-mail and any > > attachments may be confidential. If you are not an intended recipient, > you > > are hereby notified that any dissemination, distribution or copying of > this > > e-mail is strictly prohibited. If you have received this e-mail in error, > > please notify the sender and permanently delete the e-mail and any > > attachments immediately. You should not retain, copy or use this e-mail > or > > any attachment for any purpose, nor disclose all or any part of the > > contents to any other person. Thank you.* > > > > ___ > > Kamailio (SER) - Users Mailing List > > sr-users@lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] RTPENGINE question
Hey guys, Is this the right place to ask about rtpengine (ngcp) related issues with kernel packet forwarding? Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio coring ver 5.1.2
Thanks Daniel. We did perform a restart of the AWS instance to apply a kernel patch and when the process started up during bootup, that's when we saw the messages. However, manually starting it seems to work. We will work on upgrading to 5.3.x as you suggested. On Tue, Sep 1, 2020 at 10:43 AM Daniel-Constantin Mierla wrote: > Hello, > > first it is really recommended you run at least latest 5.1.x version, the > 5.1.2 is old in 5.1.x release series and many bugs may have been fixed. > Even more, 5.1.x is no longer maintained, so I would strongly recommend to > upgrade to latest in series 5.3.x or 5.4.x. > > Then, searching on google on Bad RIP value returns mainly discussions > about Kernel panic. According to this article: > > * https://www.opensourceforu.com/2011/01/understanding-a-kernel-oops/ > > RIP is the CPU register containing the address of the instruction that is > getting executed. Without a clear corefile with backtrace pointing to > kamailio, it is not easy to say if Kamailio has anything to do with or > there is some linux kernel issue on your system. Try searching on google, > there should be some hints to try to troubleshoot by ip and sp values, > maybe you can get further details. > > Cheers, > Daniel > On 01.09.20 15:12, Andrew Chen wrote: > > Hey guys, > > Our monitoring system caught kamailio coring. I did a dmesg and gave me > this: > > [Tue Sep 1 09:12:34 2020] kamailio[1375]: segfault at 1 ip > 0001 sp 7fff4203f098 error 14 in > kamailio[563969b5a000+4a4000] > [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. > [Tue Sep 1 09:12:34 2020] kamailio[1363]: segfault at 0 ip > sp 7fff4203f368 error 14 in > kamailio[563969b5a000+4a4000] > [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. > [Tue Sep 1 09:12:34 2020] kamailio[1377]: segfault at 1 ip > 0001 sp 7fff4203e308 error 14 in > kamailio[563969b5a000+4a4000] > [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. > > After doing gdb bt, didn't tell me much except it can't access some parts > of the memory: > > warning: Unexpected size of section `.reg-xstate/1624' in core file. > Cannot access memory at address 0x7fb23433e148 > Cannot access memory at address 0x7fb23433e140 > Failed to read a valid object file image from memory. > Core was generated by `/usr/sbin/kamailio -P > /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. > Program terminated with signal SIGSEGV, Segmentation fault. > > warning: Unexpected size of section `.reg-xstate/1624' in core file. > #0 0x0001 in ?? () > (gdb) bt full > #0 0x0001 in ?? () > No symbol table info available. > Backtrace stopped: Cannot access memory at address 0x7fff4203e1f8 > (gdb) quit > > Any idea on how to troubleshoot this further? > > Thanks. > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > ___ > Kamailio (SER) - Users Mailing > Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- > www.linkedin.com/in/miconda > Funding: https://www.paypal.me/dcmierla > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] kamailio coring ver 5.1.2
Hey guys, Our monitoring system caught kamailio coring. I did a dmesg and gave me this: [Tue Sep 1 09:12:34 2020] kamailio[1375]: segfault at 1 ip 0001 sp 7fff4203f098 error 14 in kamailio[563969b5a000+4a4000] [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. [Tue Sep 1 09:12:34 2020] kamailio[1363]: segfault at 0 ip sp 7fff4203f368 error 14 in kamailio[563969b5a000+4a4000] [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. [Tue Sep 1 09:12:34 2020] kamailio[1377]: segfault at 1 ip 0001 sp 7fff4203e308 error 14 in kamailio[563969b5a000+4a4000] [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. After doing gdb bt, didn't tell me much except it can't access some parts of the memory: warning: Unexpected size of section `.reg-xstate/1624' in core file. Cannot access memory at address 0x7fb23433e148 Cannot access memory at address 0x7fb23433e140 Failed to read a valid object file image from memory. Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGSEGV, Segmentation fault. warning: Unexpected size of section `.reg-xstate/1624' in core file. #0 0x0001 in ?? () (gdb) bt full #0 0x0001 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fff4203e1f8 (gdb) quit Any idea on how to troubleshoot this further? Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] siptrace not sending data to hepic
Thanks Daniel. We did check the Hepic capture server using tcpdump and confirmed the Hepic audio reports are arriving. On Fri, Jul 3, 2020 at 3:36 AM Daniel-Constantin Mierla wrote: > Hello, > > if the packets are sent out from Kamailio, check to see in hepic server if > they arrive. > > The modules in Kamailio do not control the MTU or the UDP fragmentation, > the only options are in the core. > > Cheers, > Daniel > On 01.07.20 21:48, Andrew Chen wrote: > > Hi all, > > I've been assigned a task to investigate why hepic doesn't generate MOS > scores ever since we changed the kamailio interface MTU from 9001 -> 1500. > > During my investigation, this is what I have found out so far: > > - Putting MTU back to 9001 removes this condition where no MOS was > generated. > - I did a tcpdump of port 9063 which is the port used to send data to > Hepic capture server and saw it reports packets are fragmented: > > 3:48:55.895505 IP (tos 0x68, ttl 64, id 38049, offset 0, flags [+], proto > UDP (17), length 1500) > 206.81.181.40.5060 > 10.225.88.239.9063: SIP > 13:48:55.896451 IP (tos 0x68, ttl 64, id 38050, offset 0, flags [+], proto > UDP (17), length 1500) > 206.81.181.40.5060 > 10.225.88.239.9063: SIP > > - Hepic support also caused by using 1500 MTU on the interface. > - I tried using the following core parameters to see if they could remedy > this issue but didn't seem to work: > > ## MTU related core settings > > udp4_raw=-1 > > udp4_raw_mtu=1500 > > > I can't seem to find any parameters in the siptrace module that controls > fragmentation of the packets to Hepic. > > Any suggestions on how else to troubleshoot this? > > Thanks. > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > ___ > Kamailio (SER) - Users Mailing > Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- > www.linkedin.com/in/miconda > Funding: https://www.paypal.me/dcmierla > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] siptrace not sending data to hepic
Hi all, I've been assigned a task to investigate why hepic doesn't generate MOS scores ever since we changed the kamailio interface MTU from 9001 -> 1500. During my investigation, this is what I have found out so far: - Putting MTU back to 9001 removes this condition where no MOS was generated. - I did a tcpdump of port 9063 which is the port used to send data to Hepic capture server and saw it reports packets are fragmented: 3:48:55.895505 IP (tos 0x68, ttl 64, id 38049, offset 0, flags [+], proto UDP (17), length 1500) 206.81.181.40.5060 > 10.225.88.239.9063: SIP 13:48:55.896451 IP (tos 0x68, ttl 64, id 38050, offset 0, flags [+], proto UDP (17), length 1500) 206.81.181.40.5060 > 10.225.88.239.9063: SIP - Hepic support also caused by using 1500 MTU on the interface. - I tried using the following core parameters to see if they could remedy this issue but didn't seem to work: ## MTU related core settings udp4_raw=-1 udp4_raw_mtu=1500 I can't seem to find any parameters in the siptrace module that controls fragmentation of the packets to Hepic. Any suggestions on how else to troubleshoot this? Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] rtpengine inserted random line into sdp
Interesting. Thanks for the tidbit. I will play around with msg_apply_changes and find the right place for it. On Fri, Jun 26, 2020 at 9:01 AM Richard Fuchs wrote: > Rtpengine takes and replaces the entire SDP body, so if there's another > module also manipulating the SDP, one module won't see the changes made by > the other one unless you call msg_apply_changes in between, leaving you > with bits of string in the wrong places. > > Cheers > > On 26/06/2020 08.50, Andrew Chen wrote: > > Thanks Richard. > > I do have the nathelper module running but not rtpproxy. How does > nathelper cause this issue? > > On Fri, Jun 26, 2020 at 8:27 AM Richard Fuchs wrote: > >> Looks like you're using both rtpengine and some other SDP-modifying >> module together, such as nathelper or rtpproxy, without calling >> msg_apply_changes() in between. >> >> Cheers >> >> On 25/06/2020 16.46, Andrew Chen wrote: >> >> Hi forum, >> >> I'm starting my rtpengine project and I'm facing a strange problem with >> rtpengine. I am seeing this in the SDP part of the INVITE: >> >> a=rtcp:52021 >> >> a=rtcp-mux >> >> 2001:470:7:3A7:0:0:0:2 >> >> a=direction:active >> >> a=oldmediaip:54.153.25.234 >> >> As you can see there is a random insert of the local kamailio IP in there >> and I'm have tried the following to remove it but failed to succeed: >> >> - Remove in the offer the combination of ICE and >> replace-session-connection flags >> - Switched between rtpengine_offer and rtpengine_manage >> - Restarted ngcp-rtpengine-daemon process >> - Used sdpops function sdp_remove_line_by_preifx() >> >> Currently running Kamailio 5.1.2. >> >> I am running out of ideas. >> >> Any suggestions would be greatly appreciated. >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> achen@ fuze.com >> >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> >> ___ >> Kamailio (SER) - Users Mailing >> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > ___ > Kamailio (SER) - Users Mailing > Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] rtpengine inserted random line into sdp
Thanks Richard. I do have the nathelper module running but not rtpproxy. How does nathelper cause this issue? On Fri, Jun 26, 2020 at 8:27 AM Richard Fuchs wrote: > Looks like you're using both rtpengine and some other SDP-modifying module > together, such as nathelper or rtpproxy, without calling > msg_apply_changes() in between. > > Cheers > > On 25/06/2020 16.46, Andrew Chen wrote: > > Hi forum, > > I'm starting my rtpengine project and I'm facing a strange problem with > rtpengine. I am seeing this in the SDP part of the INVITE: > > a=rtcp:52021 > > a=rtcp-mux > > 2001:470:7:3A7:0:0:0:2 > > a=direction:active > > a=oldmediaip:54.153.25.234 > > As you can see there is a random insert of the local kamailio IP in there > and I'm have tried the following to remove it but failed to succeed: > > - Remove in the offer the combination of ICE and > replace-session-connection flags > - Switched between rtpengine_offer and rtpengine_manage > - Restarted ngcp-rtpengine-daemon process > - Used sdpops function sdp_remove_line_by_preifx() > > Currently running Kamailio 5.1.2. > > I am running out of ideas. > > Any suggestions would be greatly appreciated. > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > ___ > Kamailio (SER) - Users Mailing > Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] rtpengine inserted random line into sdp
Hi forum, I'm starting my rtpengine project and I'm facing a strange problem with rtpengine. I am seeing this in the SDP part of the INVITE: a=rtcp:52021 a=rtcp-mux 2001:470:7:3A7:0:0:0:2 a=direction:active a=oldmediaip:54.153.25.234 As you can see there is a random insert of the local kamailio IP in there and I'm have tried the following to remove it but failed to succeed: - Remove in the offer the combination of ICE and replace-session-connection flags - Switched between rtpengine_offer and rtpengine_manage - Restarted ngcp-rtpengine-daemon process - Used sdpops function sdp_remove_line_by_preifx() Currently running Kamailio 5.1.2. I am running out of ideas. Any suggestions would be greatly appreciated. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio 5.2.5 core WARNING
thank you so much. I found the missing closing endif's. On Tue, Mar 3, 2020 at 4:22 PM David Villasmil < david.villasmil.w...@gmail.com> wrote: > Well, that tells you there aren’t the same amount of ifdef and endif. But > it can also mean you’ve got some other error, which SHOULD be printed out. > > Take a good look at the log, look out for ERROR, or CRITICAL. Go all the > way back. > > On Tue, 3 Mar 2020 at 21:18, Andrew Chen wrote: > >> Hi all, >> >> Can someone help shed some light as to what this core WARNING means? >> >> root@ashmaintpsg51:/etc/kamailio # kamailio -c kamailio.cfg >> 0(2192) WARNING: [core/ppcfg.c:220]: pp_ifdef_level_check(): >> different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 2 >> >> Thanks. >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> achen@ fuze.com >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > -- > Regards, > > David Villasmil > email: david.villasmil.w...@gmail.com > phone: +34669448337 > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] kamailio 5.2.5 core WARNING
Hi all, Can someone help shed some light as to what this core WARNING means? root@ashmaintpsg51:/etc/kamailio # kamailio -c kamailio.cfg 0(2192) WARNING: [core/ppcfg.c:220]: pp_ifdef_level_check(): different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 2 Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] possible TCP deadlock (tls again?) // pike module not releasing IPs
Yeah. I went to double check and there could be an issue with our Jenkins job that puts this build in our repository. I'll have to figure this out on my end. Sorry for the false alarm. On Wed, Jan 8, 2020 at 3:54 AM Daniel-Constantin Mierla wrote: > Was this a fresh installation of kamailio directly from the 52-nightly > repo? > > The jenkins build output shows that the flag was set during compilation: > > * > https://kamailio.sipwise.com/view/kam52/job/kamailio52-nightly-binaries/lastBuild/architecture=amd64,distribution=bionic,label=slave/consoleText > > The gcc command has the option -DKSR_PTHREAD_MUTEX_SHARED which sets in > the C code the TLS_PTHREAD_MUTEX_SHARED. > > Cheers, > Daniel > On 07.01.20 20:33, Andrew Chen wrote: > > So I used the nightly build option and I don't see it. > > + sudo add-apt-repository deb http://deb.kamailio.org/kamailio52-nightly > bionic main > Hit:1 https://dl.yarnpkg.com/debian stable InRelease > Hit:2 http://download.draios.com/stable/deb stable-amd64/ InRelease > Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] > Hit:4 https://deb.nodesource.com/node_11.x bionic InRelease > Ign:5 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com bionic > InRelease > Get:6 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com bionic > Release [2346 B] > Ign:7 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com bionic > InRelease > Ign:8 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com bionic > Release.gpg > Hit:9 http://ppa.launchpad.net/maxmind/ppa/ubuntu bionic InRelease > Get:10 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com bionic > Release [2346 B] > Hit:11 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic InRelease > Get:12 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates > InRelease [88.7 kB] > Get:13 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-backports > InRelease [74.6 kB] > Get:14 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com > bionic/main amd64 Packages [327 kB] > Ign:15 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com bionic > Release.gpg > Hit:16 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic > InRelease > Get:17 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages > [605 kB] > Get:18 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com > bionic/main amd64 Packages [233 kB] > Get:19 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/universe > amd64 Packages [1035 kB] > Get:20 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en > [196 kB] > Get:21 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 > Packages [16.8 kB] > Get:22 http://security.ubuntu.com/ubuntu bionic-security/restricted > Translation-en [5028 B] > Get:23 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 > Packages [628 kB] > Get:24 http://security.ubuntu.com/ubuntu bionic-security/universe > Translation-en [210 kB] > > Get:25 http://deb.kamailio.org/kamailio52-nightly bionic InRelease [4223 B] > Get:26 http://deb.kamailio.org/kamailio52-nightly bionic/main amd64 Packages > [14.8 kB] > > root@sjomainkama51:/usr/lib/x86_64-linux-gnu/kamailio/modules # kamailio -I > Print out of kamailio internals > Version: kamailio 5.2.5 (x86_64/linux) > Default config: /etc/kamailio/kamailio.cfg > Default paths to modules: /usr/lib/x86_64-linux-gnu/kamailio/modules > Compile flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, > USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, > PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, > FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, > USE_DST_BLACKLIST, HAVE_RESOLV_RES > MAX_RECV_BUFFER_SIZE=262144 > MAX_URI_SIZE=1024 > BUF_SIZE=65535 > DEFAULT PKG_SIZE=8MB > DEFAULT SHM_SIZE=64MB > ADAPTIVE_WAIT_LOOPS=1024 > TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select > Source code revision ID: unknown > Compiled with: gcc 7.4.0 > Compiled on: > Thank you for flying kamailio! > > > On Mon, Jan 6, 2020 at 2:52 PM Daniel-Constantin Mierla > wrote: > >> You can download the code from git repository and build the >> openssl_mutex_shared.so locally. >> >> Or install from the nightly builts, there should be the version with the >> fix embedded -- after installation check kamailio -I and see if it lists >> TLS_PTHREAD_MUTEX_SHARED. >> >> Cheers, >> Daniel >> On 06.01.20 16:48, Andrew Chen wrote: >> >> I have seen similar issues with pike and running 5.2.5 i
Re: [SR-Users] possible TCP deadlock (tls again?) // pike module not releasing IPs
So I used the nightly build option and I don't see it. + sudo add-apt-repository deb http://deb.kamailio.org/kamailio52-nightly bionic main Hit:1 https://dl.yarnpkg.com/debian stable InRelease Hit:2 http://download.draios.com/stable/deb stable-amd64/ InRelease Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:4 https://deb.nodesource.com/node_11.x bionic InRelease Ign:5 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com bionic InRelease Get:6 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com bionic Release [2346 B] Ign:7 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com bionic InRelease Ign:8 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com bionic Release.gpg Hit:9 http://ppa.launchpad.net/maxmind/ppa/ubuntu bionic InRelease Get:10 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com bionic Release [2346 B] Hit:11 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic InRelease Get:12 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:13 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:14 http://fuze-apt-bionic-master.s3-website-us-west-1.amazonaws.com bionic/main amd64 Packages [327 kB] Ign:15 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com bionic Release.gpg Hit:16 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic InRelease Get:17 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [605 kB] Get:18 http://fuze-apt-bionic-rc.s3-website-us-west-1.amazonaws.com bionic/main amd64 Packages [233 kB] Get:19 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1035 kB] Get:20 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [196 kB] Get:21 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [16.8 kB] Get:22 http://security.ubuntu.com/ubuntu bionic-security/restricted Translation-en [5028 B] Get:23 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [628 kB] Get:24 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [210 kB] Get:25 http://deb.kamailio.org/kamailio52-nightly bionic InRelease [4223 B] Get:26 http://deb.kamailio.org/kamailio52-nightly bionic/main amd64 Packages [14.8 kB] root@sjomainkama51:/usr/lib/x86_64-linux-gnu/kamailio/modules # kamailio -I Print out of kamailio internals Version: kamailio 5.2.5 (x86_64/linux) Default config: /etc/kamailio/kamailio.cfg Default paths to modules: /usr/lib/x86_64-linux-gnu/kamailio/modules Compile flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES MAX_RECV_BUFFER_SIZE=262144 MAX_URI_SIZE=1024 BUF_SIZE=65535 DEFAULT PKG_SIZE=8MB DEFAULT SHM_SIZE=64MB ADAPTIVE_WAIT_LOOPS=1024 TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select Source code revision ID: unknown Compiled with: gcc 7.4.0 Compiled on: Thank you for flying kamailio! On Mon, Jan 6, 2020 at 2:52 PM Daniel-Constantin Mierla wrote: > You can download the code from git repository and build the > openssl_mutex_shared.so locally. > > Or install from the nightly builts, there should be the version with the > fix embedded -- after installation check kamailio -I and see if it lists > TLS_PTHREAD_MUTEX_SHARED. > > Cheers, > Daniel > On 06.01.20 16:48, Andrew Chen wrote: > > I have seen similar issues with pike and running 5.2.5 installed using deb > repo. I don't see this openssl_mutex_shared directory: > > root@ashmainkama51:/usr/lib/x86_64-linux-gnu/kamailio # ls -lart > total 400 > -rw-r--r-- 1 root root 22528 Oct 10 12:29 libtrie.so.1.0 > lrwxrwxrwx 1 root root 14 Oct 10 12:29 libtrie.so.1 -> libtrie.so.1.0 > lrwxrwxrwx 1 root root 14 Oct 10 12:29 libtrie.so -> libtrie.so.1.0 > -rw-r--r-- 1 root root 63864 Oct 10 12:29 libsrutils.so.1.0 > lrwxrwxrwx 1 root root 17 Oct 10 12:29 libsrutils.so.1 -> > libsrutils.so.1.0 > lrwxrwxrwx 1 root root 17 Oct 10 12:29 libsrutils.so -> > libsrutils.so.1.0 > -rw-r--r-- 1 root root 51472 Oct 10 12:29 libsrdb2.so.1.0 > lrwxrwxrwx 1 root root 15 Oct 10 12:29 libsrdb2.so.1 -> > libsrdb2.so.1.0 > lrwxrwxrwx 1 root root 15 Oct 10 12:29 libsrdb2.so -> libsrdb2.so.1.0 > -rw-r--r-- 1 root root 211264 Oct 10 12:29 libsrdb1.so.1.0 > lrwxrwxrwx 1 root root 15 Oct 10 12:29 libsrdb1.so.1 -> > libsrdb1.so.1.0 > lrwxrwxrwx 1 root root 15 Oct 10 12:29 libsrdb1.so -> libsrdb1.so.1.0 > drwxr-xr-x 4 root root 4096 Dec 3 21:32 . > drwxr-xr-x 3 root root 4096 Dec 3 21:33 kamctl > drwxr-xr-x 2
Re: [SR-Users] kamcmd stuck
No command. It just gets stuck when I try to get into kamcmd cli prompt and I had to ctrl-c out of it. On Tue, Dec 17, 2019 at 9:39 AM Alex Balashov wrote: > It happens. Any particular command? > > — > Sent from mobile, with due apologies for brevity and errors. > > On Dec 17, 2019, at 9:26 AM, Andrew Chen wrote: > > > Hi everyone, > > Have anyone experienced kamcmd getting stuck and the only way to fix it > was to restart the process? > > Running 5.2.5 > > Thanks > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] kamcmd stuck
Hi everyone, Have anyone experienced kamcmd getting stuck and the only way to fix it was to restart the process? Running 5.2.5 Thanks -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Pike module never release IP
Btw Henning. Is there any case where pike would lock permanently until Kamailio process is restarted? On Fri, Dec 6, 2019 at 12:39 PM Andrew Chen wrote: > Ok thanks for the confirmation Henning. > > On Fri, Dec 6, 2019 at 5:09 AM Henning Westerholt wrote: > >> Hi Andrew, >> >> >> >> the data is hold in shared memory; it does not start child processes. >> >> >> >> Cheers, >> >> >> >> Henning >> >> >> >> -- >> >> Henning Westerholt – https://skalatan.de/blog/ >> >> Kamailio services – https://gilawa.com >> >> >> >> *From:* Andrew Chen >> *Sent:* Thursday, December 5, 2019 9:14 PM >> *To:* Henning Westerholt >> *Cc:* Kamailio (SER) - Users Mailing List >> *Subject:* Re: [SR-Users] Pike module never release IP >> >> >> >> Btw....does pike utilize shared/private memory and children process to >> run it's functionality? If so, can you provide how it's being >> allocated/utilized/ >> >> >> >> On Thu, Dec 5, 2019 at 10:22 AM Andrew Chen wrote: >> >> Hi Henning, >> >> >> >> Just this once on 5.2.5 vers. We had this running on 4.1.5 for many >> years and did not see such behavior. Our QA group ran load tests to >> trigger pike and could not reproduce this problem. >> >> >> >> I guess I'll mark this as one off for now until we run into it again. >> >> >> >> On Thu, Dec 5, 2019 at 3:36 AM Henning Westerholt wrote: >> >> Hello Andrew, >> >> >> >> I don’t remember this; pike exists for a long time now and did not see >> any big changes recently. >> >> >> >> Do you see this problem frequently and/or can reproduce it? If yes, >> consider opening a bug report with more details (e.g. logs) on our tracker. >> >> >> >> Cheers, >> >> >> >> Henning >> >> >> >> -- >> >> Henning Westerholt – https://skalatan.de/blog/ >> >> Kamailio services – https://gilawa.com >> >> >> >> *From:* sr-users *On Behalf Of *Andrew >> Chen >> *Sent:* Wednesday, December 4, 2019 7:07 PM >> *To:* Kamailio (SER) - Users Mailing List >> *Subject:* [SR-Users] Pike module never release IP >> >> >> >> Hi all, >> >> >> >> Have anyone ever experienced pike module not releasing the IP after >> "remove_latency" period? >> >> >> >> We ran a load test and this is what happened to one of the two paired >> nodes and I had to restart kamailio process to release it. >> >> >> >> I'm running Kam 5.2.5 >> >> >> >> Thanks. >> >> >> >> -- >> >> Andy Chen >> >> Sr. Telephony Lead Engineer >> >> achen@ fuze.com >> >> >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> >> >> >> >> -- >> >> Andy Chen >> >> Sr. Telephony Lead Engineer >> >> 415 516 5535 (M) >> >> achen@ fuze.com >> >> >> >> >> >> >> -- >> >> Andy Chen >> >> Sr. Telephony Lead Engineer >> >> 415 516 5535 (M) >> >> achen@ fuze.com >> >> >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> > > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Pike module never release IP
Ok thanks for the confirmation Henning. On Fri, Dec 6, 2019 at 5:09 AM Henning Westerholt wrote: > Hi Andrew, > > > > the data is hold in shared memory; it does not start child processes. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* Andrew Chen > *Sent:* Thursday, December 5, 2019 9:14 PM > *To:* Henning Westerholt > *Cc:* Kamailio (SER) - Users Mailing List > *Subject:* Re: [SR-Users] Pike module never release IP > > > > Btwdoes pike utilize shared/private memory and children process to run > it's functionality? If so, can you provide how it's being > allocated/utilized/ > > > > On Thu, Dec 5, 2019 at 10:22 AM Andrew Chen wrote: > > Hi Henning, > > > > Just this once on 5.2.5 vers. We had this running on 4.1.5 for many years > and did not see such behavior. Our QA group ran load tests to trigger > pike and could not reproduce this problem. > > > > I guess I'll mark this as one off for now until we run into it again. > > > > On Thu, Dec 5, 2019 at 3:36 AM Henning Westerholt wrote: > > Hello Andrew, > > > > I don’t remember this; pike exists for a long time now and did not see any > big changes recently. > > > > Do you see this problem frequently and/or can reproduce it? If yes, > consider opening a bug report with more details (e.g. logs) on our tracker. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* sr-users *On Behalf Of *Andrew > Chen > *Sent:* Wednesday, December 4, 2019 7:07 PM > *To:* Kamailio (SER) - Users Mailing List > *Subject:* [SR-Users] Pike module never release IP > > > > Hi all, > > > > Have anyone ever experienced pike module not releasing the IP after > "remove_latency" period? > > > > We ran a load test and this is what happened to one of the two paired > nodes and I had to restart kamailio process to release it. > > > > I'm running Kam 5.2.5 > > > > Thanks. > > > > -- > > Andy Chen > > Sr. Telephony Lead Engineer > > achen@ fuze.com > > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > > > > -- > > Andy Chen > > Sr. Telephony Lead Engineer > > 415 516 5535 (M) > > achen@ fuze.com > > > > > > > -- > > Andy Chen > > Sr. Telephony Lead Engineer > > 415 516 5535 (M) > > achen@ fuze.com > > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Pike module never release IP
Btwdoes pike utilize shared/private memory and children process to run it's functionality? If so, can you provide how it's being allocated/utilized/ On Thu, Dec 5, 2019 at 10:22 AM Andrew Chen wrote: > Hi Henning, > > Just this once on 5.2.5 vers. We had this running on 4.1.5 for many years > and did not see such behavior. Our QA group ran load tests to trigger > pike and could not reproduce this problem. > > I guess I'll mark this as one off for now until we run into it again. > > On Thu, Dec 5, 2019 at 3:36 AM Henning Westerholt wrote: > >> Hello Andrew, >> >> >> >> I don’t remember this; pike exists for a long time now and did not see >> any big changes recently. >> >> >> >> Do you see this problem frequently and/or can reproduce it? If yes, >> consider opening a bug report with more details (e.g. logs) on our tracker. >> >> >> >> Cheers, >> >> >> >> Henning >> >> >> >> -- >> >> Henning Westerholt – https://skalatan.de/blog/ >> >> Kamailio services – https://gilawa.com >> >> >> >> *From:* sr-users *On Behalf Of *Andrew >> Chen >> *Sent:* Wednesday, December 4, 2019 7:07 PM >> *To:* Kamailio (SER) - Users Mailing List >> *Subject:* [SR-Users] Pike module never release IP >> >> >> >> Hi all, >> >> >> >> Have anyone ever experienced pike module not releasing the IP after >> "remove_latency" period? >> >> >> >> We ran a load test and this is what happened to one of the two paired >> nodes and I had to restart kamailio process to release it. >> >> >> >> I'm running Kam 5.2.5 >> >> >> >> Thanks. >> >> >> >> -- >> >> Andy Chen >> >> Sr. Telephony Lead Engineer >> >> achen@ fuze.com >> >> >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> > > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Pike module never release IP
Hi Henning, Just this once on 5.2.5 vers. We had this running on 4.1.5 for many years and did not see such behavior. Our QA group ran load tests to trigger pike and could not reproduce this problem. I guess I'll mark this as one off for now until we run into it again. On Thu, Dec 5, 2019 at 3:36 AM Henning Westerholt wrote: > Hello Andrew, > > > > I don’t remember this; pike exists for a long time now and did not see any > big changes recently. > > > > Do you see this problem frequently and/or can reproduce it? If yes, > consider opening a bug report with more details (e.g. logs) on our tracker. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* sr-users *On Behalf Of *Andrew > Chen > *Sent:* Wednesday, December 4, 2019 7:07 PM > *To:* Kamailio (SER) - Users Mailing List > *Subject:* [SR-Users] Pike module never release IP > > > > Hi all, > > > > Have anyone ever experienced pike module not releasing the IP after > "remove_latency" period? > > > > We ran a load test and this is what happened to one of the two paired > nodes and I had to restart kamailio process to release it. > > > > I'm running Kam 5.2.5 > > > > Thanks. > > > > -- > > Andy Chen > > Sr. Telephony Lead Engineer > > achen@ fuze.com > > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Pike module never release IP
Hi all, Have anyone ever experienced pike module not releasing the IP after "remove_latency" period? We ran a load test and this is what happened to one of the two paired nodes and I had to restart kamailio process to release it. I'm running Kam 5.2.5 Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] TLS v 1.3 failed call
Thanks Daniel. On Tue, Nov 19, 2019 at 5:20 PM Daniel-Constantin Mierla wrote: > Hello, > > looks like client side is doing renegotiation, which is disabled by > default: > > * > https://www.kamailio.org/docs/modules/devel/modules/tls.html#tls.p.renegotiation > > Cheers, > Daniel > On 19.11.19 21:22, Andrew Chen wrote: > > Hi guys, > > I was wondering if someone can help decipher what these few lines mean? > > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls > [tls_server.c:431]: tls_accept(): tls_accept: new connection from > 10.94.98.18:51698 using TLSv1.3 TLS_AES_256_GCM_SHA384 256 > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls > [tls_server.c:434]: tls_accept(): tls_accept: local socket: > 206.81.191.45:443 > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls > [tls_server.c:445]: tls_accept(): tls_accept: client did not present a > certificate > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls > [tls_server.c:1189]: tls_read_f(): Reading on a renegotiation of connection > (n:1652) (0) > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: > [core/tcp_read.c:1527]: tcp_read_req(): EOF > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: > [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0x56367f8b8f80, > 12, -1, 0x10) fd_no=2 called > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: > [core/tcp_read.c:1680]: release_tcpconn(): releasing con 0x7fcfc20c57b0, > state -1, fd=12, id=23 ([10.94.98.18]:51698 -> [10.94.98.18]:443) > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: > [core/tcp_read.c:1684]: release_tcpconn(): extra_data 0x7fcfc2089f88 > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21517]: DEBUG: > [core/tcp_main.c:3320]: handle_tcp_child(): reader response= 7fcfc20c57b0, > -1 from 16 > Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21517]: DEBUG: tls > [tls_server.c:683]: tls_h_close(): Closing SSL connection 0x7fcfc2089f88 > > Bottom line is kamailio closed the connection and I have method setting to > this: > > root@sjomainkama51:/etc/kamailio # grep method tls.cfg > method = TLSv1.1+ > > Supposedly this should work? > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > ___ > Kamailio (SER) - Users Mailing > Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- > www.linkedin.com/in/miconda > Kamailio World Conference - April 27-29, 2020, in Berlin -- > www.kamailioworld.com > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] TLS v 1.3 failed call
Hi guys, I was wondering if someone can help decipher what these few lines mean? Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:431]: tls_accept(): tls_accept: new connection from 10.94.98.18:51698 using TLSv1.3 TLS_AES_256_GCM_SHA384 256 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:434]: tls_accept(): tls_accept: local socket: 206.81.191.45:443 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:445]: tls_accept(): tls_accept: client did not present a certificate Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:1189]: tls_read_f(): Reading on a renegotiation of connection (n:1652) (0) Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: [core/tcp_read.c:1527]: tcp_read_req(): EOF Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0x56367f8b8f80, 12, -1, 0x10) fd_no=2 called Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: [core/tcp_read.c:1680]: release_tcpconn(): releasing con 0x7fcfc20c57b0, state -1, fd=12, id=23 ([10.94.98.18]:51698 -> [10.94.98.18]:443) Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: [core/tcp_read.c:1684]: release_tcpconn(): extra_data 0x7fcfc2089f88 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21517]: DEBUG: [core/tcp_main.c:3320]: handle_tcp_child(): reader response= 7fcfc20c57b0, -1 from 16 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21517]: DEBUG: tls [tls_server.c:683]: tls_h_close(): Closing SSL connection 0x7fcfc2089f88 Bottom line is kamailio closed the connection and I have method setting to this: root@sjomainkama51:/etc/kamailio # grep method tls.cfg method = TLSv1.1+ Supposedly this should work? -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio stop responding to AWS R53 health check
Hi Karsten, These are our current settings: root@sjoprodkama51:/var/log # grep max_connections /etc/kamailio/kamailio.cfg tcp_max_connections=32768 tls_max_connections=32768 root@sjoprodkama51:/var/log # which seems more than enough I would think. On Wed, Nov 13, 2019 at 4:25 PM Andrew Chen wrote: > Thanks Jurijs. > > We just upgraded to 5.2.5 to support openssl 1.1.1 which is required for > ubuntu 18.04. Is it possible to have back port this fix to 5.2.x release > since we just released 5.2.5 through our battery of QA testing? > > On Wed, Nov 13, 2019 at 4:14 PM Jurijs Ivolga > wrote: > >> Hi Andrew, >> >> I'm pretty sure this is bug what you are talking about: >> >> https://github.com/kamailio/kamailio/issues/1860 >> >> It should be fixed in 5.3.0 I believe, or you can always downgrade >> openssl to 1.0 as described here: >> >> https://www.kamailio.org/wiki/tutorials/tls/howto-openssl-1-0 >> >> Jurijs >> >> >> On Wed, Nov 13, 2019 at 10:40 PM Andrew Chen wrote: >> >>> So another update. As it turns out, this remote IP sent a slew of tls >>> connections to the Kamailio box within the same second: >>> >>> root@sjoprodkama51:/var/log # grep 104.248.215.53 falco_events.log | wc >>> -l >>> 114 >>> root@sjoprodkama51:/var/log # >>> >>> this all came in at 18:28:05 which matches the time of those errors. >>> >>> Should this cause Kamailio to totally freeze up? >>> >>> On Wed, Nov 13, 2019 at 2:51 PM Andrew Chen wrote: >>> >>>> Hi Karsten, >>>> >>>> Good point. See below: >>>> >>>> Kamailio ver: 5.2.5+bionic >>>> Ubuntu version: 18.04.02 LTS >>>> Kernel version: 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:07:03 UTC >>>> 2019 x86_64 x86_64 x86_64 GNU/Linux >>>> openssl version: 1.1.1-1ubuntu2.1~18.04.4 >>>> >>>> >>>> Setup: >>>> - R53 is our load balancer on top running health check on a pair of >>>> kams. >>>> - First node has no issues and running the same setup + SIP traffic >>>> - Second node as shown above was the one that went into "Unhealthy" >>>> state. >>>> >>>> Hope this helps >>>> >>>> On Wed, Nov 13, 2019 at 2:46 PM Karsten Horsmann >>>> wrote: >>>> >>>>> Hi Andrew, >>>>> >>>>> Would help if you could could describe your setup a bit more. >>>>> >>>>> Like the Kamailio version, the system distro and as we see many tls >>>>> messages your openssl version. >>>>> >>>>> Maybe the traveling developers have any ideas then. >>>>> >>>>> Cheers >>>>> Karsten Horsmann >>>>> >>>>> Andrew Chen schrieb am Mi., 13. Nov. 2019, 20:29: >>>>> >>>>>> Hi all, >>>>>> >>>>>> >>>>>> R53 reported healthcheck failure on tcp port 5060. Looking at the >>>>>> system, all the ports that kamailio listens on can't be monitored >>>>>> remotely. To test this theory, I can telnet successfully to consul port. >>>>>> I ran tcpdump and see no responses returned back to R53 monitoring hosts: >>>>>> >>>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol >>>>>> decode >>>>>> listening on ens5, link-type EN10MB (Ethernet), capture size 262144 bytes >>>>>> 19:11:49.368378 IP >>>>>> ec2-54-241-32-75.us-west-1.compute.amazonaws.com.10072 > >>>>>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 1252984048, win 29200, >>>>>> options [mss 1460,sackOK,TS val 3770272726 ecr 0,nop,wscale 7], length 0 >>>>>> 19:11:49.558877 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >>>>>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >>>>>> options [mss 1460,sackOK,TS val 1780607162 ecr 0,nop,wscale 7], length 0 >>>>>> 19:11:50.572870 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >>>>>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >>>>>> options [mss 1460,sackOK,TS val 1780608175 ecr 0,nop,wscale 7], length 0 >>>>>> >>>>>> Fixed the issue after restarting kamailio process.
Re: [SR-Users] Kamailio stop responding to AWS R53 health check
Thanks Jurijs. We just upgraded to 5.2.5 to support openssl 1.1.1 which is required for ubuntu 18.04. Is it possible to have back port this fix to 5.2.x release since we just released 5.2.5 through our battery of QA testing? On Wed, Nov 13, 2019 at 4:14 PM Jurijs Ivolga wrote: > Hi Andrew, > > I'm pretty sure this is bug what you are talking about: > > https://github.com/kamailio/kamailio/issues/1860 > > It should be fixed in 5.3.0 I believe, or you can always downgrade openssl > to 1.0 as described here: > > https://www.kamailio.org/wiki/tutorials/tls/howto-openssl-1-0 > > Jurijs > > > On Wed, Nov 13, 2019 at 10:40 PM Andrew Chen wrote: > >> So another update. As it turns out, this remote IP sent a slew of tls >> connections to the Kamailio box within the same second: >> >> root@sjoprodkama51:/var/log # grep 104.248.215.53 falco_events.log | wc >> -l >> 114 >> root@sjoprodkama51:/var/log # >> >> this all came in at 18:28:05 which matches the time of those errors. >> >> Should this cause Kamailio to totally freeze up? >> >> On Wed, Nov 13, 2019 at 2:51 PM Andrew Chen wrote: >> >>> Hi Karsten, >>> >>> Good point. See below: >>> >>> Kamailio ver: 5.2.5+bionic >>> Ubuntu version: 18.04.02 LTS >>> Kernel version: 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:07:03 UTC >>> 2019 x86_64 x86_64 x86_64 GNU/Linux >>> openssl version: 1.1.1-1ubuntu2.1~18.04.4 >>> >>> >>> Setup: >>> - R53 is our load balancer on top running health check on a pair of kams. >>> - First node has no issues and running the same setup + SIP traffic >>> - Second node as shown above was the one that went into "Unhealthy" >>> state. >>> >>> Hope this helps >>> >>> On Wed, Nov 13, 2019 at 2:46 PM Karsten Horsmann >>> wrote: >>> >>>> Hi Andrew, >>>> >>>> Would help if you could could describe your setup a bit more. >>>> >>>> Like the Kamailio version, the system distro and as we see many tls >>>> messages your openssl version. >>>> >>>> Maybe the traveling developers have any ideas then. >>>> >>>> Cheers >>>> Karsten Horsmann >>>> >>>> Andrew Chen schrieb am Mi., 13. Nov. 2019, 20:29: >>>> >>>>> Hi all, >>>>> >>>>> >>>>> R53 reported healthcheck failure on tcp port 5060. Looking at the >>>>> system, all the ports that kamailio listens on can't be monitored >>>>> remotely. To test this theory, I can telnet successfully to consul port. >>>>> I ran tcpdump and see no responses returned back to R53 monitoring hosts: >>>>> >>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode >>>>> listening on ens5, link-type EN10MB (Ethernet), capture size 262144 bytes >>>>> 19:11:49.368378 IP ec2-54-241-32-75.us-west-1.compute.amazonaws.com.10072 >>>>> > sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 1252984048, win >>>>> 29200, options [mss 1460,sackOK,TS val 3770272726 ecr 0,nop,wscale 7], >>>>> length 0 >>>>> 19:11:49.558877 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >>>>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >>>>> options [mss 1460,sackOK,TS val 1780607162 ecr 0,nop,wscale 7], length 0 >>>>> 19:11:50.572870 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >>>>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >>>>> options [mss 1460,sackOK,TS val 1780608175 ecr 0,nop,wscale 7], length 0 >>>>> >>>>> Fixed the issue after restarting kamailio process. >>>>> >>>>> Given this system is support production traffic, we have minimized the >>>>> logging on it. The events that we thought may lead to this is as follows: >>>>> >>>>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >>>>> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >>>>> routines:tls_early_post_process_client_hello:unsupported protocol >>>>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >>>>> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >>>>> - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) >>>>> Nov 13 18:28:05
Re: [SR-Users] Kamailio stop responding to AWS R53 health check
So another update. As it turns out, this remote IP sent a slew of tls connections to the Kamailio box within the same second: root@sjoprodkama51:/var/log # grep 104.248.215.53 falco_events.log | wc -l 114 root@sjoprodkama51:/var/log # this all came in at 18:28:05 which matches the time of those errors. Should this cause Kamailio to totally freeze up? On Wed, Nov 13, 2019 at 2:51 PM Andrew Chen wrote: > Hi Karsten, > > Good point. See below: > > Kamailio ver: 5.2.5+bionic > Ubuntu version: 18.04.02 LTS > Kernel version: 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:07:03 UTC > 2019 x86_64 x86_64 x86_64 GNU/Linux > openssl version: 1.1.1-1ubuntu2.1~18.04.4 > > > Setup: > - R53 is our load balancer on top running health check on a pair of kams. > - First node has no issues and running the same setup + SIP traffic > - Second node as shown above was the one that went into "Unhealthy" state. > > Hope this helps > > On Wed, Nov 13, 2019 at 2:46 PM Karsten Horsmann > wrote: > >> Hi Andrew, >> >> Would help if you could could describe your setup a bit more. >> >> Like the Kamailio version, the system distro and as we see many tls >> messages your openssl version. >> >> Maybe the traveling developers have any ideas then. >> >> Cheers >> Karsten Horsmann >> >> Andrew Chen schrieb am Mi., 13. Nov. 2019, 20:29: >> >>> Hi all, >>> >>> >>> R53 reported healthcheck failure on tcp port 5060. Looking at the >>> system, all the ports that kamailio listens on can't be monitored >>> remotely. To test this theory, I can telnet successfully to consul port. >>> I ran tcpdump and see no responses returned back to R53 monitoring hosts: >>> >>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode >>> listening on ens5, link-type EN10MB (Ethernet), capture size 262144 bytes >>> 19:11:49.368378 IP ec2-54-241-32-75.us-west-1.compute.amazonaws.com.10072 > >>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 1252984048, win 29200, >>> options [mss 1460,sackOK,TS val 3770272726 ecr 0,nop,wscale 7], length 0 >>> 19:11:49.558877 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >>> options [mss 1460,sackOK,TS val 1780607162 ecr 0,nop,wscale 7], length 0 >>> 19:11:50.572870 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >>> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >>> options [mss 1460,sackOK,TS val 1780608175 ecr 0,nop,wscale 7], length 0 >>> >>> Fixed the issue after restarting kamailio process. >>> >>> Given this system is support production traffic, we have minimized the >>> logging on it. The events that we thought may lead to this is as follows: >>> >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >>> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >>> routines:tls_early_post_process_client_hello:unsupported protocol >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >>> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >>> - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >>> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >>> routines:tls_early_post_process_client_hello:unsupported protocol >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >>> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >>> - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls >>> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >>> routines:tls_early_post_process_client_hello:unsupported protocol >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: >>> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >>> - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >>> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >>> routines:tls_early_post_process_client_hello:unsupported protocol >>> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >>> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >>> - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) >>> Nov 13 18:28:05 sjoprodkama51 /usr
Re: [SR-Users] Kamailio stop responding to AWS R53 health check
Hi Karsten, Good point. See below: Kamailio ver: 5.2.5+bionic Ubuntu version: 18.04.02 LTS Kernel version: 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:07:03 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux openssl version: 1.1.1-1ubuntu2.1~18.04.4 Setup: - R53 is our load balancer on top running health check on a pair of kams. - First node has no issues and running the same setup + SIP traffic - Second node as shown above was the one that went into "Unhealthy" state. Hope this helps On Wed, Nov 13, 2019 at 2:46 PM Karsten Horsmann wrote: > Hi Andrew, > > Would help if you could could describe your setup a bit more. > > Like the Kamailio version, the system distro and as we see many tls > messages your openssl version. > > Maybe the traveling developers have any ideas then. > > Cheers > Karsten Horsmann > > Andrew Chen schrieb am Mi., 13. Nov. 2019, 20:29: > >> Hi all, >> >> >> R53 reported healthcheck failure on tcp port 5060. Looking at the >> system, all the ports that kamailio listens on can't be monitored >> remotely. To test this theory, I can telnet successfully to consul port. >> I ran tcpdump and see no responses returned back to R53 monitoring hosts: >> >> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode >> listening on ens5, link-type EN10MB (Ethernet), capture size 262144 bytes >> 19:11:49.368378 IP ec2-54-241-32-75.us-west-1.compute.amazonaws.com.10072 > >> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 1252984048, win 29200, >> options [mss 1460,sackOK,TS val 3770272726 ecr 0,nop,wscale 7], length 0 >> 19:11:49.558877 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >> options [mss 1460,sackOK,TS val 1780607162 ecr 0,nop,wscale 7], length 0 >> 19:11:50.572870 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > >> sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, >> options [mss 1460,sackOK,TS val 1780608175 ecr 0,nop,wscale 7], length 0 >> >> Fixed the issue after restarting kamailio process. >> >> Given this system is support production traffic, we have minimized the >> logging on it. The events that we thought may lead to this is as follows: >> >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >> routines:tls_early_post_process_client_hello:unsupported protocol >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >> - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >> routines:tls_early_post_process_client_hello:unsupported protocol >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >> - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls >> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >> routines:tls_early_post_process_client_hello:unsupported protocol >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: >> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >> - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >> routines:tls_early_post_process_client_hello:unsupported protocol >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >> - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >> routines:tls_early_post_process_client_hello:unsupported protocol >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading >> - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls >> [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL >> routines:tls_early_post_process_client_hello:unsupported protocol >> Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: >> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error readin
[SR-Users] Kamailio stop responding to AWS R53 health check
Hi all, R53 reported healthcheck failure on tcp port 5060. Looking at the system, all the ports that kamailio listens on can't be monitored remotely. To test this theory, I can telnet successfully to consul port. I ran tcpdump and see no responses returned back to R53 monitoring hosts: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens5, link-type EN10MB (Ethernet), capture size 262144 bytes 19:11:49.368378 IP ec2-54-241-32-75.us-west-1.compute.amazonaws.com.10072 > sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 1252984048, win 29200, options [mss 1460,sackOK,TS val 3770272726 ecr 0,nop,wscale 7], length 0 19:11:49.558877 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, options [mss 1460,sackOK,TS val 1780607162 ecr 0,nop,wscale 7], length 0 19:11:50.572870 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, options [mss 1460,sackOK,TS val 1780608175 ecr 0,nop,wscale 7], length 0 Fixed the issue after restarting kamailio process. Given this system is support production traffic, we have minimized the logging on it. The events that we thought may lead to this is as follows: Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdd829e8 r: 0x7f33fdd82a68 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb70738 r: 0x7f33fdb707b8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS
Re: [SR-Users] Kamailio v5.2.5 Released
Awesome. Thanks. On Thu, Oct 10, 2019 at 1:04 PM Joel Serrano wrote: > Hey Andy, > > I think you probably checked before the CI pipeline finished preparing the > packages haha... Right now v5.2.5 is available in the repo: > > http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/ > > > Cheers, > Joel. > > > > On Thu, Oct 10, 2019 at 7:17 AM Andrew Chen wrote: > >> Hi Daniel, >> >> Can we have this available in apt repository as well? I don't seem to >> see it: >> >> kamailio | 5.2.4+bionic | http://deb.kamailio.org/kamailio52 >> bionic/main amd64 Packages >> kamailio | 5.2.4+bionic | http://deb.kamailio.org/kamailio52 >> bionic/main Sources >> >> This is all I see even after apt-get update. >> >> Thanks. >> --Andy >> >> >> On Thu, Oct 10, 2019 at 8:26 AM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> Hello, >>> >>> Kamailio SIP Server v5.2.5 stable release is out. >>> >>> This is a maintenance release of the latest stable branch, 5.2, that >>> includes fixes since the release of v5.2.4. There is no change to >>> database schema or configuration language structure that you have to do >>> on previous installations of v5.2.x. Deployments running previous v5.2.x >>> versions are strongly recommended to be upgraded to v5.2.5. >>> >>> For more details about version 5.2.5 (including links and guidelines to >>> download the tarball or from GIT repository), visit: >>> >>> * https://www.kamailio.org/w/2019/10/kamailio-v5-2-5-released/ >>> >>> RPM, Debian/Ubuntu packages will be available soon as well. >>> >>> Many thanks to all contributing and using Kamailio! >>> >>> Cheers, >>> Daniel >>> >>> -- >>> Daniel-Constantin Mierla -- www.asipto.com >>> www.twitter.com/miconda -- www.linkedin.com/in/miconda >>> Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- >>> https://asipto.com/u/kat >>> >>> >>> ___ >>> Kamailio (SER) - Users Mailing List >>> sr-users@lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >> >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> 415 516 5535 (M) >> achen@ fuze.com >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio v5.2.5 Released
Hi Daniel, Can we have this available in apt repository as well? I don't seem to see it: kamailio | 5.2.4+bionic | http://deb.kamailio.org/kamailio52 bionic/main amd64 Packages kamailio | 5.2.4+bionic | http://deb.kamailio.org/kamailio52 bionic/main Sources This is all I see even after apt-get update. Thanks. --Andy On Thu, Oct 10, 2019 at 8:26 AM Daniel-Constantin Mierla wrote: > Hello, > > Kamailio SIP Server v5.2.5 stable release is out. > > This is a maintenance release of the latest stable branch, 5.2, that > includes fixes since the release of v5.2.4. There is no change to > database schema or configuration language structure that you have to do > on previous installations of v5.2.x. Deployments running previous v5.2.x > versions are strongly recommended to be upgraded to v5.2.5. > > For more details about version 5.2.5 (including links and guidelines to > download the tarball or from GIT repository), visit: > > * https://www.kamailio.org/w/2019/10/kamailio-v5-2-5-released/ > > RPM, Debian/Ubuntu packages will be available soon as well. > > Many thanks to all contributing and using Kamailio! > > Cheers, > Daniel > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- > https://asipto.com/u/kat > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
Hi Daniel, Just checking in to get any updates/findings on the stack trace I provided above. Thanks. On Thu, Sep 19, 2019 at 11:29 AM Andrew Chen wrote: > So what I pasted above is the same segfault we got from libcrypto.so > > On Thu, Sep 19, 2019 at 11:03 AM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> You do not need to reproduce if you still have the core files and >> installed the debug symbols for your version, just run again gdb on the >> core and get the backtraces. >> >> Cheers, >> Daniel >> On 18.09.19 22:35, Andrew Chen wrote: >> >> Yup understood. I'll provide the bt when we can reproduce this. >> >> Thanks >> >> On Wed, Sep 18, 2019 at 4:32 PM Henning Westerholt >> wrote: >> >>> Hi Andrew, >>> >>> the 5.2.4 does not contain the 5.3-pre1 workaround yet. >>> >>> So if you test the workaround you need to install the lastest 5.3 from >>> the git master debian repository. >>> >>> But nevertheless it would be good to look at the backtrace, while you >>> have it. >>> >>> Cheers, >>> >>> Henning >>> Am 18.09.19 um 22:10 schrieb Joel Serrano: >>> >>> Hi Andrew, >>> >>> Download from here: >>> http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/ >>> >>> You have kamailio-dbg v5.2.4 (latest 5.2) for all distros... >>> >>> Example for amd64+stretch: >>> http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/kamailio-dbg_5.2.4%2Bstretch_amd64.deb >>> >>> Cheers, >>> Joel. >>> >>> >>> >>> >>> >>> On Wed, Sep 18, 2019 at 12:16 PM Andrew Chen wrote: >>> >>>> Hi Henning, >>>> >>>> I'm running 5.2.4. Will this deb package work? >>>> >>>> On Wed, Sep 18, 2019 at 2:39 PM Andrew Chen wrote: >>>> >>>>> Thanks Henning >>>>> >>>>> On Wed, Sep 18, 2019 at 2:13 PM Henning Westerholt >>>>> wrote: >>>>> >>>>>> Hello Andrew, >>>>>> >>>>>> strange - it should be there, as it is available on deb.kamailio.org. >>>>>> >>>>>> >>>>>> Here e.g. the one for 64bit stretch: >>>>>> >>>>>> >>>>>> https://deb.kamailio.org/kamailiodev-nightly/pool/main/k/kamailio/kamailio-dbg_5.3.0~pre1%2B0~20190918005413.1490%2Bstretch_amd64.deb >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Henning >>>>>> Am 18.09.19 um 18:52 schrieb Andrew Chen: >>>>>> >>>>>> I don't see one for debug: >>>>>> >>>>>> root@ashintgkama51:~ # apt-cache search kamailio >>>>>> >>>>>> resource-agents - Cluster Resource Agents >>>>>> >>>>>> kamailio - very fast, dynamic and configurable SIP server >>>>>> >>>>>> kamailio-autheph-modules - authentication using ephemeral credentials >>>>>> for the Kamailio SIP server >>>>>> >>>>>> kamailio-berkeley-bin - Berkeley database module for Kamailio - >>>>>> helper program >>>>>> >>>>>> kamailio-berkeley-modules - Berkeley database module for the Kamailio >>>>>> SIP server >>>>>> >>>>>> kamailio-carrierroute-modules - carrierroute module for the Kamailio >>>>>> SIP server >>>>>> >>>>>> kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server >>>>>> >>>>>> kamailio-cpl-modules - CPL module (CPL interpreter engine) for the >>>>>> Kamailio SIP server >>>>>> >>>>>> kamailio-erlang-modules - Erlang modules for the Kamailio SIP server >>>>>> >>>>>> kamailio-geoip-modules - geoip module for the Kamailio SIP Server >>>>>> >>>>>> kamailio-geoip2-modules - geoip2 module for the Kamailio SIP Server >>>>>> >>>>>> kamailio-ims-modules - IMS module for the Kamailio SIP server >>>>>> >>>>>> kamailio-json-modules - Json parser and Json-RPC modules for the >>>>>> Kamailio SIP server >>>>>> >>>>>> On Wed, Sep 18, 2019 at 11:26 AM Da
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
So what I pasted above is the same segfault we got from libcrypto.so On Thu, Sep 19, 2019 at 11:03 AM Daniel-Constantin Mierla wrote: > You do not need to reproduce if you still have the core files and > installed the debug symbols for your version, just run again gdb on the > core and get the backtraces. > > Cheers, > Daniel > On 18.09.19 22:35, Andrew Chen wrote: > > Yup understood. I'll provide the bt when we can reproduce this. > > Thanks > > On Wed, Sep 18, 2019 at 4:32 PM Henning Westerholt wrote: > >> Hi Andrew, >> >> the 5.2.4 does not contain the 5.3-pre1 workaround yet. >> >> So if you test the workaround you need to install the lastest 5.3 from >> the git master debian repository. >> >> But nevertheless it would be good to look at the backtrace, while you >> have it. >> >> Cheers, >> >> Henning >> Am 18.09.19 um 22:10 schrieb Joel Serrano: >> >> Hi Andrew, >> >> Download from here: >> http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/ >> >> You have kamailio-dbg v5.2.4 (latest 5.2) for all distros... >> >> Example for amd64+stretch: >> http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/kamailio-dbg_5.2.4%2Bstretch_amd64.deb >> >> Cheers, >> Joel. >> >> >> >> >> >> On Wed, Sep 18, 2019 at 12:16 PM Andrew Chen wrote: >> >>> Hi Henning, >>> >>> I'm running 5.2.4. Will this deb package work? >>> >>> On Wed, Sep 18, 2019 at 2:39 PM Andrew Chen wrote: >>> >>>> Thanks Henning >>>> >>>> On Wed, Sep 18, 2019 at 2:13 PM Henning Westerholt >>>> wrote: >>>> >>>>> Hello Andrew, >>>>> >>>>> strange - it should be there, as it is available on deb.kamailio.org. >>>>> >>>>> Here e.g. the one for 64bit stretch: >>>>> >>>>> >>>>> https://deb.kamailio.org/kamailiodev-nightly/pool/main/k/kamailio/kamailio-dbg_5.3.0~pre1%2B0~20190918005413.1490%2Bstretch_amd64.deb >>>>> >>>>> Cheers, >>>>> >>>>> Henning >>>>> Am 18.09.19 um 18:52 schrieb Andrew Chen: >>>>> >>>>> I don't see one for debug: >>>>> >>>>> root@ashintgkama51:~ # apt-cache search kamailio >>>>> >>>>> resource-agents - Cluster Resource Agents >>>>> >>>>> kamailio - very fast, dynamic and configurable SIP server >>>>> >>>>> kamailio-autheph-modules - authentication using ephemeral credentials >>>>> for the Kamailio SIP server >>>>> >>>>> kamailio-berkeley-bin - Berkeley database module for Kamailio - helper >>>>> program >>>>> >>>>> kamailio-berkeley-modules - Berkeley database module for the Kamailio >>>>> SIP server >>>>> >>>>> kamailio-carrierroute-modules - carrierroute module for the Kamailio >>>>> SIP server >>>>> >>>>> kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server >>>>> >>>>> kamailio-cpl-modules - CPL module (CPL interpreter engine) for the >>>>> Kamailio SIP server >>>>> >>>>> kamailio-erlang-modules - Erlang modules for the Kamailio SIP server >>>>> >>>>> kamailio-geoip-modules - geoip module for the Kamailio SIP Server >>>>> >>>>> kamailio-geoip2-modules - geoip2 module for the Kamailio SIP Server >>>>> >>>>> kamailio-ims-modules - IMS module for the Kamailio SIP server >>>>> >>>>> kamailio-json-modules - Json parser and Json-RPC modules for the >>>>> Kamailio SIP server >>>>> >>>>> On Wed, Sep 18, 2019 at 11:26 AM Daniel-Constantin Mierla < >>>>> mico...@gmail.com> wrote: >>>>> >>>>>> You have to install the debug symbols package, otherwise the >>>>>> backtrace doesn't show any useful information. It just require to install >>>>>> that package and then get again the backtraces. The package name should >>>>>> be >>>>>> kamailio-dbg. >>>>>> >>>>>> Cheers, >>>>>> Daniel >>>>>> On 18.09.19 16:37, Andrew Chen wrote: >>>>>> >>>>>> Sorry..forgot bt full output >>>
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
- 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28568 28521 0 80 0 - 80054 ep_pol 09:53 ?00:00:01 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28569 28521 0 80 0 - 80021 ep_pol 09:53 ?00:00:01 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28570 28521 0 80 0 - 80021 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28571 28521 0 80 0 - 80021 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28572 28521 0 80 0 - 79990 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28573 28521 0 80 0 - 79988 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28574 28521 0 80 0 - 79989 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28575 28521 0 80 0 - 79989 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28576 28521 0 80 0 - 79924 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28577 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28578 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28579 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28580 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28581 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28582 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28583 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio 1 S kamailio 28584 28521 0 80 0 - 79922 ep_pol 09:53 ?00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 32 -u kamailio -g kamailio On Wed, Sep 18, 2019 at 4:35 PM Andrew Chen wrote: > Yup understood. I'll provide the bt when we can reproduce this. > > Thanks > > On Wed, Sep 18, 2019 at 4:32 PM Henning Westerholt wrote: > >> Hi Andrew, >> >> the 5.2.4 does not contain the 5.3-pre1 workaround yet. >> >> So if you test the workaround you need to install the lastest 5.3 from >> the git master debian repository. >> >> But nevertheless it would be good to look at the backtrace, while you >> have it. >> >> Cheers, >> >> Henning >> Am 18.09.19 um 22:10 schrieb Joel Serrano: >> >> Hi Andrew, >> >> Download from here: >> http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/ >> >> You have kamailio-dbg v5.2.4 (latest 5.2) for all distros... >> >> Example for amd64+stretch: >> http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/kamailio-dbg_5.2.4%2Bstretch_amd64.deb >> >> Cheers, >> Joel. >> >> >> >> >> >> On Wed, Sep 18, 2019 at 12:16 PM Andrew Chen wrote: >> >>> Hi Henning, >>> >>> I'm running 5.2.4. Will this deb package work? >>> >>> On Wed, Sep 18, 2019 at 2:39 PM Andrew Chen wrote: >>> >>>> Thanks Henning >>>> >>>> On Wed, Sep 18, 2019 at 2:13 PM Henning Westerholt >>>> wrote: >>
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
Yup understood. I'll provide the bt when we can reproduce this. Thanks On Wed, Sep 18, 2019 at 4:32 PM Henning Westerholt wrote: > Hi Andrew, > > the 5.2.4 does not contain the 5.3-pre1 workaround yet. > > So if you test the workaround you need to install the lastest 5.3 from the > git master debian repository. > > But nevertheless it would be good to look at the backtrace, while you have > it. > > Cheers, > > Henning > Am 18.09.19 um 22:10 schrieb Joel Serrano: > > Hi Andrew, > > Download from here: > http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/ > > You have kamailio-dbg v5.2.4 (latest 5.2) for all distros... > > Example for amd64+stretch: > http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/kamailio-dbg_5.2.4%2Bstretch_amd64.deb > > Cheers, > Joel. > > > > > > On Wed, Sep 18, 2019 at 12:16 PM Andrew Chen wrote: > >> Hi Henning, >> >> I'm running 5.2.4. Will this deb package work? >> >> On Wed, Sep 18, 2019 at 2:39 PM Andrew Chen wrote: >> >>> Thanks Henning >>> >>> On Wed, Sep 18, 2019 at 2:13 PM Henning Westerholt >>> wrote: >>> >>>> Hello Andrew, >>>> >>>> strange - it should be there, as it is available on deb.kamailio.org. >>>> >>>> Here e.g. the one for 64bit stretch: >>>> >>>> >>>> https://deb.kamailio.org/kamailiodev-nightly/pool/main/k/kamailio/kamailio-dbg_5.3.0~pre1%2B0~20190918005413.1490%2Bstretch_amd64.deb >>>> >>>> Cheers, >>>> >>>> Henning >>>> Am 18.09.19 um 18:52 schrieb Andrew Chen: >>>> >>>> I don't see one for debug: >>>> >>>> root@ashintgkama51:~ # apt-cache search kamailio >>>> >>>> resource-agents - Cluster Resource Agents >>>> >>>> kamailio - very fast, dynamic and configurable SIP server >>>> >>>> kamailio-autheph-modules - authentication using ephemeral credentials >>>> for the Kamailio SIP server >>>> >>>> kamailio-berkeley-bin - Berkeley database module for Kamailio - helper >>>> program >>>> >>>> kamailio-berkeley-modules - Berkeley database module for the Kamailio >>>> SIP server >>>> >>>> kamailio-carrierroute-modules - carrierroute module for the Kamailio >>>> SIP server >>>> >>>> kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server >>>> >>>> kamailio-cpl-modules - CPL module (CPL interpreter engine) for the >>>> Kamailio SIP server >>>> >>>> kamailio-erlang-modules - Erlang modules for the Kamailio SIP server >>>> >>>> kamailio-geoip-modules - geoip module for the Kamailio SIP Server >>>> >>>> kamailio-geoip2-modules - geoip2 module for the Kamailio SIP Server >>>> >>>> kamailio-ims-modules - IMS module for the Kamailio SIP server >>>> >>>> kamailio-json-modules - Json parser and Json-RPC modules for the >>>> Kamailio SIP server >>>> >>>> On Wed, Sep 18, 2019 at 11:26 AM Daniel-Constantin Mierla < >>>> mico...@gmail.com> wrote: >>>> >>>>> You have to install the debug symbols package, otherwise the backtrace >>>>> doesn't show any useful information. It just require to install that >>>>> package and then get again the backtraces. The package name should be >>>>> kamailio-dbg. >>>>> >>>>> Cheers, >>>>> Daniel >>>>> On 18.09.19 16:37, Andrew Chen wrote: >>>>> >>>>> Sorry..forgot bt full output >>>>> >>>>> (gdb) bt full >>>>> >>>>> #0 0x562fcc3544c0 in ?? () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #1 0x562fcc354632 in ?? () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #2 0x562fcc354974 in local_timer_run () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #3 0x562fcc3fb256 in ?? () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #4 0x562fcc3fb64c in tcp_receive_loop () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #5 0x562fcc2acf52 in tcp_i
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
Thanks Joel. Got it to work: root@ashintgkama51:/home/achen # dpkg -l | grep kamailio-dbg ii *kamailio-dbg*:amd64 5.2.4+bionic amd64very fast and configurable SIP server [debug symbols] root@ashintgkama51:/home/achen # Just to confirm there's no modparam or loadmodules for this to work? On Wed, Sep 18, 2019 at 4:14 PM Joel Serrano wrote: > Hi Andrew, > > Download from here: > http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/ > > You have kamailio-dbg v5.2.4 (latest 5.2) for all distros... > > Example for amd64+stretch: > http://deb.kamailio.org/kamailio52/pool/main/k/kamailio/kamailio-dbg_5.2.4%2Bstretch_amd64.deb > > Cheers, > Joel. > > > > > > On Wed, Sep 18, 2019 at 12:16 PM Andrew Chen wrote: > >> Hi Henning, >> >> I'm running 5.2.4. Will this deb package work? >> >> On Wed, Sep 18, 2019 at 2:39 PM Andrew Chen wrote: >> >>> Thanks Henning >>> >>> On Wed, Sep 18, 2019 at 2:13 PM Henning Westerholt >>> wrote: >>> >>>> Hello Andrew, >>>> >>>> strange - it should be there, as it is available on deb.kamailio.org. >>>> >>>> Here e.g. the one for 64bit stretch: >>>> >>>> >>>> https://deb.kamailio.org/kamailiodev-nightly/pool/main/k/kamailio/kamailio-dbg_5.3.0~pre1%2B0~20190918005413.1490%2Bstretch_amd64.deb >>>> >>>> Cheers, >>>> >>>> Henning >>>> Am 18.09.19 um 18:52 schrieb Andrew Chen: >>>> >>>> I don't see one for debug: >>>> >>>> root@ashintgkama51:~ # apt-cache search kamailio >>>> >>>> resource-agents - Cluster Resource Agents >>>> >>>> kamailio - very fast, dynamic and configurable SIP server >>>> >>>> kamailio-autheph-modules - authentication using ephemeral credentials >>>> for the Kamailio SIP server >>>> >>>> kamailio-berkeley-bin - Berkeley database module for Kamailio - helper >>>> program >>>> >>>> kamailio-berkeley-modules - Berkeley database module for the Kamailio >>>> SIP server >>>> >>>> kamailio-carrierroute-modules - carrierroute module for the Kamailio >>>> SIP server >>>> >>>> kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server >>>> >>>> kamailio-cpl-modules - CPL module (CPL interpreter engine) for the >>>> Kamailio SIP server >>>> >>>> kamailio-erlang-modules - Erlang modules for the Kamailio SIP server >>>> >>>> kamailio-geoip-modules - geoip module for the Kamailio SIP Server >>>> >>>> kamailio-geoip2-modules - geoip2 module for the Kamailio SIP Server >>>> >>>> kamailio-ims-modules - IMS module for the Kamailio SIP server >>>> >>>> kamailio-json-modules - Json parser and Json-RPC modules for the >>>> Kamailio SIP server >>>> >>>> On Wed, Sep 18, 2019 at 11:26 AM Daniel-Constantin Mierla < >>>> mico...@gmail.com> wrote: >>>> >>>>> You have to install the debug symbols package, otherwise the backtrace >>>>> doesn't show any useful information. It just require to install that >>>>> package and then get again the backtraces. The package name should be >>>>> kamailio-dbg. >>>>> >>>>> Cheers, >>>>> Daniel >>>>> On 18.09.19 16:37, Andrew Chen wrote: >>>>> >>>>> Sorry..forgot bt full output >>>>> >>>>> (gdb) bt full >>>>> >>>>> #0 0x562fcc3544c0 in ?? () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #1 0x562fcc354632 in ?? () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #2 0x562fcc354974 in local_timer_run () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #3 0x562fcc3fb256 in ?? () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #4 0x562fcc3fb64c in tcp_receive_loop () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #5 0x562fcc2acf52 in tcp_init_children () >>>>> >>>>> No symbol table info available. >>>>> >>>>> #6 0x56
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
Hi Henning, I'm running 5.2.4. Will this deb package work? On Wed, Sep 18, 2019 at 2:39 PM Andrew Chen wrote: > Thanks Henning > > On Wed, Sep 18, 2019 at 2:13 PM Henning Westerholt wrote: > >> Hello Andrew, >> >> strange - it should be there, as it is available on deb.kamailio.org. >> >> Here e.g. the one for 64bit stretch: >> >> >> https://deb.kamailio.org/kamailiodev-nightly/pool/main/k/kamailio/kamailio-dbg_5.3.0~pre1%2B0~20190918005413.1490%2Bstretch_amd64.deb >> >> Cheers, >> >> Henning >> Am 18.09.19 um 18:52 schrieb Andrew Chen: >> >> I don't see one for debug: >> >> root@ashintgkama51:~ # apt-cache search kamailio >> >> resource-agents - Cluster Resource Agents >> >> kamailio - very fast, dynamic and configurable SIP server >> >> kamailio-autheph-modules - authentication using ephemeral credentials for >> the Kamailio SIP server >> >> kamailio-berkeley-bin - Berkeley database module for Kamailio - helper >> program >> >> kamailio-berkeley-modules - Berkeley database module for the Kamailio SIP >> server >> >> kamailio-carrierroute-modules - carrierroute module for the Kamailio SIP >> server >> >> kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server >> >> kamailio-cpl-modules - CPL module (CPL interpreter engine) for the >> Kamailio SIP server >> >> kamailio-erlang-modules - Erlang modules for the Kamailio SIP server >> >> kamailio-geoip-modules - geoip module for the Kamailio SIP Server >> >> kamailio-geoip2-modules - geoip2 module for the Kamailio SIP Server >> >> kamailio-ims-modules - IMS module for the Kamailio SIP server >> >> kamailio-json-modules - Json parser and Json-RPC modules for the Kamailio >> SIP server >> >> On Wed, Sep 18, 2019 at 11:26 AM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> You have to install the debug symbols package, otherwise the backtrace >>> doesn't show any useful information. It just require to install that >>> package and then get again the backtraces. The package name should be >>> kamailio-dbg. >>> >>> Cheers, >>> Daniel >>> On 18.09.19 16:37, Andrew Chen wrote: >>> >>> Sorry..forgot bt full output >>> >>> (gdb) bt full >>> >>> #0 0x562fcc3544c0 in ?? () >>> >>> No symbol table info available. >>> >>> #1 0x562fcc354632 in ?? () >>> >>> No symbol table info available. >>> >>> #2 0x562fcc354974 in local_timer_run () >>> >>> No symbol table info available. >>> >>> #3 0x562fcc3fb256 in ?? () >>> >>> No symbol table info available. >>> >>> #4 0x562fcc3fb64c in tcp_receive_loop () >>> >>> No symbol table info available. >>> >>> #5 0x562fcc2acf52 in tcp_init_children () >>> >>> No symbol table info available. >>> >>> #6 0x562fcc1ad94a in main_loop () >>> >>> No symbol table info available. >>> >>> #7 0x562fcc1b4a7b in main () >>> >>> No symbol table info available. >>> >>> (gdb) >>> >>> On Wed, Sep 18, 2019 at 10:35 AM Andrew Chen wrote: >>> >>>> backtrace output: >>>> >>>> >>>> (gdb) bt >>>> >>>> #0 0x562fcc3544c0 in ?? () >>>> >>>> #1 0x562fcc354632 in ?? () >>>> >>>> #2 0x562fcc354974 in local_timer_run () >>>> >>>> #3 0x562fcc3fb256 in ?? () >>>> >>>> #4 0x562fcc3fb64c in tcp_receive_loop () >>>> >>>> #5 0x562fcc2acf52 in tcp_init_children () >>>> >>>> #6 0x562fcc1ad94a in main_loop () >>>> >>>> #7 0x562fcc1b4a7b in main () >>>> >>>> (gdb) >>>> >>>> >>>> >>>> >>>> On Wed, Sep 18, 2019 at 10:01 AM Andrew Chen wrote: >>>> >>>>> I'll look for the core. >>>>> >>>>> As part of our release process, I don't think we can release master >>>>> branch of Kamailio. >>>>> >>>>> On Wed, Sep 18, 2019 at 9:54 AM Daniel-Constantin Mierla < >>>>> mico...@gmail.com> wrote: >>>>> >>>>>> Hello, >>>>>> >>>
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
Thanks Henning On Wed, Sep 18, 2019 at 2:13 PM Henning Westerholt wrote: > Hello Andrew, > > strange - it should be there, as it is available on deb.kamailio.org. > > Here e.g. the one for 64bit stretch: > > > https://deb.kamailio.org/kamailiodev-nightly/pool/main/k/kamailio/kamailio-dbg_5.3.0~pre1%2B0~20190918005413.1490%2Bstretch_amd64.deb > > Cheers, > > Henning > Am 18.09.19 um 18:52 schrieb Andrew Chen: > > I don't see one for debug: > > root@ashintgkama51:~ # apt-cache search kamailio > > resource-agents - Cluster Resource Agents > > kamailio - very fast, dynamic and configurable SIP server > > kamailio-autheph-modules - authentication using ephemeral credentials for > the Kamailio SIP server > > kamailio-berkeley-bin - Berkeley database module for Kamailio - helper > program > > kamailio-berkeley-modules - Berkeley database module for the Kamailio SIP > server > > kamailio-carrierroute-modules - carrierroute module for the Kamailio SIP > server > > kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server > > kamailio-cpl-modules - CPL module (CPL interpreter engine) for the > Kamailio SIP server > > kamailio-erlang-modules - Erlang modules for the Kamailio SIP server > > kamailio-geoip-modules - geoip module for the Kamailio SIP Server > > kamailio-geoip2-modules - geoip2 module for the Kamailio SIP Server > > kamailio-ims-modules - IMS module for the Kamailio SIP server > > kamailio-json-modules - Json parser and Json-RPC modules for the Kamailio > SIP server > > On Wed, Sep 18, 2019 at 11:26 AM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> You have to install the debug symbols package, otherwise the backtrace >> doesn't show any useful information. It just require to install that >> package and then get again the backtraces. The package name should be >> kamailio-dbg. >> >> Cheers, >> Daniel >> On 18.09.19 16:37, Andrew Chen wrote: >> >> Sorry..forgot bt full output >> >> (gdb) bt full >> >> #0 0x562fcc3544c0 in ?? () >> >> No symbol table info available. >> >> #1 0x562fcc354632 in ?? () >> >> No symbol table info available. >> >> #2 0x562fcc354974 in local_timer_run () >> >> No symbol table info available. >> >> #3 0x562fcc3fb256 in ?? () >> >> No symbol table info available. >> >> #4 0x562fcc3fb64c in tcp_receive_loop () >> >> No symbol table info available. >> >> #5 0x562fcc2acf52 in tcp_init_children () >> >> No symbol table info available. >> >> #6 0x562fcc1ad94a in main_loop () >> >> No symbol table info available. >> >> #7 0x562fcc1b4a7b in main () >> >> No symbol table info available. >> >> (gdb) >> >> On Wed, Sep 18, 2019 at 10:35 AM Andrew Chen wrote: >> >>> backtrace output: >>> >>> >>> (gdb) bt >>> >>> #0 0x562fcc3544c0 in ?? () >>> >>> #1 0x562fcc354632 in ?? () >>> >>> #2 0x562fcc354974 in local_timer_run () >>> >>> #3 0x562fcc3fb256 in ?? () >>> >>> #4 0x562fcc3fb64c in tcp_receive_loop () >>> >>> #5 0x562fcc2acf52 in tcp_init_children () >>> >>> #6 0x562fcc1ad94a in main_loop () >>> >>> #7 0x562fcc1b4a7b in main () >>> >>> (gdb) >>> >>> >>> >>> >>> On Wed, Sep 18, 2019 at 10:01 AM Andrew Chen wrote: >>> >>>> I'll look for the core. >>>> >>>> As part of our release process, I don't think we can release master >>>> branch of Kamailio. >>>> >>>> On Wed, Sep 18, 2019 at 9:54 AM Daniel-Constantin Mierla < >>>> mico...@gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> did you get core files? If yes, it would be good to see the gdb >>>>> bracktraces. >>>>> >>>>> Have you used the pre-loaded library workaround? >>>>> >>>>> The code was not backported to branch 5.2 yet, I wanted to wait a bit >>>>> and see if there are reports with good/bad results. If you want to use it, >>>>> then you have to install nightly builds from master branch (development >>>>> version, should be 5.3.0-pre1 at this moment). >>>>> >>>>> Cheers, >>>>> Daniel >>>>> On 18.09.19 15:26, Andrew Ch
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
I don't see one for debug: root@ashintgkama51:~ # apt-cache search kamailio resource-agents - Cluster Resource Agents kamailio - very fast, dynamic and configurable SIP server kamailio-autheph-modules - authentication using ephemeral credentials for the Kamailio SIP server kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program kamailio-berkeley-modules - Berkeley database module for the Kamailio SIP server kamailio-carrierroute-modules - carrierroute module for the Kamailio SIP server kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server kamailio-cpl-modules - CPL module (CPL interpreter engine) for the Kamailio SIP server kamailio-erlang-modules - Erlang modules for the Kamailio SIP server kamailio-geoip-modules - geoip module for the Kamailio SIP Server kamailio-geoip2-modules - geoip2 module for the Kamailio SIP Server kamailio-ims-modules - IMS module for the Kamailio SIP server kamailio-json-modules - Json parser and Json-RPC modules for the Kamailio SIP server On Wed, Sep 18, 2019 at 11:26 AM Daniel-Constantin Mierla wrote: > You have to install the debug symbols package, otherwise the backtrace > doesn't show any useful information. It just require to install that > package and then get again the backtraces. The package name should be > kamailio-dbg. > > Cheers, > Daniel > On 18.09.19 16:37, Andrew Chen wrote: > > Sorry..forgot bt full output > > (gdb) bt full > > #0 0x562fcc3544c0 in ?? () > > No symbol table info available. > > #1 0x562fcc354632 in ?? () > > No symbol table info available. > > #2 0x562fcc354974 in local_timer_run () > > No symbol table info available. > > #3 0x562fcc3fb256 in ?? () > > No symbol table info available. > > #4 0x562fcc3fb64c in tcp_receive_loop () > > No symbol table info available. > > #5 0x562fcc2acf52 in tcp_init_children () > > No symbol table info available. > > #6 0x562fcc1ad94a in main_loop () > > No symbol table info available. > > #7 0x562fcc1b4a7b in main () > > No symbol table info available. > > (gdb) > > On Wed, Sep 18, 2019 at 10:35 AM Andrew Chen wrote: > >> backtrace output: >> >> >> (gdb) bt >> >> #0 0x562fcc3544c0 in ?? () >> >> #1 0x562fcc354632 in ?? () >> >> #2 0x562fcc354974 in local_timer_run () >> >> #3 0x562fcc3fb256 in ?? () >> >> #4 0x562fcc3fb64c in tcp_receive_loop () >> >> #5 0x562fcc2acf52 in tcp_init_children () >> >> #6 0x562fcc1ad94a in main_loop () >> >> #7 0x562fcc1b4a7b in main () >> >> (gdb) >> >> >> >> >> On Wed, Sep 18, 2019 at 10:01 AM Andrew Chen wrote: >> >>> I'll look for the core. >>> >>> As part of our release process, I don't think we can release master >>> branch of Kamailio. >>> >>> On Wed, Sep 18, 2019 at 9:54 AM Daniel-Constantin Mierla < >>> mico...@gmail.com> wrote: >>> >>>> Hello, >>>> >>>> did you get core files? If yes, it would be good to see the gdb >>>> bracktraces. >>>> >>>> Have you used the pre-loaded library workaround? >>>> >>>> The code was not backported to branch 5.2 yet, I wanted to wait a bit >>>> and see if there are reports with good/bad results. If you want to use it, >>>> then you have to install nightly builds from master branch (development >>>> version, should be 5.3.0-pre1 at this moment). >>>> >>>> Cheers, >>>> Daniel >>>> On 18.09.19 15:26, Andrew Chen wrote: >>>> >>>> Hi Daniel, >>>> Which apt repository can we get this workaround? Today I noticed our >>>> Kamailio 5.2.4 cored during one of our load test sessions: >>>> >>>> Wed Sep 18 09:31:14 2019] kamailio[26997]: segfault at 7f8501366000 ip >>>> 7f8501e58585 sp 7fffd5c84248 error 4 in >>>> libcrypto.so.1.1[7f8501dd4000+29b000] >>>> >>>> [Wed Sep 18 10:12:29 2019] kamailio[27110]: segfault at 7f1a8eea1000 >>>> ip 7f1a8f993585 sp 7ffddc8848c8 error 4 in >>>> libcrypto.so.1.1[7f1a8f90f000+29b000] >>>> >>>> [Wed Sep 18 10:12:43 2019] kamailio[11060]: segfault at 20 ip >>>> 7f0a85dac128 sp 7fff6847aad0 error 4 in >>>> libcrypto.so.1.1[7f0a85c4+29b000] >>>> >>>> [Wed Sep 18 10:12:44 2019] kamailio[11059]: segfault at f0 ip >>>> 7f0a85cc43ea sp 7fff6847a9e8 error 4 in >>>>
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
Sorry..forgot bt full output (gdb) bt full #0 0x562fcc3544c0 in ?? () No symbol table info available. #1 0x562fcc354632 in ?? () No symbol table info available. #2 0x562fcc354974 in local_timer_run () No symbol table info available. #3 0x562fcc3fb256 in ?? () No symbol table info available. #4 0x562fcc3fb64c in tcp_receive_loop () No symbol table info available. #5 0x562fcc2acf52 in tcp_init_children () No symbol table info available. #6 0x562fcc1ad94a in main_loop () No symbol table info available. #7 0x562fcc1b4a7b in main () No symbol table info available. (gdb) On Wed, Sep 18, 2019 at 10:35 AM Andrew Chen wrote: > backtrace output: > > > (gdb) bt > > #0 0x562fcc3544c0 in ?? () > > #1 0x562fcc354632 in ?? () > > #2 0x562fcc354974 in local_timer_run () > > #3 0x562fcc3fb256 in ?? () > > #4 0x562fcc3fb64c in tcp_receive_loop () > > #5 0x562fcc2acf52 in tcp_init_children () > > #6 0x562fcc1ad94a in main_loop () > > #7 0x562fcc1b4a7b in main () > > (gdb) > > > > > On Wed, Sep 18, 2019 at 10:01 AM Andrew Chen wrote: > >> I'll look for the core. >> >> As part of our release process, I don't think we can release master >> branch of Kamailio. >> >> On Wed, Sep 18, 2019 at 9:54 AM Daniel-Constantin Mierla < >> mico...@gmail.com> wrote: >> >>> Hello, >>> >>> did you get core files? If yes, it would be good to see the gdb >>> bracktraces. >>> >>> Have you used the pre-loaded library workaround? >>> >>> The code was not backported to branch 5.2 yet, I wanted to wait a bit >>> and see if there are reports with good/bad results. If you want to use it, >>> then you have to install nightly builds from master branch (development >>> version, should be 5.3.0-pre1 at this moment). >>> >>> Cheers, >>> Daniel >>> On 18.09.19 15:26, Andrew Chen wrote: >>> >>> Hi Daniel, >>> Which apt repository can we get this workaround? Today I noticed our >>> Kamailio 5.2.4 cored during one of our load test sessions: >>> >>> Wed Sep 18 09:31:14 2019] kamailio[26997]: segfault at 7f8501366000 ip >>> 7f8501e58585 sp 7fffd5c84248 error 4 in >>> libcrypto.so.1.1[7f8501dd4000+29b000] >>> >>> [Wed Sep 18 10:12:29 2019] kamailio[27110]: segfault at 7f1a8eea1000 ip >>> 7f1a8f993585 sp 7ffddc8848c8 error 4 in >>> libcrypto.so.1.1[7f1a8f90f000+29b000] >>> >>> [Wed Sep 18 10:12:43 2019] kamailio[11060]: segfault at 20 ip >>> 7f0a85dac128 sp 7fff6847aad0 error 4 in >>> libcrypto.so.1.1[7f0a85c4+29b000] >>> >>> [Wed Sep 18 10:12:44 2019] kamailio[11059]: segfault at f0 ip >>> 7f0a85cc43ea sp 7fff6847a9e8 error 4 in >>> libcrypto.so.1.1[7f0a85c4+29b000] >>> >>> [Wed Sep 18 10:13:02 2019] kamailio[11187]: segfault at 7f75e06c8000 ip >>> 7f75e11ba585 sp 7ffe29b47c88 error 4 in >>> libcrypto.so.1.1[7f75e1136000+29b000] >>> >>> [Wed Sep 18 10:13:17 2019] kamailio[11445]: segfault at 7f0f3743f000 ip >>> 7f0f37f31585 sp 7ffde54daa38 error 4 in >>> libcrypto.so.1.1[7f0f37ead000+29b000] >>> >>> [Wed Sep 18 10:13:36 2019] kamailio[11644]: segfault at 7f804309c000 ip >>> 7f8043b8e585 sp 7ffe89fe8228 error 4 in >>> libcrypto.so.1.1[7f8043b0a000+29b000] >>> >>> [Wed Sep 18 10:13:52 2019] kamailio[11799]: segfault at 7ff59c7e2000 ip >>> 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in >>> libcrypto.so.1.1[7ff59d25+29b000] >>> >>> [Wed Sep 18 10:13:52 2019] kamailio[11792]: segfault at 7ff59c7e2000 ip >>> 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in >>> libcrypto.so.1.1[7ff59d25+29b000] >>> >>> [Wed Sep 18 12:48:01 2019] kamailio[12066]: segfault at 7f22dca6d000 ip >>> 7f22dd55f585 sp 7fffbc766ab8 error 4 in >>> libcrypto.so.1.1[7f22dd4db000+29b000] >>> >>> [Wed Sep 18 12:48:14 2019] kamailio[16344]: segfault at 7f7cca42d000 ip >>> 7f7ccaf1f585 sp 7ffe99f16108 error 4 in >>> libcrypto.so.1.1[7f7ccae9b000+29b000] >>> >>> [Wed Sep 18 12:48:32 2019] kamailio[16708]: segfault at 7fb309141000 ip >>> 7fb309c33585 sp 7ffd07a5f3c8 error 4 in >>> libcrypto.so.1.1[7fb309baf000+29b000] >>> >>> [Wed Sep 18 12:48:49 2019] kamailio[16824]: segfault at f0 ip >>> 7fc59095b3ea sp 7ffe58a490b8 error 4 in >>&g
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
backtrace output: (gdb) bt #0 0x562fcc3544c0 in ?? () #1 0x562fcc354632 in ?? () #2 0x562fcc354974 in local_timer_run () #3 0x562fcc3fb256 in ?? () #4 0x562fcc3fb64c in tcp_receive_loop () #5 0x562fcc2acf52 in tcp_init_children () #6 0x562fcc1ad94a in main_loop () #7 0x562fcc1b4a7b in main () (gdb) On Wed, Sep 18, 2019 at 10:01 AM Andrew Chen wrote: > I'll look for the core. > > As part of our release process, I don't think we can release master branch > of Kamailio. > > On Wed, Sep 18, 2019 at 9:54 AM Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> Hello, >> >> did you get core files? If yes, it would be good to see the gdb >> bracktraces. >> >> Have you used the pre-loaded library workaround? >> >> The code was not backported to branch 5.2 yet, I wanted to wait a bit and >> see if there are reports with good/bad results. If you want to use it, then >> you have to install nightly builds from master branch (development version, >> should be 5.3.0-pre1 at this moment). >> >> Cheers, >> Daniel >> On 18.09.19 15:26, Andrew Chen wrote: >> >> Hi Daniel, >> Which apt repository can we get this workaround? Today I noticed our >> Kamailio 5.2.4 cored during one of our load test sessions: >> >> Wed Sep 18 09:31:14 2019] kamailio[26997]: segfault at 7f8501366000 ip >> 7f8501e58585 sp 7fffd5c84248 error 4 in >> libcrypto.so.1.1[7f8501dd4000+29b000] >> >> [Wed Sep 18 10:12:29 2019] kamailio[27110]: segfault at 7f1a8eea1000 ip >> 7f1a8f993585 sp 7ffddc8848c8 error 4 in >> libcrypto.so.1.1[7f1a8f90f000+29b000] >> >> [Wed Sep 18 10:12:43 2019] kamailio[11060]: segfault at 20 ip >> 7f0a85dac128 sp 7fff6847aad0 error 4 in >> libcrypto.so.1.1[7f0a85c4+29b000] >> >> [Wed Sep 18 10:12:44 2019] kamailio[11059]: segfault at f0 ip >> 7f0a85cc43ea sp 7fff6847a9e8 error 4 in >> libcrypto.so.1.1[7f0a85c4+29b000] >> >> [Wed Sep 18 10:13:02 2019] kamailio[11187]: segfault at 7f75e06c8000 ip >> 7f75e11ba585 sp 7ffe29b47c88 error 4 in >> libcrypto.so.1.1[7f75e1136000+29b000] >> >> [Wed Sep 18 10:13:17 2019] kamailio[11445]: segfault at 7f0f3743f000 ip >> 7f0f37f31585 sp 7ffde54daa38 error 4 in >> libcrypto.so.1.1[7f0f37ead000+29b000] >> >> [Wed Sep 18 10:13:36 2019] kamailio[11644]: segfault at 7f804309c000 ip >> 7f8043b8e585 sp 7ffe89fe8228 error 4 in >> libcrypto.so.1.1[7f8043b0a000+29b000] >> >> [Wed Sep 18 10:13:52 2019] kamailio[11799]: segfault at 7ff59c7e2000 ip >> 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in >> libcrypto.so.1.1[7ff59d25+29b000] >> >> [Wed Sep 18 10:13:52 2019] kamailio[11792]: segfault at 7ff59c7e2000 ip >> 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in >> libcrypto.so.1.1[7ff59d25+29b000] >> >> [Wed Sep 18 12:48:01 2019] kamailio[12066]: segfault at 7f22dca6d000 ip >> 7f22dd55f585 sp 7fffbc766ab8 error 4 in >> libcrypto.so.1.1[7f22dd4db000+29b000] >> >> [Wed Sep 18 12:48:14 2019] kamailio[16344]: segfault at 7f7cca42d000 ip >> 7f7ccaf1f585 sp 7ffe99f16108 error 4 in >> libcrypto.so.1.1[7f7ccae9b000+29b000] >> >> [Wed Sep 18 12:48:32 2019] kamailio[16708]: segfault at 7fb309141000 ip >> 7fb309c33585 sp 7ffd07a5f3c8 error 4 in >> libcrypto.so.1.1[7fb309baf000+29b000] >> >> [Wed Sep 18 12:48:49 2019] kamailio[16824]: segfault at f0 ip >> 7fc59095b3ea sp 7ffe58a490b8 error 4 in >> libcrypto.so.1.1[7fc5908d7000+29b000] >> >> [Wed Sep 18 12:49:04 2019] kamailio[16956]: segfault at 7fcc22e58000 ip >> 7fcc2394a585 sp 7fffa9c52258 error 4 in >> libcrypto.so.1.1[7fcc238c6000+29b000] >> >> [Wed Sep 18 12:49:04 2019] kamailio[16945]: segfault at f0 ip >> 7fcc2394a3ea sp 7fffa9c52128 error 4 in >> libcrypto.so.1.1[7fcc238c6000+29b000] >> >> [Wed Sep 18 12:49:16 2019] kamailio[17244]: segfault at 7f586ed2 ip >> 7f586f812585 sp 7ffeae1adcd8 error 4 in >> libcrypto.so.1.1[7f586f78e000+29b000] >> >> [Wed Sep 18 12:49:33 2019] kamailio[17431]: segfault at 8 ip >> 562fcc44c5d5 sp 7ffe825c9dd0 error 4 in >> kamailio[562fcc17c000+4a2000] >> >> [Wed Sep 18 12:49:33 2019] kamailio[17386]: segfault at 10 ip >> 7f96c3735c3e sp 7ffe825ca270 error 4 in >> dialog.so[7f96c36d6000+be000] >> >> [Wed Sep 18 12:49:33 2019] kamailio[17423]: segfault at 0 ip >> 562fcc3544c0 sp 7ffe825ca1f0 error 6 in >> kamailio[562fcc17c00
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
I'll look for the core. As part of our release process, I don't think we can release master branch of Kamailio. On Wed, Sep 18, 2019 at 9:54 AM Daniel-Constantin Mierla wrote: > Hello, > > did you get core files? If yes, it would be good to see the gdb > bracktraces. > > Have you used the pre-loaded library workaround? > > The code was not backported to branch 5.2 yet, I wanted to wait a bit and > see if there are reports with good/bad results. If you want to use it, then > you have to install nightly builds from master branch (development version, > should be 5.3.0-pre1 at this moment). > > Cheers, > Daniel > On 18.09.19 15:26, Andrew Chen wrote: > > Hi Daniel, > Which apt repository can we get this workaround? Today I noticed our > Kamailio 5.2.4 cored during one of our load test sessions: > > Wed Sep 18 09:31:14 2019] kamailio[26997]: segfault at 7f8501366000 ip > 7f8501e58585 sp 7fffd5c84248 error 4 in > libcrypto.so.1.1[7f8501dd4000+29b000] > > [Wed Sep 18 10:12:29 2019] kamailio[27110]: segfault at 7f1a8eea1000 ip > 7f1a8f993585 sp 7ffddc8848c8 error 4 in > libcrypto.so.1.1[7f1a8f90f000+29b000] > > [Wed Sep 18 10:12:43 2019] kamailio[11060]: segfault at 20 ip > 7f0a85dac128 sp 7fff6847aad0 error 4 in > libcrypto.so.1.1[7f0a85c4+29b000] > > [Wed Sep 18 10:12:44 2019] kamailio[11059]: segfault at f0 ip > 7f0a85cc43ea sp 7fff6847a9e8 error 4 in > libcrypto.so.1.1[7f0a85c4+29b000] > > [Wed Sep 18 10:13:02 2019] kamailio[11187]: segfault at 7f75e06c8000 ip > 7f75e11ba585 sp 7ffe29b47c88 error 4 in > libcrypto.so.1.1[7f75e1136000+29b000] > > [Wed Sep 18 10:13:17 2019] kamailio[11445]: segfault at 7f0f3743f000 ip > 7f0f37f31585 sp 7ffde54daa38 error 4 in > libcrypto.so.1.1[7f0f37ead000+29b000] > > [Wed Sep 18 10:13:36 2019] kamailio[11644]: segfault at 7f804309c000 ip > 7f8043b8e585 sp 7ffe89fe8228 error 4 in > libcrypto.so.1.1[7f8043b0a000+29b000] > > [Wed Sep 18 10:13:52 2019] kamailio[11799]: segfault at 7ff59c7e2000 ip > 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in > libcrypto.so.1.1[7ff59d25+29b000] > > [Wed Sep 18 10:13:52 2019] kamailio[11792]: segfault at 7ff59c7e2000 ip > 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in > libcrypto.so.1.1[7ff59d25+29b000] > > [Wed Sep 18 12:48:01 2019] kamailio[12066]: segfault at 7f22dca6d000 ip > 7f22dd55f585 sp 7fffbc766ab8 error 4 in > libcrypto.so.1.1[7f22dd4db000+29b000] > > [Wed Sep 18 12:48:14 2019] kamailio[16344]: segfault at 7f7cca42d000 ip > 7f7ccaf1f585 sp 7ffe99f16108 error 4 in > libcrypto.so.1.1[7f7ccae9b000+29b000] > > [Wed Sep 18 12:48:32 2019] kamailio[16708]: segfault at 7fb309141000 ip > 7fb309c33585 sp 7ffd07a5f3c8 error 4 in > libcrypto.so.1.1[7fb309baf000+29b000] > > [Wed Sep 18 12:48:49 2019] kamailio[16824]: segfault at f0 ip > 7fc59095b3ea sp 7ffe58a490b8 error 4 in > libcrypto.so.1.1[7fc5908d7000+29b000] > > [Wed Sep 18 12:49:04 2019] kamailio[16956]: segfault at 7fcc22e58000 ip > 7fcc2394a585 sp 7fffa9c52258 error 4 in > libcrypto.so.1.1[7fcc238c6000+29b000] > > [Wed Sep 18 12:49:04 2019] kamailio[16945]: segfault at f0 ip > 7fcc2394a3ea sp 7fffa9c52128 error 4 in > libcrypto.so.1.1[7fcc238c6000+29b000] > > [Wed Sep 18 12:49:16 2019] kamailio[17244]: segfault at 7f586ed2 ip > 7f586f812585 sp 7ffeae1adcd8 error 4 in > libcrypto.so.1.1[7f586f78e000+29b000] > > [Wed Sep 18 12:49:33 2019] kamailio[17431]: segfault at 8 ip > 562fcc44c5d5 sp 7ffe825c9dd0 error 4 in > kamailio[562fcc17c000+4a2000] > > [Wed Sep 18 12:49:33 2019] kamailio[17386]: segfault at 10 ip > 7f96c3735c3e sp 7ffe825ca270 error 4 in > dialog.so[7f96c36d6000+be000] > > [Wed Sep 18 12:49:33 2019] kamailio[17423]: segfault at 0 ip > 562fcc3544c0 sp 7ffe825ca1f0 error 6 in > kamailio[562fcc17c000+4a2000] > > [Wed Sep 18 12:49:33 2019] kamailio[17378]: segfault at 0 ip > 7f96c5dd099f sp 7ffe825c98e0 error 4 in tm.so[7f96c5da5000+13f000] > > [Wed Sep 18 12:49:33 2019] kamailio[17417]: segfault at 0 ip > 562fcc3544c0 sp 7ffe825ca1f0 error 6 in > kamailio[562fcc17c000+4a2000] > > [Wed Sep 18 12:49:33 2019] kamailio[17416]: segfault at 0 ip > 562fcc3544c0 sp 7ffe825ca1f0 error 6 in > kamailio[562fcc17c000+4a2000] > > [Wed Sep 18 12:49:33 2019] kamailio[17380]: segfault at 0 ip > 7f96c5dd099f sp 7ffe825c98e0 error 4 in tm.so[7f96c5da5000+13f000] > > [Wed Sep 18 12:49:33 2019] kamailio[17381]: segfault at 0 ip > 7f96c5dd099f sp 7ffe825c98e0 error 4 in tm.so[7f96c5da5000+13f000] > > [Wed Sep 18 12:49:34 2019] kamailio[17387]: segfault at 8 ip &g
Re: [SR-Users] Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
Hi Daniel, Which apt repository can we get this workaround? Today I noticed our Kamailio 5.2.4 cored during one of our load test sessions: Wed Sep 18 09:31:14 2019] kamailio[26997]: segfault at 7f8501366000 ip 7f8501e58585 sp 7fffd5c84248 error 4 in libcrypto.so.1.1[7f8501dd4000+29b000] [Wed Sep 18 10:12:29 2019] kamailio[27110]: segfault at 7f1a8eea1000 ip 7f1a8f993585 sp 7ffddc8848c8 error 4 in libcrypto.so.1.1[7f1a8f90f000+29b000] [Wed Sep 18 10:12:43 2019] kamailio[11060]: segfault at 20 ip 7f0a85dac128 sp 7fff6847aad0 error 4 in libcrypto.so.1.1[7f0a85c4+29b000] [Wed Sep 18 10:12:44 2019] kamailio[11059]: segfault at f0 ip 7f0a85cc43ea sp 7fff6847a9e8 error 4 in libcrypto.so.1.1[7f0a85c4+29b000] [Wed Sep 18 10:13:02 2019] kamailio[11187]: segfault at 7f75e06c8000 ip 7f75e11ba585 sp 7ffe29b47c88 error 4 in libcrypto.so.1.1[7f75e1136000+29b000] [Wed Sep 18 10:13:17 2019] kamailio[11445]: segfault at 7f0f3743f000 ip 7f0f37f31585 sp 7ffde54daa38 error 4 in libcrypto.so.1.1[7f0f37ead000+29b000] [Wed Sep 18 10:13:36 2019] kamailio[11644]: segfault at 7f804309c000 ip 7f8043b8e585 sp 7ffe89fe8228 error 4 in libcrypto.so.1.1[7f8043b0a000+29b000] [Wed Sep 18 10:13:52 2019] kamailio[11799]: segfault at 7ff59c7e2000 ip 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in libcrypto.so.1.1[7ff59d25+29b000] [Wed Sep 18 10:13:52 2019] kamailio[11792]: segfault at 7ff59c7e2000 ip 7ff59d2d4585 sp 7ffd69d76bb8 error 4 in libcrypto.so.1.1[7ff59d25+29b000] [Wed Sep 18 12:48:01 2019] kamailio[12066]: segfault at 7f22dca6d000 ip 7f22dd55f585 sp 7fffbc766ab8 error 4 in libcrypto.so.1.1[7f22dd4db000+29b000] [Wed Sep 18 12:48:14 2019] kamailio[16344]: segfault at 7f7cca42d000 ip 7f7ccaf1f585 sp 7ffe99f16108 error 4 in libcrypto.so.1.1[7f7ccae9b000+29b000] [Wed Sep 18 12:48:32 2019] kamailio[16708]: segfault at 7fb309141000 ip 7fb309c33585 sp 7ffd07a5f3c8 error 4 in libcrypto.so.1.1[7fb309baf000+29b000] [Wed Sep 18 12:48:49 2019] kamailio[16824]: segfault at f0 ip 7fc59095b3ea sp 7ffe58a490b8 error 4 in libcrypto.so.1.1[7fc5908d7000+29b000] [Wed Sep 18 12:49:04 2019] kamailio[16956]: segfault at 7fcc22e58000 ip 7fcc2394a585 sp 7fffa9c52258 error 4 in libcrypto.so.1.1[7fcc238c6000+29b000] [Wed Sep 18 12:49:04 2019] kamailio[16945]: segfault at f0 ip 7fcc2394a3ea sp 7fffa9c52128 error 4 in libcrypto.so.1.1[7fcc238c6000+29b000] [Wed Sep 18 12:49:16 2019] kamailio[17244]: segfault at 7f586ed2 ip 7f586f812585 sp 7ffeae1adcd8 error 4 in libcrypto.so.1.1[7f586f78e000+29b000] [Wed Sep 18 12:49:33 2019] kamailio[17431]: segfault at 8 ip 562fcc44c5d5 sp 7ffe825c9dd0 error 4 in kamailio[562fcc17c000+4a2000] [Wed Sep 18 12:49:33 2019] kamailio[17386]: segfault at 10 ip 7f96c3735c3e sp 7ffe825ca270 error 4 in dialog.so[7f96c36d6000+be000] [Wed Sep 18 12:49:33 2019] kamailio[17423]: segfault at 0 ip 562fcc3544c0 sp 7ffe825ca1f0 error 6 in kamailio[562fcc17c000+4a2000] [Wed Sep 18 12:49:33 2019] kamailio[17378]: segfault at 0 ip 7f96c5dd099f sp 7ffe825c98e0 error 4 in tm.so[7f96c5da5000+13f000] [Wed Sep 18 12:49:33 2019] kamailio[17417]: segfault at 0 ip 562fcc3544c0 sp 7ffe825ca1f0 error 6 in kamailio[562fcc17c000+4a2000] [Wed Sep 18 12:49:33 2019] kamailio[17416]: segfault at 0 ip 562fcc3544c0 sp 7ffe825ca1f0 error 6 in kamailio[562fcc17c000+4a2000] [Wed Sep 18 12:49:33 2019] kamailio[17380]: segfault at 0 ip 7f96c5dd099f sp 7ffe825c98e0 error 4 in tm.so[7f96c5da5000+13f000] [Wed Sep 18 12:49:33 2019] kamailio[17381]: segfault at 0 ip 7f96c5dd099f sp 7ffe825c98e0 error 4 in tm.so[7f96c5da5000+13f000] [Wed Sep 18 12:49:34 2019] kamailio[17387]: segfault at 8 ip 562fcc25d1f3 sp 7ffe825ca370 error 6 in kamailio[562fcc17c000+4a2000] and I was wondering if this core is related. Thanks On Fri, Sep 13, 2019 at 5:18 PM Alex Balashov wrote: > Hi Daniel, > > Thanks a lot for this work; it's definitely important that Kamailio > build against OpenSSL v1.1, and I'll be happy to contribute some testing > in a live environment in the coming weeks. Much appreciated. > > Have a good weekend, > > -- Alex > > On Fri, Sep 13, 2019 at 01:34:12PM +0200, Daniel-Constantin Mierla wrote: > > > Hello, > > after couple of months waiting for feedback about the workaround with the > > preloaded shared library to set the PTHREAD_PROCESS_SHARED attribute for > > pthread mutex/rwlock in order to avoid deadlocks and as it seems to be > the > > solution, I just pushed a few commits to move that code in the core of > > kamailio. > > > > It this way the initialization with the PTHREAD_PROCESS_SHARED attribute > is > > done by default when libssl v1.1 is detected at compile time, without the > > need of using the approach with a preloaded library. > > > > The shared library is still kept in the tls module: > > * > > >
Re: [SR-Users] Can't connect to db
Sorry..ignore this. Found the issue. The max connection setting on the RDS was too low. Thanks On Tue, Sep 10, 2019 at 5:43 PM Andrew Chen wrote: > Hi all, > I just installed kamailio 5.2.4 on two separate aws instances in two > separate regions. Both regions uses the same configuration template and > share the same db in AWS RDS. The issue I see is this: > - SJO location was able to launch fine without any issues. > - ASH location could not start up kamailio process due to db connection > failure: > > Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: db_mysql > [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many > connections > > Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: > [db.c:319]: db_do_init2(): could not add connection to the pool > > Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: db_mysql > [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many > connections > > Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: > [db.c:319]: db_do_init2(): could not add connection to the pool > > Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: > carrierroute [db_carrierroute.c:141]: carrierroute_db_open(): can't connect > to database. > > Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: > [core/sr_module.c:847]: init_mod_child(): error while initializing module > carrierroute (/usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so) > (idx: 30 rank: 18 desc: [tcp receiver (generic) child=9]) > > - In ASH instance, I can manually mysql to the RDS host using the > credentials in the config file. > - I checked db user permissions and it's opened for the subnet in our ASH > location (which is also proven using manual connection). > > So I don't get why one works and the other doesn't > > Thoughts? > > -- > Andy Chen > Sr. Telephony Lead Engineer > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Can't connect to db
Hi all, I just installed kamailio 5.2.4 on two separate aws instances in two separate regions. Both regions uses the same configuration template and share the same db in AWS RDS. The issue I see is this: - SJO location was able to launch fine without any issues. - ASH location could not start up kamailio process due to db connection failure: Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: db_mysql [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many connections Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: [db.c:319]: db_do_init2(): could not add connection to the pool Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: db_mysql [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many connections Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: [db.c:319]: db_do_init2(): could not add connection to the pool Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: carrierroute [db_carrierroute.c:141]: carrierroute_db_open(): can't connect to database. Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: [core/sr_module.c:847]: init_mod_child(): error while initializing module carrierroute (/usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so) (idx: 30 rank: 18 desc: [tcp receiver (generic) child=9]) - In ASH instance, I can manually mysql to the RDS host using the credentials in the config file. - I checked db user permissions and it's opened for the subnet in our ASH location (which is also proven using manual connection). So I don't get why one works and the other doesn't Thoughts? -- Andy Chen Sr. Telephony Lead Engineer -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio 5.2.3 failed to start due to incompatible openssl version
So that works however in the document it says do this at a risk. What
risk(s) is it referring to?
On Thu, Jul 18, 2019 at 3:29 PM Joel Serrano wrote:
> Hey Andrew,
>
> Can you give it a try adding:
>
> modparam("tls", "tls_force_run", 1)
>
> ?
>
> On Thu, Jul 18, 2019 at 8:29 AM Andrew Chen wrote:
>
>> Hey support,
>>
>> Today I ran into this error on my latest 5.2.3 Kamailio box:
>>
>> Jul 18 15:05:28 sjomaintpsg51 /usr/sbin/kamailio[5525]: CRITICAL: tls
>> [tls_init.c:671]: init_tls_h(): installed openssl library version is too
>> different from the library the kamailio tls module was compiled with:
>> installed “OpenSSL 1.1.1 11 Sep 2018” (0x1010100f), compiled “OpenSSL
>> 1.1.0g 2 Nov 2017" (0x1010007f).#012 Please make sure a compatible version
>> is used (tls_force_run in kamailio.cfg will override this check)
>>
>> There's not support for openssl1.1.1 ?
>>
>> Thanks
>>
>> --
>> Andy Chen
>> Sr. Telephony Lead Engineer
>> achen@ fuze.com
>>
>>
>>
>> *Confidentiality Notice: The information contained in this e-mail and any
>> attachments may be confidential. If you are not an intended recipient, you
>> are hereby notified that any dissemination, distribution or copying of
>> this
>> e-mail is strictly prohibited. If you have received this e-mail in error,
>> please notify the sender and permanently delete the e-mail and any
>> attachments immediately. You should not retain, copy or use this e-mail or
>> any attachment for any purpose, nor disclose all or any part of the
>> contents to any other person. Thank you.*
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
achen@ fuze.com
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Kamailio 5.2.3 failed to start due to incompatible openssl version
Hey support, Today I ran into this error on my latest 5.2.3 Kamailio box: Jul 18 15:05:28 sjomaintpsg51 /usr/sbin/kamailio[5525]: CRITICAL: tls [tls_init.c:671]: init_tls_h(): installed openssl library version is too different from the library the kamailio tls module was compiled with: installed “OpenSSL 1.1.1 11 Sep 2018” (0x1010100f), compiled “OpenSSL 1.1.0g 2 Nov 2017" (0x1010007f).#012 Please make sure a compatible version is used (tls_force_run in kamailio.cfg will override this check) There's not support for openssl1.1.1 ? Thanks -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 5.2.3 - dispatcher module looses setid
Hi Karsten, I confirmed the dispatcher hosts are up and running and so did my colleague who fired up the destination server himself. We confirmed it's running when we used 'dig' and 'nslookup' which both returned some IP address. I though kamcmd does what kamctl does? Also, after doing 'kamcmd dispatcher.reload' fixed it again. I just don't know when this issue will happen again given the issue is so intermittent. On Fri, Jun 21, 2019 at 3:42 PM Karsten Horsmann wrote: > Hi Andrew, > > > I use the older tool kamctl > "kamctl dispatcher dump" with kamailio 5.2.3. > Maybe all destinations are "down"? > > Did you raise log messages on event route dispatcher down / up? > > Cheers > Karsten > > Andrew Chen schrieb am Fr., 21. Juni 2019, 18:17: > >> Hi all, >> >> For a few times now I've noticed Kamailio 5.2.3 dispatcher module looses >> view of setid destination and this system been up and running for 13 days: >> >> root:~# kamcmd dispatcher.list | grep ash.tpgw.service >> >> To work around it, we have to reload the module again: >> >> root:~# kamcmd dispatcher.reload >> root:~# kamcmd dispatcher.list | grep ash.tpgw.service >> URI: sip::5062 >> URI: sip::5060 >> root:~# >> >> Process been running for several days: >> >> root:~# ps -elf | grep kam >> 0 S root 8484 6520 0 80 0 - 3714 pipe_w 16:04 pts/0 00:00:00 grep >> --color=auto kam >> 5 S kamailio 32086 1 0 80 0 - 214845 pause Jun17 ? 00:00:00 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> 1 S kamailio 32164 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> 1 S kamailio 32165 32086 0 80 0 - 233342 skb_wa Jun17 ? 00:00:02 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> 1 S kamailio 32166 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> 1 S kamailio 32167 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> 1 S kamailio 32168 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> 1 S kamailio 32169 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> 1 S kamailio 32170 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 >> /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f >> /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio >> >> Anyone seen this? >> >> Thanks >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> achen@ fuze.com >> >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] 5.2.3 - dispatcher module looses setid
Hi all, For a few times now I've noticed Kamailio 5.2.3 dispatcher module looses view of setid destination and this system been up and running for 13 days: root:~# kamcmd dispatcher.list | grep ash.tpgw.service To work around it, we have to reload the module again: root:~# kamcmd dispatcher.reload root:~# kamcmd dispatcher.list | grep ash.tpgw.service URI: sip::5062 URI: sip::5060 root:~# Process been running for several days: root:~# ps -elf | grep kam 0 S root 8484 6520 0 80 0 - 3714 pipe_w 16:04 pts/0 00:00:00 grep --color=auto kam 5 S kamailio 32086 1 0 80 0 - 214845 pause Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32164 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32165 32086 0 80 0 - 233342 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32166 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32167 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32168 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32169 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32170 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio Anyone seen this? Thanks -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] mem leak on 5.1.2?
Thanks guys. On Mon, May 27, 2019, 16:08 Henning Westerholt wrote: > Hello Andrew, > > you find updated packages for 5.1. and 5.2 releases here: deb.kamailio.org > > They are available also for Ubuntu. You need to add the correct config to > your apt configuration, have a look e.g. to this tutorial: > https://kamailio.org/docs/tutorials/devel/kamailio-install-guide-deb/ > > Cheers, > > Henning > Am 27.05.19 um 15:45 schrieb Andrew Chen: > > Thanks for the responses. I'll look into on how to do this because I > installed Kamailio using apt-get install on 18.04 Ubuntu. > > On Mon, May 27, 2019 at 4:02 AM Henning Westerholt wrote: > >> Hello Andrew, >> >> additional to the memory debugging comment - I would suggest to first >> update to a newer Kamailio version, e.g. to 5.1.8. >> >> The version you use is now over a year old and there have been a lot of >> fixes in this time. >> >> Cheers, >> >> Henning >> Am 24.05.19 um 17:34 schrieb Andrew Chen: >> >> Hey guys, >> >> Need some help with possible run away memory issue on my 5.1.2 Kamailio. >> I noticed I'm getting this memory error from kam logs: >> >> May 24 13:47:52 ashintgtpsg51 /usr/sbin/kamailio[1857]: WARNING: >> http_client [functions.c:298]: curL_query_url(): Curl library out of >> memory (url:https://) >> >> my -m on kamailio startup is currently set to 64 but there is only 1 call >> going through. >> >> In our check_mk, I noticed the memory usage is ramping up: >> >> [..] >> >> What's the cause of this? >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> achen@ fuze.com >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> >> ___ >> Kamailio (SER) - Users Mailing >> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> -- >> Henning Westerholt - https://skalatan.de/blog/ >> Kamailio services - https://skalatan.de/services >> >> > > -- > Andy Chen > Sr. Telephony Lead Engineer > 415 516 5535 (M) > achen@ fuze.com > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > -- > Henning Westerholt - https://skalatan.de/blog/ > Kamailio services - https://skalatan.de/services > > -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] mem leak on 5.1.2?
Sorry I meant for the debug params you set during recompile? How do you set them with apt repo? On Mon, May 27, 2019, 12:16 David Villasmil wrote: > You can do > > apt-get update > > Then > > apt-cache showpkg kamailio > > That will show you what version will be installed, if your happy with the > result, simply: > > apt-get install kamailio (and the mods you have installed) > > That should upgrade it. > > On Mon, 27 May 2019 at 14:47, Andrew Chen wrote: > >> Thanks for the responses. I'll look into on how to do this because I >> installed Kamailio using apt-get install on 18.04 Ubuntu. >> >> On Mon, May 27, 2019 at 4:02 AM Henning Westerholt >> wrote: >> >>> Hello Andrew, >>> >>> additional to the memory debugging comment - I would suggest to first >>> update to a newer Kamailio version, e.g. to 5.1.8. >>> >>> The version you use is now over a year old and there have been a lot of >>> fixes in this time. >>> >>> Cheers, >>> >>> Henning >>> Am 24.05.19 um 17:34 schrieb Andrew Chen: >>> >>> Hey guys, >>> >>> Need some help with possible run away memory issue on my 5.1.2 >>> Kamailio. I noticed I'm getting this memory error from kam logs: >>> >>> May 24 13:47:52 ashintgtpsg51 /usr/sbin/kamailio[1857]: WARNING: >>> http_client [functions.c:298]: curL_query_url(): Curl library out of >>> memory (url:https://) >>> >>> my -m on kamailio startup is currently set to 64 but there is only 1 >>> call going through. >>> >>> In our check_mk, I noticed the memory usage is ramping up: >>> >>> [..] >>> >>> What's the cause of this? >>> >>> -- >>> Andy Chen >>> Sr. Telephony Lead Engineer >>> achen@ fuze.com >>> >>> >>> *Confidentiality Notice: The information contained in this e-mail and any >>> attachments may be confidential. If you are not an intended recipient, >>> you >>> are hereby notified that any dissemination, distribution or copying of >>> this >>> e-mail is strictly prohibited. If you have received this e-mail in error, >>> please notify the sender and permanently delete the e-mail and any >>> attachments immediately. You should not retain, copy or use this e-mail >>> or >>> any attachment for any purpose, nor disclose all or any part of the >>> contents to any other person. Thank you.* >>> >>> ___ >>> Kamailio (SER) - Users Mailing >>> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>> -- >>> Henning Westerholt - https://skalatan.de/blog/ >>> Kamailio services - https://skalatan.de/services >>> >>> >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> 415 516 5535 (M) >> achen@ fuze.com >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > -- > Regards, > > David Villasmil > email: david.villasmil.w...@gmail.com > phone: +34669448337 > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] mem leak on 5.1.2?
Thanks for the responses. I'll look into on how to do this because I installed Kamailio using apt-get install on 18.04 Ubuntu. On Mon, May 27, 2019 at 4:02 AM Henning Westerholt wrote: > Hello Andrew, > > additional to the memory debugging comment - I would suggest to first > update to a newer Kamailio version, e.g. to 5.1.8. > > The version you use is now over a year old and there have been a lot of > fixes in this time. > > Cheers, > > Henning > Am 24.05.19 um 17:34 schrieb Andrew Chen: > > Hey guys, > > Need some help with possible run away memory issue on my 5.1.2 Kamailio. > I noticed I'm getting this memory error from kam logs: > > May 24 13:47:52 ashintgtpsg51 /usr/sbin/kamailio[1857]: WARNING: > http_client [functions.c:298]: curL_query_url(): Curl library out of > memory (url:https://) > > my -m on kamailio startup is currently set to 64 but there is only 1 call > going through. > > In our check_mk, I noticed the memory usage is ramping up: > > [..] > > What's the cause of this? > > -- > Andy Chen > Sr. Telephony Lead Engineer > achen@ fuze.com > > > *Confidentiality Notice: The information contained in this e-mail and any > attachments may be confidential. If you are not an intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > e-mail is strictly prohibited. If you have received this e-mail in error, > please notify the sender and permanently delete the e-mail and any > attachments immediately. You should not retain, copy or use this e-mail or > any attachment for any purpose, nor disclose all or any part of the > contents to any other person. Thank you.* > > ___ > Kamailio (SER) - Users Mailing > Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Henning Westerholt - https://skalatan.de/blog/ > Kamailio services - https://skalatan.de/services > > -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] $snd(proto) mapping?
Hey guys, Is there a numeric mapping for $snd(proto)? Thanks -- Andy Chen Sr. Telephony Lead Engineer achen@ fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.* ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] http_client_query module?
Sorry...my bad. It does work. I was looking at the wrong part of the log. thanks. On Wed, May 8, 2019 at 9:51 AM Andrew Chen wrote: > It is: > > #!define WITH_TLS 1 > > #!ifdef WITH_TLS > > loadmodule "tls.so" > > loadmodule "http_client.so" > > #!endif > > > is there any specific package I need to have installed? > > On Wed, May 8, 2019, 03:32 Federico Cabiddu > wrote: > >> Hi, >> the errors are about http_client module not about tls. >> did you load http_client module in your config? >> >> loadmodule "http_client.so" >> >> Federico >> >> On Tue, May 7, 2019 at 11:48 PM Andrew Chen wrote: >> >>> Hey guys, >>> >>> Need help here. What module besides tls.so I need to load in order to >>> get http_client_query to work? >>> >>> The module doc says tls.so: >>> >>> #!ifdef WITH_TLS >>> >>> loadmodule "tls.so" >>> >>> #!endif >>> >>> >>> but I keep getting this when doing config check: >>> >>> >>> root@ashmaintpsg51:/etc/kamailio# kamailio -c kamailio.cfg >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 322, column 71: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 323, column 45: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 324, column 42: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 325, column 48: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 326, column 44: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 327, column 71: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 328, column 67: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): >>> No module matching found >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 329, column 41: Can't set >>> module parameter >>> >>> 0(12971) ERROR: [core/cfg.y:3309]: yyparse(): cfg. parser: >>> failed to find command http_client_query (params 2) >>> >>> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >>> in config file /etc/kamailio/kamailio.cfg, line 859, column 105: unknown >>> command, missing loadmodule? >>> >>> >>> and I have the package installed on my ubuntu 18.04: >>> >>> >>> ii kamailio-*tls*-modules:amd64 5.1.2-1ubuntu2 >>> amd64TLS support for the Kamailio SIP server >>> (authentication, transport) >>> >>> >>> thoughts? >>> >>> -- >>> Andy Chen >>> Sr. Telephony Lead Engineer >>> achen@ fuze.com >>> >>> >>> >>> *Confidentiality Notice: The information contained in this e-mail and any >>> attachments may be
Re: [SR-Users] http_client_query module?
It is: #!define WITH_TLS 1 #!ifdef WITH_TLS loadmodule "tls.so" loadmodule "http_client.so" #!endif is there any specific package I need to have installed? On Wed, May 8, 2019, 03:32 Federico Cabiddu wrote: > Hi, > the errors are about http_client module not about tls. > did you load http_client module in your config? > > loadmodule "http_client.so" > > Federico > > On Tue, May 7, 2019 at 11:48 PM Andrew Chen wrote: > >> Hey guys, >> >> Need help here. What module besides tls.so I need to load in order to >> get http_client_query to work? >> >> The module doc says tls.so: >> >> #!ifdef WITH_TLS >> >> loadmodule "tls.so" >> >> #!endif >> >> >> but I keep getting this when doing config check: >> >> >> root@ashmaintpsg51:/etc/kamailio# kamailio -c kamailio.cfg >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 322, column 71: Can't set >> module parameter >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 323, column 45: Can't set >> module parameter >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 324, column 42: Can't set >> module parameter >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 325, column 48: Can't set >> module parameter >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 326, column 44: Can't set >> module parameter >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 327, column 71: Can't set >> module parameter >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 328, column 67: Can't set >> module parameter >> >> 0(12971) ERROR: [core/modparam.c:152]: set_mod_param_regex(): No >> module matching found >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 329, column 41: Can't set >> module parameter >> >> 0(12971) ERROR: [core/cfg.y:3309]: yyparse(): cfg. parser: >> failed to find command http_client_query (params 2) >> >> 0(12971) CRITICAL: [core/cfg.y:3449]: yyerror_at(): parse error >> in config file /etc/kamailio/kamailio.cfg, line 859, column 105: unknown >> command, missing loadmodule? >> >> >> and I have the package installed on my ubuntu 18.04: >> >> >> ii kamailio-*tls*-modules:amd64 5.1.2-1ubuntu2 >> amd64TLS support for the Kamailio SIP server >> (authentication, transport) >> >> >> thoughts? >> >> -- >> Andy Chen >> Sr. Telephony Lead Engineer >> achen@ fuze.com >> >> >> >> *Confidentiality Notice: The information contained in this e-mail and any >> attachments may be confidential. If you are not an intended recipient, you >> are hereby notified that any dissemination, distribution or copying of >> this >> e-mail is strictly prohibited. If you have received this e-mail in error, >> please notify the sender and permanently delete the e-mail and any >> attachments immediately. You should not retain, copy or use this e-mail or >> any attachment for any purpose, nor disclose all or any part of the >> contents to any other person. Thank you.* >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >>
