My server suddenly stopped all CGI processing and all returning a 500 Internal server error message.

After 3 trouble tickets with Rackshack support, they managed to fix some of it in which I think the server is misinterpreting some of the files permission. However, majority of the scripts at the moment are not working properly.

Rackshack support insists its my programming error, but how can some scripts running fantastically for the past 3 months suddenly stopped working due to programming error??? I can't understand.

Anyhow, I've emailed the situation to Patrick (whom everyone of you here think he's a great guy in support) and see what would be his solution.

However, anyone with similar problem before could tell me what's wrong with the server and how did you all fix it?

I've tried reinstalling the scripts - it doesn't work
I've CHMODded all scripts to their respective modes - it doesn't work too.
Even html files which are chmodded to 777 gives me a permission denied notice.

I'm out of my wits now, that's why I'm begging the ppl of WHT to enlighten me with advice about this.

Some examples would be http://www.anime-genesis.com/cgi-bin/ikonboard/ikonboard.cgi

I would appreciate any help anyone could give........

You'll find problem in apache logs.
1) Connect to your server via SSH
2) Look at httpd.conf and find there domain name where you just tried to run script. Search there for ErrorLog
3) Copy path to error log like it says in httpd.conf for that domain and type tail -f <path_to_error_log_you_just_copied> then run script from browser and you'll see in your terminal where is problem.:D

Definitely follow the above advice re tail -ing your httpd-error.log.

Re your comment - even HTML files cause error 500 - if they are pure HTML files causing error 500 then something in httpd.conf or a .htaccess file is causing them to be interpreted, probably, as a script - and the configuration is incorrect.

The other simple issue that crops up from time to time is uploading script files in binary mode. PHP, for example, tolerates this, but CGI will generally error out. I discovered a bug in my development editor (PrimalScript) one day after taking on a Python CGI project and knocking my head against the wall for an entire day. Turns out PrimalScript FTP'd in binary mode for everything, and as I was using PHP extensively, I never noted the problem.

Error 500 - your first step should always be to check your error logs. Invariably the issue will be highlighted plain as day there...

Is it a box running plesk?

I had the same problem with a box running plesk, it was running perfectly and the started to send "premature script header error" messages.

I upgraded Perl, I removed mod_perl and trying to work with perl as CGI, but nothing helped.

Maybe this link can help you out if you have the same problem

http://httpd.apache.org/docs/misc/FAQ.html#premature-script-headers

I tried all the options there, but didn't help me

Frankly, I am surprise to know that Rackshack even paid attention to you. They offer unmanaged server, and I rarely heard that they will do anything besides hardware and network. They must be doing you a huge favor to even look into this.

As Robert said, the thread title is greatly inappropriate.

Peter

I didn't find the thread title to be so far off, but I've edited it to better reflect the problem.

Originally posted by Chicken
I didn't find the thread title to be so far off, but I've edited it to better reflect the problem.
What was the original title? "RS server - all CGI processing stopped and returning 500 Internal server error message" makes about as much sense as "Ford car - a police officer pulled me over and gave me a speeding ticket".

Servers, rackshack or otherwise, do not break by themselves. Either the original poster screwed something up (hint 1: set permissions correctly. 777 is NOT correct; hint 2: make sure files are owned by the right user; hint 3: error logs exist for a reason), or someone else screwed something up (I count about 30 deadrat advisories in the past three months -- is this server up to date?).

It is very easy to blame PEBKAC on "a broken computer", but that is almost never the case (especially after three months).

Sorry to those whom I've offended by posting here. I did not want to but I'm trying to look at long term solutions here.

Yes, RS did answer my query and finally after great direction from Patrick (to the correct support guy), I'd have everything fixed.

The problem with such first thing first is that suexec does not allow chmodded 777 files in cgi-bin. Cause this will allow world write ability and sooner of later will increase the suexec log size to a BIG 2gb (my server) which causes the whole server to crash. (thanks to Greg of RS for telling me this).

The only way to prevent this from happening in the future is to periodically delete the suexec files or not allowing 777 files in cgi-bin. But I'm running a forum which some files like forum threads needs to be 777 to be able to function properly. So I guess my answer is the former.

I've emailed Greg of RS asking about possible ways I can do to prevent it from happening again and still waiting for some advice. Anyone having advice here??

I'm only pissed as the blame was put on the user. Everything was running perfectly without a single downtime for like 3 months, and suddenly all scripts stopped working. I do not believe its the user fault nor RS fault, but I would just like to ask for advice and solutions possible. I wished sometimes, they just don't put the blame on us even though we users to screwed up sometimes.

But for this matter, I would like to personally thanks Greg Sizemore and Patrick (referring me to Greg) both of Rackshack for helping me out.

To those skeptical of Rackshack, well, support is there but just ain't really good enough unless you get the correct person to talk to. 3 days downtime isn't too much comparing to the price we as customers are paying. Guess what, the fastest time my trouble ticket (3 for this case) was answered was less than 3 hours!!

Anyone with some other better long term solutions, do let me know...

Hey Ex,

I got a plesk box from RS about three weeks ago, and I'm having the same problem you had (premature end of script), except perl hasn't worked since the beginning.

Would you mind posting how it was fixed so I (and others) can do the same?

Thanks a bunch!

@ xMattHawkx

If it wasn't working from when the box was delivered to you, it would class as a problem for rackshack to correct as the box should be delivered in fully working order.