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 This is what I get: Oct 18 00:32:47 localhost systemd[1]: mastodon-sidekiq.service: Main proces
Oct 18 00:32:47 localhost systemd[1]: mastodon-sidekiq.service: Unit entere
Oct 18 00:32:47 localhost systemd[1]: mastodon-sidekiq.service: Failed with
Oct 18 00:32:48 localhost systemd[1]: mastodon-sidekiq.service: Service hol
Oct 18 00:32:48 localhost systemd[1]: Stopped mastodon-sidekiq.
Oct 18 00:32:48 localhost systemd[1]: Started mastodon-sidekiq.
Oct 18 0