The duration may be a result of waiting for child process to say it started
successfully and `exit_timeout` global parameter value, which is 60sec. So if
one of the child processes does not start properly (does not send back I am
ok), the main process will start shutdown procedure.
This is how
Closed #1690.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1690#event-1929327060___
Kamailio (SER) - Development Mailing List
sr-dev@l
You are right. It stopped printing (and stop running too) after ~70 seconds
after being started.
I guess it tried to connect to the database and the socket get closed
immediately by the OS and the handle to the socket became invalide. However,
the handle was still used in some epoll_wait call
sqlops doesn't connect itself to external systems, likely there was an error
related to sqlops before those that you can see. Being the start of kamailio,
likely those are printed due to large number of children, but starting kamailio
should fail at some point and everything should stop. For how
### Description
The sqlops module run into an infinite loop and print continously this line to
the stderr (or stdout):
22(17903) ERROR: [core/io_wait.h:1040]: io_wait_loop_epoll():
epoll_wait(10, 0x2ab72bb7b690, 0, 5000): Invalid argument [22]
### Troubleshooting
Reproduction
Set log_s
