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 hast
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 (*
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 fi
Hi,
my reply is inline
2011/1/18 Daniel-Constantin Mierla
> 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 ti
Hello,
do you get anything in kamailio log messages when the fifo is not
responding?
What version of kamailio do you have?
Removing and creating a new one will not help, since kamailio will not
reopen, so practically will still use the old file descriptor.
Cheers,
Daniel
On 1/18/11 10:54
Hi all,
I'm having trouble trying to execute fifo commands with "kamctl fifo
". 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/
