Closed (fixed)
Project:
Drupal.org infrastructure
Component:
Other
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
6 Nov 2013 at 20:30 UTC
Updated:
1 May 2014 at 17:10 UTC
Jump to comment: Most recent
RSS feeds of Releases (/node/X/release) are bringing the site down. They are currently blocked.
E.g.: https://drupal.org/node/3060/release
https://drupal.org/node/3060/release/feed
~ $ curl -I https://drupal.org/node/3060/release/feed
HTTP/1.1 503 Service Unavailable
Server: nginx/1.4.3
Date: Wed, 06 Nov 2013 20:23:47 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 211
Connection: keep-alive
Retry-After: 0
X-Varnish: 703585667
Age: 0
Via: 1.1 varnish
X-Cache-Svr: www6.drupal.org
X-Cache: MISS
Comments
Comment #1
eliza411 commentedI'm seeing this message now: Our servers are currently a bit busy, please try refreshing the page after a few seconds.
Thanks!
I'll see what I can find for a parent issue.
Comment #2
eporama commentedSo I got access to the devwww server but none of the existing development environments seem to have the same problem. This is a 503 error, so if it doesn't happen on devwww we might need to get someone to look at logs on the actual production web servers.
Is it worth the effort for me to request a separate development environment ala https://drupal.org/node/1018084 point #2? I would be glad to troubleshoot this, but would think that it should be present in the latest updated devwww environment, but it isn't.
Comment #3
tvn commentedInfrastructure team might have blocked release feeds because of performance issues. I am checking with them now.
In the mean time feel free to choose any other issues with Drupal.org 7.1 tag to work on :) https://drupal.org/project/issues/search?text=&projects=&assigned=&submi...
Comment #4
nnewton commentedCorrect. I currently have release feeds blocked globally as they were taking down the site. This need to be addressed.
-N
Comment #5
damienmckennaAny idea why they were taking down the site?
Comment #6
damienmckennaComment #7
tvn commentednnewton, can you give more information? Why they were taking the site down? How can we fix it?
Comment #8
tvn commentedComment #9
ricardoamaro commentedI saw that most of the servers are blocking it still but for some reason www5 is not:
so I would advise for us to move the configurations from CFEngine to puppet, so every Infra Sysadmin can change them and update them across servers
This is the actual code that's blocking the feeds:
default.vcl:
Comment #10
tvn commentedComment #11
tvn commentedUpdating issue summary.
Comment #12
tvn commentedWhile we're figuring out how to fix this issue - is there any possibility to provide a better message on this blocked feeds? Currently it says:
Which is not really a good idea, considering refreshing won't help.
Comment #13
drummI'm not sure what the root cause is here. These pages are another Display of https://drupal.org/node/3060/release, which is doing okay, as far as I know. We may be able to turn these back on, any pay attention to the DB and logs.
Comment #14
ricardoamaro commented@drumm you mean someone can remove this code from varnish?
or is that still a problem?
Comment #15
drummYes, I think that should be removed. (Or we need to know what is problematic about those pages.)
Comment #16
ricardoamaro commented@drumm where can i change those vlcs?
Comment #17
ricardoamaro commentedComment #18
ricardoamaro commentedthis is back to normal now
Comment #19
basic commentedThanks Ricardo