Fresh install - unable to start docker : "FATAL: database "plausible_db" does not exist" #3193

meepmeep · 2023-07-25T13:41:44Z

meepmeep
Jul 25, 2023

I completely messed up the upgrade to 2.0, so I decided to start again on a clean install.

removed the hosting directory, git clone the file, untouched docker-compose.yml file.
Setting up my configuration

DISABLE_REGISTRATION=true
BASE_URL=https://xyz.domain.tld
GEONAMES_SOURCE_FILE=/etc/app/geonames.csv
IP_GEOLOCATION_DB=/etc/app/geolite2-city.mmdb
SECRET_KEY_BASE=<<secret>>
[email protected]
SMTP_HOST_ADDR=xxxxxx
SMTP_HOST_PORT=465
SMTP_USER_NAME=xxxxxxx
SMTP_USER_PWD=xxxxxx
SMTP_HOST_SSL_ENABLED=true
MAXMIND_LICENSE_KEY=xxxxxx
MAXMIND_EDITION=GeoLite2-City

And the log :

hosting-plausible_db-1         | The files belonging to this database system will be owned by user "postgres".
hosting-plausible_db-1         | This user must also own the server process.
hosting-plausible_db-1         |
hosting-plausible_db-1         |
hosting-plausible_db-1         | The database cluster will be initialized with locale "en_US.utf8".
hosting-plausible_db-1         | The default database encoding has accordingly been set to "UTF8".
hosting-plausible_db-1         | The default text search configuration will be set to "english".
hosting-plausible_db-1         |
hosting-plausible_db-1         | Data page checksums are disabled.
hosting-plausible_db-1         |
hosting-plausible_db-1         | fixing permissions on existing directory /var/lib/postgresql/data ... ok
hosting-plausible_db-1         | creating subdirectories ... ok
hosting-plausible_db-1         | selecting dynamic shared memory implementation ... posix
hosting-plausible_db-1         | selecting default max_connections ...
hosting-plausible_db-1         | 100
hosting-plausible_db-1         | selecting default shared_buffers ...
hosting-plausible_db-1         | 128MB
hosting-plausible_db-1         | selecting default time zone ...
hosting-plausible_db-1         | UTC
hosting-plausible_db-1         | creating configuration files ...
hosting-plausible_db-1         | ok
hosting-plausible_db-1         | running bootstrap script ...
hosting-plausible_events_db-1  | Processing configuration file '/etc/clickhouse-server/config.xml'.
hosting-plausible_events_db-1  | Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
hosting-plausible_events_db-1  | Merging configuration file '/etc/clickhouse-server/config.d/logging.xml'.
hosting-plausible_events_db-1  | Logging warning to /var/log/clickhouse-server/clickhouse-server.log
hosting-plausible_events_db-1  | Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
hosting-plausible_db-1         | ok
hosting-plausible_db-1         | performing post-bootstrap initialization ...
hosting-plausible_events_db-1  | 2023.07.25 13:31:17.991339 [ 1 ] {} <Warning> Context: Linux transparent hugepages are set to "always". Check /sys/kernel/mm/transparent_hugepage/enabled
hosting-mail-1                 |     1 LOG: MAIN
hosting-mail-1                 |     1   exim 4.89 daemon started: pid=1, -q30m, listening for SMTP on port 25 (IPv6 and IPv4)
hosting-plausible_events_db-1  | 2023.07.25 13:31:18.235693 [ 1 ] {} <Warning> Access(local directory): File /var/lib/clickhouse/access/users.list doesn't exist
hosting-plausible_events_db-1  | 2023.07.25 13:31:18.235789 [ 1 ] {} <Warning> Access(local directory): Recovering lists in directory /var/lib/clickhouse/access/
hosting-plausible_db-1         | sh: locale: not found
hosting-plausible_db-1         | 2023-07-25 13:31:18.291 UTC [30] WARNING:  no usable system locales were found
hosting-plausible_events_db-1  | 2023.07.25 13:31:18.297268 [ 1 ] {} <Warning> Application: Listen [::]:8123 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 23.3.7.5 (official build)). If it is an IPv6
 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host>0.0.0.0</listen_host> . Example for disabled IPv4: <list
en_host>::</listen_host>
hosting-plausible_events_db-1  | 2023.07.25 13:31:18.297555 [ 1 ] {} <Warning> Application: Listen [::]:9000 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 23.3.7.5 (official build)). If it is an IPv6
 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host>0.0.0.0</listen_host> . Example for disabled IPv4: <list
en_host>::</listen_host>
hosting-plausible_events_db-1  | 2023.07.25 13:31:18.297804 [ 1 ] {} <Warning> Application: Listen [::]:9004 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 23.3.7.5 (official build)). If it is an IPv6
 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host>0.0.0.0</listen_host> . Example for disabled IPv4: <list
en_host>::</listen_host>
hosting-plausible_events_db-1  | 2023.07.25 13:31:18.298052 [ 1 ] {} <Warning> Application: Listen [::]:9005 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 23.3.7.5 (official build)). If it is an IPv6
 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host>0.0.0.0</listen_host> . Example for disabled IPv4: <list
en_host>::</listen_host>
hosting-plausible_events_db-1  | 2023.07.25 13:31:18.392062 [ 1 ] {} <Warning> Application: Listen [::]:9009 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 23.3.7.5 (official build)). If it is an IPv6
 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in <listen_host> element of configuration file. Example for disabled IPv6: <listen_host>0.0.0.0</listen_host> . Example for disabled IPv4: <list
en_host>::</listen_host>
hosting-plausible_db-1         | ok
hosting-plausible_db-1         | syncing data to disk ...
hosting-plausible_db-1         | initdb: warning: enabling "trust" authentication for local connections
hosting-plausible_db-1         | You can change this by editing pg_hba.conf or using the option -A, or
hosting-plausible_db-1         | --auth-local and --auth-host, the next time you run initdb.
hosting-plausible_db-1         | ok
hosting-plausible_db-1         |
hosting-plausible_db-1         |
hosting-plausible_db-1         | Success. You can now start the database server using:
hosting-plausible_db-1         |
hosting-plausible_db-1         |     pg_ctl -D /var/lib/postgresql/data -l logfile start
hosting-plausible_db-1         |
hosting-plausible_db-1         | waiting for server to start....
hosting-plausible_db-1         | 2023-07-25 13:31:18.903 UTC [36] LOG:  starting PostgreSQL 14.8 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
hosting-plausible_db-1         | 2023-07-25 13:31:18.907 UTC [36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
hosting-plausible_db-1         | 2023-07-25 13:31:18.921 UTC [37] LOG:  database system was shut down at 2023-07-25 13:31:18 UTC
hosting-plausible_db-1         | 2023-07-25 13:31:18.932 UTC [36] LOG:  database system is ready to accept connections
hosting-plausible_db-1         |  done
hosting-plausible_db-1         | server started
hosting-plausible_db-1         |
hosting-plausible_db-1         | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
hosting-plausible_db-1         |
hosting-plausible_db-1         |
hosting-plausible_db-1         | 2023-07-25 13:31:18.989 UTC [36] LOG:  received fast shutdown request
hosting-plausible_db-1         | waiting for server to shut down....
hosting-plausible_db-1         | 2023-07-25 13:31:18.993 UTC [36] LOG:  aborting any active transactions
hosting-plausible_db-1         | 2023-07-25 13:31:18.994 UTC [36] LOG:  background worker "logical replication launcher" (PID 43) exited with exit code 1
hosting-plausible_db-1         | 2023-07-25 13:31:18.995 UTC [38] LOG:  shutting down
hosting-plausible_db-1         | 2023-07-25 13:31:19.021 UTC [36] LOG:  database system is shut down
hosting-plausible_db-1         |  done
hosting-plausible_db-1         | server stopped
hosting-plausible_db-1         |
hosting-plausible_db-1         | PostgreSQL init process complete; ready for start up.
hosting-plausible_db-1         |
hosting-plausible_db-1         |
hosting-plausible_db-1         | 2023-07-25 13:31:19.110 UTC [1] LOG:  starting PostgreSQL 14.8 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
hosting-plausible_db-1         | 2023-07-25 13:31:19.110 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
hosting-plausible_db-1         | 2023-07-25 13:31:19.110 UTC [1] LOG:  listening on IPv6 address "::", port 5432
hosting-plausible_db-1         | 2023-07-25 13:31:19.118 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
hosting-plausible_db-1         | 2023-07-25 13:31:19.128 UTC [49] LOG:  database system was shut down at 2023-07-25 13:31:19 UTC
hosting-plausible_db-1         | 2023-07-25 13:31:19.134 UTC [1] LOG:  database system is ready to accept connections
hosting-plausible-1            | Loading plausible..
hosting-plausible-1            | Starting dependencies..
hosting-plausible-1            | Starting repos..
hosting-plausible-1            | create Plausible.Repo database if it doesn't exist
hosting-plausible_db-1         | 2023-07-25 13:31:28.697 UTC [57] FATAL:  database "plausible_db" does not exist
hosting-plausible_db-1         | 2023-07-25 13:31:28.697 UTC [56] FATAL:  database "plausible_db" does not exist
hosting-plausible_events_db-1  | 2023.07.25 13:31:28.719751 [ 48 ] {} <Error> DynamicQueryHandler: Code: 81. DB::Exception: Database plausible_events_db doesn't exist. (UNKNOWN_DATABASE), Stack trace (when copying this message, always include the lines below):
hosting-plausible_events_db-1  |
hosting-plausible_events_db-1  | 0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0xe1dc395 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 1. ? @ 0x89e5b44 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 2. DB::DatabaseCatalog::assertDatabaseExistsUnlocked(String const&) const @ 0x12e16706 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 3. DB::DatabaseCatalog::assertDatabaseExists(String const&) const @ 0x12e165d4 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 4. DB::Context::setCurrentDatabase(String const&) @ 0x12d713b1 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 5. DB::HTTPHandler::processQuery(DB::HTTPServerRequest&, DB::HTMLForm&, DB::HTTPServerResponse&, DB::HTTPHandler::Output&, std::optional<DB::CurrentThread::QueryScope>&) @ 0x149700f4 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 6. DB::HTTPHandler::handleRequest(DB::HTTPServerRequest&, DB::HTTPServerResponse&) @ 0x14974bee in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 7. DB::HTTPServerConnection::run() @ 0x149e367d in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 8. Poco::Net::TCPServerConnection::start() @ 0x179217d4 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 9. Poco::Net::TCPServerDispatcher::run() @ 0x179229fb in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 10. Poco::PooledThread::run() @ 0x17aaa287 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 11. Poco::ThreadImpl::runnableEntry(void*) @ 0x17aa7cbd in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 12. ? @ 0x7f9ba2d01609 in ?
hosting-plausible_events_db-1  | 13. clone @ 0x7f9ba2c26133 in ?
hosting-plausible_events_db-1  |  (version 23.3.7.5 (official build))
hosting-plausible_events_db-1  |
hosting-plausible_events_db-1  | 2023.07.25 13:31:28.720122 [ 49 ] {} <Error> DynamicQueryHandler: Code: 81. DB::Exception: Database plausible_events_db doesn't exist. (UNKNOWN_DATABASE), Stack trace (when copying this message, always include the lines below):
hosting-plausible_events_db-1  |
hosting-plausible_events_db-1  | 0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0xe1dc395 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 1. ? @ 0x89e5b44 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 2. DB::DatabaseCatalog::assertDatabaseExistsUnlocked(String const&) const @ 0x12e16706 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 3. DB::DatabaseCatalog::assertDatabaseExists(String const&) const @ 0x12e165d4 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 4. DB::Context::setCurrentDatabase(String const&) @ 0x12d713b1 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 5. DB::HTTPHandler::processQuery(DB::HTTPServerRequest&, DB::HTMLForm&, DB::HTTPServerResponse&, DB::HTTPHandler::Output&, std::optional<DB::CurrentThread::QueryScope>&) @ 0x149700f4 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 6. DB::HTTPHandler::handleRequest(DB::HTTPServerRequest&, DB::HTTPServerResponse&) @ 0x14974bee in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 7. DB::HTTPServerConnection::run() @ 0x149e367d in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 8. Poco::Net::TCPServerConnection::start() @ 0x179217d4 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 9. Poco::Net::TCPServerDispatcher::run() @ 0x179229fb in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 10. Poco::PooledThread::run() @ 0x17aaa287 in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 11. Poco::ThreadImpl::runnableEntry(void*) @ 0x17aa7cbd in /usr/bin/clickhouse
hosting-plausible_events_db-1  | 12. ? @ 0x7f9ba2d01609 in ?
hosting-plausible_events_db-1  | 13. clone @ 0x7f9ba2c26133 in ?
hosting-plausible_events_db-1  |  (version 23.3.7.5 (official build))
hosting-plausible_events_db-1  |
hosting-plausible-1            | 13:31:28.720 [error] Postgrex.Protocol (#PID<0.163.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "plausible_db" does not exist
hosting-plausible-1            | 13:31:28.720 [error] Postgrex.Protocol (#PID<0.164.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "plausible_db" does not exist
hosting-plausible-1            | 13:31:28.726 [error] Ch.Connection (#PID<0.172.0>) failed to connect: ** (Ch.Error) Code: 81. DB::Exception: Database plausible_events_db doesn't exist. (UNKNOWN_DATABASE) (version 23.3.7.5 (official build))
hosting-plausible-1            |
hosting-plausible-1            |
hosting-plausible-1            | 13:31:28.726 [error] Ch.Connection (#PID<0.171.0>) failed to connect: ** (Ch.Error) Code: 81. DB::Exception: Database plausible_events_db doesn't exist. (UNKNOWN_DATABASE) (version 23.3.7.5 (official build))
hosting-plausible-1            |
hosting-plausible-1            |
hosting-plausible-1            | create Plausible.IngestRepo database if it doesn't exist
hosting-plausible-1            | Creation of Db successful!
hosting-plausible-1            | Loading plausible..
hosting-plausible-1            | Starting dependencies..
hosting-plausible-1            | Starting repos..
hosting-plausible-1            | Running migrations for Elixir.Plausible.Repo
hosting-plausible-1            | Running migrations for Elixir.Plausible.IngestRepo
hosting-plausible-1            | Migrations successful!
^CGracefully stopping... (press Ctrl+C again to force)

Answered by ruslandoga

Jul 25, 2023

You can probably remove GEONAMES_SOURCE_FILE and IP_GEOLOCATION_DB and reintroduce GEONAMES_SOURCE_FILE (with a properly mounted geonames.csv) if it becomes a problem later.

And here's how to set up a custom geonames.csv (note that it's not strictly necessary)

Download it

$ curl -O https://s3.eu-central-1.wasabisys.com/plausible-application/geonames.csv

Mount it

docker-compose.yml

  plausible:
    image: plausible/analytics:v2.0.0
+   volumes:
+     - ./geonames.csv:/etc/app/geonames.csv:ro

Point Plausible to it

plausible-conf.env

+ GEONAMES_SOURCE_FILE=/etc/app/geonames.csv

More info: https://github.com/plausible/location#cities

View full answer

ruslandoga · 2023-07-25T14:13:07Z

ruslandoga
Jul 25, 2023
Collaborator

👋 @meepmeep

So what's the problem? :)

1 reply

ruslandoga Jul 25, 2023
Collaborator

Ah, sorry. I missed the title. FATAL: database "plausible_db" does not exist shouldn't be a problem. plausible checks if databases exist before creating them. Later in the logs plausible shows that the migration has been successful which is only possible if both ClickHouse and PostgreSQL are up and running.

meepmeep · 2023-07-25T14:25:09Z

meepmeep
Jul 25, 2023
Author

I tried to create the db with docker exec, and then remove the "entrypoint.sh db createdb", but it still fails.

2 replies

meepmeep Jul 25, 2023
Author

And it doesn't start 🙃

ruslandoga Jul 25, 2023
Collaborator

What makes you think it doesn't start? The provided logs do really look fine.

meepmeep · 2023-07-25T15:49:27Z

meepmeep
Jul 25, 2023
Author

Maybe I cut the log to early on this thread.

hosting-plausible-1            | create Plausible.IngestRepo database if it doesn't exist
hosting-plausible-1            | Creation of Db successful!
hosting-plausible-1            | Loading plausible..
hosting-plausible-1            | Starting dependencies..
hosting-plausible-1            | Starting repos..
hosting-plausible-1            | Running migrations for Elixir.Plausible.Repo
hosting-plausible-1            | Running migrations for Elixir.Plausible.IngestRepo
hosting-plausible-1            | Migrations successful!
hosting-plausible-1            | {"Kernel pid terminated",application_controller,"{application_start_failure,plausible,{bad_return,{{'Elixir.Plausible.Application',start,[normal,[]]},{'EXIT',{#{'__exc
hosting-plausible-1            | eption__' => true,'__struct__' => 'Elixir.File.Error',action => <<\"stream\">>,path => <<\"/etc/app/geonames.csv\">>,reason => enoent},[{'Elixir.Enumerable.File.Stream','-reduce/3-fun-0-',3,[{file,\"lib/file/stream.ex\"},{line,83}]},{'Eli
xir.Stream','-resource/3-fun-0-',5,[{file,\"lib/stream.ex\"},{line,1609}]},{'Elixir.Enumerable.Stream',do_each,4,[{file,\"lib/stream.ex\"},{line,1811}]},{'Elixir.Task.Supervised',stream_reduce,7,[{file,\"lib/task/supervised.ex\"},{line,323}]},{'Elixir.Stream',run
hosting-plausible-1            | ,1,[{file,\"lib/stream.ex\"},{l
hosting-plausible-1            | ine,689}]},{timer,tc,1,[{file,\"timer.erl\"},{line,235}]},{'Elixir.Location',load,1,[{file,\"lib/location.ex\"},{line,22}]},{'Elixir.Plausible.Application',start,2,[{file,\"lib/plausible/application.ex\"}
hosting-plausible-1            | ,{line,42}]}]}}}}}"}
hosting-plausible-1            | Kernel pid terminated (application_controller) ({application_start_failure,plausible,{bad_return,{{'Elixir.Plausible.Application',start,[normal,[]]},{'EXIT',{#{'__exception__' => true,'__struct__' => 'Elixir.File.Error',action => <<"strea
m">>,path => <<"/etc/app/geonames.csv">>,reason => enoe
hosting-plausible-1            | nt},[{'Elixir.Enumerable.File.Stream','-reduce/3-fun-0-',3,[{file,"lib/file/stream.ex"},{line,83}]},{'Elixir.Stream','-resource/3-fun-0-',5,[{file,"lib/stream.ex"},{line,1609}]},{'Elixir.Enumerable.Stream',do_each,4,[{file,"lib/stream.ex"
},{line,1811}]},{'Elixir.Task.Supervised',stream_reduce,7,[{file,"lib/task/supervised.ex"},{line,323}]},{'Elixir.Stream',run,1,[{file,"lib/stream.ex"},{line,689}]},{timer,tc,1,[{file,"timer.erl"},{line,235}]},{'Elixir.Location',load,1,[{file,"lib/location.ex"},{line,22}]
},{'Elixir.Plausible.Application',start,2,[{file,"lib/plausible/application.ex"},{line,42}]}]}}}}})
hosting-plausible-1            |
hosting-plausible-1            | Crash dump is being written to: erl_crash.dump...
hosting-plausible-1 exited with code 0

