Issue with nginx crashing 'segfault'

[Scott Larson]

     The mod_security module for nginx does require libapr-1.


*[image: userimage]Scott Larson[image: los angeles]
<https://www.google.com/maps/place/4216+Glencoe+Ave,+Marina+Del+Rey,+CA+90292/@33.9892151,-118.4421334,17z/data=!3m1!4b1!4m2!3m1!1s0x80c2ba88ffae914d:0x14e1d00084d4d09c>Lead
Systems Administrator[image: wdlogo] <https://www.wiredrive.com/> [image:
linkedin] <https://www.linkedin.com/company/wiredrive> [image: facebook]
<https://www.twitter.com/wiredrive> [image: twitter]
<https://www.facebook.com/wiredrive> [image: instagram]
<https://www.instagram.com/wiredrive>T 310 823 8238 x1106
<310%20823%208238%20x1106>  |  M 310 904 8818 <310%20904%208818>*

On Mon, Sep 21, 2015 at 11:42 AM, Frederik Nosi <frederik.nosi at postecom.it>
wrote:

> Hi,
>
> On 09/21/2015 08:32 PM, Ricardo Aravena wrote:
>
> Hi Folks,
>
> I was wondering of somebody could shed some light on this issue that we
> are experiencing.
>
> nginx[22490]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493690 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22584]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22582]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22707]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493690 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22583]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22806]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22741]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22862]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493690 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22866]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22770]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22518]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
> nginx[22896]: segfault at 10 ip 000000376e616a11 sp 00007ffed9493640 error
> 4 in libapr-1.so.0.3.9[376e600000+2b000]
>
> Basically, the nginx workers are crashing intermittently causing our
> application no server requests.  We are using nginx with mod_security and
> mod_passenger. Apparently, this may be related to mod_security but can
> somebody shed some light as to how to solve it ? Is there a fix in the
> nginx code base or mod_security code base ?
>
>
> This seems strage, as nginx does not use libapr. Being libapr an Apache
> library, maybe you're using an mod_security or mod_passenger built for
> apache instead of the nginx one?
>
>
>
> Thanks,
> Ricardo
>
>
> --
> * Follow us on Twitter <http://www.twitter.com/coupa>, LinkedIn
> <https://www.linkedin.com/company/coupa-software>, and Google+
> <https://plus.google.com/115401473825788879012> *
>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150921/1f69acf2/attachment.html>