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
Bad file descriptor (Errno::EBADF) server restart crash on ruby 2.0.0preview2 #177
Comments
I have a similar issue on Ubuntu with master and ruby 2.0.0.p0. I am using a socket instead of a tcp port so my error is
|
+1 on this, same exact message as masterkain above, but using sockets |
Seems #220 has solved this. I didn't realize ruby 2.0 changed this behavior. |
Can you release a version to rubygems.org with this fix? |
+1 (using TCP port, not socket) |
is it fixed ?
|
The puma issue is long fixed. That's something wrong with your OS probably.
|
If anyone else comes here searching for a solution to the above
It was being caused on my system by me having missed out a comma in the stdout_redirect line. i.e.
in my config/puma.rb, file when it should be:
Hope this helps someone :) |
@joeczucha Thanks so much, Your answer solves my problem. |
@joeczucha Thanks, For me it was |
I stumbled upon the same error as @muhammet and @joeczucha and @revathkumar, but it's neither a missing comma nor log folder. And the error message was really not helping in any way :/ Full log output:
puma config:
The reason was: The log files were not writable for the executing user. I missed this at first, because the log files are symlinked. It would be nice if puma could offer a meaningful error message that could actually assist in solving a problem. |
|
I'm playing around with puma on OS X 10.8.2 and tried to issue a restart through the web api using 1.6.3 started with:
results in:
Update: same error on Master.
The text was updated successfully, but these errors were encountered: