-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Sometimes client requests fail with "no cached connection was available" #3203
Comments
Is this fixed or something? |
@vito It's unclear this was ever a problem since multiple recent Vault versions have been built against Go 1.8. I think that's why the OP closed it. |
its not fixed for me, i am using vault 0.9.0. , i have this pretty often right now. Means, every 30 minutes. It seems it is not based on a single request - all requests made in that timeframe are getting those
Looking at the vault logs, nothing logged at all. Coming from the same background as vito here, using concourse. Could that be a connection pooling issue on the client side (implementation) ? those are the vault logs for that whole day:
Running vault as a docker-container, local network for the client ( same docker-network + same host ). This issue can be reproduced when running https://github.com/EugenMayer/concourseci-server-boilerplate for a while ( Seems like this could indeed be a go-lang issue golang/go#16582 .. but i guess in that case, it seems like rather the client implementation, the concourse time. It also fits the actual case it happens, when triggers are executed (scheduled tasks) .. probably those triggered are scheduled at the same time, running a lot of requests at the same time |
Depending on the concourse version you may have one that is built with a Go version where this is not fixed. Remember, this is a client issue, not a server issue. The OP probably needs to provide any further advice as I don't know much about concourse, and they closed it themselves. |
@jefferai using the newest concourse stable, 3.6.0 - i would expect 1.9, but i am not sure. I got you, that this is a client issue, reading up more sources that was exactly the same impression - thank you for clarifying that |
Unfortunately I think you need to file this as a bug against concourse. I can honestly say I've no memory of hearing of this issue anywhere else and they seem to think it's resolved. |
any method to close the connection forcefully. |
Feature Request:
The vault client library is being used in Concourse (http://concourse.ci - http://github.com/concourse/concourse). Occasionally the client code emits errors like this:
This appears to be related here: golang/go#16582 (an issue fixed in go 1.8)
This request is to update your use of http2 (
golang.org/x/net/http2
) to that included with 1.8 (I guess by implication that means only supporting golang >= 1.8).Thanks.
The text was updated successfully, but these errors were encountered: