Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-08-15 Thread Daniel-Constantin Mierla
@nshopik - yours looks more like #1189. Open a new bug if that doesn't apply and attach all the information as requested by the bug issue template. This one is going to be closed, not able to reproduce. -- You are receiving this because you are subscribed to this thread. Reply to this email dir

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-08-15 Thread Daniel-Constantin Mierla
Closed #1098. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1098#event-1206398224___ Kamailio (SER) - Development Mailing List sr-dev@l

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-08-15 Thread Nikolay Shopik
We just noticed that having same issue if socket already bind to other process and kamailio will just crash ``` segfault at 7fa0ccd6e7b0 ip 7fa0d13ce5f6 sp 7ffdeb89c9e0 error 4 in libcrypto.so.1.1[7fa0d1267000+261000] ``` -- You are receiving this because you are subscribed to this thre

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-06-24 Thread Daniel-Constantin Mierla
If there are no other details that you can provide, like all log messages with debug=3 in kamailio.cfg or output of `bt full`, I am closing this one in the near future, being not able to reproduce it here. -- You are receiving this because you are subscribed to this thread. Reply to this email

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-06-13 Thread Daniel-Constantin Mierla
I was not able to reproduce. I did a fresh install and started with default `kamailio.cfg` that has `WITH_TLS` defined. All started fine, the `kamctl srv sockets` shows that `kamailio` is listening on tls. -- You are receiving this because you are subscribed to this thread. Reply to this email

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-05-25 Thread Surendra Tiwari
this is the good functionality of kamailio if no listen is mentioned then kamailio listen to local interface. But as you are not getting proper log. we will try to reproduce it and if we found the issue then we will print the error log on this.so you can identify what things are wrong with confi

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-05-05 Thread Sarbyn
version: kamailio 5.0.1 (x86_64/linux) Tip to reproduce: enable TLS but do not define any "listen=" addresses -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1098#issuecomment-29940

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-05-04 Thread Daniel-Constantin Mierla
What version of kamailio are you using? The code seems to be safe there. I also tried to reproduce by having a listen with a non local ip and it didn't crash, it prints the error message and exits: ``` ERROR: [core/udp_server.c:397]: udp_init(): bind(6, 0x10c606504, 16) on 192.168.178.188: Can

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-04-27 Thread Sarbyn
``` #0 0x77761e71 in __strlen_sse2_pminub () from /lib64/libc.so.6 #1 0x732c62c4 in uac_init () at uac.c:96 #2 0x732ac665 in mod_init () at tm.c:782 ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on Git

Re: [sr-dev] [kamailio/kamailio] Do not start Kamailio if no listen address is configured (#1098)

2017-04-27 Thread Daniel-Constantin Mierla
Likely this is due to a module cleaning up some uninitialized structure, because kamailio should deal nicely when the listen address cannot be found. To see where the issue resides, it is good to have a core dump and get the backtrace. Be sure you set `ulimit -c ulimited` in terminal and start k