On Tue, 02 May 2023, Marek Küthe wrote: > Hello, > > thank you for the answer. > > I must admit that I was a bit hasty in reporting this error. This error > occurred when I tried to automate my ufw firewall rules with ansible. > In doing so, I had unfortunately run several scripts which inserted > rules - maybe this is the reason? In the meantime I don't have the > problem anymore and unfortunately I don't know the problematic rule. > But I also noticed that the same error occurred when I inserted > firewall rules and watched ufw status "watch -n 0.5 'ufw status > numbered | wc -l'".
Ok, no worries. I'm glad you aren't seeing the issue anymore. I plan to upload the mitigation fix to bookworm which will close out this issue. If you happen to come across this error again, perhaps consider responding with the additional info. Thanks again for the report. -- Email: ja...@strandboge.com IRC: jdstrand
