Rasa x stuck while checking database

[Deprecated] Rasa X Community Edition
1

Hello,

I have been trying to set up RasaX to use one of our own databases. It’s a PostgreSQL database, that also hosts our tracker databases. So it should be compatible.

I created an empty db and modified the env vars to match.

I am getting these messages:

rasa-x_1           | INFO:alembic.runtime.migration:Will assume transactional DDL.
rasa-x_1           | WARNING:rasax.community.database.utils:Can't check if DB is migrated to latest Alembic revision, multiple or no heads: ().
rasa-x_1           | WARNING:rasax.community.services.event_service:Database revision does not match migrations' latest, trying again in 2 seconds.
rasa-x_1           | INFO:alembic.runtime.migration:Running upgrade  -> 2a216ed121dd, Initial migration
rasa-x_1           | INFO:alembic.runtime.migration:Context impl PostgresqlImpl.
rasa-x_1           | INFO:alembic.runtime.migration:Will assume transactional DDL.
rasa-x_1           | WARNING:rasax.community.database.utils:Can't check if DB is migrated to latest Alembic revision, multiple or no heads: ().
rasa-x_1           | WARNING:rasax.community.services.event_service:Database revision does not match migrations' latest, trying again in 2 seconds.
rasa-x_1           | INFO:alembic.runtime.migration:Running upgrade 2a216ed121dd -> 9d4a16758d6e, Addition of `is_default` and `description` columns to `user_role` table.
rasa-x_1           | INFO:alembic.runtime.migration:Running upgrade 9d4a16758d6e -> e3a3a2789e20, Add index to `conversation_id` column of table `conversation_event`.
rasa-x_1           | INFO:alembic.runtime.migration:Running upgrade e3a3a2789e20 -> 59b7be3ad5fc, Add `extractor` column to table `nlu_training_data_entity`.
rasa-x_1           | INFO:alembic.runtime.migration:Running upgrade 59b7be3ad5fc -> 1dfbf67d6ae2, Support for individually unfeaturized entities in domain.
rasa-x_1           | INFO:alembic.runtime.migration:Context impl PostgresqlImpl.
rasa-x_1           | INFO:alembic.runtime.migration:Will assume transactional DDL.
rasa-x_1           | WARNING:rasax.community.database.utils:Can't check if DB is migrated to latest Alembic revision, multiple or no heads: ().
rasa-x_1           | WARNING:rasax.community.services.event_service:Database revision does not match migrations' latest, trying again in 2 seconds.
rasa-x_1           | INFO:alembic.runtime.migration:Context impl PostgresqlImpl.
rasa-x_1           | INFO:alembic.runtime.migration:Will assume transactional DDL.
rasa-x_1           | WARNING:rasax.community.database.utils:Can't check if DB is migrated to latest Alembic revision, multiple or no heads: ().
rasa-x_1           | WARNING:rasax.community.services.event_service:Database revision does not match migrations' latest, trying again in 2 seconds.
rasa-x_1           | INFO:alembic.runtime.migration:Context impl PostgresqlImpl.
rasa-x_1           | INFO:alembic.runtime.migration:Will assume transactional DDL.
rasa-x_1           | WARNING:rasax.community.database.utils:Can't check if DB is migrated to latest Alembic revision, multiple or no heads: ().
rasa-x_1           | WARNING:rasax.community.services.event_service:Database revision does not match migrations' latest, trying again in 2 seconds.
rasa-x_1           | INFO:alembic.runtime.migration:Context impl PostgresqlImpl.
rasa-x_1           | INFO:alembic.runtime.migration:Will assume transactional DDL.
rasa-x_1           | WARNING:rasax.community.database.utils:Can't check if DB is migrated to latest Alembic revision, multiple or no heads: ().

adding @nbeuchat

2

Did you find solution for this? Facing same problem

3

I also have the same problem.

4

Me too

5

Did anyone found solution to this issue

6

Is there any solution for this ? I’m facing the same issue on an OpenShift Cluster.

7

I was facing the same message in our OpenShift cluster. The fundamental problem is that the event service is not able to correctly establish a connection to the database host. This is quite hard to understand as of Rasa X 0.38.1 no clear exception is logged.

In general, make sure that your database is reachable and your credentials are correct.

Inside OpenShift there could be a variety of reasons why the connection fails e.g. secrets (DB_PASSWORD) or the endpoints.yml file were not mounted. The process could also fail due to some unresolvable variables while reading the endpoints configuration.

1 Like
8

Yes! as mentioned by @witling My endpoints were messed up, and because of that, rasa-x was not able to connect and perform migrations.