It's mostly there so that we can find out. It is completely recoverable now that we've fixed the bug, so perhaps downgrading to info is appropriate, but we'd then be less likely to notice dodgy connections. I think it's appropriate for the framework to warn; we can always filter the logs if our environment turns out to be very unreliable.

By virtue of the previous bug we could grep the syslogs to find out how often it happens in practice. I'd rather not though!