The server is currently in commercial use. I can't afford downgrading php. If I want to do it with yum I need to remove php first (also with downgrade) and plesk gets removed as well... So, how would you replicate the problem? How would you do a binary post to a server without setting the content type header? If there is a bug in php 5.3.9 how could we test this? There are some somewhat similar bugs in php. I think we can indeed conclude it is a php thing. So lets remove the discussion from this mailing list. I'll post my findings on php mailing list. tanx!
2012/1/29 Yehuda Katz <yeh...@ymkatz.net> > On Sun, Jan 29, 2012 at 9:46 AM, Yehuda Katz <yeh...@ymkatz.net> wrote: > >> On Sun, Jan 29, 2012 at 6:36 AM, Bardo Bakker <bardobak...@gmail.com>wrote: >> >>> Tanx for reply! >>> >>> In run on CentOS 5.7 (Latest). CentOS' policy is to have most stable >>> versions which is apache 2.2.3... And this is not stable behaviour. >>> >>> PHP Version => 5.3.9 >>> mysql Ver 14.14 Distrib 5.5.20, for Linux (x86_64) using readline 5.1 >>> >>> Acording to this version info only my httpd is a out of date but should >>> be stable. >>> >> >> Were you able to run php -i ? >> That will usually tell you why PHP is crashing. >> > > If php -i does not segfault, you should check that it is actually loading > all of your extensions. Compare he output of php -i with the expected > information from your php.ini . Sometimes the PHP CLI will not load MySQL > and mod_php will, so you will miss the errors that are caused by that > extension. > > It looks like you updated PHP and MySQL some time since January 10 (since > that is when 5.3.9 and 5.5.20 where released). > I would suggest that you downgrade to the previous versions (try the ones > that ship with CentOS, since as you mentioned, they are supposed to be > stable) and see if you still have the problem. Or, rebuild PHP, making sure > that it is using the correct MySQL libraries. > > As I mentioned, the segfault is in mod_php, not in the Apache core. > If you want you can send me (privately if you want) the PHP script you use > and your php.ini (and any included ini files) and I can see if I can > replicate the problem and file an official PHP bug if necessary. > > - Y >