Just got an error loading this site from SMF saying that the server was busy, just started getting some old boys back and the server starts to fall over

 

LOL this happens literally all the time but usually in the wee hours when no one notices (I get notification emails), I've no idea what's causing it as the server is fast as hell usually (it's a 1&1 business package so I've got about 20 sites running off it). It is rather annoying though so I may contact 1&1 and see if they can sort it out.

It was only for about a minute (or I tried for about a minute anyway) so not a biggie, but thought I'd let you know

Quote from: XEntity on January 03, 2013, 12:56:08 PM
It was only for about a minute (or I tried for about a minute anyway) so not a biggie, but thought I'd let you know

As is the age old proverb, he who smelt it dealt it, I blame XEntity 

Just got this:

QuoteInternal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webadmin@kundenserver.de and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Had to refresh to load the site.

I've noticed slowdown on other sites today, so I think its a general 1&1 issue.

Quote500 Errors are commonly produced when there are errors in the .htaccess file or one of the package limitations has been exceeded.

The package limitations restrict the use of no more than:

- 8 seconds of 100% CPU usage
-10MB of memory
- 16 simultaneous processes


It is common to experience 500 errors intermittently when the package limitations have been exceeded which may correspond to swells in traffic during the day.

When there is an error with a .htaccess file, all pages of the website will display a 500 error indefinitely until the .htaccess file is corrected or removed. As little as a simple spelling mistake or syntax error will cause a 500 error. If the .htaccess file has been edited recently, replace the file with a backup. If no backup is available, try to undo the changes to the file if you can remember what has been altered. If those options are not feasible, you can try commenting lines one by one by placing a pound sign(#) at the beginning of the line to comment it out. Then try to access a page of the site. Continue to add the pound sign to more lines until the 500 error stops which should help you pinpoint which line needs to be corrected.

To have this resolve we suggest you to upgrade the package to 1&1 Business or Server accounts or you may optimized the script used.

Best response I've received from a webhost in some time. I'll look into the server config and consider upgrading my package yet again if it becomes an issue.

I don't think it can cope with the bandwidth - we seem to be getting more than two posters a day now j/k

I hope the returning posters Ice and Cool do stick around though.

it's since we got that S back

the extra s is sucking up all the bandwidth and cpu cycles :-(

I know its the news you've all been waiting for, it seems it is traffic spikes causing the drops on the webserver as it hits its performance limits, so it looks like I'll be upgrading it tonight/tomorrow night.

Quote from: knighty on January 08, 2013, 18:12:32 PM
it's since we got that S back

the extra s is sucking up all the bandwidth and cpu cycles :-(

I've got a couple of new logo's on standby..



The latter one has a low res S to use less bandwidth

Actually LOL'd when I saw the Loading...