No tables in schema when following quick start guide

1

I’m learning snowplow with the community edition.

I’ve run the terraform and DB has been created in RDS.

And I can send request to following the instruction here(Tracking your first events | Snowplow Documentation):

curl ‘…plow/tp2’
-H ‘accept: /’
-H ‘accept-language: en,zh;q=0.9,zh-TW;q=0.8,en-US;q=0.7,zh-CN;q=0.6’
-H ‘content-type: application/json; charset=UTF-8’
…
–data-raw ‘{“schema”:“…”,“data”:[{“e”:“pp”,“url”:“”,“page”:“Tracking your first events | Snowplow Documentation”,“refr”:“”,“pp_miy”:“495”,“pp_may”:“495”,“eid”:“9e6121d9-569d-4a0a-8206-f6a25e6ef07b”,“tv”:“js-3.14.0”,“tna”:“snplow5”,“aid”:“docs2”,“p”:“web”,“cookie”:“1”,“cs”:“UTF-8”,“lang”:“en”,“res”:“1728x1117”,“cd”:“30”,“dtm”:“1722958822732”,“vp”:“1173x873”,“ds”:“1173x3297”,“vid”:“4”,“sid”:“ac14bd2f-b86b-4214-9536-96640ecc74db”,“duid”:“95485fd5-b3d0-4e80-be12-112784f80133”,“cx”:“eyJzY2hlbWEiOiJpZ2x1OmNvbS5zbm93cGxvd2FuYWx5dGljcy5zbm93cGxvdy9jb250ZXh0cy9qc29uc2NoZW1hLzEtMC0wIiwiZGF0YSI6W3sic2NoZW1hIjoiaWdsdTpjb20uc25vd3Bsb3dhbmFseXRpY3Muc25vd3Bsb3cvd2ViX3BhZ2UvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsiaWQiOiI3YjkwZDg4YS1iY2E3LTQxMjctYmRhOC1kNjJhMDFkM2I4ZjcifX0seyJzY2hlbWEiOiJpZ2x1OmNvbS5zbm93cGxvd2FuYWx5dGljcy5kb2NzL3NlbGVjdGVkX3RhYnMvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsiZGF0YV93YXJlaG91c2UiOiJwb3N0Z3JlcyJ9fV19”,“stm”:“1722958822737”}]}’
ok%

And I can connect to the db:

psql --host=… --port=5432 --username=snowplow --password --dbname=snowplow

But there’s no tables in the schema:

snowplow=> SELECT table_name FROM information_schema.tables WHERE table_schema = ‘atomic’; table_name

(0 rows)

How to proceed here?

Thanks!

2

Does the atomic schema itself exist? select schema_name from information_schema.schemata where schema_name = 'atomic'; should be the rough equivalent of your query.

If it doesn’t exist, there may be an issue with the startup script that runs the Docker container that sets up the table. Maybe check the startup script output?

3

If you’re running terraform from Windows, this could also be the issue encountered in this thread, which caused the startup scripts to fail to execute because of the CRLF-style line endings.