-
For some reason, my paperless jumped into year 2060 and does not check any may anymore: full logs:
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
Time is provided by your operating system. If you are using Docker, I'd be sure the timezone environment is set and re-create the container fully |
Beta Was this translation helpful? Give feedback.
-
I recreated the container (using docker) but nothing changed. I also removed the task results from the postgres db which had a 2060 timestamp. Where does paperless store that date of the last mail run, then i could simply change that. |
Beta Was this translation helpful? Give feedback.
-
time is fine in those containers:
I checked the others too. The main paperless.log shows the correct time only the mail.log doesn't show anything after the 2060 entry anymore. I tried to remove the mail account and rules and recreated them but still nothing is happening. Can i force trigger the mail task manually somehow? |
Beta Was this translation helpful? Give feedback.
-
great, that worked. So i was able to fetch mail attachments manually with that command, but automatic mail fetching is still not triggered anymore. Who/Where would that be triggered usually? |
Beta Was this translation helpful? Give feedback.
-
thanks a lot, that did the trick. Now everything is running smoothly again. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. |
Beta Was this translation helpful? Give feedback.
Scheduled tasks are handled by celery beat. You could remove the celerybeat file in your data directory and let the container re-create it on startup.