@djsundog Exactly the same thing, so it's definitely not RAM >.> 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'.
Notices by Witchy Delphox (spiderrobotpig@witches.town)
-
Witchy Delphox (spiderrobotpig@witches.town)'s status on Tuesday, 17-Oct-2017 20:35:40 EDT Witchy Delphox
-
Witchy Delphox (spiderrobotpig@witches.town)'s status on Tuesday, 17-Oct-2017 20:13:14 EDT Witchy Delphox
@djsundog Oct 18 00:12:37 localhost systemd[1]: mastodon-sidekiq.service: Main process exited, code=exited, status=1/FAILURE
Oct 18 00:12:37 localhost systemd[1]: mastodon-sidekiq.service: Unit entered failed state.
Oct 18 00:12:37 localhost systemd[1]: mastodon-sidekiq.service: Failed with result 'exit-code'.
Oct 18 00:12:37 localhost npm[29084]: info Starting worker 1024Same as every other time I've gotten to this point