Description | This article describes how to resolve the Clickhouse Keeper ID failure error during Keeper Setup in FortiSIEM. |
Scope | FortiSIEM. |
Solution |
While adding a new Clickhouse Keeper in Admin -> Settings -> Database -> Clickhouse config, the following error is observed:
While checking into the backend Phoenix logs of the Supervisor node from which the Keeper node is being added, the following logs have been observed.
tail -f /opt/phoenix/log/phoenix.log 2025-08-14T12:55:40.338901+01:00 FSMSuper phMonitorSupervisor[5349]: [PH_GENERIC_INFO]:[eventSeverity]=PHL_INFO,[procName]=phMonitorSupervisor,[fileName]=phMonitorProcess.cpp,[lineNumber]=9921,[phLogDetail]=Node 10.10.10.100 returns ClickHouse Keeper Server Id Failure
The reason for the above error could be that the same node was previously added as a Keeper node. The cleanup needs to be performed before adding it again.
The script below needs to be run from the Keeper node CLI. This script would perform cleanup on Keeper directories.
cd /opt/phoenix/phscripts/clickhouse ./cleanup_clickhouse_keeper.sh
After running the script, try adding the same node as a Keeper node, and it should be successful. |
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 2025 Fortinet, Inc. All Rights Reserved.