docker compose logs says

hosting_plausible_db_1  | 
hosting_plausible_db_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
hosting_plausible_db_1  | 
hosting_plausible_db_1  | 2024-10-21 06:55:41.654 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
hosting_plausible_db_1  | 2024-10-21 06:55:41.667 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
hosting_plausible_db_1  | 2024-10-21 06:55:41.667 UTC [1] LOG:  listening on IPv6 address "::", port 5432
hosting_plausible_db_1  | 2024-10-21 06:55:41.681 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
hosting_plausible_db_1  | 2024-10-21 06:55:41.699 UTC [27] LOG:  database system was interrupted; last known up at 2024-10-21 06:50:47 UTC
hosting_plausible_db_1  | 2024-10-21 06:55:41.779 UTC [27] LOG:  database system was not properly shut down; automatic recovery in progress
hosting_plausible_db_1  | 2024-10-21 06:55:41.809 UTC [27] LOG:  redo starts at 0/15227B0
hosting_plausible_db_1  | 2024-10-21 06:55:41.809 UTC [27] LOG:  invalid record length at 0/1522898: expected at least 24, got 0
hosting_plausible_db_1  | 2024-10-21 06:55:41.809 UTC [27] LOG:  redo done at 0/1522860 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
hosting_plausible_db_1  | 2024-10-21 06:55:41.826 UTC [25] LOG:  checkpoint starting: end-of-recovery immediate wait
hosting_plausible_db_1  | 2024-10-21 06:55:41.843 UTC [25] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.022 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB; lsn=0/1522898, redo lsn=0/1522898
hosting_plausible_db_1  | 2024-10-21 06:55:41.901 UTC [1] LOG:  database system is ready to accept connections
hosting_plausible_db_1  | 2024-10-21 06:57:36.845 UTC [31] FATAL:  database "plausible_db" does not exist
hosting_plausible_db_1  | 2024-10-21 06:57:36.845 UTC [32] FATAL:  database "plausible_db" does not exist
hosting_plausible_db_1  | 2024-10-21 07:00:41.940 UTC [25] LOG:  checkpoint starting: time
hosting_plausible_db_1  | 2024-10-21 07:02:14.729 UTC [25] LOG:  checkpoint complete: wrote 929 buffers (5.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=92.771 s, sync=0.004 s, total=92.790 s; sync files=300, longest=0.002 s, average=0.001 s; distance=4309 kB, estimate=4309 kB; lsn=0/1957DF8, redo lsn=0/1957DC0
hosting_plausible_db_1  | 
hosting_plausible_db_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
hosting_plausible_db_1  | 
hosting_plausible_db_1  | 2024-10-21 07:24:33.616 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
hosting_plausible_db_1  | 2024-10-21 07:24:33.617 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
hosting_plausible_db_1  | 2024-10-21 07:24:33.617 UTC [1] LOG:  listening on IPv6 address "::", port 5432
hosting_plausible_db_1  | 2024-10-21 07:24:33.624 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
hosting_plausible_db_1  | 2024-10-21 07:24:33.635 UTC [28] LOG:  database system was shut down at 2024-10-21 07:23:32 UTC
hosting_plausible_db_1  | 2024-10-21 07:24:33.665 UTC [1] LOG:  database system is ready to accept connections
hosting_plausible_db_1  | 2024-10-21 07:29:33.722 UTC [26] LOG:  checkpoint starting: time
hosting_plausible_db_1  | 2024-10-21 07:29:33.803 UTC [26] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.028 s, sync=0.012 s, total=0.083 s; sync files=2, longest=0.006 s, average=0.006 s; distance=0 kB, estimate=0 kB; lsn=0/1957F90, redo lsn=0/1957F58
hosting_plausible_events_db_1  | ClickHouse Database directory appears to contain a database; Skipping initialization
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_events_db_1  | 2024.10.21 10:05:52.669826 [ 1 ] {} <Warning> Context: Linux is not using a fast clock source. Performance can be degraded. Check /sys/devices/system/clocksource/clocksource0/current_clocksource
hosting_plausible_events_db_1  | 2024.10.21 10:05:52.674343 [ 1 ] {} <Warning> Context: Linux threads max count is too low. Check /proc/sys/kernel/threads-max
hosting_plausible_events_db_1  | 2024.10.21 10:05:52.674533 [ 1 ] {} <Warning> Context: Delay accounting is not enabled, OSIOWaitMicroseconds will not be gathered. You can enable it using `echo 1 > /proc/sys/kernel/task_delayacct` or by using sysctl.
hosting_plausible_events_db_1  | 2024.10.21 10:05:52.674616 [ 1 ] {} <Warning> Context: Available memory at server startup is too low (2GiB).
hosting_plausible_events_db_1  | 2024.10.21 10:05:56.012438 [ 1 ] {} <Warning> Context: Maximum number of threads is lower than 30000. There could be problems with handling a lot of simultaneous queries.
hosting_plausible_events_db_1  | 2024.10.21 10:05:56.080668 [ 1 ] {} <Error> Application: Disabling cgroup memory observer because of an error during initialization: Code: 107. DB::Exception: Cannot find cgroups v1 or v2 current memory file. (FILE_DOESNT_EXIST), 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) @ 0x000000000cbc851b
hosting_plausible_events_db_1  | 1. DB::Exception::Exception<>(int, FormatStringHelperImpl<>) @ 0x00000000076614c3
hosting_plausible_events_db_1  | 2. DB::CgroupsMemoryUsageObserver::CgroupsMemoryUsageObserver(std::chrono::duration<long long, std::ratio<1l, 1l>>) @ 0x000000000cce452e
hosting_plausible_events_db_1  | 3. DB::Server::main(std::vector<String, std::allocator<String>> const&) @ 0x000000000cd562bd
hosting_plausible_events_db_1  | 4. Poco::Util::Application::run() @ 0x0000000014ca8606
hosting_plausible_events_db_1  | 5. DB::Server::run() @ 0x000000000cd46671
hosting_plausible_events_db_1  | 6. Poco::Util::ServerApplication::run(int, char**) @ 0x0000000014cb14b9
hosting_plausible_events_db_1  | 7. mainEntryClickHouseServer(int, char**) @ 0x000000000cd4246a
hosting_plausible_events_db_1  | 8. main @ 0x0000000007651578
hosting_plausible_events_db_1  | 9. ? @ 0x0000776c3f468083
hosting_plausible_events_db_1  | 10. _start @ 0x0000000005dee46e
hosting_plausible_events_db_1  |  (version 24.3.3.102 (official build))
hosting_plausible_events_db_1  | 2024.10.21 10:05:56.188166 [ 1 ] {} <Warning> Application: Listen [::]:9009 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 24.3.3.102 (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: <listen_host>::</listen_host>
hosting_plausible_events_db_1  | 2024.10.21 10:05:56.254746 [ 1 ] {} <Warning> Application: Listen [::]:8123 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 24.3.3.102 (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: <listen_host>::</listen_host>
hosting_plausible_events_db_1  | 2024.10.21 10:05:56.255297 [ 1 ] {} <Warning> Application: Listen [::]:9000 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 24.3.3.102 (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: <listen_host>::</listen_host>
hosting_plausible_events_db_1  | 2024.10.21 10:05:56.255939 [ 1 ] {} <Warning> Application: Listen [::]:9004 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 24.3.3.102 (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: <listen_host>::</listen_host>
hosting_plausible_events_db_1  | 2024.10.21 10:05:56.257173 [ 1 ] {} <Warning> Application: Listen [::]:9005 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 24.3.3.102 (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: <listen_host>::</listen_host>

Uh oh!

Export data doesn't work. #175

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions