[SR-Users] kamctl fifo <command> not responding
Daniel-Constantin Mierla
miconda at gmail.com
Mon Jan 24 17:12:57 CET 2011
Hello,
On 1/24/11 4:50 PM, Anton Roman wrote:
> Hello,
>
> I've already got the fifo listener PID. Kamailio had to be restarted
> and now it's working fine. When it gets unresponsive again I'll check
> it with gdb. I'll keep you informed.
>
> On the other hand, we use fifo pipe quite often to update hastables
> (/sht_reload/) and to get hashtable dumps (/sht_dump/). These HTs are
> used to implement a CAC mechanism. We also regularly use the
> /cr_reload_routes/ command.
fifo is not suitable for heavy traffic - depending on the operating
system, messages in fifo are limited in size. You should consider using
RPC interface over XMLRPC or via sercmd. If you want to stick to MI
control interface, a better option is using datagram (mi_datagram) via
unix socket or inet socket over 127.0.0.1.
Cheers,
Daniel
>
> Thanks.
>
> Regards,
> Antón
>
> 2011/1/18 Daniel-Constantin Mierla <miconda at gmail.com
> <mailto:miconda at gmail.com>>
>
> Hello,
>
> do you have ctl module loaded? If yes, you can connect with sercmd
> and get the pid of the fifo listener:
>
> sercmd> ps
>
> Then connect with gdb:
>
> gdb /path/to/kamailio pidoffifolistener
>
> and get the backtrace.
>
> That should show what the fifo process is doing.
>
> Also, you can get the pid of fifo process at startup, with kamctl
> ps, store it for the time when it blocks in order to use it with gdb.
>
> I haven't encountered this issue, do you have lot of communication
> over fifo file? How many commands and how often are sent through
> fifo file?
>
> Cheers,
> Daniel
>
>
>
> On 1/18/11 11:52 AM, Anton Roman wrote:
>> Hi,
>>
>> my reply is inline
>>
>> 2011/1/18 Daniel-Constantin Mierla <miconda at gmail.com
>> <mailto:miconda at gmail.com>>
>>
>> Hello,
>>
>> do you get anything in kamailio log messages when the fifo is
>> not responding?
>>
>> No, I didn't find anything regarding the fifo command in the logs.
>>
>>
>> What version of kamailio do you have?
>>
>> kamailio-3.0.2, the last time we updated the code was on August
>> 1st, since then it is in production.
>>
>>
>> Removing and creating a new one will not help, since kamailio
>> will not reopen, so practically will still use the old file
>> descriptor.
>>
>> It makes all the sense.
>>
>>
>> Cheers,
>> Daniel
>>
>> Thank you very much,
>> regards,
>> Anton
>>
>>
>> On 1/18/11 10:54 AM, Anton Roman wrote:
>>> Hi all,
>>>
>>> I'm having trouble trying to execute fifo commands with
>>> "kamctl fifo <command>". Just after restarting Kamailio it
>>> works fine, however, sometimes after some days running it
>>> doesn't respond.
>>>
>>> kamailio1:~#*kamctl fifo which*
>>>
>>> It doesn't respond so I input *Crtl+c* and I get:
>>> /usr/local/lib/kamailio//kamctl/kamctl.fifo: line 89:
>>> /tmp/kamailio_fifo: Interrupted system call
>>>
>>> If I delete and create the fifo file again (with "rm
>>> /tmp/kamailio_fifo" and "mkfifo /tmp/kamailio_fifo" and
>>> "chmod 660 /tmp/kamailio_fifo") it keeps not responding.
>>>
>>> Any help is welcome, what can be happening? Below you can
>>> find info about the pipe and the running kamailio.
>>>
>>> Thanks in advance,
>>> Best regards
>>>
>>> Antón
>>>
>>>
>>>
>>> kamailio1:~# *ls -hall /tmp/kamailio_fifo *
>>> prw-rw---- 1 root root 0 ene 17 12:01 /tmp/kamailio_fifo
>>>
>>> After deleting and creating the fifo file again:
>>>
>>> kamailio1:~# *ls -hall /tmp/kamailio_fifo *
>>> prw-rw-r-- 1 root root 0 ene 18 10:28 /tmp/kamailio_fifo
>>>
>>> kamailio1:~#*ps -ef | grep kama*
>>> root 17369 17245 0 10:12 pts/0 00:00:00 grep kama
>>> kamailio 23277 1 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23289 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23291 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23293 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23294 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23295 23277 0 Jan15 ? 00:01:14
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23299 23277 0 Jan15 ? 00:01:13
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23300 23277 0 Jan15 ? 00:01:13
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23303 23277 0 Jan15 ? 00:01:13
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23305 23277 0 Jan15 ? 00:05:29
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23306 23277 0 Jan15 ? 00:05:33
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23309 23277 0 Jan15 ? 00:05:30
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23311 23277 0 Jan15 ? 00:05:31
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23312 23277 0 Jan15 ? 00:00:02
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23313 23277 0 Jan15 ? 00:00:39
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23315 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23320 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23321 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23322 23277 0 Jan15 ? 00:00:05
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>> kamailio 23323 23277 0 Jan15 ? 00:00:00
>>> /usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid
>>> -m 512 -u kamailio -g kamailio
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierla
>> Kamailio (OpenSER) Advanced Training
>> Jan 24-26, 2011, Irvine, CA, USA
>> http://www.asipto.com
>>
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla
> Kamailio (OpenSER) Advanced Training
> Jan 24-26, 2011, Irvine, CA, USA
> http://www.asipto.com
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20110124/d9d0aa2a/attachment-0001.htm>
More information about the sr-users
mailing list