-
-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: tasks container gets stuck on updating remote instances nightly #5112
Comments
So the loop stops at midnight, but the process keeps handling HTTP requests? And there is no error message in between? Thats very weird, I cant think of any reason why this would happen. |
This is just the tasks container - does it actually handle any requests? I have - for now - set up a cron that restarts the tasks container at 00:30 just to keep the other tasks applied, but this means that my instance always thinks 98% of the fediverse is dead as no other interaction happens to keep them "updated". |
No I misread, the second log shows some outgoing HTTP requests. Seems that the loop is stopped, but some scheduled tasks are still active at that point. The logs you shared are missing the most relevant part between 0:00 and 0:11, can you share that also? |
Attaching the full log from midnight till it stops printing anything at all |
So it prints "beginning of loop", but not "middle of loop" which indicates that the problem is with |
The only thing I can think of, is that you might be running lemmy manually with an older rust version that doesn't play well with the library or async. Or there is some misconfigured network setting causing the fetch to stall out. |
It's literally whatever the dockerfile contains. It's also the same with the official 0.19.5 as well as 0.19.6-beta.9. |
Hrm... if its docker then I can only think that its some network issue causing the job to stall out. It looks like we have reqwest timeouts on that client also though. Not really sure what it could be. |
Requirements
Summary
Every midnight the scheduled daily tasks kick off and get stuck at the same spot. Per @Nutomic suggestion I have patched the scheduler to be more verbose. Attaching the diff, the log at midnight and the log at point of getting stuck in the
technical details
field.The tasks container stays stuck indefinitely. In this particular case I have restarted it after ~8 hours, but I had it stuck in this state for 5 days when I was busy and it just wouldn't come back into action on its own.
I'm also aware from the chat on matrix that nobody else seems be experiencing this.
Steps to Reproduce
Technical Details
Version
0.19.5
Lemmy Instance URL
lemmy.cafe
The text was updated successfully, but these errors were encountered: