Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Error 500 on comments url #37
hope you can provide some guide to fix this issue.
Hi Matias, thank you for your quick response! sure i have an output! not sure whats really going on, but tracing the issue i found out that disabling the Devel module "fixes" the issue. Seems to be a overflow issue, i also tried changing the workspace_client memory to 512k but no luck, only disabling Devel, lets access the comment pages through varnish
/usr/sbin/varnishd -j unix,user=vcache -F -a :8080 -T 192.168.10.15:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,1G -p workspace_client=512k
LW@req 86 rxreq+PW@Start: 1487082335.510768 0.000000 0.000000)PW@Req: 1487082335.510768 0.000000 0.000000?W@127.0.0.1 48624W@GET
Looks like your error is
Let me know how that goes!
Hi Mattias, sorry for the late feedback.. I added the config params you mentioned except for the sess_workspace, since it's causing an error on Varnish 4, when restarting the service you get an "Unknown paramenter" error. (more info here: http://stackoverflow.com/questions/26788794/varnish-error-sess-workspace) and the error when accessing the page is still present. I'm pasting the new log for your review if possible:
root@inferno:/var/log/varnish# varnishlog -a -q "RespStatus >= 500 or BerespStatus >= 500"
Ow, Varnish 4, my bad. Please add the following;
Increase those values as you debug, they determine;
Hi Mattias! thanks once again for your support!
unfortunately i can't get rid of this weird issue, i've tried multiple combinations on the parameters you suggested and included other combinations as well to see if that might fix the issue. i tried combinations like this one for example:
but no matter what values you set for the varnish daemon theres no way to access the /comment/19#comment-19 URL on this specific Drupal 8 site (lets call it site A).
I tried on a new Drupal 8 install ( fresh install, lets call it site B ) with similar Drupal modules enabled as site A and with a standard daemon params for varnish:
and the comments url (i.e comment/19#comment-19) on site B is completely accesible! Which makes me think that is either a some sort of combination of modules on site A that break varnish no matter what configuration you set for the deamon ( which makes no much sense ) or is a Varnish 4.1 bug on the Ubuntu package.
if you have the time eventually to go over this, here's the guide i followed (which includes your vcl) to setup the environment where im doing my tests,
I don't think Varnish will ever handle this, it adheres to the HTTP protocol, and those duplicate headers violate that protocol. Only (*) the
The only fix is in the code, which you did: you should be good now. :-)
(*) Could be more, but I doubt it.