Joomla 1.0.13 and Apache2

[mwcannon]

I had three websites with HM that are using Joomla 1.0.13 which were working fine until they upgraded to Apache 2 on 1 Feb. Now I get :

[an error occurred while processing this directive][an error occurred while processing this directive]

Anyone have any suggestions as to what is causing this error? The log for one of the sites is below:

[Wed Feb 06 00:56:06 2008] [error] [client 66.249.70.182] Premature end of script headers: index.php
[Wed Feb 06 00:56:33 2008] [error] [client 208.36.144.10] Premature end of script headers: index.php
[Wed Feb 06 00:56:33 2008] [error] [client 208.36.144.10] invalid CGI ref "/500.php" in /home/organizi/public_html/indy/500.shtml
[Wed Feb 06 00:56:33 2008] [error] [client 213.203.254.150] Invalid URI in request GET blok.rozanek.cz HTTP/1.0
[Wed Feb 06 00:56:33 2008] [error] [client 213.203.254.150] File does not exist: /usr/local/apache/htdocs/400.shtml
[Wed Feb 06 00:56:38 2008] [error] [client 66.249.70.182] Premature end of script headers: index2.php [Wed Feb 06 00:57:21 2008] [error] [client 66.249.70.182] Premature end of script headers: index.php
[Wed Feb 06 00:57:47 2008] [error] [client 208.36.144.10] Premature end of script headers: index.php
[Wed Feb 06 00:57:47 2008] [error] [client 208.36.144.10] invalid CGI ref "/500.php" in /home/organizi/public_html/indy/500.shtml
[Wed Feb 06 00:57:48 2008] [error] [client 151.118.130.194] Premature end of script headers: index.php
[Wed Feb 06 00:57:48 2008] [error] [client 151.118.130.194] invalid CGI ref "/500.php" in /home/organizi/public_html/indy/500.shtml

I wish HM would put out a broadcast message about server upgrades when they happen. I took one of the sites I had and reinstalled Joomla from scratch and then restored the database using a backup and it's all farkled up now. I have spent a day of billable time thinking it was a user foul up when I would have contacted HM support first if I had known there had been a server upgrade. (Of course support's response was that it was a coding issue and they did not tell me they had upgraded server software until I argued with them about how unlikely it was that three sites I had not touched would suddenly go bad because of a coding error.)

[shadmego]

Can you give us a link to one of your sites with the error?

From the log you posted, it looks like the errors are from the entire server, not just your account.

I have several sites hosted with HM also that are running 1.0.13 and I haven't noticed any errors or other problems with any of the sites. If there is an error in any php files, then I would check the php error logs, not the main logs, which I think you posted above.

~regards

[mwcannon]

Much to my embarrassment, this was an issue I created for myself. A few months ago I was attempting to solve a problem by adding a Hostmonster developed php.ini file. Once I removed this file from the sites, they all began to behave. (I believe I had placed it in the sites to resolve the register_globals issue but don't remember exactly why it was there now....):confused:

Thanks for the help.