-
Notifications
You must be signed in to change notification settings - Fork 57
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
See dial tcp i/o timeouts once a day #443
Comments
Can you post the [appropriately redacted] output of this happening with |
I can tomorrow =) (which is likely when I'll see it again) |
This reminds me that I had built a local copy to work around issues I had with rebuilding servers from an older versions. Let me update that and test it out. |
Hmm, that's an error I've never seen before. Seems like it might be this bug that was recently filed in the |
I just finished upgrading to the the latest commit of Go and was finally able to recompile rack. (I was getting segmentation faults before) and rack works again! |
Great, thanks for reporting and testing this. |
I use Rack every day. The first request of the day, I always get:
It's as if there's some kind of connection pooling that's happening between processes and making this first request clears a connection. It seems unlikely that there's connection pooling, but it's a bit annoying regardless.
The text was updated successfully, but these errors were encountered: