Opened 6 years ago

Closed 6 years ago

#505 closed defect (worksforme)

Nginx worker randomly segfault during the day

Reported by: Arnaud B. Owned by:
Priority: minor Milestone: 1.4.5
Component: nginx-core Version: 1.4.x
Keywords: segfault Cc: arnaud@…
uname -a: Linux meuh 3.10.23-xxxx-std-ipv6-64 #1 SMP Mon Dec 9 18:53:52 CET 2013 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.4.5
built by gcc 4.7.2 (Debian 4.7.2-5)
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock --http-client-body-temp-path=/var/cache/nginx/client_temp --http-proxy-temp-path=/var/cache/nginx/proxy_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx --group=nginx --with-http_ssl_module --with-http_realip_module --with-http_addition_module --with-http_sub_module --with-http_dav_module --with-http_flv_module --with-http_mp4_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_random_index_module --with-http_secure_link_module --with-http_stub_status_module --with-mail --with-mail_ssl_module --with-file-aio --with-http_spdy_module --with-cc-opt='-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-z,relro -Wl,--as-needed' --with-ipv6

Description

I saw this occuring since the last update :

nginx[605]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[606]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[6183]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[4768]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[4769]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[4771]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[4770]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9239]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9240]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9241]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9242]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9243]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9244]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9245]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9246]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9247]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9248]: segfault at 8 ip 00000000004270fd sp 00007fff97af5dc0 error 4 in nginx[400000+b0000]
nginx[9249]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9251]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9250]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9336]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[9334]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[10010]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]
nginx[19633]: segfault at 8 ip 00000000004270fd sp 00007fff97af5e30 error 4 in nginx[400000+b0000]

Change History (3)

comment:1 by Maxim Dounin, 6 years ago

Please see instructions at http://wiki.nginx.org/Debugging on how to obtain a backtrace.

If you use WebSocket proxying, ticket #503 may be relevant (segfault may occur if a backend closes a connection right after returning a "101 Switching Protocols" response).

comment:2 by Arnaud B., 6 years ago

Ok, I'll obtain a backtrace soon. I'm not using a websocket actually, I managed to reproduce the cause of segfaulting, it seems that my ownCloud mobile client makes a few queries that are not handled well by nginx.
I'll keep you posted.

comment:3 by Maxim Dounin, 6 years ago

Resolution: worksforme
Status: newclosed

Feedback timeout.

Note: See TracTickets for help on using tickets.