This message was deleted.
# rke2a
adamant-kite-43734
05/02/2025, 3:46 PMThis message was deleted.
c
creamy-pencil-82913
05/02/2025, 3:57 PMcan’t say I’ve ever seen that. When are you seeing it? what are you using for the db backend?
b
bright-lifeguard-9803
05/02/2025, 4:22 PMsqlitebright-lifeguard-9803
05/02/2025, 4:29 PMI don't see a pattern for when we see it. It is very spammy. It does seem to stop if we restart rke2
c
creamy-pencil-82913
05/02/2025, 4:30 PMare there any errors or warnings before it starts doing that?
b
bright-lifeguard-9803
05/02/2025, 4:31 PMGood question. I'll have to dig around and see if I can find something where the logs have not rolled over.
bright-lifeguard-9803
07/22/2025, 3:03 PM@creamy-pencil-82913 this is still causing us issues. We're on
1.33.1👀 1
c
creamy-pencil-82913
07/22/2025, 5:47 PMplease provide steps to reproduce. As I said earlier, I’ve not seen any other reports of this and you’ve provided very little info so far.
creamy-pencil-82913
07/22/2025, 5:49 PMDoes it happen during startup or shutdown? After any particular event? Are you running kine embedded in k3s, or rke2, or standalone?
b
bright-lifeguard-9803
07/22/2025, 6:11 PMIt seems to be an edge case, it happens during runtime. Restarting RKE2 is our workaround. We don't have a reproducer yet, we're working on that now. We're running kine embedded in RKE2.
19 Views