6781#0: worker process xxxx exited on signal 11

Server NGINX
1

Hi,

I’m sorry my bad english

We are put in place a proxy web server. It’s functionnal with 8 vhosts
with
severals certificats SSL autosignated. It was functionnal. We bought a
true
certificat SSL multidomain to Geotrust and we installed this certificats
on
vhosts.
Since to install this certifcat, on Internet Explorer broswer, we
received
an error. In the log,

/var/log/nginx/error.log

2015/05/05 07:48:07 [alert] 18687#0: worker process 32496 exited on
signal
11
2015/05/05 07:48:55 [alert] 6781#0: worker process 6782 exited on signal
11
2015/05/05 07:49:24 [alert] 6781#0: worker process 6783 exited on signal
11

dmesg

[6186233.729153] nginx[6834]: segfault at 4 ip 08071076 sp bf8dc180
error 4
in nginx[8048000+b9000]
[6186236.938752] nginx[6845]: segfault at 4 ip 08071076 sp bf8dc180
error 4
in nginx[8048000+b9000]
[6186264.888254] nginx[6846]: segfault at 4 ip 08071076 sp bf8dc150
error 4
in nginx[8048000+b9000]

My confi

Server : Linux poivron 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686
GNU/Linux

nginx version: nginx/1.2.1

paquets installed
ii nginx 1.2.1-2.2+wheezy3
all
small, powerful, scalable web/proxy server
ii nginx-common 1.2.1-2.2+wheezy3
all
small, powerful, scalable web/proxy server - common files
ii nginx-full 1.2.1-2.2+wheezy3
i386
nginx web/proxy server (standard version)

I don’t know to resolve this issue. I don’t know if this issue is only
on
the browser Internet Explorer. I’m tested with chrome and Firefox.I’m
not
error with these broswers.

Can you please help to me for this issue ?

Thanks
Regards,

ikoulamathieu

Posted at Nginx Forum:

2

Hello!

On Tue, May 05, 2015 at 03:03:00AM -0400, ikoulamathieu wrote:

/var/log/nginx/error.log

2015/05/05 07:48:07 [alert] 18687#0: worker process 32496 exited on signal
11
2015/05/05 07:48:55 [alert] 6781#0: worker process 6782 exited on signal 11
2015/05/05 07:49:24 [alert] 6781#0: worker process 6783 exited on signal 11

This sounds similar to this ticket:

http://trac.nginx.org/nginx/ticket/235

If it indeed the case, try the workaround as suggested in the
first comment.

If it doesn’t help, please see this page for some basic debugging
hints:

–
Maxim D.
http://nginx.org/

3

Hi,

thanks to your respond.
In deed, I was found this article and this
https://andreastan.com/fixing-nginx-random-segfaults-safari-cant-access/.
In fact, i add a directive on all vhosts in the nginx configuration with

ssl_session_cache shared:SSL:600m;

I put this directive on five vhosts and it’s correct on all browser and
i
don’t the errors in the logs.

Thanks to your help.

Regards.

Mathieu

Posted at Nginx Forum: