Re: [OpenSIPS-Devel] [opensips] Opensips 2.1 problems on start when cannot connect to redis (#753)

2016-01-13 Thread Răzvan Crainea 
Closed #753 via 76034ad60dfd991232ac3053c07f7a72de234e43.

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/753#event-513520575___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] Opensips 2.1 problems on start when cannot connect to redis (#753)

2016-01-12 Thread Nick Altmann 
It has no timeout and it's not just warning. If it cannot connect redis, it 
cannot start, just hangs. I've waited for about 5 minutes, it is still 
complaining into logs and hangs.

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/753#issuecomment-171167832___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] Opensips 2.1 problems on start when cannot connect to redis (#753)

2016-01-12 Thread Nick Altmann 
How to reproduce. Just set redis to working ip with no (not working) redis. 
Like 8.8.8.8.

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/753#issuecomment-171167891___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

[OpenSIPS-Devel] [opensips] Opensips 2.1 problems on start when cannot connect to redis (#753)

2016-01-12 Thread Nick Altmann 
When opensips 21 cannot connect to redis on start, it hangs with these messages 
in log:

Jan 12 11:57:06 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 160 ms (now 210 ms), it may overlap
Jan 12 11:57:06 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 210 ms (now 350 ms), it may overlap
Jan 12 11:57:06 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 350 ms (now 410 ms), it may overlap
Jan 12 11:57:06 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 410 ms (now 540 ms), it may overlap
Jan 12 11:57:06 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 540 ms (now 610 ms), it may overlap
Jan 12 11:57:07 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 610 ms (now 720 ms), it may overlap
Jan 12 11:57:07 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 720 ms (now 850 ms), it may overlap
Jan 12 11:57:07 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 850 ms (now 920 ms), it may overlap
Jan 12 11:57:07 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 920 ms (now 1050 ms), it may overlap
Jan 12 11:57:07 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1050 ms (now 1120 ms), it may overlap
Jan 12 11:57:07 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1120 ms (now 1200 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1200 ms (now 1310 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1310 ms (now 1400 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1400 ms (now 1510 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1510 ms (now 1610 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1610 ms (now 1710 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1710 ms (now 1810 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1810 ms (now 1920 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 1920 ms (now 2010 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 2010 ms (now 2110 ms), it may overlap
Jan 12 11:57:08 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 2110 ms (now 2200 ms), it may overlap
Jan 12 11:57:09 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 2200 ms (now 2300 ms), it may overlap
Jan 12 11:57:09 [25689] WARNING:core:utimer_ticker: utimer task  
already schedualed for 2300 ms (now 2400 ms), it may overlap

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/753___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] Opensips 2.1 problems on start when cannot connect to redis (#753)

2016-01-12 Thread Răzvan Crainea 
Hi, Nick!

After it times out, do you still continue to see these logs?
This warning is a known issue, we are working on a fix for it.

Best regards,
Răzvan

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/753#issuecomment-170978640___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel