unexpected status code 503; error message: {"error_msg":"has no healthy etcd endpoint available"} 2024-05-19T16:17:43+08:00 error apisix/route.go:90 failed to list routes: unexpected status code 503; error message: {"error_msg":"has no healthy etcd endpoint available"} 2024-05-19T16...
config_etcd.lua:567: no healthy etcd endpoint available, next retry after 32s, context: ngx.timer exporter.lua:320: handler(): prometheus: failed to reach config serverwhileprocessing metrics endpoint: has no healthy etcd endpoint available, client:172.26.0.3, server: , request:"GET /apisix/pr...
" [lua] health_check.lua:90: report_failure(): update endpoint: http://xxxx:32002 to unhealthy, context: ngx.timer" [lua] v3.lua:647: request_chunk(): has no healthy etcd endpoint available. Retrying, context: ngx.timer [lua] config_etcd.lua:567: no healthy etcd endpoint available,...
log.error("no healthy etcd endpoint available, next retry after " .. backoff_duration .. "s") end end elseif err ~= "timeout" and err ~= "Key not found" and self.last_err ~= err then log.error("failed to fetch data from etcd: ", err, ", ", tostring(self)) end if err ...
Fix(etcd): can't sync etcd data if key has special character: #9967 Fix(tencent-cloud-cls): dns parsing failure: #9843 Fix(reload): worker not exited when executing quit or reload command #9909 Fix(traffic-split): upstream_id validity verification #10008 3.4.0 Core Support route-level ...
{\"error_msg\":\"has no healthy etcd endpoint available\"}\n\n\t* unexpected status code 503; error message: {\"error_msg\":\"has no healthy etcd endpoint available\"}\n\n\t* unexpected status code 503; error message: {\"error_msg\":\"has no healthy etcd endpoint available\"}...
2021/12/06 02:24:14 [warn] 49#49: *14319 [lua] v3.lua:647: request_chunk(): has no healthy etcd endpoint available. Retrying, context: ngx.timer 2021/12/06 02:24:14 [error] 49#49: *14319 [lua] config_etcd.lua:563: no healthy etcd endpoint available, next retry after 64s...
Release"apisix"has been upgraded. Happy Helming! NAME: apisix LAST DEPLOYED: Thu Apr 25 16:15:51 2024 NAMESPACE: ingress-apisix STATUS: deployed REVISION: 2 NOTES: 1. Get the application URL by running these commands:exportNODE_PORT=$(kubectl get --namespace ingress-apisix -o jsonpath="...
Available add-ons Advanced Security Enterprise-grade security features GitHub Copilot Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... Provide feedback We read every piece ...
After installing APISIX 2.0, theapisix/logs/error.logfile shows thatconfig_etcd.luahas been consistently and frequently reporting errors. The phenomenon still exists after reinstallingapisixandetcdwithout modifying any configuration during the period. Nearly 2,200 lines of error logs typed in nearly 20...