Created on
01-11-2026
11:57 PM
Edited on
01-12-2026
12:12 AM
By
Jean-Philippe_P
| Description | This article describes the steps to resolve the ClickHouse server down issue on FortiSIEM and the worker node cannot be added to the ClickHouse cluster configuration. This issue is commonly caused by a missing or invalid macros.xml file, which is required for shard and replica identification in a clustered ClickHouse deployment. |
| Scope |
FortiSIEM. |
| Solution |
After a worker node failure or power cycle, a FortiSIEM ClickHouse worker may fail to start clickhouse-server, preventing it from being added back to the ClickHouse cluster. This is typically caused by a missing macros.xml file required for shard and replica identification.
The following log details can be observed from clickhouse-server.log below:
This error indicates that ClickHouse is unable to start because it cannot resolve the {shard} macro required by FortiSIEM’s distributed ClickHouse table configuration.
Most importantly, these macros are mandatory on worker nodes that participate in a ClickHouse cluster.
Resolution steps:
ls -lah /etc/clickhouse-server/config.d/
Modify the contents of macros.xml in (Wrk_2) to avoid any similarity conflict.
vi /etc/clickhouse-server/config.d/macros.xml
Example:
<macros>
chmod 0755 /etc/clickhouse-server/config.d/macros.xml
phstatus
/opt/phoenix/phscripts/clickhouse/cleanup_clickhouse.sh
After that, verify the clickhouse-server status is online again through the command phstatus. Then, proceed to re-add the worker in the FortiSIEM GUI Clickhouse configuration.
Root Cause:
Related article: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2026 Fortinet, Inc. All Rights Reserved.