Hi folks – we just ran into this issue and there’s not an obvious immediate fix on our side. Our node is operating well. I did notice another issue which looked somewhat similar, but that suggested a change in our packages and we haven’t knowingly made any changes there recently.
Just wondering if anybody recognises the error