Opened 9 years ago

Closed 9 years ago

Last modified 5 months ago

#710 closed defect (worksforme)

stable segfault on default Unbuntu 12.04 LTS binaries.

Reported by: Серж К Owned by:
Priority: major Milestone:
Component: nginx-core Version: 1.6.x
Keywords: Cc:
uname -a: Linux esca 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.6.2
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -Wl,-z,relro' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/ --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_spdy_module --with-http_sub_module --with-http_xslt_module --with-mail --with-mail_ssl_module --add-module=/build/buildd/nginx-1.6.2/debian/modules/nginx-auth-pam --add-module=/build/buildd/nginx-1.6.2/debian/modules/nginx-dav-ext-module --add-module=/build/buildd/nginx-1.6.2/debian/modules/nginx-echo --add-module=/build/buildd/nginx-1.6.2/debian/modules/nginx-upstream-fair --add-module=/build/buildd/nginx-1.6.2/debian/modules/ngx_http_substitutions_filter_module


C:\Users\Serj>curl --head -L
curl: (56) SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054

C:\Users\Serj>curl --head -L
curl: (56) SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054

2015/02/03 15:21:41 [alert] 25992#0: worker process 13511 exited on signal 11 (core dumped)
2015/02/03 15:22:00 [alert] 25992#0: worker process 13512 exited on signal 11 (core dumped)

Change History (4)

comment:1 by thresh, 9 years ago

Please try to reproduce without third-party modules, e.g. using official nginx packages from If the problem is there with Ubuntu-provided packages, it would make sense to report this bug to Ubuntu maintainers.

comment:2 by Maxim Dounin, 9 years ago

Resolution: worksforme
Status: newclosed

Feedback timeout.

comment:3 by lutzmex@…, 5 months ago

Check the Logs:

Look in the /var/log/nginx/error.log file for any specific error messages or clues about what might be causing the segfault. You may find more information there that can help diagnose the problem.
Check the System Logs:

Check the system logs in /var/log/syslog for any related messages or errors that might be relevant to the nginx segfault.
Update nginx:

Your version of nginx (1.6.2) is relatively old. Consider upgrading to a more recent version of nginx to see if the issue has been resolved in newer releases. You can check the official nginx website for the latest version and instructions on how to upgrade.
Disable Third-Party Modules:

You have several third-party modules enabled in your nginx configuration. Try disabling these modules one by one to see if the segfault still occurs. Sometimes, third-party modules can be the cause of stability issues.
Check Dependencies:

Ensure that all necessary dependencies for nginx are installed and up to date. Run sudo apt-get update followed by sudo apt-get upgrade to update your system packages.
Memory and Hardware:

Check the hardware health of your server. Memory issues or faulty hardware can sometimes lead to segfaults. Run memory tests and check for any hardware errors.

Review your nginx configuration files (e.g., /etc/nginx/nginx.conf) for any syntax errors or misconfigurations. Incorrect configuration settings can sometimes cause crashes.
Test on a Different System:

If possible, try running nginx on a different system or virtual machine to see if the issue persists. This can help determine if the problem is specific to your server or the nginx binary itself.

You can use tools like gdb (GNU Debugger) to attach to the nginx process when it crashes and get a backtrace to identify the source of the segfault. However, debugging can be complex and may require expertise in using such tools.
Consider an OS Upgrade:

Ubuntu 12.04 LTS has reached its end of life and is no longer receiving security updates. Consider upgrading your server to a more recent LTS version, such as Ubuntu 14.04 LTS or a newer release, to ensure a more secure and stable environment.

in reply to:  3 comment:4 by Maxim Dounin, 5 months ago

Replying to lutzmex@…:

Check the Logs:

If you are a real person, you might want to avoid posting meaningless generic recommendations on 9-years old closed tickets.

If you are a spammer, you might want to avoid spending your time here. Spam won't be tolerated and will be removed anyway, even if posted as comments on old closed tickets.

Note: See TracTickets for help on using tickets.