Internal Server Errors... *sigh*

[riskynil]

Any suggestions? I just logged in to go to my website at http://www.atlasquest.com/ and got an Internal Server error. It had been working just fine the last time I looked at it, and my log file records activity up until 9:48pm tonight (about 40 minutes ago). Everything else seems to be working--ftp, webmail, ops, etc.

Any suggestions about what might have happened? I haven't changed a thing since since it stopped working. Help!

-- Ryan

[riskynil]

In the time it took me to make that post, it started working again. *shrug* Whatever. =)

So just ignore me....

-- Ryan

[SeattleOtaku]

"sakuracon.org" was failing on all *.php pages as well (splash page *.html was working), and we're hosted on "www13.powweb.com", so if yours was on the same server, you're not alone. Sent an email to 'support@powweb.com' and then was composing a note in here when I noticed it back up when doing another test. Ours is back up now too.

[mr. TCB]

Same here :confused:

I'm hosted on www10.powweb.com. Without having changed anything I'm getting the 500 errors. Non-php files are working with no problem though, just as ftp-access....

[msirie]

Are you getting 500 Internal Server Error too?

On which page? Did you report this to support?

I've been getting 500 Internal Server Error since yesterday.

[extras]

I saw that there WAS a problem on www10 for a few minutes.

Notice that /powweb/web/cgi-bin/error.cgi is also failing.

[Fri Sep 10 00:56:15 2004] [error] [client 64.68.82.xxx] Premature end of script headers: /www/x/xxx.com/htdocs/xxx.cgi
[Fri Sep 10 00:56:15 2004] [error] [client 64.68.82.xxx] Premature end of script headers: /powweb/web/cgi-bin/error.cgi
[Fri Sep 10 00:57:55 2004] [error] [client 202.214.127.xxx] Premature end of script headers: /www/x/xxx.com/htdocs/xxx.cgi
[Fri Sep 10 00:57:55 2004] [error] [client 202.214.127.xxx] Premature end of script headers: /powweb/web/cgi-bin/error.cgi

As I said, it lasted for only a few minutes, and everything (Other than the BUG of loggin) is
working fine on www10 as far as I know.

500 Error can be caused by multitude of reason.

You CANNOT say what is causing it until you check error_log,
maybe access_log, .htaccess if any, permission of script and directories,
and the script itself.

Thinking that the problem is caused by someone other than ourselves
without any verification won't help finding real cause.
It's much better and quicker to suspect our own mistakes
if we want to solve the problem, because usually that's the case

So, please don't swanp support before to verify
and you are sure that it's caused by serverside problem.
Otherwise we all may suffer slower support response
and possibly increase of the price in the future.

Let's use any resources carafully.

[msirie]

If you didn't make any changes to ANY of your files, where would you say that a site problem was coming from?

[extras]

We have seen one guy who had a script that started to fail
when data file grew larger than it could handle as a CGI process.

I guess, he thought exactly like you,
"I didn't change anything, So, it must be PowWeb."

But it turned out to be otherwise.
And there are many other possibilities.


While I'm not saying that it's always our fault,
we should at least do routine check process before to jump on the conclusion.

I understand that it can be more confortable to blame someone else and wait
than checking this and that by yourself.
But that kind of attitude will end up in the support cost...the cost we all will be paying in the end.