Gregory's Server@Claire @Gargron if you were in my shoes, would you just un-comment out the sidekiq line here:
https://pastebin.com/H0CrSnHu
or is there something else I can try
|
Top-level
 13 comments
  @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 |
@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..."
https://pastebin.com/4AjZ6waR
At least this is predictable 😬