Giter Site home page Giter Site logo

Comments (8)

0x7f avatar 0x7f commented on July 20, 2024

Same issue here (nginx 1.6.2 as well). Let me know if you need any additional information.

from nginx_upstream_check_module.

yaoweibin avatar yaoweibin commented on July 20, 2024

Could you show me any error information in the error.log?

from nginx_upstream_check_module.

64kramsystem avatar 64kramsystem commented on July 20, 2024

Hello! Nginx's error logs don't show any error on reload, both in the cases when the reload works as expected, and when it doesn't.

Note that the problem always happens at the second reload call (after the nginx startup).

from nginx_upstream_check_module.

NikolayMurha avatar NikolayMurha commented on July 20, 2024

Hello.
I have same issue.
After reload, master process disappeared, and workers still run.

2015/08/07 13:05:26 [emerg] 5956#0: bind() to 0.0.0.0:443 failed (98: Address already in use)
2015/08/07 13:05:26 [emerg] 5956#0: bind() to 127.0.0.1:8085 failed (98: Address already in use)
2015/08/07 13:05:26 [emerg] 5956#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2015/08/07 13:05:26 [emerg] 5956#0: bind() to 0.0.0.0:443 failed (98: Address already in use)
2015/08/07 13:05:26 [emerg] 5956#0: bind() to 127.0.0.1:8085 failed (98: Address already in use)
2015/08/07 13:05:26 [emerg] 5956#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2015/08/07 13:05:26 [emerg] 5956#0: bind() to 127.0.0.1:8085 failed (98: Address already in use)   

I have try nginx version 1.7.4 and 1.8.0.

nginx version: nginx/1.8.0
built by gcc 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) 
built with OpenSSL 1.0.1f 6 Jan 2014
TLS SNI support enabled
configure arguments: --prefix=/usr --conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/sbin/nginx --error-log-path=/var/log/nginx/error.log --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 --http-log-path=/var/log/nginx/access.log --lock-path=/var/lock/nginx.lock --with-debug --with-http_ssl_module --with-http_gzip_static_module --add-module=/var/chef/cache/upstream_check_module_v0.3.0 --add-module=/var/chef/cache/ajp_module_bf6cd93f2098b59260de8d494f0f4b1f11a84627 --add-module=/var/chef/cache/sticky_module_1e96371 --add-module=/var/chef/cache/nginx_upload_progress/3fb903dab595cf6656fa0fc5743a48daffbba2f6b5c554836be630800eaad4e2 --with-http_stub_status_module

Thanks.

from nginx_upstream_check_module.

NikolayMurha avatar NikolayMurha commented on July 20, 2024

For 1.7.4

nginx version: nginx/1.7.4
built by gcc 4.8.2 (Ubuntu 4.8.2-19ubuntu1) 
TLS SNI support enabled
configure arguments: --prefix=/var/lib/nginx --conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/sbin/nginx --error-log-path=/var/log/nginx/error.log --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-log-path=/var/log/nginx/access.log --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --lock-path=/var/lock/nginx.lock --with-http_ssl_module --with-http_gzip_static_module --add-module=/var/chef/cache/upstream_check_module_v0.3.0 --add-module=/var/chef/cache/ajp_module_v0.3.0 --add-module=/var/chef/cache/nginx_upload_progress/3fb903dab595cf6656fa0fc5743a48daffbba2f6b5c554836be630800eaad4e2 --add-module=/var/chef/cache/sticky_module_1e96371 --with-http_stub_status_module

from nginx_upstream_check_module.

NikolayMurha avatar NikolayMurha commented on July 20, 2024

In strace -p 28779 (some worker pid) I see many call like:

epoll_wait(42, {}, 512, 5) = 0
epoll_wait(42, {}, 512, 5) = 0
epoll_wait(42, {}, 512, 5) = 0
epoll_wait(42, {}, 512, 5) = 0
epoll_wait(42, {}, 512, 5) = 0
epoll_wait(42, {}, 512, 5) = 0
epoll_wait(42, {}, 512, 5) = 0
epoll_wait(42, {}, 512, 5) = 0

And this messages appear very very quickly. Normally they appear approximately once per second.

from nginx_upstream_check_module.

 avatar commented on July 20, 2024

On nginx 1.8.0, the problem doesn't happen anymore. It used to happen on previous version; the O/S is the same.

from nginx_upstream_check_module.

toddyhan avatar toddyhan commented on July 20, 2024

same issue on nginx1.8.0, with check module0.3.0, patch version is check_1.7.2+.patch.

Then download the newest master zip package, and change the patch version to check_1.7.5+.patch. reload works now .

from nginx_upstream_check_module.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.