While running this command on my DigitalOcean install:
$ sudo systemctl restart forem-traefik.service
The command is stalling.
I've checked the forem services:
$ systemctl list-units forem* --all
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
forem-container.service loaded inactive dead Forem container service
forem-imgproxy.service loaded active running Forem Imgproxy Service
forem-openresty.service loaded inactive dead start Forem OpenResty Service
forem-pod.service loaded active running Forem pod service
forem-postgresql.service loaded active running Forem Postgresql Service
forem-rails.service loaded activating auto-restart start Forem Rails Service
forem-redis.service loaded active running Forem Redis Service
forem-traefik.service loaded active running Forem Traefik Service
forem-worker.service loaded inactive dead start Forem Worker Service
forem.service loaded active exited Forem Service
For Openresty:
$ sudo journalctl -u forem-openresty.service -n 200 --no-pager
... (all the same)
systemd[1]: Dependency failed for Forem OpenResty Service.
systemd[1]: forem-openresty.service: Job forem-openresty.service/start failed with result 'dependency'.
...
For Worker:
$ sudo journalctl -u forem-worker.service -n 200 --no-pager
systemd[1]: Dependency failed for Forem Worker Service.
systemd[1]: forem-worker.service: Job forem-worker.service/start failed with result 'dependency'.
I tried to use sudo systemctl start forem-container.service
.
But it doesn't help.
Please help me.
Top comments (12)
Hey @tien thanks for trying out Selfhost!
Can you show us some logs from
forem-container.service
? That's what handles retrieving the Forem container, and if there are issues pulling that container, nothing will really work.Hi, thanks for your fast comment.
This is logs from
forem-container.service
.Ok, that's fine; looks like it's correctly pulling down the
quay.io/forem/forem:latest
container.Can you show your logs for
forem-rails.service
as well? Looks like it's restarting, wonder if there are any obvious errors in there.Hi, this is my logs for
forem-rails.service
:)Not sure what's going on there - can you reboot your droplet and see if you're still getting errors on
forem-rails.service
? Thanks!Thanks! But unfortunately it still doesn't work :(.
I recently ran into this same issue when building the Docker config at github/forem/forem.
This is not very helpful, but my temporary "fix" was to comment out the offending
index_exists?
invocations in that particular migration and then everything was ok..ish:Hi, thank you, I will try :)
With this PR, now you should not face any such migration issues.
Hi, thank you so much! :)
were you able to fix? can you explain what have you done? @tien
how to use this PR solve this issue? @akhil