-
Notifications
You must be signed in to change notification settings - Fork 100
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
Errno::ECHILD: No child processes error when starting SolidQueue with rake solid_queue:start #298
Comments
Huh, this is very strange. Could you share a bit more about your setup? Or the full log since it starts until it triggers that error? At that point it should have forked some process so there should be at least a child process... I wonder if there's no configuration at all and no forks are being created... I might not be handling this case well 🤔 |
And could you share your solid queue configuration as well? |
Thanks! And are you testing this in |
i'm testing this in dev, but somehow it takes the config for production |
Ok, so when you added the configuration in Now, to the second issue:
By default it'll use config.solid_queue.logger = ActiveSupport::Logger.new(STDOUT) And see if that shows the workers and dispatcher starting and running. |
Hmm yes... that one is new to me... Maybe this helps? |
It's working fine. |
Nice! 👏 So glad to hear it's working! I'll ship an improvement for the configuration problem and the |
When attempting to start SolidQueue using bundle exec rake solid_queue:start, an Errno::ECHILD: No child processes error is raised. The error occurs during the waitpid2 system call within the reap_and_replace_terminated_forks method in the fork_supervisor.rb file. This seems to indicate an issue with handling child processes in the forking supervisor.
Environment
The text was updated successfully, but these errors were encountered: