Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version tengine-2.3.1 #1318

Closed
johnripperdec opened this issue Jul 18, 2019 · 4 comments
Closed

Version tengine-2.3.1 #1318

johnripperdec opened this issue Jul 18, 2019 · 4 comments

Comments

@johnripperdec
Copy link

Ⅰ. Issue Description

Upstream health checks are not supported in this release Version tengine-2.3.1

Ⅱ. Describe what happened

can not found config "check_status"

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. ./configure --prefix=/usr/local/nginx --user=www --group=www --with-http_ssl_module --with-http_stub_status_module --with-file-aio --with-http_dav_module --with-pcre=/opt/pcre-8.37 --with-stream --with-stream_ssl_module
  2. make
  3. make install
  4. /usr/local/nginx/sbin/nginx -t

my one of conf file like this:
cat vhost/zabbix.conf
upstream zabbix1 {
#server 10.10.24.19:8081 weight=3 max_fails=2 fail_timeout=5s;
server 10.10.24.19:8081 ;
check interval=3000 rise=2 fall=5 timeout=5000;

           }

server {
listen 80;
server_name zabbix.bol110.bo;
location = / {
rewrite ^(.*)$ $scheme://zabbix.bol110.bo/zabbix/$1 permanent;

proxy_pass http://zabbix1;

		}

location / {
proxy_pass http://zabbix1;
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_403 http_404;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_headers_hash_max_size 51200;
proxy_headers_hash_bucket_size 6400;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

         }

location /status {
check_status;
access_log off;

}

}

Ⅴ. Anything else we need to know?

  1. If applicable, add nginx debug log doc.

Ⅵ. Environment:

  • Tengine version (use sbin/nginx -V): Version tengine-2.3.1
  • OS (e.g. from /etc/os-release):centos6.8
  • Kernel (e.g. uname -a):Linux LA-JCJ-NGINX1-RED-10-10-22-4 2.6.32-358.el6.x86_64 fixed bugs of the limit_req module #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
  • Others:
@wangfakang
Copy link
Collaborator

@johnripperdec The check_status directive is provided by the ngx_http_upstream_check_module module, so it needs to be --add-module=modules/ngx_http_upstream_check_module at compile time.

@johnripperdec
Copy link
Author

@wangfakang Tengine brought her own health check,and I changed to version Tengine 2.2.3,it is worked.
image
and i do not change the configure.
image

And i create a test pc to test this problem, it is still have the same problem. so I think this problem is just have in version 2.3.1. And it is not include the nginx_upstream_check_module. i will still to test.

@wangfakang
Copy link
Collaborator

@johnripperdec After tengine-2.3.0 version put all Tengine's modules to the modules directory. Use --add-module=modules/<tengine_module_name> to compile. For more details, please refer to #1220 .

@johnripperdec
Copy link
Author

@wangfakang thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants