Fix PHP bug on srv107.typo3.org
I've already mentioned this twice, but up till now a proper error report was missing.
There is a bug in PHP 5.3.3 that is not fixed in the Debian Squeeze Repositories. I asume this is that one: https://bugs.php.net/bug.php?id=50027
That bug is a real issue on typo3.org and caused the few minutes unavailability during the launch of TYPO3 6.2 and a few minutes back. It is totally unclear how it is triggered, but you can reliably do that on the vagrant box by editing any Scheduler Task in the backend (I changed some configuration on production to avoid triggering this bug - see below).
The problem with this bug is that it poisons the whole apache process and thus also affects frontend requests that then also return a 500 until the apache process is killed (this seems to happen automatically after a few minutes)
A quick way to fix this would be to use the dotdeb packages . I'm not sure what you think about using them in production!? But we also used them on the Vagrant Boxes and they fixed the issues and did not have any obvious issues.
These are the lines I added to circumvent this issue on production. Note that this is not a fix, but only a way to not trigger the bug:
$TYPO3_CONF_VARS['SYS']['caching']['cacheConfigurations']['cache_extbase_reflection'] = array( 'frontend' => 't3lib_cache_frontend_VariableFrontend', 'backend' => 't3lib_cache_backend_NullBackend', ); $TYPO3_CONF_VARS['SYS']['caching']['cacheConfigurations']['cache_extbase_object'] = array( 'frontend' => 't3lib_cache_frontend_VariableFrontend', 'backend' => 't3lib_cache_backend_NullBackend', );
#2 Updated by Christian Zenker about 6 years ago
Fabien Udriot wrote:
but what about upgrading the server to Wheezy which would have the benefit to have a more up to date PHP version?
I would like that, but as we plan to migrate to 6.2 in the next year, we would need to migrate some stuff then anyways. So I think it is better suited then.
It depends how urgently is the fix required
Well, everyone editing scheduler jobs on production triggers this. If it is not a problem for you I would like to get a fixed PHP Version as soon as possible.