Restart not possible

InfluxDB 3
1

Hi,
the very first start of influxdb 3 worked without any problems.

2025-05-03T12:18:08.521536Z INFO influxdb3::commands::serve: Creating io runtime executor w/ 1 threads
2025-05-03T12:18:08.521751Z INFO influxdb3::commands::serve: InfluxDB 3 Enterprise server starting node_id=host01 mode=[All] git_hash=96e4aad870b44709e149160d523b4319ea91b54c version=3.0.1 uuid=cde74343-b81c-4e2e-890c-49dc6927b1c4 licensed_cores=2
2025-05-03T12:18:08.522002Z INFO influxdb3::commands::serve: Creating shared query executor w/ 1 threads
2025-05-03T12:18:08.523440Z INFO influxdb3_catalog::catalog::update: create database name=“_internal”
2025-05-03T12:18:08.523573Z INFO influxdb3::commands::serve: catalog initialized catalog_uuid=8b5e8152-df8f-4c38-a9e8-9a0cb08c61a6
2025-05-03T12:18:08.523782Z WARN influxdb3_enterprise_licensing::commercial: no license file found in local filesystem
2025-05-03T12:18:08.523799Z WARN influxdb3_enterprise_licensing::commercial: no license file found in object store
2025-05-03T12:18:08.523848Z WARN influxdb3_enterprise_licensing::commercial: failed to verify commercial license: no valid license found
2025-05-03T12:18:08.524151Z INFO influxdb3_enterprise_licensing::trial: Home Enterprise license verified
2025-05-03T12:18:08.524238Z INFO influxdb3::commands::serve: valid license found, happy data crunching
2025-05-03T12:18:08.524974Z INFO influxdb3::commands::serve: setting up background mem check for query buffer
2025-05-03T12:18:08.525072Z INFO influxdb3_catalog::catalog::update: register node node_id=“host01” core_count=2 mode=[All]
2025-05-03T12:18:08.525091Z INFO influxdb3_catalog::catalog::update: registering new node to the catalog node_id=“host01” instance_id=“416e9455-e29d-4df3-8781-2fee8131af7a”
2025-05-03T12:18:08.525310Z INFO influxdb3_catalog::object_store: persisted next catalog sequence put_result=PutResult { e_tag: Some(“12d483-6343a427d620c-12d”), version: None } object_path=CatalogFilePath(Path { raw: “cluster01/catalogs/00000000000000000002.catalog” })
2025-05-03T12:18:08.525413Z INFO influxdb3_enterprise_buffer::replica: registering new ingest node host01
2025-05-03T12:18:08.525452Z INFO influxdb3_enterprise_buffer::replica: received update for current node, will not add as replica
2025-05-03T12:18:08.525484Z INFO influxdb3::commands::serve: node registered licensed_cores=2 instance_id=“416e9455-e29d-4df3-8781-2fee8131af7a”
2025-05-03T12:18:08.525494Z INFO influxdb3::commands::serve: setting up telemetry store
2025-05-03T12:18:08.708674Z INFO influxdb3_server: startup time: 10363ms address=0.0.0.0:8181
^C2025-05-03T12:18:16.902586Z INFO influxdb3_shutdown: Received SIGINT
2025-05-03T12:18:16.902724Z INFO influxdb3::commands::serve: shutdown requested
2025-05-03T12:18:16.902816Z INFO influxdb3_catalog::catalog::enterprise: updating node state to stopped in catalog node_id=“host01”
2025-05-03T12:18:16.902835Z INFO influxdb3_catalog::catalog::update: updating node state to Stopped in catalog node_id=“host01”
2025-05-03T12:18:16.902886Z INFO influxdb3_enterprise_licensing::trial: process shutdown detected, terminating trial license validation loop
2025-05-03T12:18:16.903142Z INFO influxdb3_catalog::object_store: persisted next catalog sequence put_result=PutResult { e_tag: Some(“12d484-6343a42fd34dc-d3”), version: None } object_path=CatalogFilePath(Path { raw: “cluster01/catalogs/00000000000000000003.catalog” })
2025-05-03T12:18:16.903463Z INFO influxdb3::commands::serve: frontend shutdown completed
2025-05-03T12:18:16.903506Z INFO influxdb3::commands::serve: backend shutdown completed

I then want to restart with this command
influxdb3 serve --node-id host01 --cluster-id cluster01 --object-store file --data-dir influxdb_data

But it get this error
2025-05-03T12:18:19.430615Z INFO influxdb3::commands::serve: Creating io runtime executor w/ 1 threads
2025-05-03T12:18:19.431002Z INFO influxdb3::commands::serve: InfluxDB 3 Enterprise server starting node_id=host01 mode=[All] git_hash=96e4aad870b44709e149160d523b4319ea91b54c version=3.0.1 uuid=8642d1d7-21b5-40d8-a361-e4505f83d436 licensed_cores=2
2025-05-03T12:18:19.431731Z INFO influxdb3::commands::serve: Creating shared query executor w/ 1 threads
2025-05-03T12:18:19.434316Z INFO influxdb3_catalog::catalog::update: create database name=“_internal”
2025-05-03T12:18:19.434366Z INFO influxdb3::commands::serve: catalog initialized catalog_uuid=8b5e8152-df8f-4c38-a9e8-9a0cb08c61a6
2025-05-03T12:18:19.434615Z WARN influxdb3_enterprise_licensing::commercial: no license file found in local filesystem
2025-05-03T12:18:19.434683Z WARN influxdb3_enterprise_licensing::commercial: no license file found in object store
2025-05-03T12:18:19.434694Z WARN influxdb3_enterprise_licensing::commercial: failed to verify commercial license: no valid license found
2025-05-03T12:18:19.434934Z INFO influxdb3_enterprise_licensing::trial: Home Enterprise license verified
2025-05-03T12:18:19.434976Z INFO influxdb3::commands::serve: valid license found, happy data crunching
2025-05-03T12:18:19.434993Z WARN executor: DedicatedExecutor dropped without calling shutdown()
2025-05-03T12:18:19.435014Z WARN executor: DedicatedExecutor dropped without waiting for worker termination
2025-05-03T12:18:19.435325Z INFO influxdb3_cache::parquet_cache: cache request handler closed
Serve command failed: only one node is allowed when using Home License

2

At home license: This is designed for hobbyist use and has more limitations than other license types. One key limitation is that it only supports a single node configuration.

The error occurs because the system is detecting that you’re trying to use a home license with what appears to be a multi-node setup or configuration. Please take a look at the license feature comparison documentation.

Can you please confirm you’re only running a single node with your Home license?
If you need multi-node capabilities you would need to upgrade to a Commercial license.

Just as a reminder the home license is perpetual (never expires) but is limited to 2 CPU cores and doesn’t support multi-node deployments or commercial use.

3

Yes i´m running a single node with my home license.
If i understand the docu correclty i have to provide node and cluster-id no matter if i run a home license or not.

4

Hello @Tobias1,
I’m asking around thank you.

5

Hey @Tobias1 - the issue you are experiencing was fixed in a more recent version of the database (3.0.2 - looks like you are on 3.0.1). Upgrading to 3.0.2 should allow you to restart the node. However, we will soon be releasing 3.0.3, which includes several other fixes to the Home licensing, so I would recommend upgrading to 3.0.3 when it is released.

2 Likes