I'm testing failure scenarios before going to production.
This test has the MySQL server offline to observe the Proxy's behavior when it cannot reach the DB server.
In this case we are using the DB for checking a global black list, we are not using the DB for auth or location.
If the DB server goes offline after Kamailio has started there does not seem to be an issue. However if the DB server is offline when Kamailio is starting, Kamailio fails to start correctly.
Kamailio log (hostnames and IP addresses changed or redacted):
```
Jun 4 10:21:24 robo-proxy kamailio: INFO: <core> [tcp_main.c:4748]: init_tcp(): using epoll_lt as the io watch method (auto detected)
Jun 4 10:21:24 robo-proxy kamailio: WARNING: <core> [daemonize.c:360]: daemonize(): pid file contains old pid, replacing pid
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: pike [pike.c:115]: pike_init(): PIKE - initializing
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: pike [ip_tree.c:88]: init_lock_set(): probing 256 set size
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4635]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4635]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4635]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4635]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4635]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 1, pid 4635, "udp receiver child=0 sock=127.0.0.1:5060"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4635]: CRITICAL: <core> [main.c:1621]: main_loop(): Cannot fork
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4638]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4638]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4638]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4638]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4638]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 3, pid 4638, "udp receiver child=2 sock=127.0.0.1:5060"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4638]: CRITICAL: <core> [main.c:1621]: main_loop(): Cannot fork
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4636]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4636]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4636]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4636]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4636]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 2, pid 4636, "udp receiver child=1 sock=127.0.0.1:5060"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4636]: CRITICAL: <core> [main.c:1621]: main_loop(): Cannot fork
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4640]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4640]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4640]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4640]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4640]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 4, pid 4640, "udp receiver child=3 sock=127.0.0.1:5060"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4640]: CRITICAL: <core> [main.c:1621]: main_loop(): Cannot fork
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4647]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4647]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4647]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4647]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4647]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 8, pid 4647, "udp receiver child=3 sock=1.2.3.4:5060"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4647]: CRITICAL: <core> [main.c:1621]: main_loop(): Cannot fork
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4642]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4642]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4642]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4645]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4642]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4645]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4645]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4645]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4645]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 7, pid 4645, "udp receiver child=2 sock=1.2.3.4:5060"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4642]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 5, pid 4642, "udp receiver child=0 sock=1.2.3.4:5060"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4645]: CRITICAL: <core> [main.c:1621]: main_loop(): Cannot fork
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4642]: CRITICAL: <core> [main.c:1621]: main_loop(): Cannot fork
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4654]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4654]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4654]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4654]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4654]: ERROR: <core> [pt.c:341]: fork_process(): init_child failed for process 10, pid 4654, "timer"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: ALERT: <core> [main.c:781]: handle_sigs(): child process 4635 exited normally, status=255
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: ALERT: <core> [main.c:781]: handle_sigs(): child process 4636 exited normally, status=255
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: ALERT: <core> [main.c:781]: handle_sigs(): child process 4638 exited normally, status=255
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: ALERT: <core> [main.c:781]: handle_sigs(): child process 4640 exited normally, status=255
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: ALERT: <core> [main.c:781]: handle_sigs(): child process 4642 exited normally, status=255
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: ALERT: <core> [main.c:781]: handle_sigs(): child process 4645 exited normally, status=255
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: ALERT: <core> [main.c:781]: handle_sigs(): child process 4647 exited normally, status=255
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4634]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4653]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4660]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4644]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4661]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 12
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 13
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 14
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 15
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 16
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 17
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4658]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 18
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 19
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 20
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 21
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 26
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 24
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 23
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4659]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4659]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4659]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4659]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4659]: ERROR: <core> [pt.c:479]: fork_tcp_process(): init_child failed for process 13, pid 4659, "tcp receiver (generic) child=0"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4659]: ERROR: <core> [tcp_main.c:4871]: tcp_init_children(): fork failed: Connection refused
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4664]: ERROR: db_mysql [km_my_con.c:111]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'lab-mysql01' (111)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4664]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4664]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [nomo_con]
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4664]: ERROR: <core> [sr_module.c:923]: init_mod_child(): Error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/kamailio/modules/sqlops.so)
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4664]: ERROR: <core> [pt.c:479]: fork_tcp_process(): init_child failed for process 16, pid 4664, "tcp receiver (generic) child=3"
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4664]: ERROR: <core> [tcp_main.c:4871]: tcp_init_children(): fork failed: Connection refused
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 5
Jun 4 10:21:24 robo-proxy /usr/sbin/kamailio[4666]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 28
```
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/192
Module: kamailio
Branch: master
Commit: 363027e7fc5020ba80f0b183fc87921f3d3b641b
URL: https://github.com/kamailio/kamailio/commit/363027e7fc5020ba80f0b183fc87921…
Author: Stefan Mititelu <stefan.mititelu(a)1and1.ro>
Committer: Stefan Mititelu <stefan.mititelu(a)1and1.ro>
Date: 2015-06-10T15:43:36+03:00
debugger: add a new dbg_sip_msg() config function
Added a config function which prints how the sip message would look like
if it were to be sent out at that point in config. Displays how the message
looks after apllying all the lumps; but it is just printing, not actual
lump application. Updated doku.
---
Modified: dprint.h
Modified: modules/debugger/debugger_mod.c
Modified: modules/debugger/doc/debugger_admin.xml
Modified: msg_translator.c
Modified: msg_translator.h
---
Diff: https://github.com/kamailio/kamailio/commit/363027e7fc5020ba80f0b183fc87921…
Patch: https://github.com/kamailio/kamailio/commit/363027e7fc5020ba80f0b183fc87921…
Module: kamailio
Branch: master
Commit: 57e05de6dbb2de117be32b785944dabdbff4e49e
URL: https://github.com/kamailio/kamailio/commit/57e05de6dbb2de117be32b785944dab…
Author: Stefan Mititelu <stefan.mititelu(a)1and1.ro>
Committer: Stefan Mititelu <stefan.mititelu(a)1and1.ro>
Date: 2015-06-10T15:41:43+03:00
debugger: updated documentation for the new facility parameters.
Updated documentation for the new debugger facility params.
---
Modified: modules/debugger/doc/debugger_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/57e05de6dbb2de117be32b785944dab…
Patch: https://github.com/kamailio/kamailio/commit/57e05de6dbb2de117be32b785944dab…
---
diff --git a/modules/debugger/doc/debugger_admin.xml b/modules/debugger/doc/debugger_admin.xml
index 031e9e0..c4b6eb2 100644
--- a/modules/debugger/doc/debugger_admin.xml
+++ b/modules/debugger/doc/debugger_admin.xml
@@ -19,8 +19,9 @@
<para>
This module provides an interactive config file debugger. It can print
a trace of config script execution for a SIP message to log and set
- breakpoints on every script action, allowing step-by-step execution of
- the routing and response scripts.
+ breakpoints on every script action, allowing step-by-step execution of
+ the routing and response scripts. Moreover, this module allows setting
+ static and dynamic module specific debug settings.
</para>
<para>
Debugging can be done from local or remote host via RPC interface (e.g.,
@@ -247,8 +248,11 @@ modparam("debugger", "step_loops", 100)
<title><varname>mod_hash_size</varname> (int)</title>
<para>
Used to compute power of two as size of internal hash table to store levels
- per module (e.g., if its set to 4, internal hash table has 16 slots). This
- parameter is accesible readonly via the Kamailio config framework.
+ per module (e.g., if its set to 4, internal hash table has 16 slots). One
+ must set it's value grater than 0 such that memory to be allocated
+ to save the module specific debug levels or facility configured by
+ <varname>mod_level</varname> or <varname>mod_facility</varname>.
+ This parameter is accesible readonly via the Kamailio config framework.
</para>
<para>
<emphasis>
@@ -306,6 +310,52 @@ modparam("debugger", "mod_level", "tm=3")
</example>
</section>
+ <section id="dbg.p.mod_facility_mode">
+ <title><varname>mod_facility_mode</varname> (int)</title>
+ <para>
+ Enable or disable per module log facility (0 - disabled, 1 - enabled).
+ This parameter is tunable via the Kamailio config framework. To use
+ per module log facility you also have to set <varname>mod_hash_size</varname>.
+ </para>
+ <para>
+ <emphasis>
+ Default value is <quote>0</quote>.
+ </emphasis>
+ </para>
+ <example>
+ <title>Set <varname>mod_facility_mode</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("debugger", "mod_facility_mode", 1)
+...
+ </programlisting>
+ </example>
+ </section>
+
+ <section id="dbg.p.mod_facility">
+ <title><varname>mod_facility</varname> (str)</title>
+ <para>
+ Specify module log facility - the value must be in the format:
+ modulename=facility. The parameter can be set many times. For core
+ log facility, use module name 'core'. You also must enable
+ <varname>mod_facility_mode</varname> and <varname>mod_hash_size</varname>.
+ </para>
+ <para>
+ NOTE: See the <emphasis>syslog()</emphasis> library call for facility names (http://linux.die.net/man/3/syslog).
+ The most used facilities are LOG_LOCAL[0-7].
+ </para>
+
+ <example>
+ <title>Set <varname>mod_facility</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("debugger", "mod_facility", "core=LOG_LOCAL0")
+modparam("debugger", "mod_facility", "debugger=LOG_LOCAL1")
+...
+ </programlisting>
+ </example>
+ </section>
+
<section id="dbg.p.log_assign">
<title><varname>log_assign</varname> (int)</title>
<para>
Module: kamailio
Branch: master
Commit: e5250430035b6e620dd1ac86d2fb9ebcbc717d84
URL: https://github.com/kamailio/kamailio/commit/e5250430035b6e620dd1ac86d2fb9eb…
Author: Stefan Mititelu <stefan.mititelu(a)1and1.ro>
Committer: Stefan Mititelu <stefan.mititelu(a)1and1.ro>
Date: 2015-06-10T15:41:43+03:00
debugger: add support for static and dynamic, module specific, logging facility
Added two new debugger params which will support setting per module logging facility.
This is useful when one might want to change logging for a certain module to a different file.
mod_facility_mode (0/1) is used for enabling this. mod_facility (str) is used for
setting the facility.
---
Modified: dprint.c
Modified: dprint.h
Modified: modules/debugger/debugger_api.c
Modified: modules/debugger/debugger_api.h
Modified: modules/debugger/debugger_config.c
Modified: modules/debugger/debugger_config.h
Modified: modules/debugger/debugger_mod.c
---
Diff: https://github.com/kamailio/kamailio/commit/e5250430035b6e620dd1ac86d2fb9eb…
Patch: https://github.com/kamailio/kamailio/commit/e5250430035b6e620dd1ac86d2fb9eb…