-
Notifications
You must be signed in to change notification settings - Fork 342
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
Intermittent Waiting for control socket to be removed...
after unit reconfiguration
#610
Comments
It looks like a duplicate of this issue: #600. |
Yes, this is using 1.26.0 - I ran unit with debug and couldn't see any obvious extra information:
|
It doesn't look like Unit with debug. When debug is enabled, there will be lots of |
I added a layer to my docker image as per the docs - does that not pass the arguments to the entrypoint script?
That is the unsuccessful run - the last message just repeats forever. A successful run in debug mode:
etc etc - this then responds to requests. |
@cgearing Your parameters don't affect the command for starting Unit in Probably it needs to be fixed for respecting |
Sorry @VBart my brain has finally caught up with what you're saying. Here's a gist for the logs https://gist.github.com/cgearing/d1bbe789181c4400f5381301c9550be3 (I thought it would be too much for this thread). |
Thanks for debug log. I've inspected it and confirm the issue caused by the bug in SIGCHLD handler which was fixed in #600 . In the log I was unable to find the last records from PID 16 (controller), notable |
I've just tried 1.26.1 and I'm fairly sure that it has fixed the issue - thank you for creating a brilliant tool - it's made developing/deploying small applications very easy! |
Hi,
I've noticed since moving from threaded to multiprocess nginx-unit with python 3.9 I frequently get a loop of
Waiting for control socket to be removed
after the container starts up.The nginx-unit config:
Logs from the container:
The text was updated successfully, but these errors were encountered: