#support

ElerianAI User Experiences ClickHouse Error

TLDR Michele from ElerianAI experienced a Poco::Exception error preventing ClickHouse from starting. Srikanth suggested checking file system permissions, which solved the issue.

Powered by Struct AI
Jul 31, 2023 (4 months ago)
Michele
Photo of md5-62f29f3eff6c150a1e8290517f04d7ef
Michele
06:59 PM
Hi all! I'm Michele Mastrogiovanni from ElerianAI.
Hope anybody can help me.
I'm using Signoz as standard user.
In the past I just downloaded the github repo and run with docker-compose up into deployment/docker/clickhouse-server...
Today, I downloaded the new repo and when I tried to run it I received the following strange error that is preventing clickouse to start:
clickhouse   | Processing configuration file '/etc/clickhouse-server/config.xml'.
clickhouse   | Poco::Exception. Code: 1000, e.code() = 13, Access to file denied: /etc/clickhouse-server/config.xml, Stack trace (when copying this message, always include the lines below):
clickhouse   | 
clickhouse   | 0. Poco::FileImpl::handleLastErrorImpl(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x18b3d476 in /usr/bin/clickhouse
clickhouse   | 1. ? @ 0x18b417c6 in /usr/bin/clickhouse
clickhouse   | 2. Poco::FileStreamBuf::open(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, unsigned int) @ 0x18b4f2ac in /usr/bin/clickhouse
clickhouse   | 3. Poco::FileInputStream::FileInputStream(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, unsigned int) @ 0x18b4fcdb in /usr/bin/clickhouse
clickhouse   | 4. Poco::FileStreamFactory::open(Poco::Path const&) @ 0x18bb1a65 in /usr/bin/clickhouse
clickhouse   | 5. Poco::URIStreamOpener::open(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) const @ 0x18bb0570 in /usr/bin/clickhouse
clickhouse   | 6. Poco::XML::EntityResolverImpl::resolveEntity(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&) @ 0x18a38bfd in /usr/bin/clickhouse
clickhouse   | 7. Poco::XML::SAXParser::parse(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x18a301b2 in /usr/bin/clickhouse
clickhouse   | 8. Poco::XML::DOMBuilder::parse(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x18a1963a in /usr/bin/clickhouse
clickhouse   | 9. Poco::XML::DOMParser::parse(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x18a18a44 in /usr/bin/clickhouse
clickhouse   | 10. DB::ConfigProcessor::processConfig(bool*, zkutil::ZooKeeperNodeCache*, std::__1::shared_ptr<Poco::Event> const&) @ 0x16131ef2 in /usr/bin/clickhouse
clickhouse   | 11. DB::ConfigProcessor::loadConfig(bool) @ 0x16134874 in /usr/bin/clickhouse
clickhouse   | 12. BaseDaemon::reloadConfiguration() @ 0xa63688b in /usr/bin/clickhouse
clickhouse   | 13. BaseDaemon::initialize(Poco::Util::Application&) @ 0xa637ffc in /usr/bin/clickhouse
clickhouse   | 14. DB::Server::initialize(Poco::Util::Application&) @ 0xa481be3 in /usr/bin/clickhouse
clickhouse   | 15. Poco::Util::Application::run() @ 0x189f19ba in /usr/bin/clickhouse
clickhouse   | 16. DB::Server::run() @ 0xa48191e in /usr/bin/clickhouse
clickhouse   | 17. mainEntryClickHouseServer(int, char**) @ 0xa47eeb7 in /usr/bin/clickhouse
clickhouse   | 18. main @ 0xa3dd88b in /usr/bin/clickhouse
clickhouse   | 19. __libc_start_main @ 0x7f6462d00083 in ?
clickhouse   | 20. _start @ 0xa19cf2e in /usr/bin/clickhouse
clickhouse   |  (version 22.8.8.3 (official build)) 

Some knows why clickhouse cannot read the config file?
No changes are done, just download and run
Thanks in advance!
Aug 01, 2023 (4 months ago)
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
03:16 AM
Check your file system permissions
Michele
Photo of md5-62f29f3eff6c150a1e8290517f04d7ef
Michele
07:37 AM
It was my bad, sorry, permission problems...