[sr-dev] [tracker] Task opened: Potential issue with kamctl

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Morten Tryfoss (mtryfoss) Attached to Project - sip-router Summary - Potential issue with kamctl Task Type - Bug Report Category - sercmd Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - 4.1 Due in Version - Undecided Due Date - Undecided Details - There seems to be a potential issue with kamctl.fifo if a script crashes for some reason. The file /tmp/kamailio_receiver_<pid> might be left again after script finish, and this causes kamctl to fail next time it runs with that pid: Feb 24 07:04:45 bnsip1ha /usr/sbin/kamailio[16767]: ERROR: mi_fifo [fifo_fnc.c:224]: mi_open_reply_pipe(): open error (/tmp/kamailio_receiver_16613): Permission denied Feb 24 07:04:45 bnsip1ha /usr/sbin/kamailio[16767]: ERROR: mi_fifo [fifo_fnc.c:488]: mi_fifo_server(): cannot open reply pipe /tmp/kamailio_receiver_16613 Feb 24 07:04:48 bnsip1ha kamailio(kamailio)[16605]: WARNING: Kamailio is not up according to kamctl monitor! This is not critical at all, but we use "kamctl monitor" from heartbeat for health checking. Would it be safe to add this to the start of kamctl.fifo, to clean up files that are not deleted? name=kamailio_receiver_$$ path=$CHROOT_DIR/tmp/$name if test -p $path; then rm $path fi More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=399 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.