|
Top-level
 @jeff One way we can try this is if you launch the Rails console like this (from the Mastodon directory): RAILS_ENV=production RAILS_LOG_LEVEL=debug bin/rails c Then you can try manually executing one of the jobs that I see in the screenshot, like this, by copying the arguments from the page: ThreadResolveWorker.new.perform(106.... etc) You should then see output of it fetching something through HTTP, doing database queries, and finally executing ffmpeg commands 8 comments
@jeff Well, that didnât get stuck at all. Weird. The relevant part would be the line that says âRunning commandâ with ffmpeg. If the problem was there, thatâs what would get stuck and you wouldnât get past that. @jeff Could you check if you are affected by this bug? https://bugs.ruby-lang.org/issues/17781 There are instructions how to check inside, you would run them from the console as well  @Gargron I don't think my command is outputting the desired results: Unless I didn't run the command correctly đŹ @jeff Yeah, you are affected by this bug. Maybe it was that all along. Try installing Ruby 2.6.6 instead and running with that @Gargron alright - lets see if this works. also - appreciate you giving me your time. will let you know how things turn out soon @jeff Think you need to also do `rbenv local 2.6.6` within the Mastodon directory, global won't affect it |
Gregory's Server
@Gargron okay, here are the results from one of the workers that has been stuck for 7 hours:
https://pastebin.com/F4DijcZU
But tbh, this looks less helpful to me. I don't understand anything on this output.
I can try doing this using a different stuck command or worker if you think it would result in more helpful output. đ¤