Comment 7 for bug 1847203

We have since updated the l3-agent to better log when it starts/stops processing messages, so there is at least a way to look at the logs and help determine what happened. That said, as only this one user has seen this issue and it was on an older release, I'll close this as there have been no other reports (and might have been fixed in any number of changes). If you still see if on a newer release please re-open this bug with more information.