Comment 1 for bug 1989004

Also just to mention that paste was from indico-pebble-ready, but here's a similar one just after from indico-celery-pebble-ready https://paste.ubuntu.com/p/Sn8NSC82Kj/. We've seen 5 container restarts on the indico-celery container since the pod was created as part of a charm upgrade, and 5 container restarts on indico-nginx. It's not clear that the `socket.timeout` errors are directly tied to the container restarts given we've also seen them (per the paste above) on containers that haven't restarted, but it does seem like it could be related, and certainly seems worth investigation.