Email or username:

Password:

Forgot your password?
All posts jeff's posts Post Back to profile
Top-level
Eugen Rochko

@jeff @spla Watch the dashboard and see if there's more failures than processed jobs, or if no jobs are being processed (e.g. all stuck)

29 Apr 2021 at 0:33 | Wall-to-wall | Open on mastodon.social
11 comments
jeff

@Gargron @spla failures graph/line is just flatlining at the bottom. But I can't click on the word to see failure specifics if they exist.

29 Apr 2021 at 0:39 | Open on my0.net
Eugen Rochko

@jeff @spla Well, is there a "processed" line?

29 Apr 2021 at 0:39 | Open on mastodon.social
jeff

@Gargron @spla not when everything stops its just all at the bottom.

29 Apr 2021 at 0:40 | Open on my0.net
Eugen Rochko

@jeff @spla Go on the Busy tab and look at the Started column, is it basically 25 jobs that have been going for a long time? What are they?

29 Apr 2021 at 0:42 | Open on mastodon.social
jeff

@Gargron @spla this is what's started. It's showing only 5 this time after a sidekiq restart 🤔
29 Apr 2021 at 0:45 | Open on my0.net
Eugen Rochko

@jeff @spla What do you mean after restart? Did you restart while investigating. This will make finding the cause more difficult. That being said none of those jobs are supposed to take an hour, or more than like a minute, realistically.

You will want to send the Sidekiq process a TTIN signal to make it print backtraces of what it's currently executing

github.com/mperham/sidekiq/wik

29 Apr 2021 at 0:47 | Open on mastodon.social
jeff replied to Eugen

@Gargron @spla had to restart the service in order see the responses here 😬 sorry I'm so awful at this. Do I use the kill command for backtrace? How do I retrieve the pid? I only see jit & tid 😬😬

29 Apr 2021 at 0:54 | Open on my0.net
Eugen Rochko replied to jeff

@jeff @spla See the pid through `systemctl status mastodon-sidekiq`, execute `kill -TTIN pid`, view the backtrace dump with `journalctl -u mastodon-sidekiq --since="1 minute ago"`

29 Apr 2021 at 0:56 | Open on mastodon.social
jeff replied to Eugen

@Gargron @spla ok this is what it says. but tbh I don't really understand anything. are you able to decipher any issues?

pastebin.com/jbQNFbt0

29 Apr 2021 at 1:11 | Open on my0.net
Eugen Rochko replied to jeff

@jeff @spla What are the TIDs of the jobs that are stuck for an hour? Search for those in the log output.

From a cursory glance I see some jobs are in the middle of executing ffmpeg conversions. But I don't know if those are the ones that are stuck since you restarted Sidekiq.

29 Apr 2021 at 1:15 | Open on mastodon.social
jeff replied to Eugen

@Gargron @spla the first row didn't even return any results. The 2nd row down tid search just came up with 1 line:

Apr 28 21:09:08 ubuntu bundle[13509]: 2021-04-29T01:09:08.212Z pid=13509 tid=58x WARN: Thread TID-2hth processor

Just doesn't make sense why something can be stuck without much of a description (now showing 6 stuck)
29 Apr 2021 at 1:27 | Open on my0.net
Go Up