Plausible not starting #1536

alkarkhi · 2021-12-13T09:02:18Z

alkarkhi
Dec 13, 2021

When I go to the webpage it gives me a 502 error. When I use curl localhost:8000 in the server it gives me a curl: (56) Recv failure: Connection reset by peer. The same error is also mentioned in nginx logs. I also reinstalled the container but the same issue is there. I'm not sure what the issue is but I think it's a port issue. I have another container using port 9000 (which plausible used for clickhouse) and port 25 (which plausible uses for smtp). How do I change these ports for plausible? Is it also possible to disable the smtp server since I already have another one I could use?

Fokarr · 2021-12-13T17:17:07Z

Fokarr
Dec 13, 2021

It could be due to your firewall. try to open the 8000er port with:
sudo ufw allow 8000/tcp

1 reply

alkarkhi Dec 13, 2021
Author

Yes but I'm configuring it through a reverse proxy so only port 80/443 needs to be open afaik

bedax · 2021-12-25T00:12:12Z

bedax
Dec 25, 2021

I'm also getting this error, with no firewall or reverse proxy

3 replies

bedax Dec 25, 2021

Note I used the following:

git clone https://github.com/plausible/hosting
cd hosting
# set up the .env file
sudo docker-compose up -d

bedax Dec 25, 2021

It's working for me now. Turns out there's a delay while the Plausible docker container sets itself up, and any interaction with it before it has finished results in the above error.

bedax Dec 25, 2021

This is also caused when Plausible fails to start for whatever reason; see docker logs plausible

nsgoyat · 2022-10-18T07:14:17Z

nsgoyat
Oct 18, 2022

Hey Folks!
I recently configured Plausible on Ubuntu 20.04 using this guide: https://www.digitalocean.com/community/tutorials/how-to-install-plausible-analytics-on-ubuntu-22-04

I use Hetzner Server with 80, 443, and SSH port being opened for the incoming connections. Plausible was working totally fine for me but due to the high-traffic website, I resized the Plausible server to have more vCPU available.

Now, after the server resize, Plausible isn't working for me at all.

I get "502 Bad Gateway - nginx" when I open my Plausible URL.

Also, curl http:https://localhost:8000 returns the following error:
curl: (56) Recv failure: Connection reset by peer

I also ran docker logs plausible and got the following output:

Loading plausible..
Starting dependencies..
Starting repos..
create Plausible.Repo database if it doesn't exist
create Plausible.ClickhouseRepo database if it doesn't exist
07:06:47.036 [error] Task #PID<0.197.0> started from #PID<0.94.0> terminating
** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 5998ms. This means requests are coming in and your connection pool cannot serve them fast enough.

It seems Plausible is unable to start and I just can't get to fix it :(

4 replies

ruslandoga Oct 18, 2022
Collaborator

@nsgoyat 👋

What do logs say about other containers, plausible_db and plausible_events_db?

nsgoyat Oct 18, 2022

Thank you very much for such a quick reply, @ruslandoga

I am new to Docker/Containers stuff still I will try my best to share the information. I have the following 4 Containers as an output of sudo docker compose up --detach

Output of docker logs plausible-plausible_db-1

PostgreSQL Database directory appears to contain a database; Skipping initializa                                                                                                 tion

2022-10-15 18:35:04.423 UTC [1] LOG:  starting PostgreSQL 14.5 on x86_64-pc-linu                                                                                                 x-musl, compiled by gcc (Alpine 11.2.1_git20220219) 11.2.1 20220219, 64-bit
2022-10-15 18:35:04.424 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port                                                                                                  5432
2022-10-15 18:35:04.424 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2022-10-15 18:35:04.427 UTC [1] LOG:  listening on Unix socket "/var/run/postgre                                                                                                 sql/.s.PGSQL.5432"
2022-10-15 18:35:04.433 UTC [21] LOG:  database system was shut down at 2022-10-                                                                                                 15 18:34:47 UTC
2022-10-15 18:35:04.437 UTC [1] LOG:  database system is ready to accept connect                                                                                                 ions
2022-10-15 18:39:20.498 UTC [1] LOG:  received fast shutdown request
2022-10-15 18:39:20.499 UTC [1] LOG:  aborting any active transactions
2022-10-15 18:39:20.509 UTC [1] LOG:  background worker "logical replication lau                                                                                                 ncher" (PID 27) exited with exit code 1
2022-10-15 18:39:20.509 UTC [22] LOG:  shutting down
2022-10-15 18:39:20.528 UTC [1] LOG:  database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initializa                                                                                                 tion

