Greetings, the attached shows the full backtrace of core file generated by Kamailio 5.1.4 after receiving a REGISTER message. Thanks and best regards Abdul On Wed, Aug 22, 2018 at 12:51 PM, Daniel-Constantin Mierla < miconda(a)gmail.com&gt; wrote:

Hi Daniel, the module was developed by a former colleauge. As I found out it queries the Database to check some Info about the clients. If they have set Call Forwarding or they were Blacklisted or to check their Numbers' Prefixes. So as I know no authentication tasks. I noticed that the obsoleted avp_db_query() was used. I will try to use sql_xquery() instead and update you. Although I am not sure it is the cause for such Crash because Kamailio is answering the REGISTER with "SIP/2.0 407 Proxy Authentication Required" then immediately finishing with "SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL)" I will provide you with more Info soon. Thanks for you patience with a Kamailio Beginner. Besr regards Abdul On Thu, Aug 23, 2018 at 4:25 PM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com > Hello, > > the frame 0 in bt full output has no details, so somehow the symbols stack > is broken. Does any of your custom modules have anything to do > authentication? Fetching username/password, or proving different encryption > algorithm? > Cheers, > Daniel > > > On 23.08.18 16:20, Abdulaziz Alghosh wrote: > > Greetings, > > the attached shows the full backtrace of core file generated by Kamailio > 5.1.4 after receiving a REGISTER message. > > Thanks and best regards > Abdul > > On Wed, Aug 22, 2018 at 12:51 PM, Daniel-Constantin Mierla < > miconda(a)gmail.com> >> Hello, >> >> the error message from dispatcher is not relevant for runtime, it is >> saying that you have to set some parameters to dispatcher module (those >> with avp names) because you use ds_next_dst()/ds_next_domain() -- without >> those parameters, you can't do re-routing using failure_route and >> dispatcher functions. >> >> From the logs, it is nothing showing the cause of the issue, could be >> your own modules or something else. >> >> Try to generate a corefile and then get the backtrace with gdb. To >> generate the corefile: >> >> - run "ulimit -c unlimited" in the terminal where you start kamailio >> - run kamailio as root user >> - reproduce the issue >> - there should be a log message saying that the "core was generated" >> - get the output of "bt full" from gdb inspecting the core file >> >> Cheers, >> Daniel >> >> On 22.08.18 11:40, Abdulaziz Alghosh wrote: >> >> Hi Everyone, >> >> I am trying to start kamailio 5.1.4 with two own modules. After >> /etc/init.d/kamailio start , I am getting one error of the dispatcher >> module and bunch of warrnings because of missed reply and failure routes. >> >> The first error before crashing is: >> >> ERROR: dispatcher [dispatcher.c:814]: ds_warn_fixup(): failover functions >> used, but required AVP parameters are NULL -- feature disabled >> >> >> Later on, when I am trying to register a user (from a soft phone) i am >> getting the following: >> >> ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: >> I'm terribly sorry, server error occurred (1/SL) >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6960]: CRITICAL: <core> >> [core/pass_fd.c:277]: receive_fd(): EOF on 20 >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ALERT: <core> [main.c:746]: >> handle_sigs(): child process 6942 exited by a signal 11 >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ALERT: <core> [main.c:749]: >> handle_sigs(): core was not generated >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: INFO: <core> [main.c:771]: >> handle_sigs(): terminating due to SIGCHLD >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6959]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6958]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6957]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6956]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6955]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6954]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6953]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6950]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6941]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6944]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6948]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6951]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6946]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6952]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6943]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6949]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6947]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6938]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6937]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6940]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6939]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a kernel: [296301.271457] kamailio[6942]: segfault at >> 0 ip (null) sp 00007fffb3ddf368 error 14 in >> kamailio[400000+442000] >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6945]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6960]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6936]: INFO: <core> [main.c:826]: >> sig_usr(): signal 15 received >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ERROR: jsonrpcs >> [jsonrpcs_fifo.c:594]: jsonrpc_fifo_destroy(): cannot delete the fifo >> (/tmp/kamailio_jsonrpc.fifo): Operation not permitted >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ERROR: jsonrpcs >> [jsonrpcs_sock.c:511]: jsonrpc_dgram_destroy(): cannot delete the socket >> (/tmp/kamailio_rpc.sock): Operation not permitted >> Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: INFO: <core> >> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized >> >> Regarding to the first error of the dispatcher module i could not find >> out which calibration i can follow with its parameters to get rid of this >> error. >> >> Regarding the jasonrpcs and the last two erros, here are my configuration >> in kamailio.cfg: >> >> #/* set the path to RPC fifo control file */ >> modparam("jsonrpcs", "fifo_name", "/tmp/kamailio_jsonrpc.fifo") >> modparam("jsonrpcs", "fifo_mode", 0755) >> modparam("jsonrpcs", "fifo_group", "kamailio") >> modparam("jsonrpcs", "fifo_user", "kamailio") >> >> >> #/* set the path to RPC unix socket control file */ >> modparam("jsonrpcs", "dgram_socket", "/tmp/kamailio_rpc.sock") >> modparam("jsonrpcs", "dgram_mode", 0755) >> modparam("jsonrpcs", "dgram_user", "kamailio") >> modparam("jsonrpcs", "dgram_group", "kamailio") >> >> I think the root cause is even beyond the dispatcher and jsonrpcs modules >> setting. >> >> Please check the attached where you can find my complete log file after >> starting Kamailio. >> >> Best regards >> Abdulaziz >> >> >> >> >> _______________________________________________ >> 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 -- www.kamailioworld.com >> >> > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference -- www.kamailioworld.com > >