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

error reading status line #167

Closed
rgs1 opened this issue Mar 9, 2015 · 3 comments
Closed

error reading status line #167

rgs1 opened this issue Mar 9, 2015 · 3 comments

Comments

@rgs1
Copy link
Contributor

rgs1 commented Mar 9, 2015

Seeing this when accessing a nickel app via apache's mod_proxy:

The timeout specified has expired: proxy: error reading status line from remote server localhost:8080

Might be a new thing (i.e.: after the hyper port). Has anyone else seen this? Looking with GDB, I see the worker thread hanged on CloneTcpStream#read().
@Ryman
Copy link
Member

Ryman commented Mar 11, 2015

This is probably a keepalive issue related to hyperium/hyper#368.

According to some searching, the temporary fix would be: 'There is a way to de-activate keep-alive for back-end connections: setting the proxy-nokeepalive environment variable (see the "Protocol Adjustments" section of the mod_proxy manual pages)'

@rgs1
Copy link
Contributor Author

rgs1 commented Mar 11, 2015

yeah saw that thread! thanks @Ryman!

@rgs1
Copy link
Contributor Author

rgs1 commented Mar 12, 2015

closing since this seems to be hyper (and disabling keep-alive is a valid workaround for now).

@rgs1 rgs1 closed this as completed Mar 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ryman @rgs1