Bug #53287 [NEW]: PDO 5 Byte write to a broken pipe when forked

From: Operating system: CentOS 5.5 x86-64 PHP version: 5.3SVN-2010-11-10 (snap) Package: PDO related Bug Type: Bug Bug description:PDO 5 Byte write to a broken pipe when forked Description: ------------ When switching from PHP 5.1.6 to PHP 5.3.3 the following notice has begun to show up in our scripts. PDO::__construct(): send of 5 bytes failed with errno=32 Broken pipe We are running a daemon and the forked children throw this error on the PDO construct that is used to refresh the class. The error changes depending on whether a persistent connection is set or not. When persistent is on the above error is produced. Without persistent connection applied the error is thrown when the class is destructed. Example: $pdo = null; send of 5 bytes failed with errno=32 Broken pipe We have confirmed this to be apparent in PHP 5.3.3 and the trunk build. I was unable to test on 5.2, but I was able to confirm this bug does not occur on 5.1.6 I have tried wrapping ob functions around the calls in case the broken pipe happened to be stdout but I think it is the mysql socket that is in question. On that same note, switching mysql to connect via tcp did not help. From searching I found a site that threw this error but no discussions of it. Let me know any additional information that is needed. Test script: --------------- // without persistance public static function shutdown(){ $base = Base::getBase(); $base->db = null; self::$base = false; } // with persistance $this->pdo = new PDO( $dsn, $user, $pass, array( PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION, PDO::ATTR_PERSISTENT=> true ) ); Expected result: ---------------- The PDO class should startup quietly when persistent connections are enabled and destruct quietly when persistent connections are disabled. Actual result: -------------- PDO::__construct(): send of 5 bytes failed with errno=32 Broken pipe with persistent connections. Base::shutdown(): send of 5 bytes failed with errno=32 Broken pipe without persistent connections. I believe this problem is only related to forked processes. I have confirmed the standard page serving to not throw this. -- Edit bug report at http://bugs.php.net/bug.php?id=53287&edit=1 -- Try a snapshot (PHP 5.2): http://bugs.php.net/fix.php?id=53287&r=trysnapshot52 Try a snapshot (PHP 5.3): http://bugs.php.net/fix.php?id=53287&r=trysnapshot53 Try a snapshot (trunk): http://bugs.php.net/fix.php?id=53287&r=trysnapshottrunk Fixed in SVN: http://bugs.php.net/fix.php?id=53287&r=fixed Fixed in SVN and need be documented: http://bugs.php.net/fix.php?id=53287&r=needdocs Fixed in release: http://bugs.php.net/fix.php?id=53287&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=53287&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=53287&r=needscript Try newer version: http://bugs.php.net/fix.php?id=53287&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=53287&r=support Expected behavior: http://bugs.php.net/fix.php?id=53287&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=53287&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=53287&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=53287&r=globals PHP 4 support discontinued: http://bugs.php.net/fix.php?id=53287&r=php4 Daylight Savings: http://bugs.php.net/fix.php?id=53287&r=dst IIS Stability: http://bugs.php.net/fix.php?id=53287&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=53287&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=53287&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=53287&r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=53287&r=mysqlcfg