Hello,
I am doing some tests with version 4.2.3 (installed of RPM centos 7 packages) in a clean installation, I have a kamailio running in production already configured and working, but I would like to start a totally clean configuration to learn more about kamailio. I am using the configuration file that comes in the default installation (kamailio-basic.cfg) just by adding a log on the main route.
I kept the log in messages file and increased the verbosity as below, and when i send any package (INVITE or REGISTER) I assume that the log or xlog lines should be displayed in file, but no. I see the packets arriving via tcpdump, and netstat shows that port 5060 is being listened by kamailio, but I have nothing else besides the initialization information (and the debug of MYSQL querys when activated unrelated to INVITE or REGISTRY packets).
Am I doing something wrong?
*Configs **Log :*
### LOG Levels: 3 = DBG, 2 = INFO, 1 = NOTICE, 0 = WARN, -1 = ERR #! ifdef WITH_DEBUG debug = 4 log_stderror = no #! else debug = 4 log_stderror = no #! endif
memdbg = 5 memlog = 5
log_facility = LOG_LOCAL0
*Main route log test:*
request_route { log ("Log main request TEST"); xlog ("Log main request TEST 2"); # not displayed route (REQINIT);
*/var/log/messages:*
Oct 5 23:39:12 pabxmodelo kamailio: Stopping kamailio: [ OK ] Oct 5 23:39:12 pabxmodelo systemd: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Oct 5 23:39:13 pabxmodelo kamailio: INFO: <core> [tcp_main.c:4745]: init_tcp(): using epoll_lt as the io watch method (auto detected) Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo kamailio: Starting kamailio: Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30070]: INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Oct 5 23:39:13 pabxmodelo systemd: Started SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Oct 5 23:39:13 pabxmodelo kamailio: [ OK ]
--------------------------------------------
Bruno H. G. Gouvêa
---
Hello,
systemd might divert the logs to its journal, and no longer seen via syslog, use journalctl to see if there are available there.
Cheers, Daniel
On 06.10.17 02:12, Bruno Henrique Gomes Gouvêa wrote:
Hello,
I am doing some tests with version 4.2.3 (installed of RPM centos 7 packages) in a clean installation, I have a kamailio running in production already configured and working, but I would like to start a totally clean configuration to learn more about kamailio. I am using the configuration file that comes in the default installation (kamailio-basic.cfg) just by adding a log on the main route.
I kept the log in messages file and increased the verbosity as below, and when i send any package (INVITE or REGISTER) I assume that the log or xlog lines should be displayed in file, but no. I see the packets arriving via tcpdump, and netstat shows that port 5060 is being listened by kamailio, but I have nothing else besides the initialization information (and the debug of MYSQL querys when activated unrelated to INVITE or REGISTRY packets).
Am I doing something wrong?
*Configs **Log :*
### LOG Levels: 3 = DBG, 2 = INFO, 1 = NOTICE, 0 = WARN, -1 = ERR #! ifdef WITH_DEBUG debug = 4 log_stderror = no #! else debug = 4 log_stderror = no #! endif
memdbg = 5 memlog = 5
log_facility = LOG_LOCAL0
*Main route log test:*
request_route { log ("Log main request TEST"); xlog ("Log main request TEST 2"); # not displayed route (REQINIT);
*/var/log/messages:*
Oct 5 23:39:12 pabxmodelo kamailio: Stopping kamailio: [ OK ] Oct 5 23:39:12 pabxmodelo systemd: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Oct 5 23:39:13 pabxmodelo kamailio: INFO: <core> [tcp_main.c:4745]: init_tcp(): using epoll_lt as the io watch method (auto detected) Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo kamailio: Starting kamailio: Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30070]: INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Oct 5 23:39:13 pabxmodelo systemd: Started SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Oct 5 23:39:13 pabxmodelo kamailio: [ OK ]
Bruno H. G. Gouvêa
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Thanks for the reply.
journalctl does not show me any additional information as well. I changed the log to /var/log/kamailio.log using: debug = 3; log_stderror = no; log_facility = LOG_LOCAL6 and in rsyslog.conf local6. * /var/log/kamailio.log
but I still see the initialization of kamailio correctly, but no log of incoming requests: request_route { log ("Log main request"); xlog ("L_INFO", "Log main request 2");
I assume this line should be executed on any received request right?
Thank you
--------------------------------------------
Bruno H. G. Gouvêa
CEO - CiberCloud LTDA http://cibercloud.com.br http://ligou.me bruno@cibercloud.com.br
---
2017-10-11 4:48 GMT-03:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
systemd might divert the logs to its journal, and no longer seen via syslog, use journalctl to see if there are available there.
Cheers, Daniel
On 06.10.17 02:12, Bruno Henrique Gomes Gouvêa wrote:
Hello,
I am doing some tests with version 4.2.3 (installed of RPM centos 7 packages) in a clean installation, I have a kamailio running in production already configured and working, but I would like to start a totally clean configuration to learn more about kamailio. I am using the configuration file that comes in the default installation (kamailio-basic.cfg) just by adding a log on the main route.
I kept the log in messages file and increased the verbosity as below, and when i send any package (INVITE or REGISTER) I assume that the log or xlog lines should be displayed in file, but no. I see the packets arriving via tcpdump, and netstat shows that port 5060 is being listened by kamailio, but I have nothing else besides the initialization information (and the debug of MYSQL querys when activated unrelated to INVITE or REGISTRY packets).
Am I doing something wrong?
*Configs **Log :*
### LOG Levels: 3 = DBG, 2 = INFO, 1 = NOTICE, 0 = WARN, -1 = ERR #! ifdef WITH_DEBUG debug = 4 log_stderror = no #! else debug = 4 log_stderror = no #! endif
memdbg = 5 memlog = 5
log_facility = LOG_LOCAL0
*Main route log test:*
request_route { log ("Log main request TEST"); xlog ("Log main request TEST 2"); # not displayed route (REQINIT);
*/var/log/messages:*
Oct 5 23:39:12 pabxmodelo kamailio: Stopping kamailio: [ OK ] Oct 5 23:39:12 pabxmodelo systemd: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Oct 5 23:39:13 pabxmodelo kamailio: INFO: <core> [tcp_main.c:4745]: init_tcp(): using epoll_lt as the io watch method (auto detected) Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30050]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Oct 5 23:39:13 pabxmodelo kamailio: Starting kamailio: Oct 5 23:39:13 pabxmodelo /usr/sbin/kamailio[30070]: INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Oct 5 23:39:13 pabxmodelo systemd: Started SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Oct 5 23:39:13 pabxmodelo kamailio: [ OK ]
Bruno H. G. Gouvêa
Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com
Hello,
On 11.10.17 22:31, Bruno Henrique Gomes Gouvêa wrote:
Thanks for the reply.
journalctl does not show me any additional information as well. I changed the log to /var/log/kamailio.log using: debug = 3; log_stderror = no; log_facility = LOG_LOCAL6 and in rsyslog.conf local6. * /var/log/kamailio.log
but I still see the initialization of kamailio correctly, but no log of incoming requests: request_route { log ("Log main request"); xlog ("L_INFO", "Log main request 2");
I assume this line should be executed on any received request right?
yes, if the xlog() is at the top of request_route, it should be printed for each valid request received by Kamailio.
Can you set log_stderror=yes and see if the messages are printed in the terminal?
Cheers, Daniel
Hello,
even with log on console I do not get anything yet.
[root@pabxmodelo ~]# /usr/sbin/kamailio -P /var/run/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio loading modules under config path: /usr/lib64/kamailio/modules/ Listening on udp: PUBLIC_IP:5060 Aliases: udp: PUBLIC_HOSTNAME:5060
WARNING: no fork mode 0(9355) INFO: <core> [tcp_main.c:4745]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(9355) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(9355) INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available 0(9355) INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 0(9355) INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(9355) INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 4(9359) INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config)
Thank you
--------------------------------------------
Bruno H. G. Gouvêa
CEO - CiberCloud LTDA http://cibercloud.com.br http://ligou.me bruno@cibercloud.com.br
---
2017-10-12 7:26 GMT-03:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
On 11.10.17 22:31, Bruno Henrique Gomes Gouvêa wrote:
Thanks for the reply.
journalctl does not show me any additional information as well. I changed the log to /var/log/kamailio.log using: debug = 3; log_stderror = no; log_facility = LOG_LOCAL6 and in rsyslog.conf local6. * /var/log/kamailio.log
but I still see the initialization of kamailio correctly, but no log of incoming requests: request_route { log ("Log main request"); xlog ("L_INFO", "Log main request 2");
I assume this line should be executed on any received request right?
yes, if the xlog() is at the top of request_route, it should be printed for each valid request received by Kamailio.
Can you set log_stderror=yes and see if the messages are printed in the terminal?
Cheers, Daniel
-- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, in Berlin, Nov 13-15, 2017 - www.asipto.com Kamailio World Conference - www.kamailioworld.com
-
Bruno Henrique Gomes Gouvêa -
Daniel-Constantin Mierla