2022-10-15 18:39:42.374 UTC [1] LOG:  starting PostgreSQL 14.5 on x86_64-pc-linu                                                                                                 x-musl, compiled by gcc (Alpine 11.2.1_git20220219) 11.2.1 20220219, 64-bit
2022-10-15 18:39:42.374 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port                                                                                                  5432
2022-10-15 18:39:42.374 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2022-10-15 18:39:42.376 UTC [1] LOG:  listening on Unix socket "/var/run/postgre                                                                                                 sql/.s.PGSQL.5432"
2022-10-15 18:39:42.380 UTC [21] LOG:  database system was shut down at 2022-10-                                                                                                 15 18:39:20 UTC
2022-10-15 18:39:42.385 UTC [1] LOG:  database system is ready to accept connect                                                                                                 ions

PostgreSQL Database directory appears to contain a database; Skipping initializa                                                                                                 tion

2022-10-18 05:40:47.955 UTC [1] LOG:  starting PostgreSQL 14.5 on x86_64-pc-linu                                                                                                 x-musl, compiled by gcc (Alpine 11.2.1_git20220219) 11.2.1 20220219, 64-bit
2022-10-18 05:40:47.955 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port                                                                                                  5432
2022-10-18 05:40:47.955 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2022-10-18 05:40:47.957 UTC [1] LOG:  listening on Unix socket "/var/run/postgre                                                                                                 sql/.s.PGSQL.5432"
2022-10-18 05:40:47.961 UTC [20] LOG:  database system was interrupted; last kno                                                                                                 wn up at 2022-10-18 05:30:39 UTC
2022-10-18 05:40:48.043 UTC [20] LOG:  database system was not properly shut dow                                                                                                 n; automatic recovery in progress
2022-10-18 05:40:48.045 UTC [20] LOG:  redo starts at 0/219BDF0
2022-10-18 05:40:48.045 UTC [20] LOG:  invalid record length at 0/219BED8: wante                                                                                                 d 24, got 0
2022-10-18 05:40:48.045 UTC [20] LOG:  redo done at 0/219BEA0 system usage: CPU:                                                                                                  user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2022-10-18 05:40:48.053 UTC [1] LOG:  database system is ready to accept connect                                                                                                 ions
2022-10-18 05:49:18.661 UTC [1] LOG:  received fast shutdown request
2022-10-18 05:49:18.662 UTC [1] LOG:  aborting any active transactions
2022-10-18 05:49:18.665 UTC [1] LOG:  background worker "logical replication lau                                                                                                 ncher" (PID 26) exited with exit code 1
2022-10-18 05:49:18.665 UTC [21] LOG:  shutting down
2022-10-18 05:49:18.677 UTC [1] LOG:  database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initializa                                                                                                 tion

2022-10-18 05:49:40.489 UTC [1] LOG:  starting PostgreSQL 14.5 on x86_64-pc-linu                                                                                                 x-musl, compiled by gcc (Alpine 11.2.1_git20220219) 11.2.1 20220219, 64-bit
2022-10-18 05:49:40.489 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port                                                                                                  5432
2022-10-18 05:49:40.489 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2022-10-18 05:49:40.492 UTC [1] LOG:  listening on Unix socket "/var/run/postgre                                                                                                 sql/.s.PGSQL.5432"
2022-10-18 05:49:40.496 UTC [21] LOG:  database system was shut down at 2022-10-                                                                                                 18 05:49:18 UTC
2022-10-18 05:49:40.503 UTC [1] LOG:  database system is ready to accept connect                                                                                                 ions
2022-10-18 06:22:46.272 UTC [1] LOG:  received fast shutdown request
2022-10-18 06:22:46.273 UTC [1] LOG:  aborting any active transactions
2022-10-18 06:22:46.275 UTC [1] LOG:  background worker "logical replication lau                                                                                                 ncher" (PID 27) exited with exit code 1
2022-10-18 06:22:46.275 UTC [22] LOG:  shutting down
2022-10-18 06:22:46.288 UTC [1] LOG:  database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initializa                                                                                                 tion

