My feeling is that it is caused by one of the cronjobs we run to process articles.
Instead of trying to find the culprit, I am thinking about reviewing the cronjobs and removing https://github.com/Tivix/django-cron/ from the code base. This route implies moving the cronjobs to custom django commands and adding more documentation to include the new commands in the system's crontab.
The reason for removing django-cron is because the project wasn't updated in the last two years. We will lose some logging, but there are alternatives using healthchecks.io or something similar.
This is happening for https://gregory-ms.com/
My feeling is that it is caused by one of the cronjobs we run to process articles.
Instead of trying to find the culprit, I am thinking about reviewing the cronjobs and removing https://github.com/Tivix/django-cron/ from the code base. This route implies moving the cronjobs to custom django commands and adding more documentation to include the new commands in the system's crontab.
The reason for removing django-cron is because the project wasn't updated in the last two years. We will lose some logging, but there are alternatives using healthchecks.io or something similar.