Hi,
Message resend due to size exceeded. Yes, it is running that is something I don’t understand how it can start with this error: [root@vm-vse02-siprouter2 ~]# ps -ef |grep kam kamailio 1225 1 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1226 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1227 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1228 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1229 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1230 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1231 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1232 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1233 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1234 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1235 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1236 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1237 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1238 1225 0 14:03 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio root 1344 1171 0 14:26 pts/0 00:00:00 grep --color=auto kam So I kill the processes and then start again Kamailio, that again doesn’t end without CTRL-C. After that I can see Kamailio running: [root@vm-vse02-siprouter2 ~]# ps -ef |grep kam kamailio 1426 1 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1427 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1428 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1429 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1430 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1431 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1432 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1433 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1434 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1435 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1436 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1437 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1438 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio kamailio 1439 1426 0 14:31 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio root 1444 1171 0 14:32 pts/0 00:00:00 grep --color=auto kam Do you have an idea that could explain this result? Cordialement Patrick GINHOUX De : Daniel-Constantin Mierla [ <mailto:mico...@gmail.com> mailto:mico...@gmail.com] Envoyé : mercredi 5 avril 2017 14:22 À : Ginhoux, Patrick < <mailto:patrick.ginh...@fr.unisys.com> patrick.ginh...@fr.unisys.com> Cc : Kamailio (SER) - Users Mailing List < <mailto:sr-users@lists.sip-router.org> sr-users@lists.sip-router.org> Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem Hello, is kamailio already running there? Cheers, Daniel On 05.04.17 14:12, Ginhoux, Patrick wrote: Hi, I have downloaded and installed only the new rpm : kamailio-5.0.0-10.1.x86_64.rpm. Is it enough ? Then I try to start Kamailio that fails : [root@vm-vse02-siprouter2 kamailio]# service kamailio start Starting kamailio (via systemctl): Job for kamailio.service failed. See 'systemctl status kamailio.service' and 'journalctl -xn' for details. [FAILED] [root@vm-vse02-siprouter2 kamailio]# [root@vm-vse02-siprouter2 kamailio]# [root@vm-vse02-siprouter2 kamailio]# systemctl status kamailio.service -l kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Wed 2017-04-05 13:58:33 CEST; 4s ago Process: 4724 ExecStop=/etc/rc.d/init.d/kamailio stop (code=exited, status=0/SUCCESS) Process: 4867 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Main PID: 2946 (code=exited, status=0/SUCCESS) Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#63 #0/2: 21(15)/ 0x7fdd400f638 8 Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#63 #1/2: 22(16)/ 0x7fdd400f588 8 Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: DEBUG: <core> [core/pvapi.c:321]: pv_cache_lookup(): pvar [$var(i:NodePath)] found in cache Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: WARNING: <core> [core/cfg.y:3378]: warn_at(): warning in config file //etc/kamailio/kamailio .cfg, line 978, column 6-13: constant value in if(...) Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: INFO: <core> [core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4880]: CRITICAL: <core> [core/daemonize.c:345]: daemonize(): running process found in the pid file /var/run/kamailio/kamailio.pid Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4867]: Starting kamailio: Apr 05 13:58:33 vm-vse02-siprouter2 systemd[1]: kamailio.service: control process exited, code=exited status=1 Apr 05 13:58:33 vm-vse02-siprouter2 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Apr 05 13:58:33 vm-vse02-siprouter2 systemd[1]: Unit kamailio.service entered failed state. I get also a strange result when I try to start Kamailio using the service Kamailio command, that is nothing happen, the server doesn’t give a status : [root@vm-vse02-siprouter2 ~]# service kamailio start Starting kamailio (via systemctl): ^C I have to send a CTRL C to break the action. Cordialement Patrick GINHOUX De : Daniel-Constantin Mierla [ <mailto:mico...@gmail.com> mailto:mico...@gmail.com] Envoyé : mercredi 5 avril 2017 13:45 À : Ginhoux, Patrick <mailto:patrick.ginh...@fr.unisys.com> <patrick.ginh...@fr.unisys.com>; Kamailio (SER) - Users Mailing List <mailto:sr-users@lists.sip-router.org> <sr-users@lists.sip-router.org>; Kamailio (SER) - Users Mailing List <mailto:sr-us...@lists.kamailio.org> <sr-us...@lists.kamailio.org> Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem Hello, apparently the /var/run/kamailio folder was not created by the init.d script for rpm, as it is done in the deb specs. I updated it and triggered a rebuild of rpms, available at: <https://build.opensuse.org/package/show/home:kamailio:v5.0.x-rpms/kamailio50> https://build.opensuse.org/package/show/home:kamailio:v5.0.x-rpms/kamailio50 Try to upgrade and then see if it works. Later today we will release v5.0.1 and the rpms for it will have the new init.d script. Cheers, Daniel On 03.04.17 15:01, Ginhoux, Patrick wrote: Hi, I use « service kamailio start », so the init.d script that is the one created at the installation. Cordialement Patrick GINHOUX De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de Daniel-Constantin Mierla Envoyé : lundi 3 avril 2017 14:56 À : Kamailio (SER) - Users Mailing List <mailto:sr-us...@lists.kamailio.org> <sr-us...@lists.kamailio.org> Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem Hello, how do you start Kamailio? Via init.d/systemd script? Cheers, Daniel On 03.04.17 14:34, Ginhoux, Patrick wrote: Hi, Selinux is disabled. Cordialement Patrick GINHOUX De : Daniel-Constantin Mierla [ <mailto:mico...@gmail.com> mailto:mico...@gmail.com] Envoyé : lundi 3 avril 2017 14:33 À : Ginhoux, Patrick <mailto:patrick.ginh...@fr.unisys.com> <patrick.ginh...@fr.unisys.com>; Kamailio (SER) - Users Mailing List <mailto:sr-users@lists.sip-router.org> <sr-users@lists.sip-router.org> Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem Hello, have you disabled selinux to see if starts ok without it? Cheers, Daniel On 03.04.17 13:54, Ginhoux, Patrick wrote: Hi, Well, with one of my colleagues, we did some research and test, but we don’t find where the privilege issue is with the /var/ FS. If the fifo filename is "/var/run/kamailio/kamailio_rpc_fifo" or "/var/run/kamailio_rpc_fifo", we have this privilege issue. I thought that the following declaration would prevent this security issue : modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME) modparam("jsonrpcs", "fifo_mode", 0755) modparam("jsonrpcs", "fifo_group", "kamailio") modparam("jsonrpcs", "fifo_user", "kamailio") but it is not the case. For the moment only the fifo filename “/tmp/kamailio_rpc_fifo" is valid for kamailio to start. Cordialement Patrick GINHOUX
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