And then it goes on infinite loop (restarting the hosting-plausible-1 container, crashing, etc.)

5 replies

ruslandoga Jul 25, 2023
Collaborator

This error means /etc/app/geonames.csv doesn't exist. Please check that it's properly mounted into the container.

meepmeep Jul 25, 2023
Author

well simething is wrong with geoname.csv and/or maxmind db.
I'm quite lost on this one.

What should I create outside of the container ?
I have 3 lines in my configuration for that :
-- GEONAMES_SOURCE_FILE=/etc/app/geonames.csv
-- IP_GEOLOCATION_DB=/etc/app/geolite2-city.mmdb
-- MAXMIND_LICENSE_KEY=xxxxxx
-- MAXMIND_EDITION=GeoLite2-City

And no file / directory created locally.

meepmeep Jul 25, 2023
Author

well, documentation for v2.0 said that everything is handle from Plausible... But I still need to mount it inside the docker volume ?

ruslandoga Jul 25, 2023
Collaborator

You can probably remove GEONAMES_SOURCE_FILE and IP_GEOLOCATION_DB and reintroduce GEONAMES_SOURCE_FILE (with a properly mounted geonames.csv) if it becomes a problem later.

And here's how to set up a custom geonames.csv (note that it's not strictly necessary)

Download it

