THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#199 - kamailio does not stop if debug >= 3 User who did this - Rob Gagnon (rgagnon)

---------- While working on fetching the information requested, and copying portions of huge log files between commands, it seems now (because of the time it takes to find and copy the data between commands) that this "not stopping" issue I reported could be a non-issue. Here's why.

It appears it could just take an awful long time for kamailio to dump what it needs to dump to the logs when debug is 3 or more and it is told to stop.

When debug is 3 or more, and I issue "service kamailio stop", the issuance of the stop command takes approx. 5 seconds on the server I am using before the command prompt returns.

At this point a "ps -ef | grep kamailio" shows it to still be running. I believe this is just because the parent process has died, and all the children are busy logging their own demises.

It took another 20 seconds or so before no process with the name kamailio was running, at which time the opensips.log file was well over 10MB.

You should probably just close this ticket, and maybe a note could be put somewhere in the documentation to let people know that it can take a while for kamailio to fully shut down when debug is set high enough that all the malloc's and free's are logged while it is dying off.

If the logs are not needed when shutting down, then the work-around I use (putting debug to 1 before stop) might be a good suggestion. ----------

More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=199#comment65...

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.