Hi Daniel<div><br></div><div>both values are null. I might have found something: apparently some of the sockets kamailio->redis were inactive for a while and were being closed in the redis end. This is redis default config:</div>
<div><div># Close the connection after a client is idle for N seconds (0 to disable)</div><div>timeout 600</div><div><br></div><div>I've set the timeout value to 0 to confirm if this is actually the problem. </div><div>
<br></div><div>In case it might be useful for somebody, we've used lsof in recurrent mode to monitor the sockets status:</div><div><br></div><div>server# lsof -i :6379 -r 5"m===%T===" | grep -e == -e kamailio</div>
<div><div>===05:28:26===</div><div>kamailio 13365 kamailio 4u IPv4 58622 0t0 TCP localhost:34994->localhost:6379 (ESTABLISHED)</div><div>kamailio 13366 kamailio 4u IPv4 58626 0t0 TCP localhost:34995->localhost:6379 (ESTABLISHED)</div>
<div>kamailio 13367 kamailio 4u IPv4 58628 0t0 TCP localhost:34996->localhost:6379 (ESTABLISHED)</div><div>kamailio 13368 kamailio 4u IPv4 58632 0t0 TCP localhost:34997->localhost:6379 (ESTABLISHED)</div>
<div>kamailio 13369 kamailio 4u IPv4 58649 0t0 TCP localhost:35000->localhost:6379 (ESTABLISHED)</div><div>kamailio 13370 kamailio 4u IPv4 58661 0t0 TCP localhost:35003->localhost:6379 (ESTABLISHED)</div>
<div>kamailio 13376 kamailio 10u IPv4 58710 0t0 TCP localhost:35013->localhost:6379 (ESTABLISHED)</div><div>kamailio 13377 kamailio 4u IPv4 58705 0t0 TCP localhost:35012->localhost:6379 (ESTABLISHED)</div>
<div>kamailio 13378 kamailio 4u IPv4 58695 0t0 TCP localhost:35008->localhost:6379 (ESTABLISHED)</div><div>kamailio 13381 kamailio 4u IPv4 58691 0t0 TCP localhost:35006->localhost:6379 (ESTABLISHED)</div>
<div>kamailio 13382 kamailio 4u IPv4 58693 0t0 TCP localhost:35007->localhost:6379 (ESTABLISHED)</div><div>===05:28:31===</div><div>kamailio 13365 kamailio 4u IPv4 58622 0t0 TCP localhost:34994->localhost:6379 (ESTABLISHED)</div>
<div>kamailio 13366 kamailio 4u IPv4 58626 0t0 TCP localhost:34995->localhost:6379 (CLOSE_WAIT)</div><div>kamailio 13367 kamailio 4u IPv4 58628 0t0 TCP localhost:34996->localhost:6379 (ESTABLISHED)</div>
<div>kamailio 13368 kamailio 4u IPv4 58632 0t0 TCP localhost:34997->localhost:6379 (CLOSE_WAIT)</div><div>kamailio 13369 kamailio 4u IPv4 58649 0t0 TCP localhost:35000->localhost:6379 (CLOSE_WAIT)</div>
<div>kamailio 13370 kamailio 4u IPv4 58661 0t0 TCP localhost:35003->localhost:6379 (CLOSE_WAIT)</div><div>kamailio 13376 kamailio 10u IPv4 58710 0t0 TCP localhost:35013->localhost:6379 (CLOSE_WAIT)</div>
<div>kamailio 13377 kamailio 4u IPv4 58705 0t0 TCP localhost:35012->localhost:6379 (CLOSE_WAIT)</div><div>kamailio 13378 kamailio 4u IPv4 58695 0t0 TCP localhost:35008->localhost:6379 (CLOSE_WAIT)</div>
<div>kamailio 13381 kamailio 4u IPv4 58691 0t0 TCP localhost:35006->localhost:6379 (CLOSE_WAIT)</div><div>kamailio 13382 kamailio 4u IPv4 58693 0t0 TCP localhost:35007->localhost:6379 (CLOSE_WAIT)</div>
</div><div><br></div><div>Regards</div><div><br></div><div>Javi</div><div><br></div><div class="gmail_quote">On Fri, Jan 13, 2012 at 9:35 AM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<div class="im"><br>
<br>
On 1/13/12 8:00 AM, Javier Gallart wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all<br>
<br>
I have started making some tests with the ndb_redis module. So far we have not stressed the module (no more than 5 HGET commands/second at maximum). It works well, but with at some point it starts failing. The failures are easily found because the logs always show this:<br>
INFO: <core> [main.c:811]: INFO: signal 13 received<br>
</blockquote></div>
this due to a broken connection. What do you get in redis reply and info variables?<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
After that the redis value is always null. If I restart kamailio it starts working again.<br>
I've run kamailio with debug=4 but I haven't seen more useful information. On the redis side, I could find nothing in the logs either, the number of clientes connected is alway much less than the configured maximum, Any idea?<br>
On the other hand, if I restart redis we need to restart kamailio to restore the connections. Is the reconnection to redis on the roadmap?<br>
</blockquote>
<br></div>
It should not be that complex, there is the code for initializing the connection, it should be reused for doing it again in case of failure.<br>
<br>
Cheers,<br>
Daniel<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a><br>
<a href="http://linkedin.com/in/miconda" target="_blank">http://linkedin.com/in/miconda</a> -- <a href="http://twitter.com/miconda" target="_blank">http://twitter.com/miconda</a><br>
<br>
</font></span></blockquote></div><br></div>