Comment 9 for bug 1700453

I ran bare juju debug-log for quite a while during upgrades of my Canonistack controllers today. I had one instance of debug-log failing unexpectedly which might be attributable to this still being present, but I can't be certain. One interesting side-effect of the fix is that I got about 4 days of backlogs before the current logs started coming through. So it seems that this fix has uncovered a few unseen log messages still hanging around.