On May 14, 2013 20:07 , Matt Stapleton <matt1...@gmail.com> wrote: > Has anyone experienced issues using curl with the Cosign 3.2.0 Apache > module enabled? > > After upgrading to Cosign 3.2.0, we started receiving a segmentation > fault in Apache2 whenever the Cosign module was enabled. > Specifically, the fault only seems to occur when we call curl_exec() > from our PHP script, and it returns a 'No data received' Error 324 > (net::ERR_EMPTY_RESPONSE) in Chrome. When the mod_cosign.so is > disabled, curl_exec() works fine. >
I have not experienced this, but it may be an OpenSSL version conflict. Use ldd to make sure that httpd, mod_cosign, mod_php (actually, libphp5.so), PHP's curl.so module, and cURL itself are all linking against the same version of the OpenSSL library. If this doesn't turn up anything, my next suggestion would be to make sure that you have debugging symbols for all of the packages you have installed (Red Hat, for example, includes these in separate "debuginfo" RPMs), recompiling mod_cosign if necessary in order to include debugging symbols, and then enable core dumps. Once you get a core dump, use a debugger to get a stack trace and post that here. I hope this helps. -- Mark Montague m...@catseye.org ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
