This repository has been archived by the owner on May 26, 2023. It is now read-only.
After hard drive runs full, CheckforstatusesScheduler job did not recover automatically #810
Comments
|
@rriemann I don't believe this job is treated any different than the others, it should follow the regular rules for Sidekiq jobs: retry about 21 times in the period of two weeks before finally giving up. I will test it locally soon. |
|
Maybe after few days the break between attempts grows quickly? Maybe we can also prevent sidekiq to put this job to the dead queue? See answer here: https://stackoverflow.com/a/23090499/1407622 |
renatolond
added a commit
that referenced
this issue
May 26, 2023
Closes #930, #913, #911, #906, #904, #897, #896, #895, #890, #886, #880 Closes #877, #872, #871, #868, #866, #863, #862, #859, #820, #810, #809 Closes #724, #721, #711, #688, #679, #606, #603, #593, #581, #577, #551 Closes #533, #517, #506, #505, #493, #430, #422, #311, #297, #241, #238 Closes #233, #197, #165, #164, #161, #160, #159, #151, #150, #148, #146 Closes #140, #139, #138, #135, #134, #127, #124, #123, #120, #119, #118 Closes #116, #112, #109, #106, #105, #103, #96, #90, #88, #86, #85, #74 Closes #65, #55, #47, #36, #33, #28, #19, #18 Closes #957, #955, #953, #950, #949, #936, #927, #925, #894, #873, #867 Closes #864, #650
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear all,
the crossposter stopped crossposting (at least from Twitter to Mastodon) and did not recover automatically until the problem was manually identified and the button "retry all" was activated on sidekiq:
This is most likely a problem caused by a hard drive running out of space, so that some services (DB?) failed. The issue was solved eventually, but the crossposter did not retry again cross posting.
Could the retry rule in sidekiq could be adjusted to just keep on trying?
If the problem is only discovered a few days later, no content is lost for import, but its timestamps will the a few days off.
Best,
Robert
The text was updated successfully, but these errors were encountered: