5 ms·

Took forever to load, then gave me "Page Does Not Exist." Anybody else having issues?

by monochromatic 10y ago

pirocks 10y ago
I too am having issues.
- twiss 10y ago
  I filed a report through the "report a website issue" button at the blog homepage. Hope they fix it soon.
smhenderson 10y ago
I am getting the same. Tried about 15 minutes ago and then again just now. Still showing the Page Does Not Exist error.
ParadoxOryx 10y ago
Here's the Google cached version - http://webcache.googleusercontent.com/search?q=cache:https://developers.redhat.com/blog/2017/02/13/testing-testing-gcc/ http://webcache.googleusercontent.com/search?q=cache:https:/...
- egwynn 10y ago
  For me, that version refreshes indefinitely. I recommend reading the plain-text version: http://webcache.googleusercontent.com/search?q=cache:https://developers.redhat.com/blog/2017/02/13/testing-testing-gcc/&num=1&prmd=ivns&strip=1&vwsrc=0 http://webcache.googleusercontent.com/search?q=cache:https:/...
dmalcolm 10y ago
[author of the post here] Thanks; am chasing it up at my end
- i336_ 10y ago
  Thanks for chasing it up! Would I be right in guessing that we're looking at a well-built security system responding to high page load? Saying the page doesn't exist in these types of situations is interesting. Users consider 404s permanent, so some proportion is unlikely to come back. Furthermore, because each user is hitting the page individually, there's going to be very little out-of-band "no it doesn't work", so it won't reduce server load by much. From a security standpoint, if high load like this is causing "lp0 on fire"-type issues, a generic 404 may be the correct answer, depending on the situation. A 404 is quite generic, but I'm sure it could still leak useful information depending on the scenario. Whatever's going on, hearing what actually happened would be very cool (and educational, most people here are Web developers!).
  - dmalcolm 10y ago
    It seems to be working again. Sorry about the snafu. I've been exchanging emails with the team on the hosting side, but I don't yet have info on what happened.
    - i336_ 10y ago
      Yay! Yep, it's back up. Thanks again! In case it's useful, some of the page resources were 503ing/404ing before: http://i.imgur.com/5JUyphf.png http://i.imgur.com/5JUyphf.png (the intermixed connection_refused errors are from my /etc/hosts blocking)

Took forever to load, then gave me "Page Does Not Exist." Anybody else having issues?

pirocks 10y ago

I too am having issues.

twiss 10y ago
I filed a report through the "report a website issue" button at the blog homepage. Hope they fix it soon.

smhenderson 10y ago

I am getting the same. Tried about 15 minutes ago and then again just now. Still showing the Page Does Not Exist error.

ParadoxOryx 10y ago

Here's the Google cached version - http://webcache.googleusercontent.com/search?q=cache:https://developers.redhat.com/blog/2017/02/13/testing-testing-gcc/ http://webcache.googleusercontent.com/search?q=cache:https:/...

egwynn 10y ago
For me, that version refreshes indefinitely. I recommend reading the plain-text version: http://webcache.googleusercontent.com/search?q=cache:https://developers.redhat.com/blog/2017/02/13/testing-testing-gcc/&num=1&prmd=ivns&strip=1&vwsrc=0 http://webcache.googleusercontent.com/search?q=cache:https:/...

dmalcolm 10y ago

[author of the post here] Thanks; am chasing it up at my end

i336_ 10y ago
Thanks for chasing it up! Would I be right in guessing that we're looking at a well-built security system responding to high page load? Saying the page doesn't exist in these types of situations is interesting. Users consider 404s permanent, so some proportion is unlikely to come back. Furthermore, because each user is hitting the page individually, there's going to be very little out-of-band "no it doesn't work", so it won't reduce server load by much. From a security standpoint, if high load like this is causing "lp0 on fire"-type issues, a generic 404 may be the correct answer, depending on the situation. A 404 is quite generic, but I'm sure it could still leak useful information depending on the scenario. Whatever's going on, hearing what actually happened would be very cool (and educational, most people here are Web developers!).
- dmalcolm 10y ago
  It seems to be working again. Sorry about the snafu. I've been exchanging emails with the team on the hosting side, but I don't yet have info on what happened.
  - i336_ 10y ago
    Yay! Yep, it's back up. Thanks again! In case it's useful, some of the page resources were 503ing/404ing before: http://i.imgur.com/5JUyphf.png http://i.imgur.com/5JUyphf.png (the intermixed connection_refused errors are from my /etc/hosts blocking)