|
Top-level
 @Gargron I have no clue either. I just ran the 3 "stuck" workers in ruby console: AND FROM WHAT I CAN TELL THEY ARE RUNNING FINE maybe I should just let this go for now. if you're out of ideas, I certainly wouldnt be able to figure it out I'll just set up a cron to restart sidekiq every other hour or so. But please if you think of anything else to try, please let me know! 22 comments
 @Claire @Gargron no worries. attached a screenshot of htop, I think it looks normal. Here is the pstree output: But when I pick a PID, I don't get much output from strace: root@ubuntu:~# strace -p 2850 (unless I'm doing something wrong?) @Claire @Gargron I don't get it either. I literally followed these instructions: https://docs.joinmastodon.org/admin/install/ is just restarting the sidekiq service hourly from crontab my best bet? @Claire @Gargron if you were in my shoes, would you just un-comment out the sidekiq line here: or is there something else I can try @Claire @Gargron okay. so not surprisingly, it is impossible to upload an animated gif, gets stuck at the progress bar. But each time an attempt made, it gets a worker stuck with PostProcessMediaWorker. When manually running the ruby command, it has a message saying "trying to..." At least this is predictable 😬  @jeff @Claire Okay, let's try this: Change Sidekiq log level to debug (you can add RAILS_LOG_LEVEL=debug to .env.production and restart Sidekiq), then watch the logs with: journalctl -u mastodon-sidekiq -f And try uploading a GIF. You should see output similar to when running stuff from the console. And you should notice at which step it hangs... @Gargron @Claire ok I had to use zerobin (because pastebin said it contained adult languege) sorry if this isnt very readable: https://zerobin.net/?f1a9cd18ffded8dc#MSF1QE7wDYC9yvg7NqlegdIOHIbB3zpI6uw6xnxh30Y= uploaded image around 10:23A system time if that helps you find it. but there is a ton of info there about other statuses. according to my sidekiq gui, the stuck worker has TID of gokotqmd8 @jeff @Claire Can you try replacing it with this file: https://github.com/tootsuite/mastodon/blob/6465972caf77cb7008e1d751778f53ed2e6f698e/dist/mastodon-sidekiq.service Then restarting Sidekiq this way: systemctl daemon-reload |
Gregory's Server
@jeff @Gargron this issue really is odd…
if you happen to get stuck jobs again, could you check the following:
pstree -a -t mastodoncheck if the ffmpeg processes are currently using CPU
find one of the ffmpeg processes and do
strace -p PIDwhere PID is the PID of one such process