$ curl -O https://s3.eu-central-1.wasabisys.com/plausible-application/geonames.csv

Mount it

docker-compose.yml

  plausible:
    image: plausible/analytics:v2.0.0
+   volumes:
+     - ./geonames.csv:/etc/app/geonames.csv:ro

Point Plausible to it

plausible-conf.env

+ GEONAMES_SOURCE_FILE=/etc/app/geonames.csv

More info: https://github.com/plausible/location#cities

Answer selected by meepmeep

meepmeep Jul 25, 2023
Author

thank you :)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fresh install - unable to start docker : "FATAL: database "plausible_db" does not exist" #3193

{{title}}

Replies: 3 comments 8 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Fresh install - unable to start docker : "FATAL: database "plausible_db" does not exist" #3193

meepmeep Jul 25, 2023

Replies: 3 comments · 8 replies

ruslandoga Jul 25, 2023 Collaborator

ruslandoga Jul 25, 2023 Collaborator

meepmeep Jul 25, 2023 Author

meepmeep Jul 25, 2023 Author

ruslandoga Jul 25, 2023 Collaborator

meepmeep Jul 25, 2023 Author

ruslandoga Jul 25, 2023 Collaborator

meepmeep Jul 25, 2023 Author

meepmeep Jul 25, 2023 Author

ruslandoga Jul 25, 2023 Collaborator

meepmeep Jul 25, 2023 Author

meepmeep
Jul 25, 2023

Replies: 3 comments 8 replies

ruslandoga
Jul 25, 2023
Collaborator

ruslandoga Jul 25, 2023
Collaborator

meepmeep
Jul 25, 2023
Author

meepmeep Jul 25, 2023
Author

ruslandoga Jul 25, 2023
Collaborator

meepmeep
Jul 25, 2023
Author

ruslandoga Jul 25, 2023
Collaborator

meepmeep Jul 25, 2023
Author

meepmeep Jul 25, 2023
Author

ruslandoga Jul 25, 2023
Collaborator

meepmeep Jul 25, 2023
Author