So sidekiq still failephanting for @spiderrobotpig​ even with plenty of RAM

Any ideas?

@djsundog @spiderrobotpig what sayth the logs?

@bea @djsundog Variations of this: Oct 18 00:35:12 localhost systemd[1]: mastodon-sidekiq.service: Main process exited, code=exited, status=1/FAILURE
Oct 18 00:35:12 localhost systemd[1]: mastodon-sidekiq.service: Unit entered failed state.
Oct 18 00:35:12 localhost systemd[1]: mastodon-sidekiq.service: Failed with result 'exit-code'.

@spiderrobotpig @djsundog no, not this log

the log emitted by sidekiq itself

how are you viewing that log?

@bea @djsundog journalctl -f

I'm not sure how I would check sidekiqs logs if I can't get into it

@spiderrobotpig @djsundog

what do you get from

journalctl -u mastodon-sidekiq

?

@bea @djsundog https://witches.town/media/52AflSflf73ex8Gfd8w

@spiderrobotpig @djsundog yep

it's looking for redis as host 'redis'

so either add an /etc/hosts for a redis host

or start redis on a host with that name

or change your redis host to point to the ip of redis (even if it is localhost)

@bea @djsundog Do I need to restart stuff after? Cos it's still not working

@spiderrobotpig @bea yeah systemctl restart mastodon-*

@bea @spiderrobotpig hopefully ;)

@djsundog @bea DING DING DING THAT WAS THE CORRECT ANSWER

@spiderrobotpig @bea AWOOOOOO https://toot-lab.reclaim.technology/media/HwZilzC8vF1kgjDMUII