From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3) Gecko/20040924 Description of problem: From IT#49222 I have reproduced this. I looked at the php.ini from the failing system last night, and saw nothing obvious. Then I actually added the settings from the Production server one at a time in my test environment and narrowed it to the following (seemingly innocuous) line: extension=imap.so This line is missing from the /etc/php.ini files on the Production environment. This line is created in the /etc/php.ini file by the php-imap package, which contains the following post installation script: # rpm -q --scripts php-imap postinstall scriptlet (through /bin/sh): /usr/bin/perl -pi -e "s|^;extension=imap.so|extension=imap.so|" /etc/php .ini /usr/bin/perl -pi -e "s|^;extension=php_imap.dll|extension=imap.so|" /et c/php.ini preuninstall scriptlet (through /bin/sh): if [ $1 = 0 -a -f /etc/php.ini ] ; then /usr/bin/perl -pi -e "s|^extension=imap.so|;extension=imap.so|" /etc/p hp.ini fi Don tested on the inactive production server after running the follwoing command: up2date php-imap and the issue was resolved.. ------------------------ Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Use php curl 2. 3. Actual Results: Fails with error message: "SSL: couldn't create a context!" Expected Results: No failure Additional info: See details in IT#49222
Did you manage to establish that this was not a genuine (if transient) out-of-memory error?
I did not do any work in establishing whether or not it is a genuine out-of-memory error case. J
The bug is in the way PHP initializes the curl library: it doesn't request OpenSSL library initialization. When the imap extension is also loaded, the imap extension itself initializes OpenSSL, so the problem doesn't manifest in that case. It's a simple fix, will integrate for a future update.
Joe, did this make U6?
No, per the blocker list, it's scheduled for U7.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-031.html