[SOLVED] 500 error on Bluehost

[Mister Denial]

Hi there,

I have a really bad case of internal server error which was caused by my very own incompetence. I was trying to speed up my Bluehost Pro account by following instructions on Fast CGI and zlib from the Bluehost forum, and discovered that both PS 1.4.0.9 test websites I am tinkering with are no longer working, neither BO or FO.

I have tried reverting the setting, but no prevail, I can no longer get it to work - and it did work perfectly fine until stupid me tinkered with the settings.

Does anyone have an idea on what to modify or how to get out of this mess?

New installations of PS do work, but trying to use the upgrade option does not work. The installer does show that version 1.4.0.9 is found, but I can not check the update radio button.

Can anyone get this poor sod out of this mess?

Thanks in advance!

Dan

[tomerg3]

Check your error log from the cpanle to try and get the specific error (error 500 is a general error)

[Mister Denial]

Hi tomerg,

thank you for your fast help. Here's the last line in the error log:

[Wed Jan 26 15:44:32 2011] [warn] RewriteCond: NoCase option for non-regex pattern '-f' is not supported and will be ignored.

I tried upgrading to 0.10 and got this installer error: Ajax error: parsererror

Hope this helps finding the error. I must admit I am a bit desperate at the moment.

[tomerg3]

I'm not sure that's the right one, try to reproduce the error and check the log again (comparing times)

[Mister Denial]

Ok, according to the timestamp, this should be the right one:

[26-Jan-2011 15:55:49] PHP Fatal error: Class 'Memcached' not found in /home1/xxx/public_html/PS_shop/classes/Cache.php on line 40

and

PHP Warning: PHP Startup: Unable to load dynamic library './magickwand.so' - ./magickwand.so: cannot open shared object file: No such file or directory in Unknown on line 0

Both match from a time point of view.

[tomerg3]

1.4.0.10 was just released, try using that instead.

I believe they fixed a Memcache bug

[Mister Denial]

I tried installing RC1 by using the upgrade option, and I get this error message: Ajax error: parsererror

If I have to do a clean, new install, is there any way I can transfer the changes made to the catalog? I already have put quite some work in building the catalog and would really hate losing that. Maybe exporting a specific set of tables from the SQL database?

[tomerg3]

You should be able to export the tables, try everything with product, category, attribute, feature and then the /img folder as well

[Mister Denial]

Thanks a lot for the help. One last question, if I export 1.4.0.9 SQL tables and import them back into a 0.10 PS shop, do i risk to compromise the integrity of my installation? I m' more a merchant than a DB expert, so I just want to be sure to make no mistake.

[tomerg3]

I have not compared the tables, but I don't think there were any changes to the sql structure.

[Mister Denial]

Perfect, it did work! Thanks so much for your help!

[Mister Denial]

UPDATE: I think I just found out what caused the initial error - Bluehost switched memcached off again on the server where I am hosted! DOH!!!

[inveostore.com]

1.4.0.9 and 1.4.0.10 database structure is different. However, If I understood correctly, tomerg3 advised you to use higher version than you currently use, so you can perform standard PS upgrade process.

[Mister Denial]

Hi! Unfortunately no, I can't use the regular upgrade, it causes an Ajax error: parsererror.

But manually exporting / importing the tables mentioned by tomerg did work.

[inveostore.com]

Then take a look to /install/sql/upgrade/1.4.0.10.sql file, change PREFIX to your table prefix a then copy & paste and run each SQL query via e.g. phpMyAdmin.

[Mister Denial]

INFO ABOUT MEMCACHE: Memcached PECL is not installed by default on Bluehost servers. It was installed by request on my account extension, and when I changed the PHP processing to FastCGI, the info line extension_dir = "/home1/myaccount/php/extensions" was changed to extension_dir = "/usr/lib64/php/modules"

That's what caused the internal server error, because memcache was suddenly disabled.

Just thought this info might be useful if someone runs into the same error.