-
Notifications
You must be signed in to change notification settings - Fork 937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in dns_cache.c with dns_cache_init=off #3350
Comments
Without topoh, calling +437200101011, resolved by the enum module to sip:enum-test@sip.nemox.net, running under valgrind with
I get:
→ CRASHES
→ CRASHES
→ NO CRASH, Kamailio receives “SIP/2.0 488 Not acceptable here” from the remote server. (This is not a problem of Kamailio)
→ NO CRASH, Kamailio receives “SIP/2.0 488 Not acceptable here” from the remote server. (This is not a problem of Kamailio) In each case I have performed the test twice and got consistent results. |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
Closing valid bugs, without fixing the real problem, results very few current reports for real problems in the software. This practice leads to the wrong impression, that Kamailio has no known problems, and therefore is good software. This is misleading and nobody has interest in having such misleading context. |
See #3475 (comment) . |
/notexpired |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
@dilyanpalauzov Hey can you confirm if this only happens on LUA config or also on the native config file? I've tried on native config file and it seems to be operating fine for both dns_cache_init=off/on. |
Also used in lua with no problems. Using the kamailio.cfg
kamailio.lua
test_message.sh
These are the logs produced when I call the
|
With Kamailio 5.8 it still crashes. I use in the meantime the bytecode of luajit as KEMI. kamailio.cfg
routing_logic.luajit
|
Hmm interesting thing, indeed with LuaJIT and your Edit: It seems the crash is coming from |
@dilyanpalauzov I just pushed #3858 for a possible fix. Can you confirm that you no longer see the crash, and that it functions properly? Thanks |
Thank you very much for looking into this! The setup I had in the past, six months ago, with 5.7, has connected me to +437200101012. When dns_cache_init=off without this patch applied on the 5.8 branch, with the configuration files I have, Kamailio crashes more or less immediately after it is started, or whenever a WebSocket connection is established. When dns_cache_init=off with this patch applied on the 5.8 branch, Kamailio crashes after I try to call +437200101012 over WebSocket. When dns_cache_init=on with this patch applied and I dial +437200101012 Kamailio does not crash, but does not connect me neither, with the latter being irrelevant here. So I think the initial problem is not solved, but your patch addreses a problem, which has not existed at the time I reported about this crash. |
So in 5.7 it worked correctly? I could try to see what changed in between. Do you have any more details of where it crashed after the patch or some trace I can look into? Thanks |
I pushed a new update on the PR, can you maybe try it again and report back? With your config and without the patch, indeed kamailio crashes at some point. With the new patch, it doesn't crash at all but want to verify that I replicated it correctly. |
I meant that in the past on 5.6 branch with my configuration Kamailio has not crashed immediately after start. Kamailio 5.8 crashes immediately after start. With your first version of the patch Kamailio does not crash anymore immediately after start. The problem report here is that Kamailio 5.6.3 crashed in my configuration when I try to call an ENUM resolved number +437200101012. With your second patch applied on the 5.8 branch, the call is performed and there is no crash. Thanks! |
Thanks for reporting and testing! #3858 Merged to master. |
With Kamailio 5.6.3 I add this code
and dial +437200101011 . The code above produces the output “ENUM RESULT 1 :RURI sip:enum-test@sip.nemox.net”.
I have the DNS-related settings:
Kamailio logs during the dial-in process:
The full backtrace is:
111.11.111.11 is the IP address of the server. 22.222.222.222 is my public IP address. 192.168.0.199 is my address behind NAT.
The text was updated successfully, but these errors were encountered: