Hi,
i'm trying to use the ndb_redis connector , but i've a problem when redis server is down and i try to restart kamailio.
Kamailio in this case not start and release this log:
2(19590) ERROR: ndb_redis [redis_client.c:112]: redisc_init(): error communicating with redis server [srv1] (xxxxxx/0): Connection refused
2(19590) ERROR: ndb_redis [ndb_redis_mod.c:126]: child_init(): failed to initialize redis connections
2(19590) ERROR: <core> [sr_module.c:927]: init_mod_child(): init_mod_child(): Error while initializing module ndb_redis (//lib/kamailio/modules/ndb_redis.so)
30(19622) ERROR: <core> [tcp_main.c:4962]: tcp_init_children(): ERROR: tcp_main: fork failed: Connection refused
31(19624) : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 11
31(19624) : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 31
0(19588) ALERT: <core> [main.c:775]: handle_sigs(): child process 19589 exited normally, status=255
0(19588) ALERT: <core> [main.c:775]: handle_sigs(): child process 19590 exited normally, status=255
What would you like to happen when a service on which you depend is not available?
On 22 December 2014 at 15:56, pars3c pars3c@gmail.com wrote:
Hi,
i’m trying to use the ndb_redis connector , but i’ve a problem when redis server is down and i try to restart kamailio.
Kamailio in this case not start and release this log:
2(19590) ERROR: ndb_redis [redis_client.c:112]: redisc_init(): error communicating with redis server [srv1] (xxxxxx/0): Connection refused
2(19590) ERROR: ndb_redis [ndb_redis_mod.c:126]: child_init(): failed to initialize redis connections
2(19590) ERROR: <core> [sr_module.c:927]: init_mod_child(): init_mod_child(): Error while initializing module ndb_redis (//lib/kamailio/modules/ndb_redis.so)
30(19622) ERROR: <core> [tcp_main.c:4962]: tcp_init_children(): ERROR: tcp_main: fork failed: Connection refused
31(19624) : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 11
31(19624) : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 31
0(19588) ALERT: <core> [main.c:775]: handle_sigs(): child process 19589 exited normally, status=255
0(19588) ALERT: <core> [main.c:775]: handle_sigs(): child process 19590 exited normally, status=255
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
I wold like that the Service kamailio start and then write on the log that the server not answer.
If kamailio is up, and redis go down, kamailio continue to work and write on the log the error connecting to redis, but it remainder up.
Thanks
Il lunedì 22 dicembre 2014, Ben Langfeld ben@langfeld.co.uk ha scritto:
What would you like to happen when a service on which you depend is not available?
On 22 December 2014 at 15:56, pars3c <pars3c@gmail.com javascript:_e(%7B%7D,'cvml','pars3c@gmail.com');> wrote:
Hi,
i’m trying to use the ndb_redis connector , but i’ve a problem when redis server is down and i try to restart kamailio.
Kamailio in this case not start and release this log:
2(19590) ERROR: ndb_redis [redis_client.c:112]: redisc_init(): error communicating with redis server [srv1] (xxxxxx/0): Connection refused
2(19590) ERROR: ndb_redis [ndb_redis_mod.c:126]: child_init(): failed to initialize redis connections
2(19590) ERROR: <core> [sr_module.c:927]: init_mod_child(): init_mod_child(): Error while initializing module ndb_redis (//lib/kamailio/modules/ndb_redis.so)
30(19622) ERROR: <core> [tcp_main.c:4962]: tcp_init_children(): ERROR: tcp_main: fork failed: Connection refused
31(19624) : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 11
31(19624) : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 31
0(19588) ALERT: <core> [main.c:775]: handle_sigs(): child process 19589 exited normally, status=255
0(19588) ALERT: <core> [main.c:775]: handle_sigs(): child process 19590 exited normally, status=255
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org javascript:_e(%7B%7D,'cvml','sr-users@lists.sip-router.org'); http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users