retrying of unary invoker failed

[GRYBD1]

Scale 23.10.0.1. This warning is logged about every 40 seconds. I do have PLEX running without any issues but the constant logging does create a lot of clutter. Is there a way to stop it from being written to the journal?

Dec 20 00:43:04 Max k3s[7341]: {"level":"warn","ts":"2023-12-20T00:43:04.738-0500","logger":"etcd-client","caller":"v3@v3.5.7-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000cc4000/kine.sock","attempt":0,"error":"rpc>
Dec 20 00:43:48 Max k3s[7341]: {"level":"warn","ts":"2023-12-20T00:43:48.070-0500","logger":"etcd-client","caller":"v3@v3.5.7-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000cc4000/kine.sock","attempt":0,"error":"rpc>
Dec 20 00:44:32 Max k3s[7341]: {"level":"warn","ts":"2023-12-20T00:44:32.284-0500","logger":"etcd-client","caller":"v3@v3.5.7-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000cc4000/kine.sock","attempt":0,"error":"rpc>
Dec 20 00:45:08 Max k3s[7341]: {"level":"warn","ts":"2023-12-20T00:45:08.781-0500","logger":"etcd-client","caller":"v3@v3.5.7-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000cc4000/kine.sock","attempt":0,"error":"rpc>

 

[CacheMeIfYouCan]

I have a similar log on my two Scale 23.10.0.1 servers, repeated every 30-40 seconds. Except mine also mentions a dbstat table, which I don't know.

Example :
Jan 19 06:01:36 serveur4 k3s[6163]: {"level":"warn","ts":"2024-01-19T06:01:36.908-0500","logger":"etcd-client","caller":"v3@v3.5.7-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000590000/kine.sock","attempt":0,"error":"rpc error: code = Unknown desc = no such table: dbstat"}

@GRYBD1 have you found the cause or a solution?

EDIT: I just found that a ticket was opened 6 months ago and closed without addressing the issue, which seems trivial to fix. I suggest you also comment on it.