Autostart server after upgrade from Influxdb 1.8 to 2.4 with specific paths

Hello,
I’ve been using Influx 1.8 for quite a while and now upgraded to 2.4.

I did so based on an upgrade command trying to control the paths for the database, specifically I used:

sudo influxd upgrade
–config-file=“/etc/influxdb/influxdb.conf”
–influx-configs-path=“/db/influxdb_v2/Logging.conf”
–bolt-path=“/db/influxdb_v2/logging.bolt”
–engine-path=“/db/influxdb_v2/Logging/engine”
–continuous-query-export-path=“/db/influxdb_v2/Logging/scripts/cs.sql”
–v2-config-path=“/db/influxdb_v2/dba/Logging/cfg/Logging.toml”
–log-path=“/db/influxdb_v2/dba/Logging/log/upgrade.log”
–bucket=“Logging”
–org=“xxx”
–username=“dba” \

Everything works fine so far, at least when I start the server with

sudo nohup influxd --engine-path=/db/influxdb_v2/Logging/engine --bolt-path=/db/influxdb_v2/logging.bolt run

I’m now trying to move that over to a process starting automatically at boot-time.
I’m feeling bad, but I was not yet able to do so, some paths of standard installation interfere and the server is starting with a fresh database.

Would be grateful for a hint on how to start the server or where to place the config file exactly.

Hello @TimTom,
I actually recommend holding off on upgrading to 2.x. Instead I’d wait for 3.x OSS to release later this year.
It offers significant performance benefits and is centered around interoperability so you don’t have to learn Flux. Instead you can use InfluxQL and SQL with 3.x OSS.