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
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:
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
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
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:
