Page 1 of 1

No output *at all* vom s9y anymore

Posted: Fri Oct 23, 2009 12:02 pm
by bleeb
Hi!

Today after I've edited (tried to use a symlink) a template file s9y totally stopped producing ANY output.

Even the administration pages are blank.

It does not produce any errors (server- and php-errorlog only show some warnings about timezone settings) either.

template_c is writable and smarty does produce files here - but appart from an HTML comment they don't contain any content.

I already tried a backup and upgrading to 1.4.1. To no avail.

Tried re-installing 1.4.1 - and the second the installation is over I'm back to blank screens.

Using php 5.3.0 on lighttpd on a rootserver - didn't touch anything on the server though.

*any* ideas?

edit: everything else on that server, including a different s9y installation(!), runs perfectly fine.

edit2: setting the working s9y installation to use the database of the defunct one produces no output, too. So there must be something blown up in the tables. No errors though. any ideas?


edit3: reverting to PHP5.2.11 seems to have solved this issue.. probably a strange PHP 5.3.0 bug.
Thanks, sorry, close.

Re: No output *at all* vom s9y anymore

Posted: Fri Oct 23, 2009 2:10 pm
by hyejohn
Were you getting output? (If you "View source", was there anything there?)

Re: No output *at all* vom s9y anymore

Posted: Fri Oct 23, 2009 2:13 pm
by bleeb
nope, no output.

Some 500 Internal Server Errors though...

which might proof it's not s9y's fault anyway.

Re: No output *at all* vom s9y anymore

Posted: Fri Oct 23, 2009 2:29 pm
by kleinerChemiker
maybe missconfiguration in .htaccess?

Re: No output *at all* vom s9y anymore

Posted: Fri Oct 23, 2009 2:57 pm
by garvinhicking
Hi!

Note that for PHP5.3 you should use serendipity 1.5

Regards,
Garvin

Re: No output *at all* vom s9y anymore

Posted: Fri Oct 23, 2009 5:32 pm
by Don Chambers
Just ran into the same thing myself... did not revert php from 5.3.0, instead used the latest 1.5 beta 2.

Re: No output *at all* vom s9y anymore

Posted: Wed Oct 28, 2009 1:28 pm
by bleeb
Thanks, problem has now *really* been solved and was quite stupid:

php (up to and including 5.3.0!) dies silently if it's errorlog grows to the size of 2GB.

Since s9y (and smarty) log a GIANT HEAP of "deprecated" messages (which are tricky to get rid of) it made php's errorlog grow to this legacy 2GB limit before the log was rotated.

My own code didn't throw deprecated messages, so it seemed like only s9y wouldn't run.

Re: No output *at all* vom s9y anymore

Posted: Tue Nov 10, 2009 4:19 pm
by larsent
I'm getting the same output (none - but a 500 server error).

It's a fresh install of 1.5 beta. All I did was copy the files over, and make the 3 folders mentioned in the install docs, as well as the main install folder chmod 777. (I tried 775 as well).

It just displays a blank page.

I have no .htacess because there isn't one in the download file. Am I supposed to make one?

Also - am I supposed to modify the config file before running the index.php?

In the installation docs, all it says is to upload the files, check the permissions and run the index.php file which is what I did. Am I missing anything?

Re: No output *at all* vom s9y anymore

Posted: Tue Nov 10, 2009 5:40 pm
by garvinhicking
Hi Larsent!

A blank page usually means a PHP Fatal Error. Check your CGI oder PHP Error log output for specifics. Usually it's corrupted file, missing read privileges or an incompatible PHP Version.

Regards,
Garvin

Re: No output *at all* vom s9y anymore

Posted: Tue Nov 10, 2009 7:17 pm
by larsent
Sorry to sound like an idiot, but how do I check the php error logs?

Thx!

Re: No output *at all* vom s9y anymore

Posted: Tue Nov 10, 2009 10:53 pm
by garvinhicking
Hi!

You could ask your server provider; or try to create a .htaccess file (or edit the existing one) and inserT:

Code: Select all

php_value display_errors on
php_value error_log ./php-error.log
If that doesn'T help, you'll need to contact your server provider and ask him where the logs are stored and if you can have access to them. Also make sure you mention "PHP error logs" specifically, because they are not the same as Apache error logs.

HTH,
Garvin