On Tue, Mar 17, 2009 at 1:35 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
Hi Sara,
this is strange. If you increase the debug level to 4, you should see some message about the module loading. Is the mi_fifo module correctly loaded? Perhaps you configured another path in another modparam statement, so that the first one is overwritten, and subsequently not found from the ctl command?
Cheers,
Henning
Hello,
The log i get after increasing the debug level to 4 is in the attached. Hope it's fine to attach files in this mailing list :-)
On Wednesday 18 March 2009, Sara EL KABIRI wrote:
this is strange. If you increase the debug level to 4, you should see some message about the module loading. Is the mi_fifo module correctly loaded? Perhaps you configured another path in another modparam statement, so that the first one is overwritten, and subsequently not found from the ctl command?
The log i get after increasing the debug level to 4 is in the attached. Hope it's fine to attach files in this mailing list :-)
Hi Sara,
the log looks good so far, the fifo is loaded and also initialized. But, this line is also present:
Mar 17 18:40:03 [6236] ERROR:core:tcp_init: bind(6, 0x8190a44, 16) on 127.0.0.1:5065 : Address already in use
This means that the server did not start, because it still runs from some earlier start. Perhaps the server that runs here still uses a old/ wrong configuration?
Cheers,
Henning
On Wed, Mar 18, 2009 at 4:00 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
Hi Sara,
the log looks good so far, the fifo is loaded and also initialized. But, this line is also present:
Mar 17 18:40:03 [6236] ERROR:core:tcp_init: bind(6, 0x8190a44, 16) on 127.0.0.1:5065 : Address already in use
This means that the server did not start, because it still runs from some earlier start. Perhaps the server that runs here still uses a old/ wrong configuration?
Cheers,
Henning
Hi, I did many tests actually... Maybe i forgot sometime to stop Kamailio before restarting it, and appearently that was the log i've posted :-)
However, i am starting Kamailio properly right now, i'm not getting the "ERROR:core:tcp_init: bind(6, 0x8190a44, 16) on 127.0.0.1:5065 : Address already in use", but the mi_fifo error is still there! Is there anyway i could test if the mi_fifo module is working effectively? Would it be possible for the error to be a bug?
On Wednesday 18 March 2009, Sara EL KABIRI wrote:
I did many tests actually... Maybe i forgot sometime to stop Kamailio before restarting it, and appearently that was the log i've posted :-)
However, i am starting Kamailio properly right now, i'm not getting the "ERROR:core:tcp_init: bind(6, 0x8190a44, 16) on 127.0.0.1:5065 : Address already in use", but the mi_fifo error is still there! Is there anyway i could test if the mi_fifo module is working effectively? Would it be possible for the error to be a bug?
Hi Sara,
do you've actually a file in /tmp/kamailio_fifo ? And can you check with "strace kamctl ps 2>&1 |grep "fifo"" what file it tries to open?
Cheers,
Henning
On Wed, Mar 18, 2009 at 5:19 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
Hi Sara,
do you've actually a file in /tmp/kamailio_fifo ? And can you check with "strace kamctl ps 2>&1 |grep "fifo"" what file it tries to open?
Cheers,
Henning
Hello Henning,
I do have a kamailio_fifo in my /tmp directory. "*strace kamctl ps 2>&1 |grep "fifo"*" and "*kamctl ps 2>&1 |grep "fifo"*" return nothing...
On Wednesday 18 March 2009, Sara EL KABIRI wrote:
I do have a kamailio_fifo in my /tmp directory. "*strace kamctl ps 2>&1 |grep "fifo"*" and "*kamctl ps 2>&1 |grep "fifo"*" return nothing...
Hi Sara,
ok, take a look to the plain output from strace, without the grep command. Does it shows any errors from a file open, or a stat? Probably stupid question, but do you've the strace command installed?
Cheers,
Henning
-
Henning Westerholt -
Sara EL KABIRI