Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Plausible's Clickhouse database doesn't start (Access to file denied: /etc/clickhouse-server/config.d/logging.xml) #4409

Closed
pshemek opened this issue Nov 26, 2024 · 3 comments

Comments

@pshemek
Copy link

pshemek commented Nov 26, 2024

Error Message and Logs

Suddenly Plausible events db Clickhouse stopped working on my VPS.
It looks like there is some issue with file access. I haven't been messing with that, I'm not sure why it happened suddenly.

Clickhouse service log:

2024-11-26T21:39:19.285343719Z ClickHouse Database directory appears to contain a database; Skipping initialization
2024-11-26T21:39:19.332056193Z Processing configuration file '/etc/clickhouse-server/config.xml'.
2024-11-26T21:39:19.333164606Z Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
2024-11-26T21:39:19.333218607Z Merging configuration file '/etc/clickhouse-server/config.d/logging.xml'.
2024-11-26T21:39:19.386398677Z Poco::Exception. Code: 1000, e.code() = 0, Exception: Failed to merge config with '/etc/clickhouse-server/config.d/logging.xml': Access to file denied: /etc/clickhouse-server/config.d/logging.xml, Stack trace (when copying this message, always include the lines below):
2024-11-26T21:39:19.386446838Z 
2024-11-26T21:39:19.386458358Z 0. DB::ConfigProcessor::processConfig(bool*, zkutil::ZooKeeperNodeCache*, std::shared_ptr<Poco::Event> const&) @ 0x000000001119c3a8
2024-11-26T21:39:19.386468918Z 1. DB::ConfigProcessor::loadConfig(bool) @ 0x000000001119c640
2024-11-26T21:39:19.386476838Z 2. BaseDaemon::initialize(Poco::Util::Application&) @ 0x000000000c192aac
2024-11-26T21:39:19.386486318Z 3. DB::Server::initialize(Poco::Util::Application&) @ 0x000000000c09f96c
2024-11-26T21:39:19.386497118Z 4. Poco::Util::Application::run() @ 0x0000000012f3628c
2024-11-26T21:39:19.386502878Z 5. DB::Server::run() @ 0x000000000c09f770
2024-11-26T21:39:19.386507879Z 6. Poco::Util::ServerApplication::run(int, char**) @ 0x0000000012f3f544
2024-11-26T21:39:19.386512679Z 7. mainEntryClickHouseServer(int, char**) @ 0x000000000c09bdd4
2024-11-26T21:39:19.386517039Z 8. main @ 0x0000000007731438
2024-11-26T21:39:19.386522319Z 9. ? @ 0x0000000000020e10
2024-11-26T21:39:19.386526519Z  (version 24.3.3.102 (official build))

Steps to Reproduce

Not sure. I was using the standard Plausible service stack for some time and suddenly it happened.
Maybe after VPS restart.

Example Repository URL

No response

Coolify Version

v.4.0.0-beta.370

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

No response

@pshemek pshemek added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Nov 26, 2024
@peaklabs-dev
Copy link
Member

I just tested the plausible template and it works fine. I think this is a permission issues on you server.

@peaklabs-dev peaklabs-dev removed the 🔍 Triage Issues that need assessment and prioritization. label Nov 27, 2024
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Nov 27, 2024
@peaklabs-dev peaklabs-dev added the 💤 Waiting for feedback Issues awaiting a response from the author. label Nov 27, 2024
@pshemek
Copy link
Author

pshemek commented Nov 27, 2024

You're right, I've actually found when it happened.

Some tutorial instructed me to perform:

    chown -R 9999:root /data/coolify
    chmod -R 700 /data/coolify

Shouldn't I have done it?

EDIT: Oh, maybe I shouldn't have done that after installing the services...

@pshemek
Copy link
Author

pshemek commented Nov 27, 2024

I have set back proper permissions and ownership for the services directories.

@pshemek pshemek closed this as completed Nov 27, 2024
@github-actions github-actions bot removed 🐛 Bug Reported issues that need to be reproduced by the team. 💤 Waiting for feedback Issues awaiting a response from the author. labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants