We had approximately 20 minutes where the site was flopping on and off today due to trying to properly fix the portscanning bug (the feature wasn't fully disabled, and had to push a fix which made thing worse before getting it properly fixed).
I got some about 3 hours ago. First the site was totally down. Then it was half-working, with several 503s.
I didn't notice anything at http://status.soylentnews.org/ [soylentnews.org] - I wonder if it's worth having a "most recent website problem" entry on that page permanently, so that we can check you were aware of any apparently temporary problems we've encountered. OTOH, maybe it's not a big deal at this stage in the site's development.
Linode switch went out, the site was inaccessible for approximately 30-45 minutes, and then I have to scrape Apache's remains and bring it back to life.
(Score: 3, Informative) by NCommander on Sunday April 13 2014, @07:42PM
When did you get these?
We had approximately 20 minutes where the site was flopping on and off today due to trying to properly fix the portscanning bug (the feature wasn't fully disabled, and had to push a fix which made thing worse before getting it properly fixed).
Still always moving
(Score: 2) by Open4D on Tuesday April 15 2014, @12:48AM
I got some about 3 hours ago. First the site was totally down. Then it was half-working, with several 503s.
I didn't notice anything at http://status.soylentnews.org/ [soylentnews.org] - I wonder if it's worth having a "most recent website problem" entry on that page permanently, so that we can check you were aware of any apparently temporary problems we've encountered. OTOH, maybe it's not a big deal at this stage in the site's development.
(Score: 3, Informative) by NCommander on Tuesday April 15 2014, @05:52PM
Linode switch went out, the site was inaccessible for approximately 30-45 minutes, and then I have to scrape Apache's remains and bring it back to life.
Still always moving