status:
- runner: fine (no crash, no restart)
- listener: fine (same)
- workers: fine (same)
status:
WIP as the new version has been deployed (runner, listener, workers, etc...)
Let's see if the occurrences still occur.
I've done the upgrade on saatchi and restarted both listener and runner. I've removed the runner restart from the saatchi crontab.
I've pushed an updated kombu to our repository.
bunch of celery workers (loader*, lister*) indeed have a ConnectionResetError stacktrace (not necessarily the same):
As per our pair-programming yesterday, I think we reproduce this in production now (with the runner at least).
I confirm that I do not see ConnectionResetError: [Errno 104] Connection reset by peer and BrokenPipeError: [Errno 32] Broken pipe so far in the runner logs with kombu from git's master.