Hello Ali,
(please keep the sr-users list in CC, that other people can also participate)
Remove the “-D” from your Kamailio command line – then the warning will disappear. This is also necessary because you want to have Kamailio listen on several addresses. If you want to test it more in a production like setting, you should also remove the “-E” from the command line. You will find the logging in your system log then.
Cheers,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services
From: ali mahfouz arm037@usal.edu.lb Sent: Wednesday, July 10, 2019 11:54 AM To: Henning Westerholt hw@skalatan.de Subject: Re: [SR-Users] kamailio warning
Dear Mr.Henning, I am working on high availability on two Kamailio servers connected to the database using keepalived and when I am testing Kamailio I got this issue and I have no idea about fixing it
i am trying to see by this command
kamailio -E -D -f /etc/kamailio/kamailio.cfg 0(16101) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.10.10.20:5060http://10.10.10.20:5060 udp: 10.10.10.3:5060http://10.10.10.3:5060 tcp: 10.10.10.20:5060http://10.10.10.20:5060 tcp: 10.10.10.3:5060http://10.10.10.3:5060 Aliases: tcp: 10.10.10.3:5060http://10.10.10.3:5060 tcp: 10.10.10.20:5060http://10.10.10.20:5060 udp: 10.10.10.3:5060http://10.10.10.3:5060 udp: 10.10.10.20:5060http://10.10.10.20:5060 *: sip.domain.local:*
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(16101) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(16101) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(16101) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(16101) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(16101) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(16101) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(16101) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(16101) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 6(16131) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 5(16130) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/16130 ^C 6(16131) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(16130) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(16126) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16131 exited normally, status= 3(16128) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16126 exited normally, status= 4(16129) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16128 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16129 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16130 exited normally, status=0 0(16101) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(16101) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(16101) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(16127) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(16101) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Please help thank you for giving time from your time
On Wed, Jul 10, 2019 at 12:40 PM Henning Westerholt <hw@skalatan.demailto:hw@skalatan.de> wrote: Hello Ali,
the first warning is related about the starting mode of Kamailio. You should not start it with “no forking mode” if you want to get rid of it. Have a look to your command line parameters: “-D” is the one to change.
Cheers,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services
From: sr-users <sr-users-bounces@lists.kamailio.orgmailto:sr-users-bounces@lists.kamailio.org> On Behalf Of ali mahfouz Sent: Wednesday, July 10, 2019 8:46 AM To: sr-users@lists.kamailio.orgmailto:sr-users@lists.kamailio.org; sr-users-request@lists.kamailio.orgmailto:sr-users-request@lists.kamailio.org; sr-users-owner@lists.kamailio.orgmailto:sr-users-owner@lists.kamailio.org Subject: [SR-Users] kamailio warning
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(8777) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(8777) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(8777) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(8777) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(8777) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(8777) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(8777) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(8777) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 5(8782) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/8782 6(8783) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) ^C 6(8783) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(8782) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 4(8781) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 3(8780) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(8778) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8782 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8778 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8781 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8783 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8780 exited normally, status=0 0(8777) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(8777) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(8777) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(8779) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(8777) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Thanks for the tip! Dear Mr.Henning really i dont know how to use sr-users how to post and how to view replies last question please: when i am sending a message it is sent and appears in other user but why it appears as an error in /var/log/messages as seen below: Jul 10 09:29:04 k-2 local0.err /usr/sbin/kamailio[6255]: ERROR: {1 2 MESSAGE 99142N2NjYmFjZmI0YmRkN2Y1NGNmYTdjOGY1M2VkZDYxZDE} <script>: [MESSAGE] this is an moh ali MESSAGE
On Wed, Jul 10, 2019 at 1:02 PM Henning Westerholt hw@skalatan.de wrote:
Hello Ali,
(please keep the sr-users list in CC, that other people can also participate)
Remove the “-D” from your Kamailio command line – then the warning will disappear. This is also necessary because you want to have Kamailio listen on several addresses. If you want to test it more in a production like setting, you should also remove the “-E” from the command line. You will find the logging in your system log then.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
*From:* ali mahfouz arm037@usal.edu.lb *Sent:* Wednesday, July 10, 2019 11:54 AM *To:* Henning Westerholt hw@skalatan.de *Subject:* Re: [SR-Users] kamailio warning
Dear Mr.Henning,
I am working on high availability on two Kamailio servers connected to the database using keepalived and when I am testing Kamailio
I got this issue and I have no idea about fixing it
i am trying to see by this command
kamailio -E -D -f /etc/kamailio/kamailio.cfg 0(16101) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.10.10.20:5060 udp: 10.10.10.3:5060 tcp: 10.10.10.20:5060 tcp: 10.10.10.3:5060 Aliases: tcp: 10.10.10.3:5060 tcp: 10.10.10.20:5060 udp: 10.10.10.3:5060 udp: 10.10.10.20:5060 *: sip.domain.local:*
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(16101) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(16101) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(16101) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(16101) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(16101) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(16101) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(16101) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(16101) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 6(16131) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 5(16130) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/16130 ^C 6(16131) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(16130) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(16126) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16131 exited normally, status= 3(16128) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16126 exited normally, status= 4(16129) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16128 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16129 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16130 exited normally, status=0 0(16101) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(16101) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(16101) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(16127) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(16101) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Please help
thank you for giving time from your time
On Wed, Jul 10, 2019 at 12:40 PM Henning Westerholt hw@skalatan.de wrote:
Hello Ali,
the first warning is related about the starting mode of Kamailio. You should not start it with “no forking mode” if you want to get rid of it. Have a look to your command line parameters: “-D” is the one to change.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
*From:* sr-users sr-users-bounces@lists.kamailio.org *On Behalf Of *ali mahfouz *Sent:* Wednesday, July 10, 2019 8:46 AM *To:* sr-users@lists.kamailio.org; sr-users-request@lists.kamailio.org; sr-users-owner@lists.kamailio.org *Subject:* [SR-Users] kamailio warning
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(8777) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(8777) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(8777) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(8777) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(8777) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(8777) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(8777) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(8777) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 5(8782) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/8782 6(8783) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) ^C 6(8783) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(8782) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 4(8781) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 3(8780) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(8778) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8782 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8778 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8781 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8783 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8780 exited normally, status=0 0(8777) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(8777) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(8777) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(8779) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(8777) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Hello Ali,
about the sr-users – it is easy, just make sure that you use “reply to all” or a similar feature in your mail client.
About the question: you can give the log level to the “xlog” function, that it is not output as ERROR, but e.g. as NOTICE etc.. Have a look to the xlog module reference docs.
Cheers,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services
From: ali mahfouz arm037@usal.edu.lb Sent: Wednesday, July 10, 2019 1:20 PM To: Henning Westerholt hw@skalatan.de Cc: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: Re: [SR-Users] kamailio warning
Thanks for the tip! Dear Mr.Henning really i dont know how to use sr-users how to post and how to view replies last question please: when i am sending a message it is sent and appears in other user but why it appears as an error in /var/log/messages as seen below: Jul 10 09:29:04 k-2 local0.err /usr/sbin/kamailio[6255]: ERROR: {1 2 MESSAGE 99142N2NjYmFjZmI0YmRkN2Y1NGNmYTdjOGY1M2VkZDYxZDE} <script>: [MESSAGE] this is an moh ali MESSAGE
On Wed, Jul 10, 2019 at 1:02 PM Henning Westerholt <hw@skalatan.demailto:hw@skalatan.de> wrote: Hello Ali,
(please keep the sr-users list in CC, that other people can also participate)
Remove the “-D” from your Kamailio command line – then the warning will disappear. This is also necessary because you want to have Kamailio listen on several addresses. If you want to test it more in a production like setting, you should also remove the “-E” from the command line. You will find the logging in your system log then.
Cheers,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services
From: ali mahfouz <arm037@usal.edu.lbmailto:arm037@usal.edu.lb> Sent: Wednesday, July 10, 2019 11:54 AM To: Henning Westerholt <hw@skalatan.demailto:hw@skalatan.de> Subject: Re: [SR-Users] kamailio warning
Dear Mr.Henning, I am working on high availability on two Kamailio servers connected to the database using keepalived and when I am testing Kamailio I got this issue and I have no idea about fixing it
i am trying to see by this command
kamailio -E -D -f /etc/kamailio/kamailio.cfg 0(16101) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.10.10.20:5060http://10.10.10.20:5060 udp: 10.10.10.3:5060http://10.10.10.3:5060 tcp: 10.10.10.20:5060http://10.10.10.20:5060 tcp: 10.10.10.3:5060http://10.10.10.3:5060 Aliases: tcp: 10.10.10.3:5060http://10.10.10.3:5060 tcp: 10.10.10.20:5060http://10.10.10.20:5060 udp: 10.10.10.3:5060http://10.10.10.3:5060 udp: 10.10.10.20:5060http://10.10.10.20:5060 *: sip.domain.local:*
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(16101) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(16101) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(16101) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(16101) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(16101) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(16101) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(16101) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(16101) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 6(16131) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 5(16130) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/16130 ^C 6(16131) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(16130) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(16126) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16131 exited normally, status= 3(16128) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16126 exited normally, status= 4(16129) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16128 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16129 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16130 exited normally, status=0 0(16101) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(16101) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(16101) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(16127) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(16101) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Please help thank you for giving time from your time
On Wed, Jul 10, 2019 at 12:40 PM Henning Westerholt <hw@skalatan.demailto:hw@skalatan.de> wrote: Hello Ali,
the first warning is related about the starting mode of Kamailio. You should not start it with “no forking mode” if you want to get rid of it. Have a look to your command line parameters: “-D” is the one to change.
Cheers,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services
From: sr-users <sr-users-bounces@lists.kamailio.orgmailto:sr-users-bounces@lists.kamailio.org> On Behalf Of ali mahfouz Sent: Wednesday, July 10, 2019 8:46 AM To: sr-users@lists.kamailio.orgmailto:sr-users@lists.kamailio.org; sr-users-request@lists.kamailio.orgmailto:sr-users-request@lists.kamailio.org; sr-users-owner@lists.kamailio.orgmailto:sr-users-owner@lists.kamailio.org Subject: [SR-Users] kamailio warning
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(8777) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(8777) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(8777) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(8777) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(8777) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(8777) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(8777) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(8777) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 5(8782) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/8782 6(8783) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) ^C 6(8783) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(8782) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 4(8781) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 3(8780) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(8778) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8782 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8778 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8781 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8783 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8780 exited normally, status=0 0(8777) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(8777) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(8777) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(8779) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(8777) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
In other words, don’t just paste the error, but message BEFORE the error, so we can see what led to the error
:)
On Wed, 10 Jul 2019 at 14:46, Henning Westerholt hw@skalatan.de wrote:
Hello Ali,
about the sr-users – it is easy, just make sure that you use “reply to all” or a similar feature in your mail client.
About the question: you can give the log level to the “xlog” function, that it is not output as ERROR, but e.g. as NOTICE etc.. Have a look to the xlog module reference docs.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
*From:* ali mahfouz arm037@usal.edu.lb *Sent:* Wednesday, July 10, 2019 1:20 PM *To:* Henning Westerholt hw@skalatan.de *Cc:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Subject:* Re: [SR-Users] kamailio warning
Thanks for the tip!
Dear Mr.Henning
really i dont know how to use sr-users how to post and how to view replies
last question please:
when i am sending a message it is sent and appears in other user
but why it appears as an error in /var/log/messages as seen below:
Jul 10 09:29:04 k-2 local0.err /usr/sbin/kamailio[6255]: ERROR: {1 2 MESSAGE 99142N2NjYmFjZmI0YmRkN2Y1NGNmYTdjOGY1M2VkZDYxZDE} <script>: [MESSAGE] this is an moh ali MESSAGE
On Wed, Jul 10, 2019 at 1:02 PM Henning Westerholt hw@skalatan.de wrote:
Hello Ali,
(please keep the sr-users list in CC, that other people can also participate)
Remove the “-D” from your Kamailio command line – then the warning will disappear. This is also necessary because you want to have Kamailio listen on several addresses. If you want to test it more in a production like setting, you should also remove the “-E” from the command line. You will find the logging in your system log then.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
*From:* ali mahfouz arm037@usal.edu.lb *Sent:* Wednesday, July 10, 2019 11:54 AM *To:* Henning Westerholt hw@skalatan.de *Subject:* Re: [SR-Users] kamailio warning
Dear Mr.Henning,
I am working on high availability on two Kamailio servers connected to the database using keepalived and when I am testing Kamailio
I got this issue and I have no idea about fixing it
i am trying to see by this command
kamailio -E -D -f /etc/kamailio/kamailio.cfg 0(16101) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.10.10.20:5060 udp: 10.10.10.3:5060 tcp: 10.10.10.20:5060 tcp: 10.10.10.3:5060 Aliases: tcp: 10.10.10.3:5060 tcp: 10.10.10.20:5060 udp: 10.10.10.3:5060 udp: 10.10.10.20:5060 *: sip.domain.local:*
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(16101) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(16101) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(16101) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(16101) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(16101) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(16101) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(16101) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(16101) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 6(16131) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 5(16130) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/16130 ^C 6(16131) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(16130) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(16126) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16131 exited normally, status= 3(16128) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16126 exited normally, status= 4(16129) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16128 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16129 exited normally, status=0 0(16101) ALERT: <core> [main.c:751]: handle_sigs(): child process 16130 exited normally, status=0 0(16101) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(16101) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(16101) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(16127) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(16101) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Please help
thank you for giving time from your time
On Wed, Jul 10, 2019 at 12:40 PM Henning Westerholt hw@skalatan.de wrote:
Hello Ali,
the first warning is related about the starting mode of Kamailio. You should not start it with “no forking mode” if you want to get rid of it. Have a look to your command line parameters: “-D” is the one to change.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
*From:* sr-users sr-users-bounces@lists.kamailio.org *On Behalf Of *ali mahfouz *Sent:* Wednesday, July 10, 2019 8:46 AM *To:* sr-users@lists.kamailio.org; sr-users-request@lists.kamailio.org; sr-users-owner@lists.kamailio.org *Subject:* [SR-Users] kamailio warning
WARNING: no fork mode and more than one listen address found (will use only the first one) 0(8777) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(8777) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... 0(8777) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(8777) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available 0(8777) INFO: <core> [main.c:2669]: main(): processes (at least): 16 - shm size: 67108864 - pkg size: 8388608 0(8777) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(8777) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(8777) WARNING: <core> [main.c:1347]: main_loop(): using only the first listen address (no fork) 5(8782) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/8782 6(8783) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) ^C 6(8783) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 5(8782) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 4(8781) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 3(8780) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 1(8778) INFO: <core> [main.c:836]: sig_usr(): signal 2 received 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8782 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8778 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8781 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8783 exited normally, status=0 0(8777) ALERT: <core> [main.c:751]: handle_sigs(): child process 8780 exited normally, status=0 0(8777) INFO: <core> [main.c:778]: handle_sigs(): dont_fork turned on, living on 0(8777) INFO: <core> [main.c:772]: handle_sigs(): SIGCHLD received, but no child has stopped, ignoring it 0(8777) NOTICE: <core> [main.c:709]: handle_sigs(): Thank you for flying kamailio!!! 2(8779) INFO: <core> [main.c:836]: sig_usr(): signal 15 received 0(8777) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
ali mahfouz -
David Villasmil -
Henning Westerholt