Re: [SR-Users] Kamailio (docker) not even starting

hi, it is starting perfectly for me(my host OS is Centos 7): vagrant### docker run -d --name mykamailio -h mykamailio -p "5060-5061:5060-5061" -p "5060:5060/udp" -p "5064-5065:5064-5065" -p "5064-5065:5064-5065/udp" -p "7000-7001:7000-7001" -p "7000:7000/udp" -e "KAMAILIO_LOG_LEVEL=info" -e  "KAMAILIO_ENABLE_ROLES=websockets,message,presence_query,presence_sync,presence_notify_sync,registrar_sync" -e "RABBITMQ_HOSTS=rabbitmq.local" --cap-add IPC_LOCK --cap-add SYS_NICE --cap-add SYS_RESOURCE --cap-add NET_RAW kamailio/kamailio:5.4.4-trusty       44f1868649ad28aff0f67f170dfa763d8e8d3f0648cbb1018b8e254b1a2da643 vagrant### docker ps -a  | grep kama 44f1868649ad        kamailio/kamailio:5.4.4-trusty     "kamailio -DD -E"        11 seconds ago      Up 8 seconds           0.0.0.0:5060-5061->5060-5061/tcp, 0.0.0.0:5060->5060/udp, 0.0.0.0:5064-5065->5064-5065/tcp, 0.0.0.0:5064-5065->5064-5065/udp, 0.0.0.0:7000-7001->7000-7001/tcp, 0.0.0.0:7000->7000/udp   mykamailiovagrant###  your kamailio is already started "kamailio -DD -E"  and listenining on mentioned ports inside container: root@mykamailio:/# ps -ef | grep kamailioroot         1     0  0 00:46 ?        00:00:00 kamailio -DD -Eroot         6     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot         7     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot         8     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot         9     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        10     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        11     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        12     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        13     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        14     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        15     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        16     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        17     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        18     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        19     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        20     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        21     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        22     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        23     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        24     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        25     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        26     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        27     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        28     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        29     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        30     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        31     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        32     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        33     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        34     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        35     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        36     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot        37     1  0 00:46 ?        00:00:00 kamailio -DD -Eroot       224    97  0 00:51 pts/0    00:00:00 grep --color=auto kamailioroot@mykamailio:/# kamctl uptime         {  "jsonrpc":  "2.0",  "result": {    "now":  "Thu Feb 18 00:51:50 2021",    "up_since": "Thu Feb 18 00:46:29 2021",    "uptime": 321  },  "id": 225}root@mykamailio:/# kamctl stats | grep -i invite    "core:rcv_replies_1xx_invite = 0",    "core:rcv_replies_2xx_invite = 0",    "core:rcv_replies_3xx_invite = 0",    "core:rcv_replies_4xx_invite = 0",    "core:rcv_replies_5xx_invite = 0",    "core:rcv_replies_6xx_invite = 0",    "core:rcv_requests_invite = 0",root@mykamailio:/#  you cant stop/start it within container. for better experience you can map/attach the kamailio config ( e.g. -v /opt/kamailio/f2am_kam/etc/kamailio:/etc/kamailio) and then if you make config change stop/start the container. Best On Wednesday, February 17, 2021, 08:09:23 AM EST, Nuñez, Mario &lt;mario.nunez(a)atos.net&gt; wrote: Hello, I started from scratch by getting this Docker image: https://hub.docker.com/layers/kamailio/kamailio/5.4.4-trusty/images/sha256-…   Then running: docker pull kamailio/kamailio:5.4.4-trusty   Then starting an container with the command: docker run -d --name mykamailio -h mykamailio -p "5060-5061:5060-5061" -p "5060:5060/udp" -p "5064-5065:5064-5065" -p "5064-5065:5064-5065/udp" -p "7000-7001:7000-7001" -p "7000:7000/udp" -e "KAMAILIO_LOG_LEVEL=info" -e  "KAMAILIO_ENABLE_ROLES=websockets,message,presence_query,presence_sync,presence_notify_sync,registrar_sync" -e "RABBITMQ_HOSTS=rabbitmq.local" --cap-add IPC_LOCK --cap-add SYS_NICE --cap-add SYS_RESOURCE --cap-add NET_RAW kamailio/kamailio:5.4.4-trusty   I get into container using cli and ran: Kamtcl start Then container stopped with this log: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:2854]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28 23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 0(1) ALERT: <core> [main.c:780]: handle_sigs(): child process 77 exited normally, status=255 0(1) INFO: <core> [main.c:808]: handle_sigs(): terminating due to SIGCHLD 2(9) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 1(8) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 4(11) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 5(12) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 7(14) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 10(17) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 8(15) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 9(16) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 3(10) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 11(18) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 14(21) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 17(24) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 15(22) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 12(19) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 18(25) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 6(13) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 13(20) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 16(23) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 23(30) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 22(29) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 19(26) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 21(28) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 20(27) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 32(39) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 32(39) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 25(32) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 27(34) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 29(36) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 30(37) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 26(33) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 28(35) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 31(38) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 24(31) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2) 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized     Any idea about what could be the problem? Thank you in advance This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus._______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users