9 replies to this topic

[Bryn AKA Interhacker]

> Board Message

Sorry, an error occurred. If you are unsure on how to use a feature, or don't know why you got this error message, try looking through the help files for more information.
The error returned was:

Sorry, the server is too busy to handle your request, please try again in a moment


For a few minutes?

[Robert]

The clue is

'Sorry, the server is too busy to handle your request, please try again in a moment'

[Bryn AKA Interhacker]

The clue is

'Sorry, the server is too busy to handle your request, please try again in a moment'

Am after a direct reason not a bad attempt at sarcasm

[sarah.]

That was the reason.

[Bryn AKA Interhacker]

That was the reason.

By busy does it mean to many people?

[Eeyore]

I've come to the conclusion that because we're on a shared server with other sites using the same server (or whatever) if there is a lot of people visiting those sites, we can end up suffering.

It's the only conclusion that makes sense to me with my limited knowledge on such things, given that we get these server errors when there's practically nobody visiting codex.

Someone might know better though, at which point I'll return to my kitchen.

[Bryn AKA Interhacker]

I've come to the conclusion that because we're on a shared server with other sites using the same server (or whatever) if there is a lot of people visiting those sites, we can end up suffering.

It's the only conclusion that makes sense to me with my limited knowledge on such things, given that we get these server errors when there's practically nobody visiting codex.

Someone might know better though, at which point I'll return to my kitchen.

Hmm i did wonder why it went down even tho there was relitively no-one online...

[gsquared]

I've had that occur to me on a lot of sites, not just this one, i really think its just when too many people get on, like eeyore said.

[Gargar]

Anyone remember when we were getting those every 5 mins or so back in the day?

[Waser Lave]

Hmm i did wonder why it went down even tho there was relitively no-one online...

It can also happen when we (or other sites on the same server) are doing backups too since that uses a lot of CPU cycles.