[X] My Assistant

Other parts of e-hentai can still be accessed through https://e-hentai.org/ though if you logoff.

Yep fjords are still working for me for some unknown reason (IMG:[invalid] style_emoticons/default/blink.gif) .

EDIT: Main site and galleries are working fine again (IMG:[invalid] style_emoticons/default/smile.gif) .

This post has been edited by DarkNemesis: Mar 13 2012, 13:37

well, at least the forums aren't going all wonky with "failed to lock on" errors... crap, now I need to reset my days successfully lurked calender (IMG:[invalid] style_emoticons/default/unsure.gif)... its like one of those days since last accident work calenders (IMG:[invalid] style_emoticons/default/lurk.gif)

No worries. g.e-hentai still works. (IMG:[invalid] style_emoticons/default/laugh.gif)

The crash also corrupted parts of the locking mechanism, which caused "Failed to acquire lock" errors. This should now be fixed.

[twitter.com] https://twitter.com/#!/ehentai/status/179530308696281090

Seems the 'Failed to acquire lock' problem is fixed. Check if you have further problems.

It would seem that everything is back to normal, including the karma. (IMG:[invalid] style_emoticons/default/smile.gif)

The Hentaiverse pages seem to be taking a longer-than-usual time to load and display. Is anyone else getting this, or is it just my browser and/or STAT?

Who knows, I'm back to getting the good ol' 503 guru meditation error again on the galleries and hv

le sigh >.>

Who knows, I'm back to getting the good ol' 503 guru meditation error again on the galleries and hv

le sigh >.>

What's more annoying is that this is going on for weeks now (IMG:[invalid] style_emoticons/default/dry.gif) . Seriously when will it be finally fixed (IMG:[invalid] style_emoticons/default/sad.gif) .

This post has been edited by DarkNemesis: Mar 13 2012, 17:52

Problem solved, thread can be locked now. (IMG:[invalid] style_emoticons/default/biggrin.gif)

Hopefully problem solved, thread can be locked now. (IMG:[invalid] style_emoticons/default/biggrin.gif)

This post has been edited by Kaosumx: Mar 13 2012, 18:06

Before the memory cache processes crashed, there hadn't been any 503 events for a week. But to answer your question, I finally got the price list for the new servers today, so as soon as I have a minute to decide on the specific build they'll be ordered.

And there you have it

Yup thanks for the quick response Tenboro (IMG:[invalid] style_emoticons/default/wink.gif) .

Error 503 again at the main site. ;p

Oh well at least the problem will be solved eventually. :)

Before the memory cache processes crashed, there hadn't been any 503 events for a week. But to answer your question, I finally got the price list for the new servers today, so as soon as I have a minute to decide on the specific build they'll be ordered.

Just curious, but is it a capacity issue, or did something hit the end of its life and died physically?

Just curious, but is it a capacity issue, or did something hit the end of its life and died physically?

From other posts on the forum and Tenboro's Twitter it seems it's a crash bug in new memory cache version.

Just curious, but is it a capacity issue, or did something hit the end of its life and died physically?

The causes of 503s can be varied, but this particular one is a capacity issue. Especially at peak hours (which we're at right now) there will be problems without a fully warmed up cache. Which takes about two days to reach, starting from zero.

(ignore this, mistaken post)

This post has been edited by whorethag: Mar 13 2012, 22:34

The causes of 503s can be varied, but this particular one is a capacity issue. Especially at peak hours (which we're at right now) there will be problems without a fully warmed up cache. Which takes about two days to reach, starting from zero.

What are the peak hours because if I were going by the 503's I've gotten lately it would point to between the hours of midnight and midnight in a time zone of your choosing.

There are three distinct peaks, but the peakiest is from around 12:00 to around 18:00 UTC, give or take.