invalid auth token - Githubissues

Niklauson commented 1 year ago

After the e3w service runs for a period of time, the error is as follows:

e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.534Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":83,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.666Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":84,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.777Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":85,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.928Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":86,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.031Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":87,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.176Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":88,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.275Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":89,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.403Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":90,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.513Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":91,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.648Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":92,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.750Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":93,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.888Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":94,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.988Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":95,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.122Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":96,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.243Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":97,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.381Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":98,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.505Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":99,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}

After restarting the service, it will be fine, how to solve this problem without restarting the service

Thanks!!!

soyking commented 1 year ago

Could you reproduce it? I sam some issues said that it would happen after JWT Token expired after 5 minutes. Does it perform like this at your environment?

Niklauson commented 1 year ago

Could you reproduce it? I sam some issues said that it would happen after JWT Token expired after 5 minutes. Does it perform like this at your environment?

I found that no request is sent after the system has been idle for a period of time, and if I request again, an error will be reported。Maybe the token has expired during this time

soyking / e3w

invalid auth token #34