yxs0201

Results 7 comments of yxs0201

用源码编译jdk 1,7 ,1.8都可以?

## nginx.conf ``` bash worker_processes 1; error_log /usr/local/nginx/logs/error.log debug; events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; sendfile on; keepalive_timeout 65; server { listen 80; server_name localhost;...

> What's output of > `curl consul.nginx.xxx.com/v1/kv/upstreams/test/10.1.1.1:51668?raw` ``` bash # 带参数raw执行,无值返回 curl consul.nginx.xxx.com/v1/kv/upstreams/test/10.1.1.1:51668?raw # 无参数raw执行,正常返回 curl consul.nginx.xxx.com/v1/kv/upstreams/test/10.1.1.1:51668 [{"LockIndex":0,"Key":"upstreams/test/10.1.1.1:51668","Flags":0,"Value":null,"CreateIndex":40576,"ModifyIndex":40576}] ```

> 请确认nginx用户可以改写文件servers_test_tcp.conf ### 确认有权限,如下文日志信息所示,http能正常dump: ``` bash 2018/12/20 17:09:01 [notice] 25065#0: upsync_dump_server: dump conf file /usr/local/nginx/conf/servers/servers_test.conf succeeded, number of servers is 2 2018/12/20 17:09:01 [error] 25065#0: upsync_del_peer: upstream "testTcp" cannot delete...

#### Nginx版本从1.12.2升级到1.14.2,也一样的报错。

servers_test.conf dump成功,这个是http模块的,http模块正常。servers_test_tcp.conf是TCP模块的,tcp模块就报错:upsync_del_peer: upstream "testTcp" cannot delete all peers

确实有过变更,之前的编译信息只是tcp,后面为证明http是可用的,我加过http的编译及相关配置。并且尝试更换过Nginx版本,系统版本。通过更换环境的方式验证tcp是否可用(都报相同的错:upsync_del_peer)。建议不要纠结这个问题,是否有实际可指导的解决方案用于**定位tcp报错**的根本原因。