2022-10-18 06:23:07.612 UTC [1] LOG:  starting PostgreSQL 14.5 on x86_64-pc-linu                                                                                                 x-musl, compiled by gcc (Alpine 11.2.1_git20220219) 11.2.1 20220219, 64-bit
2022-10-18 06:23:07.612 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port                                                                                                  5432
2022-10-18 06:23:07.612 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2022-10-18 06:23:07.614 UTC [1] LOG:  listening on Unix socket "/var/run/postgre                                                                                                 sql/.s.PGSQL.5432"
2022-10-18 06:23:07.618 UTC [21] LOG:  database system was shut down at 2022-10-                                                                                                 18 06:22:46 UTC
2022-10-18 06:23:07.625 UTC [1] LOG:  database system is ready to accept connect                                                                                                 ions
2022-10-18 06:38:23.700 UTC [1] LOG:  received fast shutdown request
2022-10-18 06:38:23.701 UTC [1] LOG:  aborting any active transactions
2022-10-18 06:38:23.703 UTC [1] LOG:  background worker "logical replication lau                                                                                                 ncher" (PID 27) exited with exit code 1
2022-10-18 06:38:23.704 UTC [217] FATAL:  terminating connection due to administ                                                                                                 rator command
2022-10-18 06:38:23.705 UTC [218] FATAL:  terminating connection due to administ                                                                                                 rator command
2022-10-18 06:38:23.705 UTC [22] LOG:  shutting down
2022-10-18 06:38:23.714 UTC [1] LOG:  database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initializa                                                                                                 tion

2022-10-18 06:38:44.770 UTC [1] LOG:  starting PostgreSQL 14.5 on x86_64-pc-linu                                                                                                 x-musl, compiled by gcc (Alpine 11.2.1_git20220219) 11.2.1 20220219, 64-bit
2022-10-18 06:38:44.770 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port                                                                                                  5432
2022-10-18 06:38:44.770 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2022-10-18 06:38:44.772 UTC [1] LOG:  listening on Unix socket "/var/run/postgre                                                                                                 sql/.s.PGSQL.5432"
2022-10-18 06:38:44.775 UTC [21] LOG:  database system was shut down at 2022-10-                                                                                                 18 06:38:23 UTC
2022-10-18 06:38:44.782 UTC [1] LOG:  database system is ready to accept connect                                                                                                 ions

Output of docker logs plausible-plausible_events_db-1

0. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0xb8a4c1a in /usr/bin/clickhouse
1. DB::Exception::Exception<unsigned long&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, DB::SettingFieldNumber<unsigned long> const&>(int, fmt::v8::basic_format_string<char, fmt::v8::type_identity<unsigned long&>::type, fmt::v8::type_identity<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >::type, fmt::v8::type_identity<DB::SettingFieldNumber<unsigned long> const&>::type>, unsigned long&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&&, DB::SettingFieldNumber<unsigned long> const&) @ 0x16b84b2e in /usr/bin/clickhouse
2. DB::MergeTreeData::loadDataPartsFromDisk(std::__1::vector<std::__1::shared_ptr<DB::IMergeTreeDataPart const>, std::__1::allocator<std::__1::shared_ptr<DB::IMergeTreeDataPart const> > >&, std::__1::vector<std::__1::shared_ptr<DB::IMergeTreeDataPart const>, std::__1::allocator<std::__1::shared_ptr<DB::IMergeTreeDataPart const> > >&, ThreadPoolImpl<ThreadFromGlobalPool>&, unsigned long, std::__1::queue<std::__1::vector<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::shared_ptr<DB::IDisk> >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::shared_ptr<DB::IDisk> > > >, std::__1::deque<std::__1::vector<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::shared_ptr<DB::IDisk> >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::shared_ptr<DB::IDisk> > > >, std::__1::allocator<std::__1::vector<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::shared_ptr<DB::IDisk> >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::shared_ptr<DB::IDisk> > > > > > >&, bool, std::__1::shared_ptr<DB::MergeTreeSettings const> const&) @ 0x16b83f68 in /usr/bin/clickhouse
3. DB::MergeTreeData::loadDataParts(bool) @ 0x16b86bbb in /usr/bin/clickhouse
4. DB::StorageMergeTree::StorageMergeTree(DB::StorageID const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, DB::StorageInMemoryMetadata const&, bool, std::__1::shared_ptr<DB::Context>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, DB::MergeTreeData::MergingParams const&, std::__1::unique_ptr<DB::MergeTreeSettings, std::__1::default_delete<DB::MergeTreeSettings> >, bool) @ 0x16979847 in /usr/bin/clickhouse
5. ? @ 0x16dfcc26 in /usr/bin/clickhouse
6. DB::StorageFactory::get(DB::ASTCreateQuery const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::shared_ptr<DB::Context>, std::__1::shared_ptr<DB::Context>, DB::ColumnsDescription const&, DB::ConstraintsDescription const&, bool) const @ 0x167d685d in /usr/bin/clickhouse
7. DB::createTableFromAST(DB::ASTCreateQuery, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::shared_ptr<DB::Context>, bool) @ 0x15895228 in /usr/bin/clickhouse
8. DB::DatabaseOrdinary::loadTableFromMetadata(std::__1::shared_ptr<DB::Context>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, DB::QualifiedTableName const&, std::__1::shared_ptr<DB::IAST> const&, bool) @ 0x15931bea in /usr/bin/clickhouse
9. ? @ 0x159615cb in /usr/bin/clickhouse
10. ThreadPoolImpl<ThreadFromGlobalPool>::worker(std::__1::__list_iterator<ThreadFromGlobalPool, void*>) @ 0xb95002a in /usr/bin/clickhouse
11. ThreadFromGlobalPool::ThreadFromGlobalPool<void ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()>(void&&)::'lambda'()::operator()() @ 0xb952005 in /usr/bin/clickhouse
12. ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) @ 0xb94d9b7 in /usr/bin/clickhouse
13. ? @ 0xb950ddd in /usr/bin/clickhouse
14. ? @ 0x7fa646abf609 in ?
15. clone @ 0x7fa6469e4133 in ?
 (version 22.6.9.11 (official build))
