Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix Failed to write response: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" } #56

Closed
ZNielsen opened this issue Apr 26, 2021 · 2 comments
Closed

Fix Failed to write response: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" } #56

ZNielsen opened this issue Apr 26, 2021 · 2 comments
Labels
bug Something isn't working core Issues relating to the PodRacer core ops server Issues relating to the server side

Comments

@ZNielsen
Copy link
Owner

ZNielsen commented Apr 26, 2021 •
edited
Loading

Ever since I moved it to /etc/, I've been getting periodic timeouts that I never got before. Move it back to a home directory.

Also remove the retrying I put in to combat this. Apparently the error is happening downstream -- those retries are never firing.
@ZNielsen ZNielsen added bug Something isn't working core Issues relating to the PodRacer core ops server Issues relating to the server side labels Apr 26, 2021
@ZNielsen ZNielsen changed the title Move podracer dir Fix Failed to write response: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" } Apr 26, 2021
@ZNielsen
Copy link
Owner Author

Possible this is rocket having a socket error. Is there a way to request that rocket just blocks and waits for the resource?

ZNielsen added a commit that referenced this issue Apr 26, 2021
@ZNielsen
GH-56 - Attempt to fix the "would block" resource error
d48e235 
Per rwf2/Rocket#243, attempting to
fix this by jacking up the number of workers. Once async is done, this
shouldn't be needed.
ZNielsen added a commit that referenced this issue Apr 26, 2021
@ZNielsen
GH-56 - Bumping workers down a bit since it locked up the pi.
59ff898
@ZNielsen
Copy link
Owner Author

Have not seen this in a while, fixed by increasing workers?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working core Issues relating to the PodRacer core ops server Issues relating to the server side
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ZNielsen