Email or username:

Password:

Forgot your password?
jeff

@Gargron Hey, so sorry to bother you again. If you are busy and don't feel like responding, I totally get it.

Looks like less than 1 day, there are 9 stuck busy workers. Here is the full dump:
pastebin.com/DMFBZXgf

What is interesting, is it still has the same warnings as before.

Is there a way to verify the patch was installed correctly? Attached a screenshot of me applying the git command.

I dont know if this helps but here are the TID that were stuck:
pastebin.com/8Nhxfe4f

12 comments
Eugen Rochko

@jeff Seems like it's running my patch and still getting stuck in it

Is there anything blocking ffmpeg on the system somehow?

jeff

@Gargron not that I can think of. The only software I installed before masto was just fail2ban. But is there a way to double check that or test?

Eugen Rochko

@jeff The next step is for you to try and find one of the ffmpeg commands it's running (should be in the logs with appropriate RAILS_LOG_LEVEL) and try executing it from the shell and see what happens...

Eugen Rochko

@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

jeff

@Gargron okay, here are the results from one of the workers that has been stuck for 7 hours:
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. 🤔

Eugen Rochko

@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.

Eugen Rochko

@jeff Could you check if you are affected by this bug? bugs.ruby-lang.org/issues/1778 There are instructions how to check inside, you would run them from the console as well

jeff

@Gargron I don't think my command is outputting the desired results:
pastebin.com/vL3Xn1GJ

Unless I didn't run the command correctly 😬
Maybe my masto is cursed. or Im bad luck

Eugen Rochko

@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

jeff

@Gargron alright - lets see if this works.
pastebin.com/dGk0Shs4

also - appreciate you giving me your time. will let you know how things turn out soon

Eugen Rochko replied to jeff

@jeff Think you need to also do `rbenv local 2.6.6` within the Mastodon directory, global won't affect it

jeff replied to Eugen

@Gargron good catch, thanks for the tip. looks like that did make a major change, because I had to do bundle install again then restart

pastebin.com/f3rqQWhb

lets see if this improves things

Go Up