post deployment errors #15

New Issue

ammaratef45 · 2024-11-23T02:57:12Z

ammaratef45 commented

2024-11-23 02:57:12 +00:00

After managing to get a successful deployment (oh boy this recipe is complicated!), I had the following errors

If I try to run the streaming setup

╰─ abra app cmd <app_domain> streaming setup                                                                                                ─╯
/tmp/abra.sh: line 71: bundle: command not found
FATA[0002] Status: , Code: 127

When I look at the logs without doing the streaming setup (since I can't do it)

/usr/local/bundle/gems/activerecord-7.1.4.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:19:in `exec': ERROR:  relation "users" does not exist (PG::UndefinedTable)
P2024-11-23T02:51:42.345362082Z LINE 10:  WHERE a.attrelid = '"users"'::regclass

After managing to get a successful deployment (oh boy this recipe is complicated!), I had the following errors # If I try to run the streaming setup ``` ╰─ abra app cmd <app_domain> streaming setup ─╯ /tmp/abra.sh: line 71: bundle: command not found FATA[0002] Status: , Code: 127 ``` # When I look at the logs without doing the streaming setup (since I can't do it) ``` /usr/local/bundle/gems/activerecord-7.1.4.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:19:in `exec': ERROR: relation "users" does not exist (PG::UndefinedTable) P2024-11-23T02:51:42.345362082Z LINE 10: WHERE a.attrelid = '"users"'::regclass ```

3wordchant commented

2024-11-23 05:25:01 +00:00

abra app cmd <app_domain> streaming setup

I think the README might be wrong. Mastodon split the streaming image into a separate one in 4.3. If this command is still required, it should probably be run against the app container. I'll try to investigate.

relation "users" does not exist

Could be because of failed setup, or that rake db:migrate is needed.

oh boy this recipe is complicated!

Yes 😢

> `abra app cmd <app_domain> streaming setup` I think the README might be wrong. Mastodon split the streaming image into a separate one in 4.3. If this command is still required, it should probably be run against the `app` container. I'll try to investigate. > `relation "users" does not exist` Could be because of failed `setup`, or that `rake db:migrate` is needed. > oh boy this recipe is complicated! Yes 😢

ammaratef45 commented

2024-11-23 06:21:52 +00:00

@3wordchant helped me on matrix figure this out, the container doesn't stay app long enough to run the db:setup or db:migrate

The steps followed to resolve this are:

comment all command: ... and entrypoint: ... mentions in the compose.yml file.
abra app deploy -C <app_domain>
abra app cmd <app_domain> app setup
abra app cmd <app_domain> app shell
rake db:migrate
undeploy
revert changes to compose.yml
deploy

I'm sure we can do something to make this pain go away, but I'll take the win and call it a day 😆

TYSM 3wc!

@3wordchant helped me on matrix figure this out, the container doesn't stay app long enough to run the `db:setup` or `db:migrate` The steps followed to resolve this are: - comment all `command: ...` and `entrypoint: ...` mentions in the compose.yml file. - `abra app deploy -C <app_domain>` - `abra app cmd <app_domain> app setup` - `abra app cmd <app_domain> app shell` - `rake db:migrate` - undeploy - revert changes to compose.yml - deploy I'm sure we can do something to make this pain go away, but I'll take the win and call it a day 😆 TYSM 3wc!

❤️ 2

benjaminlyng commented

2025-04-27 19:09:48 +00:00

Thanks for this fix. I was stuck on the same issue. Perhaps these steps should be added to the readme? Or somehow scripted to make it easier to deploy 🤔

👍 1

decentral1se commented

2025-04-28 10:16:32 +00:00

toolshed/organising#381 could with a boost @benjaminlyng @ammaratef45 🙏

https://git.coopcloud.tech/toolshed/organising/issues/381 could with a boost @benjaminlyng @ammaratef45 🙏

👍 1

3wordchant referenced this issue from a commit

2025-06-07 18:05:50 +00:00

Run rake db:migrate during startup

3wordchant closed this issue

2025-06-07 18:05:50 +00:00

Sign in to join this conversation.