Page 1 of 1

Error 500 After MySQL Upgrade

PostPosted: Mon Jan 28, 2008 12:13 pm
by Smoniz
Hello All

My web host upgraded their MySQL & Apache to the latest version last night, I noticed while they were in the middle of it I was getting an error 500 when accessing coranto, I deleted my .htaccess file and re did it. Then everything worked fine, but this morning I am back to getting an Error 500. Before the MySQL & Apache upgrade everything was working just fine. Does anyone have any ideas?

PostPosted: Tue Jan 29, 2008 4:33 am
by Jackanape
Try double-checking your CHMOD values on your files, there's a possiblity the upgrade affected that, I suppose. Barring that, could there be something else they did during the upgrade--it might be worth contacting them as well.

PostPosted: Tue Jan 29, 2008 8:14 pm
by Smoniz
Yeah I ended up contacting my host, they said that the likely culprit was that some scripts are not compatible with the newer versions of Apache & PHP. So I switched hosts last night and all is well now. Thanks!

PostPosted: Wed Mar 26, 2008 11:46 am
by Smoniz
haha this is funny my new host just upgraded to the same software argh. I was able to get everything working though with the exception of my news feeds. I use the Feed Builder beta 0.06a by Dale Ray.

When I access the feed i get an Error 500.

Any clue lol?

PostPosted: Wed Mar 26, 2008 1:14 pm
by SrNupsen
You can create perfectly valid feeds from using a specially crafted style, and so the Feed Builder is somewhat deprecated, I think.

More info int this thread.

PostPosted: Wed Mar 26, 2008 2:06 pm
by Smoniz
Thanks for the reply, I just downloaded another feed builder add on still doesn't work. I just checked my server error logs, and it says that I have insufficient execute privleges for the XML file. so far i've tried chmod settings 644 & 777 & 755 with no luck lol. This is odd.

I've also found that this XML feed issue isn't even narrowed to just coranto its happening on feeds on other sections of my site as well. That is just weird. Now just waiting on my hosts support team to get back with me.