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.
Any suggestions or ideas on what to try would be much appreciated.
We are running:
Debian 6.0.7
Apache 2.2.16
OpenSSL/1.0.1e
PHP 5.4.13-1
cURL 7.21.0
The errors from the Apache2 error log:
[Tue May 14 16:21:05 2013] [notice] mod_cosign: version 3.2.0 initialized.
[Tue May 14 16:21:05 2013] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16
OpenSSL/1.0.1e configured -- resuming normal operations
[Tue May 14 16:21:25 2013] [notice] child pid 2195 exit signal Segmentation
fault (11)
[Tue May 14 16:21:26 2013] [notice] child pid 2194 exit signal Segmentation
fault (11)
[Tue May 14 16:21:26 2013] [notice] child pid 2208 exit signal Segmentation
fault (11)
------------------------------------------------------------------------------
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
