File '/usr/sbin/nginx' seems to be deleted

I am seeing a lot of these entries in my logs

Nov 6 04:29:13 sv1 kernel: nginx[62598]: segfault at 0 ip
0000000000438f38
sp 0 0007fffa5a934c0 error 4 in nginx (deleted)[400000+e2000]
Nov 6 04:29:13 sv1 abrt[22289]: File ‘/usr/sbin/nginx’ seems to be
deleted
Nov 6 04:29:13 sv1 abrt[22289]: Not saving repeating crash in
‘/usr/sbin/nginx’
Nov 6 04:29:17 sv1 abrtd: Package ‘nginx’ isn’t signed with proper key
Nov 6 04:29:17 sv1 abrtd: ‘post-create’ on
‘/var/spool/abrt/ccpp-2014-11-06-04: 29:08-56907’ exited with
1
Nov 6 04:29:17 sv1 abrtd: Deleting problem directory
‘/var/spool/abrt/ccpp-2014 -11-06-04:29:08-56907’

How can i fix this

nginx version: nginx/1.7.7
built by gcc 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC)
TLS SNI support enabled
configure arguments: --prefix=/usr/share/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
–http-client-body-temp-path=/var/lib/nginx/tmp/client_body
–http-proxy-temp-path=/var/lib/nginx/tmp/proxy
–http-fastcgi-temp-path=/var/lib/nginx/tmp/fastcgi
–http-uwsgi-temp-path=/var/lib/nginx/tmp/uwsgi
–http-scgi-temp-path=/var/lib/nginx/tmp/scgi
–pid-path=/var/run/nginx.pid
–lock-path=/var/lock/subsys/nginx --user=nginx --group=nginx
–with-file-aio --with-ipv6 --with-http_ssl_module
–with-http_spdy_module
–with-http_realip_module --with-http_addition_module
–with-http_xslt_module --with-http_image_filter_module
–with-http_geoip_module --with-http_sub_module --with-http_dav_module
–with-http_flv_module --with-http_mp4_module
–with-http_gzip_static_module
–with-http_random_index_module --with-http_secure_link_module
–with-http_degradation_module --with-http_stub_status_module
–with-http_perl_module --with-mail --with-mail_ssl_module --with-debug
–with-cc-opt=’-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic’
–with-ld-opt=-Wl,-E

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254626,254626#msg-254626

Hello!

On Thu, Nov 06, 2014 at 12:32:58AM -0500, khav wrote:

Nov 6 04:29:17 sv1 abrtd: Deleting problem directory
‘/var/spool/abrt/ccpp-2014 -11-06-04:29:08-56907’

How can i fix this

The message suggests the nginx binary on disk is not the one which
is running. You have to restart nginx or follow the binary
upgrade procedure, see http://nginx.org/en/docs/control.html#upgrade.


Maxim D.
http://nginx.org/

Hello!

On Fri, Nov 14, 2014 at 12:43:58AM -0500, khav wrote:

@Maxim D.

So a simple service nginx restart would do the job ?

This depends on your OS, but likely yes.


Maxim D.
http://nginx.org/

@Maxim D.

So a simple service nginx restart would do the job ?

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254626,254811#msg-254811

I did a nginx restart but the errors still here

Nov 15 11:22:06 sv1 abrtd: Package ‘nginx’ isn’t signed with proper key
Nov 15 11:22:06 sv1 abrtd: ‘post-create’ on
‘/var/spool/abrt/ccpp-2014-11-15-11:21:50-44431’ exited with 1
Nov 15 11:22:06 sv1 abrtd: Deleting problem directory
‘/var/spool/abrt/ccpp-2014-11-15-11:21:50-44431’
Nov 15 11:27:47 sv1 kernel: nginx[9263]: segfault at 0 ip
0000000000438f38
sp 00007fff961821b0 error 4 in nginx[400000+e2000]
Nov 15 11:27:54 sv1 abrtd: Directory ‘ccpp-2014-11-15-11:27:47-9263’
creation detected

Earlier i was using nginx install from epel repo and then i compiled
from
source

Thanks for helping me out maxim

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254626,254823#msg-254823

Hello!

On Sat, Nov 15, 2014 at 07:37:44AM -0500, khav wrote:

creation detected
These are different errors - there are no “… seems to be
deleted” errors as you may notice, so it should be able to obtain
proper stack traces now to find out why segfault happens.

Earlier i was using nginx install from epel repo and then i compiled from
source

You may want to follow generic hints outlined here:

http://wiki.nginx.org/Debugging

In this particular case I would recommend you to start looking
from “nginx -V” output (look 3rd party modules, try to test
without them if there are any) and a stack backtrace.


Maxim D.
http://nginx.org/