Hello! On Wed, Apr 15, 2015 at 09:31:21AM -0400, cobain86 wrote:
> hi > i'm not sure if this is an nginx or pagespeed or maybe linux problem > > we're using nginx on RedHat > Linux 2.6.32-504.8.1.el6.x86_64 #1 SMP Fri Dec 19 12:09:25 EST 2014 x86_64 > x86_64 x86_64 GNU/Linux > > nginx1.6.2 with pagespeed 1.9.32.3beta: > nginx version: nginx/1.6.2 > built by gcc 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) > TLS SNI support enabled > configure arguments: --sbin-path=/usr/sbin/nginx > --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid > --lock-path=/var/lock/subsys/nginx --error-log-path=/var/log/nginx/error.log > --http-log-path=/var/log/nginx/access.log --with-http_ssl_module > --with-http_stub_status_module --with-http_geoip_module > --http-client-body-temp-path=/var/cache/nginx/client_body_temp > --http-proxy-temp-path=/var/cache/nginx/proxy_temp > --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_tempmake > --add-module=/tmp/nginx-1.6.2/ngx_pagespeed-1.9.32.3-beta > > our problem is, since we have added the new pagespeed version, our reload > wont work properly. > we're using the following command to reload our nginx. > > "nginx -s reload" > > sometimes it happens that the master process is killed, but the worker > process of the old master process are still running. > So we are not able to start a new master process while the old workers are > still there. > We have no idea why this happens. > > the message log file shows the following error: > Apr 15 11:20:51 kernel: nginx[11423]: segfault at 7 ip 000000000047bbe3 sp > 00007fffdd7740f0 error 4 in nginx[400000+957000] > Apr 15 11:20:51 init: nginx main process (11423) killed by SEGV signal > Apr 15 11:20:51 init: nginx main process ended, respawning > Apr 15 11:20:55 init: nginx main process (6642) terminated with status 1 > Apr 15 11:20:55 init: nginx main process ended, respawning > > i have also make/installed pagespeed and nginx again, but no solution for > that. > > does anybody has that problem? or has an idea what i to do? >From your description it looks like a pagespeed problem. For additional details you may try obtaining a stack trace, see some hints here: http://wiki.nginx.org/Debugging -- Maxim Dounin http://nginx.org/ _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
