aryayangx-afk opened a new issue, #12866:
URL: https://github.com/apache/apisix/issues/12866

   ### Current Behavior
   
   After restarting APISIX, sporadic errors occur:  
    [lua] server-info.lua:216: report(): failed to get lease_id from shdict: 
nil, context: ngx.timer
   
   1. Out of our 20 APISIX pods, only one pod is reporting this error.
   2. Other pods on the same node as the faulty pod are not experiencing this 
issue.
   3. Upon checking basic monitoring for the problematic pod, we found no 
issues with memory, CPU, or connectivity to etcd.
   
   I want to confirm, what impact does this error have on the overall service?  
I noticed that server-info is no longer used in newer versions, but we cannot 
upgrade APISIX at the moment. How can we avoid this issue in our current version
   
   ### Expected Behavior
   
   There should not be this error
   
   
   ### Error Logs
   
    [lua] server-info.lua:216: report(): failed to get lease_id from shdict: 
nil, context: ngx.timer
   
   ### Steps to Reproduce
   
   1. kubectl apply -f new apisix deployment yaml
   
   ### Environment
   
   APISIX version (run apisix version):
   ```
   3.10.0
   ```
   - Operating system (run uname -a):
   ```
   Linux apisix-test-8497c69d5d-9ggxj 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC 
Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
   ```
   OpenResty / Nginx version (run openresty -V or nginx -V):
   ```
   nginx version: openresty/1.25.3.2
   built by gcc 10.2.1 20210110 (Debian 10.2.1-6) 
   built with OpenSSL 3.2.0 23 Nov 2023
   TLS SNI support enabled
   ```
   etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
   ```
   3.5.16
   ```
   APISIX Dashboard version, if relevant:
   ```
   3.0.1
   ```
   Plugin runner version, for issues related to plugin runners:
   ```
   Not applicable
   ```
   LuaRocks version, for installation issues (run luarocks --version):
   ```
   Not applicable
   ````


-- 
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