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

sip-router bugtracker at sip-router.org
Mon Mar 3 14:33:00 CET 2014


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has been changed.  The changes are listed below.  For full information about what has changed, visit the URL and click the History tab.

FS#399 - Potential issue with kamctl
User who did this: Daniel-Constantin Mierla (miconda)
Task details edited:
-------
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?

<code>name=kamailio_receiver_$$
path=$CHROOT_DIR/tmp/$name
if test -p $path; then
        rm $path
fi</code>

-------

More information can be found at the following URL:
http://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.



More information about the sr-dev mailing list