Hello Sean! >> Well, the only thing the server shows are these two lines: >> [Fri Dec 08 14:17:08 2006] [error] [client 84.162.86.223] (104)Connection >> reset by peer: FastCGI: comm with server >> "/var/www/php-fcgi-scripts/www.domain.tld/php-fcgi-starter" aborted: read >> failed, referer: >> http://www.domain.tld/typo3/alt_mod_frameset.php?fW=0&nav=/typo3/alt_db_navframe.php%3F&script=sysext%2Fcms%2Flayout%2Fdb_layout.php&id= >> [Fri Dec 08 14:17:08 2006] [error] [client 84.162.86.223] FastCGI: >> incomplete headers (0 bytes) received from server >> "/var/www/php-fcgi-scripts/www.domain.tld/php-fcgi-starter", referer: >> http://www.domain.tld/typo3/alt_mod_frameset.php?fW=0&nav=/typo3/alt_db_navframe.php%3F&script=sysext%2Fcms%2Flayout%2Fdb_layout.php&id= > which are actually indicative of a problem. my guess is that the > underlying cgi script is segfaulting or otherwise prematurely aborting. > it looks like typo3 is actually available in sid so i'm going to try > playing around with it a little tonight. however if you can get any more > information from rupert or otherwise i'd appreciate hearing it. esp if > you can narrow the problem down to a particular php function.
As I'm not a PHP programmer I refer to what Rupert told me. He told me that this is not a problem with my a bit special configuration (FastCGI instead of mod_php). The only problem about FastCGI is that all errors look a bit like the errors shown above. You cannot tell what the problem is, also you cannot find anything with Google. At least it's a problem for me. I contacted Rupert again and I hope that he can help out with some more specific information about this issue. Regards, Martin
