HTTP Error 500 (Internal Server Error): An unexpected condit

[twoblink]

My "adventure" with s9y really has added about 20 years to my life..

So today, nothing works all of a sudden, and I get an HTTP Error 500.

?? ??

It's not a webserver problem, because it serves up other virtual hosts without problem and it was working fine yesterday, and so I have no idea what is going on.. I am running this under nginx after apache has been constantly attacked by php script viruses.. and it worked just fine.. Until today.

I see no errors under nginx logs, I see no errors under php logs, so any help is appreciated..

[twoblink]

I cannot find any reason why it's not serving up pages; I've turned on error logging on php as well as nginx, and neither says there's an error. php works, I did a phpinfo.php page and it comes up with php info. but s9y is not serving anything... it's super frustrating.. any help appreciated. I've checked every log I could think of, /var/log/nginx /var/log/php5-fpm, and I put the webserver into debug logging mode; and see no reason.. I'm about to pull my hair out...

[twoblink]

Super frustrated; said screw it, let's just reinstall it from scratch!

And apparently I can't even do that now..

Fatal error: Call to undefined function serendipity_getCharset() in /home/xxxxxxxx/include/lang.inc.php on line 14


??

[Timbalu]

Well, using a Nginx server is a story for itself.... but this might help you in all your trouble.
http://board.s9y.org/viewtopic.php?f=1& ... #p10428819

[garvinhicking]

Hi!

Do you remember if you changed anything since the last time s9y worked? You say "all of a sudden", but usually things only go berserks if something changed?

Which storage backend do you use, mysql? Did you check all involved tables, especially serendipity_config? Did you check your serendipity_config_local.inc.php file for proper syntax?

A new s9y installation usually preserves the old database and does NOT overwrite it, so that could be the reason you still get an error. If you want to start a-fresh, you could install into a different database, or first delete the current one.

Sadly I don't have that much experience where nginx stores the errors that come from a PHP CGI. You might want to forcible create a "error.php" file and make it have a fatal error like:

Code: Select all

<?php
function $x (;

then, execute that file in the browser and see in which file the error appears (maybe use a touch /tmp/lastfile ; find / -newer /tmp/lastfile on your server)

HTH,
Garvin