2022.10.18 07:31:15.595626 [ 43 ] {} <Error> Application: DB::Exception: Suspiciously many (12 parts, 0.00 B in total) broken parts to remove while maximum allowed broken parts count is 10. You can change the maximum value with merge tree setting 'max_suspicious_broken_parts' in <merge_tree> configuration section or in table settings in .sql file (don't forget to return setting back to default value): Cannot attach table `plausible_events_db`.`events` from metadata file /var/lib/clickhouse/store/0e1/0e19f612-4c47-4ae8-acd0-2415a9720708/events.sql from query ATTACH TABLE plausible_events_db.events UUID 'b1545c30-4a6b-4973-b922-f9da7f6e60eb' (`name` String, `domain` String, `user_id` UInt64, `session_id` UInt64, `hostname` String, `pathname` String, `referrer` String, `referrer_source` String, `country_code` LowCardinality(FixedString(2)), `screen_size` LowCardinality(String), `operating_system` LowCardinality(String), `browser` LowCardinality(String), `timestamp` DateTime, `utm_medium` String, `utm_source` String, `utm_campaign` String, `meta.key` Array(String), `meta.value` Array(String), `browser_version` LowCardinality(String), `operating_system_version` LowCardinality(String)) ENGINE = MergeTree PARTITION BY toYYYYMM(timestamp) ORDER BY (name, domain, user_id, timestamp) SAMPLE BY user_id SETTINGS index_granularity = 8192

ruslandoga Oct 18, 2022
Collaborator

Seems like clickhouse fails to start up.

Relevant error message:

2022.10.18 07:31:15.595626 [ 43 ] {} Application: DB::Exception: Suspiciously many (12 parts, 0.00 B in total) broken parts to remove while maximum allowed broken parts count is 10. You can change the maximum value with merge tree setting 'max_suspicious_broken_parts' in <merge_tree> configuration section or in table settings in .sql file (don't forget to return setting back to default value): Cannot attach table plausible_events_db.events from metadata file /var/lib/clickhouse/store/0e1/0e19f612-4c47-4ae8-acd0-2415a9720708/events.sql from query ATTACH TABLE plausible_events_db.events UUID 'b1545c30-4a6b-4973-b922-f9da7f6e60eb' (name String, domain String, user_id UInt64, session_id UInt64, hostname String, pathname String, referrer String, referrer_source String, country_code LowCardinality(FixedString(2)), screen_size LowCardinality(String), operating_system LowCardinality(String), browser LowCardinality(String), timestamp DateTime, utm_medium String, utm_source String, utm_campaign String, meta.key Array(String), meta.value Array(String), browser_version LowCardinality(String), operating_system_version LowCardinality(String)) ENGINE = MergeTree PARTITION BY toYYYYMM(timestamp) ORDER BY (name, domain, user_id, timestamp) SAMPLE BY user_id SETTINGS index_granularity = 8192

See https://kb.altinity.com/altinity-kb-setup-and-maintenance/suspiciously-many-broken-parts/

Modifying config is probably enough to make it work.

nsgoyat Oct 18, 2022

Ah! Probably, I will set up a new Plausible instance as the resolution sound out of my knowledge scope. Thank you very much for the very quick response @ruslandoga :)

ElMahdiAboulmanadel · 2022-12-04T16:23:57Z

ElMahdiAboulmanadel
Dec 4, 2022

I have the same issue and when I try : docker logs plausible_plausible_1
I get the following logs :

Crash dump is being written to: erl_crash.dump...done
ERROR! Config provider Config.Reader failed with:
** (Jason.DecodeError) unexpected byte at position 38: 0x70 ("p")
    lib/jason.ex:92: Jason.decode!/2
    (stdlib 3.17.1) erl_eval.erl:685: :erl_eval.do_apply/6
    (stdlib 3.17.1) erl_eval.erl:446: :erl_eval.expr/5
    (elixir 1.13.4) src/elixir.erl:296: :elixir.recur_eval/3
    (elixir 1.13.4) src/elixir.erl:274: :elixir.eval_forms/3
    (elixir 1.13.4) lib/code.ex:404: Code.validated_eval_string/3
    (elixir 1.13.4) lib/config.ex:260: Config.__eval__!/3
    (elixir 1.13.4) lib/config/reader.ex:92: Config.Reader.read!/2

5 replies

bilyboy785 Dec 4, 2022

Same issue here. Infos :

Plausible Self Hosted : Docker
Docker Version : Docker version 20.10.21, build baeda1f
Host informations : 5.4.0-97-generic #110-Ubuntu SMP Thu Jan 13 18:22:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Compose version : 3.3
Docker tag : latest

Error :

ERROR! Config provider Config.Reader failed with:
** (Jason.DecodeError) unexpected byte at position 38: 0x70 ("p")
    lib/jason.ex:92: Jason.decode!/2
    (stdlib 3.17.1) erl_eval.erl:685: :erl_eval.do_apply/6
    (stdlib 3.17.1) erl_eval.erl:446: :erl_eval.expr/5
    (elixir 1.13.4) src/elixir.erl:296: :elixir.recur_eval/3
    (elixir 1.13.4) src/elixir.erl:274: :elixir.eval_forms/3
    (elixir 1.13.4) lib/code.ex:404: Code.validated_eval_string/3
    (elixir 1.13.4) lib/config.ex:260: Config.__eval__!/3
    (elixir 1.13.4) lib/config/reader.ex:92: Config.Reader.read!/2

ruslandoga Dec 5, 2022
Collaborator

@bilyboy785 @ElMahdiAboulmanadel 👋

What version are you running? If it's 1.5, please see #2491 (comment)

bilyboy785 Dec 5, 2022

It's Works, thanks !

ElMahdiAboulmanadel Dec 5, 2022

It worked here! Thanks a lot!

ruslandoga Dec 7, 2022
Collaborator

v1.5.1 has been released with a fix.

bilyboy785 · 2022-12-04T17:56:27Z

bilyboy785
Dec 4, 2022

Same here #1536 (reply in thread)

0 replies

artfulrobot · 2023-06-05T10:48:38Z

artfulrobot
Jun 5, 2023

I'm new here, but also getting these errors.

$ docker-compose up
Starting plausibe_plausible_events_db_1 ... done
Starting plausibe_plausible_db_1        ... done
Starting plausibe_mail_1                ... done
Starting plausibe_plausible_1           ... done
Attaching to plausibe_plausible_events_db_1, plausibe_mail_1, plausibe_plausible_db_1, plausibe_plausible_1
mail_1                 |     1 LOG: MAIN
mail_1                 |     1   exim 4.89 daemon started: pid=1, -q30m, listening for SMTP on port 25 (IPv6 and IPv4)
plausible_db_1         | 
plausible_db_1         | PostgreSQL Database directory appears to contain a database; Skipping initialization
plausible_db_1         | 
plausible_db_1         | 2023-06-05 10:13:52.598 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
plausible_db_1         | 2023-06-05 10:13:52.598 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
plausible_db_1         | 2023-06-05 10:13:52.598 UTC [1] LOG:  listening on IPv6 address "::", port 5432
plausible_db_1         | 2023-06-05 10:13:52.600 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
plausible_db_1         | 2023-06-05 10:13:52.603 UTC [22] LOG:  database system was shut down at 2023-06-05 10:06:37 UTC
plausible_db_1         | 2023-06-05 10:13:52.609 UTC [1] LOG:  database system is ready to accept connections
plausible_events_db_1  | Processing configuration file '/etc/clickhouse-server/config.xml'.
plausible_events_db_1  | Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
plausible_events_db_1  | Merging configuration file '/etc/clickhouse-server/config.d/logging.xml'.
plausible_events_db_1  | Logging warning to /var/log/clickhouse-server/clickhouse-server.log
plausible_events_db_1  | Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
plausible_events_db_1  | 2023.06.05 10:13:52.769688 [ 43 ] {} <Warning> Context: Linux is not using a fast TSC clock source. Performance can be degraded. Check /sys/devices/system/clocksource/clocksource0/current_clocksource
plausible_events_db_1  | 2023.06.05 10:13:52.770320 [ 43 ] {} <Warning> Context: Linux transparent hugepages are set to "always". Check /sys/kernel/mm/transparent_hugepage/enabled
plausible_1            | Loading plausible..
plausible_1            | Starting dependencies..
plausible_1            | Starting repos..
plausible_1            | create Plausible.Repo database if it doesn't exist
plausible_1            | create Plausible.ClickhouseRepo database if it doesn't exist
plausible_1            | Creation of Db successful!
plausible_1            | Loading plausible..
plausible_1            | Starting dependencies..
plausible_1            | Starting repos..
plausible_1            | Running migrations for Elixir.Plausible.Repo
plausible_1            | Running migrations for Elixir.Plausible.ClickhouseRepo
plausible_1            | Migrations successful!

My config:

ADMIN_USER_NAME=me
[email protected]
ADMIN_USER_PASSWORD=password123ofcourse
BASE_URL=https://valid.example.org
SECRET_KEY_BASE={REDACTED_LONG_STR}
LISTEN_IP=127.0.0.1
RELEASE_DISTRIBUTION=none
ERL_EPMD_ADDRESS=127.0.0.1

But then

curl http:https://127.0.0.1:8000
curl: (56) Recv failure: Connection reset by peer

(note this is different to when it's not running which gives: curl: (7) Failed to connect to 127.0.0.1 port 8000: Connection refused)

It looks like it's running but just can't get any life out of it.

Firewall-wise, I have got a firewall in place but I've configured it as I have done for other docker-compose projects, so I feel that should be ok. And I'm connecting (trying to) from localhost with curl. And there's nothing created in the firewall logs when I do the curl command (the firewall logs everything it drops/rejects/doesn't understand). I've also just installed umami via docker-compose without a hitch, so yep, it's not the firewall.

Using the hosting git repo which specifies plausible/analytics:v1.5 as the image (I've tried changing it to v1.5.1 too - still no beans.)

5 replies

ruslandoga Jun 5, 2023
Collaborator

👋 @artfulrobot

Could you please try removing LISTEN_IP from your config?

When you run a service inside a container and bind it to the IP address 127.0.0.1 it's binding to the container's internal loopback interface, not the host's. Containers have their own network stack and their own 127.0.0.1 interface. Therefore, a service bound to 127.0.0.1 in a container isn't reachable from the host or any other containers.

ruslandoga Jun 5, 2023
Collaborator

Also note that ADMIN_ env vars are deprecated and no-op since v1.5. And RELEASE_DISTRIBUTION is most likely unnecessary as well (and it would cause problems during v2.0 migration).

artfulrobot Jun 5, 2023

Thanks @ruslandoga. I'd added the LISTEN_IP as ipv6 is disabled. But I removed it and the others and did docker-compose down and then up again. Still the same symptoms. curl: (56) Recv failure: Connection reset by peer

ruslandoga Jun 5, 2023
Collaborator

You might need to recreate the container, not just restart it. Env vars are not updated inside the container once it has been created.

artfulrobot Jun 5, 2023

Ah ha! it's working. Thanks!

Plausible not starting #1536

Replies: 6 comments · 18 replies

alkarkhi Dec 13, 2021 Author

ruslandoga Oct 18, 2022 Collaborator

ruslandoga Oct 18, 2022 Collaborator

ruslandoga Dec 5, 2022 Collaborator

ruslandoga Dec 7, 2022 Collaborator

ruslandoga Jun 5, 2023 Collaborator

ruslandoga Jun 5, 2023 Collaborator

ruslandoga Jun 5, 2023 Collaborator

Replies: 6 comments 18 replies

alkarkhi Dec 13, 2021
Author

ruslandoga Oct 18, 2022
Collaborator

ruslandoga Oct 18, 2022
Collaborator

ruslandoga Dec 5, 2022
Collaborator

ruslandoga Dec 7, 2022
Collaborator

ruslandoga Jun 5, 2023
Collaborator

ruslandoga Jun 5, 2023
Collaborator

ruslandoga Jun 5, 2023
Collaborator