fatihbm commented on issue #6530:
URL: https://github.com/apache/apisix/issues/6530#issuecomment-1063791267


   I made your suggestion, now I can see the `host` value. But the only thing 
that changes seems to be the number of logs.
   
   ```
   root@ubuntu-bionic:/# curl http://192.168.44.53:9080 -H "Host: abc.cc" -v
   
   * Rebuilt URL to: http://192.168.44.53:9080/
   *   Trying 192.168.44.53...
   * TCP_NODELAY set
   * Connected to 192.168.44.53 (192.168.44.53) port 9080 (#0)
   > GET / HTTP/1.1
   > Host: abc.cc
   > User-Agent: curl/7.58.0
   > Accept: */*
   >
   < HTTP/1.1 500 Internal Server Error
   < Date: Thu, 10 Mar 2022 08:14:09 GMT
   < Content-Type: text/plain; charset=utf-8
   < Transfer-Encoding: chunked
   < Connection: keep-alive
   < Server: APISIX/2.12.1
   <
   {"error_msg":"failed to limit count"}
   * Connection #0 to host 192.168.44.53 left intact
   root@ubuntu-bionic:/#
   ```
   `root@apisix3:/apisix-2.12.1# tail -f -n 0 logs/error.log | nl
   `
   
   
        1       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
limit-count-redis-cluster.lua:57: new_redis_cluster(): issue-6530-P: redis 
server ip : port => 192.168.55.50 : 7000, client: 192.168.44.1, server: _, 
request: "GET / HTTP/1.1", host: "abc.cc"
        2       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
limit-count-redis-cluster.lua:57: new_redis_cluster(): issue-6530-P: redis 
server ip : port => 192.168.55.51 : 7001, client: 192.168.44.1, server: _, 
request: "GET / HTTP/1.1", host: "abc.cc"
        3       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
limit-count-redis-cluster.lua:57: new_redis_cluster(): issue-6530-P: redis 
server ip : port => 192.168.55.52 : 7002, client: 192.168.44.1, server: _, 
request: "GET / HTTP/1.1", host: "abc.cc"
        4       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
limit-count-redis-cluster.lua:57: new_redis_cluster(): issue-6530-P: redis 
server ip : port => 192.168.55.53 : 7003, client: 192.168.44.1, server: _, 
request: "GET / HTTP/1.1", host: "abc.cc"
        5       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
limit-count-redis-cluster.lua:57: new_redis_cluster(): issue-6530-P: redis 
server ip : port => 192.168.55.54 : 7004, client: 192.168.44.1, server: _, 
request: "GET / HTTP/1.1", host: "abc.cc"
        6       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
limit-count-redis-cluster.lua:57: new_redis_cluster(): issue-6530-P: redis 
server ip : port => 192.168.55.55 : 7005, client: 192.168.44.1, server: _, 
request: "GET / HTTP/1.1", host: "abc.cc"
        7       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:110: try_hosts_slots(): issue-6530-1: loop = 1 
---------------------------, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
        8       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:111: try_hosts_slots(): issue-6530-1: redis server ip : port 
=> 192.168.55.50 : 7000, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
        9       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:110: try_hosts_slots(): issue-6530-1: loop = 1 
---------------------------, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       10       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:111: try_hosts_slots(): issue-6530-1: redis server ip : port 
=> 192.168.55.50 : 7000, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       11       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:110: try_hosts_slots(): issue-6530-1: loop = 1 
---------------------------, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       12       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:111: try_hosts_slots(): issue-6530-1: redis server ip : port 
=> 192.168.55.50 : 7000, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       13       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:110: try_hosts_slots(): issue-6530-1: loop = 1 
---------------------------, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       14       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:111: try_hosts_slots(): issue-6530-1: redis server ip : port 
=> 192.168.55.50 : 7000, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       15       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:110: try_hosts_slots(): issue-6530-1: loop = 1 
---------------------------, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       16       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:111: try_hosts_slots(): issue-6530-1: redis server ip : port 
=> 192.168.55.50 : 7000, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       17       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:110: try_hosts_slots(): issue-6530-1: loop = 1 
---------------------------, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       18       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
rediscluster.lua:111: try_hosts_slots(): issue-6530-1: redis server ip : port 
=> 192.168.55.50 : 7000, client: 192.168.44.1, server: _, request: "GET / 
HTTP/1.1", host: "abc.cc"
       19       2022/03/10 08:14:09 [error] 6395#6395: *509 [lua] 
limit-count.lua:272: phase_func(): failed to limit count: connection refused, 
client: 192.168.44.1, server: _, request: "GET / HTTP/1.1", host: "abc.cc"
       20       2022/03/10 08:14:09 [warn] 6395#6395: *509 [lua] 
plugin.lua:724: run_plugin(): limit-count exits with http status code 500, 
client: 192.168.44.1, server: _, request: "GET / HTTP/1.1", host: "abc.cc"
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to