Sat, Apr 13
Tue, Apr 2
Mon, Mar 25
Let's call it done, event if the small dataset part has not been addressed.
Let's call it done, some minor parts may still need a bit of attention thou
Mar 17 2019
Mar 8 2019
Mar 6 2019
Closing this as I forgot it exists a configuration entry to force the serving of assets by Django (https://forge.softwareheritage.org/rCDFD7b3213293ca1670a738d540cbba05e87e5cf6042).
Feb 25 2019
Feb 20 2019
- runner: fine (no crash, no restart)
- listener: fine (same)
- workers: fine (same)
Feb 19 2019
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.
Feb 17 2019
bunch of celery workers (loader*, lister*) indeed have a ConnectionResetError stacktrace (not necessarily the same):
Feb 16 2019
As per our pair-programming yesterday, I think we reproduce this in production now (with the runner at least).
Feb 5 2019
Jan 28 2019
Jan 24 2019
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.