I'm running a self-hosted core and just finished s...
# support-questions-legacy
h
I'm running a self-hosted core and just finished setting up my Postgresql. Everything is dockerized and networked with docker-compose. The database and everything else seems to work just fine, however, these errors are logged by the database at startup.
Copy code
ERROR:  relation "st_key_value" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_key_value LIMIT 1
ERROR:  relation "st_all_auth_recipe_users" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_all_auth_recipe_users LIMIT 1
ERROR:  relation "st_session_access_token_signing_keys" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_session_access_token_signing_keys LIMIT 1
ERROR:  relation "st_session_info" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_session_info LIMIT 1
ERROR:  relation "st_emailpassword_users" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_emailpassword_users LIMIT 1
ERROR:  relation "st_emailpassword_pswd_reset_tokens" does not exist at character 15
STATEMENT:  SELECT 1 FROM st_emailpassword_pswd_reset_tokens LIMIT 1
ERROR:  relation "st_emailverification_verified_emails" does not exist at character 15
It seems SuperToken is trying to access something inside the db which is not there? Though sign up/in works and account are persistent until I rebuild the db container
r
that is OK. The core does that to check if it needs to create those tables in the db or not.
the next time you start the core, the errors should not come
assuming that you have connected it to the same db
h
I see, thanks you. I was just a bit concerned, considering they were marked as errors 😅