Internal Server Error 500 after php5.3.4 installed by hostingcompany

[Reneetje]

Hi,

my provider installed php5.3.4 last week (I had an already working patched and working 1.3.8 cart on their server) and suddenly every few hours the error (500 Internal Server Error, Error Number: 258 (0x80070102)) is displayed and the site is down for minutes or even much longer.

I have mydebug run for days at both admin and includes but nothing could be found there.....

The hostingcompany VEVIDA in the Netherlands could not fix it immediately so I started upgrading to 1.3.9h which I did and uploaded to the same server last wednesday. However also the same problems remain. It looks like it has more error´s when a lot of people try to visit the website.....they changed something into their PHP on thursday but that didn´t seem to help.

Does anyone have the same problems and/or maybe have an idea how to fix or what the problem could be ?

If you want to take a look (type in your own browser), w w w . d y n a m i t e m a g i c . n l . The spaces are because of the searchengines...

Hope somebody can help.....I need my shop, it is my living...

Also, can it be something which is caused by zen-cart or is it a problem with my provider....

René

[kuroi]

A 500 Internal Server error is a very non-specific response that can be caused by many different things.

At the bottom of this page you'll find links to some examples. Your server log files may also have useful information (ask your hosting company how to access them).

From what you've described it's simply not possible to tell whether this is a problem with files contained within your Zen Cart, or the way in which the server hosting your account has been configured elsewhere.

[Reneetje]

The strange thing is that it the problems started after the installation of php5.3.4 (under 5.3 the site worked great before).

Even when I upgrated to 1.3.9h will al new language packs the same problem excists.....sometimes it takes 90 seconds for the message to show up, other times when I typ the url in my browser I get the message instantly which means the site is not even possible to work.

As I make my living with this webshop I can´t have it NOT available....

Thanks for helping!

[kuroi]

Depending upon how your host upgraded to PHP 5.3.4, they could have made other changes to their server settings as well.

That this doesn't sound to have been triggered by any changes you made, means that changes to the server configuration are the first place to look, and the error logs may give some clues as to what's tripping the errors.

For example (and it's only one possible example), if they've changed the security settings to tighten what permissions are allowed on files (e.g. from 777 to 755), files that worked fine previously may now trip these errors. But this is really something to work through with them.

[Reneetje]

They also tell php5.3 had a bug which did not show 500 internal server errors, with the upgrade to 5.3.4. these show up again.

They however put a an .ini file in my root to prevent errors showing, however that doesn´t seem to help.

I also tried mebug on admin and includes but no logs were made so to me that means there are no problems with these...

Maybe they put a wrong code into my .ini-file. Is there a way you would or could do that ?

[kuroi]

I would run fast and far from this host.

I don't claim to be an expert in this area and so am happy to be proven wrong, but if you're reporting accurately what they're telling you, it sounds like complete nonsense.

Firstly, in so far as there is such a thing as PHP 5.3, it includes version 5.3.4.

I suspect that what they are describing here is the warning messages that started being output in with PHP 5.3.0 to warn people when they were using features that were going to be withdrawn in future versions. And it is possible to suppress them by adding an instruction to your php.ini file.

However, if that is what they're talking about, it's evidence that they don't know what they're doing, since that's not a bug. The warnings are completely intentional. And anyway, I don't see how this could contribute to the 500 Internal Server Errors that you're reporting.

Maybe somebody else will see a connection, but it sounds to me as though they're trying to apply a solution that worked for them to solve a different problem, without actually knowing what the real problem is here. And just spraying around solutions without a proper diagnosis of the problem can be very dangerous.