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.

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

Issues with some pages with 4.1.1-1 on Xenial #32

Closed
carlalexander opened this issue Sep 2, 2016 · 1 comment
Closed

Issues with some pages with 4.1.1-1 on Xenial #32

carlalexander opened this issue Sep 2, 2016 · 1 comment

Comments

@carlalexander
Copy link
Contributor

I've been using your configuration for a while with WordPress sites and it's been great! I'm slowly moving everything to Xenial and I've started running into issues where pages are half rendered. If I remove Varnish, the backend returns everything correctly.

I've had this issue before. But it's more consistent now. I managed to dig down to inside varnishlog and find this:

-   Fetch_Body     4 eof stream
-   FetchError     Resource temporarily unavailable
-   FetchError     eof socket fail

When this happens, the request is incomplete. Yet Varnish returns it anyways. No retries are attempted.

Is there a way to make a check for these FetchError and trigger a retry? I tried using vcl_backend_error and doing return (retry);, but that didn't work. Is there a way to check for this in vcl_backend_response? I've looked around, but information on this is sparse (or my GoogleFu failed me lol).

@carlalexander
Copy link
Contributor Author

I'm doing some extensive debugging and I think this is an issue with Varnish itself. So I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant