Bug #32010
closedtypo3/mod.php leads to Segmentation Fault
100%
Description
Since installing TYPO3 4.6, I can't reach mod.php in my backend anymore, which makes my backend quite useless. Apache logs tell me that a Segmentation Fault occured. I don't know really where to report this, but I think this would be the right place. I hoped it would be maybe fixed in 4.6.1, but it's not. I have tried this on 2 different websites and it both gave the same result.
Maybe a bigger problem is, that it's not giving me any other hints to where the bug could be. Can you help me?
PHP 5.3.6, TYPO3 4.6.0/4.6.1
Apache's error log states:
[Wed Nov 23 00:30:53 2011] [notice] child pid 31897 exit signal Segmentation fault (11)
Updated by Markus Klein almost 13 years ago
I'm not aware of a possibility to segfault Apache with a php script, so this should be a server issue.
Are you using eAccelerator or similar? Does it help to clear its cache?
Updated by Bart Laarhoven almost 13 years ago
Ah, removing eaccelerator fixed it. Apparently the combination of eaccelerator and TYPO3 4.6 is now really not supported anymore. ;) Thanks for the quick reply!
Updated by Ingo Renner almost 13 years ago
- Status changed from New to Closed
- Priority changed from Should have to Won't have this time
- % Done changed from 0 to 100
resolved, not a bug.