-
-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG, NEED VERIFICATION] $worker->getWorker()->error((string)$e); cause a force kill and lost error msg #691
Comments
Hey @drefixs. Thanks for the report.
|
Hi @48d90782 thanks for the quick responce:
Also I noticed that if you change http.pool.debug=true it starts to work normally without force killing the process with log
|
@48d90782 May be i found the reason after that it try again to do graceful termination with w.Stop() when I just remove this else condition all start work as expected and worker_watcher push stopped worker back to the vector queue also stop command have fallback kill logic inside. |
First of all, please, provide a worker you used and full steps on how to reproduce this issue. I'll definitely take into account your investigation, thanks 👍🏻 |
Fixed, will be as on the second screenshot. |
When I created my own worker process and use the code example for the push error to the rr server for workers
I don't see my original error only the next errors:
I expected to see my (string)$e in the rr logs
Instead, i see that worker process was force killed
I create a simple fix for my issue: #690
The text was updated successfully, but these errors were encountered: