Hi guys, I am currently using kamailio v5.2.5 and running it inside a container. I already attempted to upgrade the kamailio to the latest version however the problem persists.
This is the core dump that I got from using gdb:
Core was generated by `/usr/sbin/kamailio -f
/etc/kazoo/kamailio/kamailio.cfg -m 512 -M 64 -x tlsf -w'. Program terminated with signal 11, Segmentation fault. #0 0x000000000071c63c in select_cfg_var (res=0x7ffd57d49b10, s=0x7f2649395040, msg=0x7ffd57d4c340) at core/cfg/cfg_select.c:211 211 i = *(int *)p;
It seems that the problem is with this line:
modparam("dmq", "notification_address", "sip:DMQ_NOTIFY_ADDRESS")
Also, I only have this issue while running on an AWS instance, I have the same setup on my local computer, however kamailio is able to start correctly.
While kamailio is starting, I have this line
#!substdef "!DMQ_NOTIFY_ADDRESS!10.10.10.10:5090!g"
It seems that after DMQ is able to obtain the IP address, when it comes to actually sending the message, it is interpreting the ip address of the DMQ_NOTIFY_ADDRESS as an integer and then it gives out a segmentation fault and the module stops.
Another interesting thing is that if the DMQ_NOTIFY_ADDRESS is the MY_IP_ADDRESS variable instead of the 10.10.10.10, it seems to work properly.
#!substdef "!DMQ_NOTIFY_ADDRESS!MY_IP_ADDRESS:5090!g"
It also doesn't seem related to the ip being in a variable, since I already tried using a DNS record, and once again, it is able to obtain the IPs from the DNS record, and the same issue applies.
Has anyone ever seen anything like this? I can't find any evidence of this actually happening.
Thank you kindly for your time.
Best Regards, José Santos
you need to make sure you used the latest commits in branch 5.5 or used master. https://github.com/kamailio/kamailio/issues/2843
On Thu, Sep 16, 2021 at 9:22 AM Zé Santos individuoestima@gmail.com wrote:
Hi guys, I am currently using kamailio v5.2.5 and running it inside a container. I already attempted to upgrade the kamailio to the latest version however the problem persists.
This is the core dump that I got from using gdb:
Core was generated by `/usr/sbin/kamailio -f
/etc/kazoo/kamailio/kamailio.cfg -m 512 -M 64 -x tlsf -w'. Program terminated with signal 11, Segmentation fault. #0 0x000000000071c63c in select_cfg_var (res=0x7ffd57d49b10, s=0x7f2649395040, msg=0x7ffd57d4c340) at core/cfg/cfg_select.c:211 211 i = *(int *)p;
It seems that the problem is with this line:
modparam("dmq", "notification_address", "sip:DMQ_NOTIFY_ADDRESS")
Also, I only have this issue while running on an AWS instance, I have the same setup on my local computer, however kamailio is able to start correctly.
While kamailio is starting, I have this line
#!substdef "!DMQ_NOTIFY_ADDRESS!10.10.10.10:5090!g"
It seems that after DMQ is able to obtain the IP address, when it comes to actually sending the message, it is interpreting the ip address of the DMQ_NOTIFY_ADDRESS as an integer and then it gives out a segmentation fault and the module stops.
Another interesting thing is that if the DMQ_NOTIFY_ADDRESS is the MY_IP_ADDRESS variable instead of the 10.10.10.10, it seems to work properly.
#!substdef "!DMQ_NOTIFY_ADDRESS!MY_IP_ADDRESS:5090!g"
It also doesn't seem related to the ip being in a variable, since I already tried using a DNS record, and once again, it is able to obtain the IPs from the DNS record, and the same issue applies.
Has anyone ever seen anything like this? I can't find any evidence of this actually happening.
Thank you kindly for your time.
Best Regards, José Santos
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:
Hello,
the commit you references has nothing to do with version 5.2.5 -- it was a revert of commits done during 5.5.x development.
So the issue should be somewhere else, unless it was a mistake in typing the version and instead of 5.2.5 was supposed to be 5.5.2.
Cheers, Daniel
On 16.09.21 09:13, Sergey Safarov wrote:
you need to make sure you used the latest commits in branch 5.5 or used master. https://github.com/kamailio/kamailio/issues/2843 https://github.com/kamailio/kamailio/issues/2843
On Thu, Sep 16, 2021 at 9:22 AM Zé Santos <individuoestima@gmail.com mailto:individuoestima@gmail.com> wrote:
Hi guys, I am currently using kamailio v5.2.5 and running it inside a container. I already attempted to upgrade the kamailio to the latest version however the problem persists. This is the core dump that I got from using gdb: Core was generated by `/usr/sbin/kamailio -f /etc/kazoo/kamailio/kamailio.cfg -m 512 -M 64 -x tlsf -w'. Program terminated with signal 11, Segmentation fault. #0 0x000000000071c63c in select_cfg_var (res=0x7ffd57d49b10, s=0x7f2649395040, msg=0x7ffd57d4c340) at core/cfg/cfg_select.c:211 211 i = *(int *)p; It seems that the problem is with this line: modparam("dmq", "notification_address", "sip:DMQ_NOTIFY_ADDRESS") Also, I only have this issue while running on an AWS instance, I have the same setup on my local computer, however kamailio is able to start correctly. While kamailio is starting, I have this line #!substdef "!DMQ_NOTIFY_ADDRESS!10.10.10.10:5090!g" It seems that after DMQ is able to obtain the IP address, when it comes to actually sending the message, it is interpreting the ip address of the DMQ_NOTIFY_ADDRESS as an integer and then it gives out a segmentation fault and the module stops. Another interesting thing is that if the DMQ_NOTIFY_ADDRESS is the MY_IP_ADDRESS variable instead of the 10.10.10.10, it seems to work properly. #!substdef "!DMQ_NOTIFY_ADDRESS!MY_IP_ADDRESS:5090!g" It also doesn't seem related to the ip being in a variable, since I already tried using a DNS record, and once again, it is able to obtain the IPs from the DNS record, and the same issue applies. Has anyone ever seen anything like this? I can't find any evidence of this actually happening. Thank you kindly for your time. Best Regards, José Santos __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org <mailto: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 <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
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:
As I understand, the 5.2.5 version is stable. Issue happens during Kamailio upgrade current latest stable release.
On Thu, Sep 16, 2021 at 10:22 AM Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
the commit you references has nothing to do with version 5.2.5 -- it was a revert of commits done during 5.5.x development.
So the issue should be somewhere else, unless it was a mistake in typing the version and instead of 5.2.5 was supposed to be 5.5.2.
Cheers, Daniel On 16.09.21 09:13, Sergey Safarov wrote:
you need to make sure you used the latest commits in branch 5.5 or used master. https://github.com/kamailio/kamailio/issues/2843
On Thu, Sep 16, 2021 at 9:22 AM Zé Santos individuoestima@gmail.com wrote:
Hi guys, I am currently using kamailio v5.2.5 and running it inside a container. I already attempted to upgrade the kamailio to the latest version however the problem persists.
This is the core dump that I got from using gdb:
Core was generated by `/usr/sbin/kamailio -f
/etc/kazoo/kamailio/kamailio.cfg -m 512 -M 64 -x tlsf -w'. Program terminated with signal 11, Segmentation fault. #0 0x000000000071c63c in select_cfg_var (res=0x7ffd57d49b10, s=0x7f2649395040, msg=0x7ffd57d4c340) at core/cfg/cfg_select.c:211 211 i = *(int *)p;
It seems that the problem is with this line:
modparam("dmq", "notification_address", "sip:DMQ_NOTIFY_ADDRESS")
Also, I only have this issue while running on an AWS instance, I have the same setup on my local computer, however kamailio is able to start correctly.
While kamailio is starting, I have this line
#!substdef "!DMQ_NOTIFY_ADDRESS!10.10.10.10:5090!g"
It seems that after DMQ is able to obtain the IP address, when it comes to actually sending the message, it is interpreting the ip address of the DMQ_NOTIFY_ADDRESS as an integer and then it gives out a segmentation fault and the module stops.
Another interesting thing is that if the DMQ_NOTIFY_ADDRESS is the MY_IP_ADDRESS variable instead of the 10.10.10.10, it seems to work properly.
#!substdef "!DMQ_NOTIFY_ADDRESS!MY_IP_ADDRESS:5090!g"
It also doesn't seem related to the ip being in a variable, since I already tried using a DNS record, and once again, it is able to obtain the IPs from the DNS record, and the same issue applies.
Has anyone ever seen anything like this? I can't find any evidence of this actually happening.
Thank you kindly for your time.
Best Regards, José Santos
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:
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:
-- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
-
Daniel-Constantin Mierla -
Sergey Safarov -
Zé Santos