Failed to start nats streaming server

__Steps to reproduce:__
After a server reboot I'm getting the following error on InfluxDB startup:

2021-01-13T16:38:31.182037Z error Failed to start nats streaming server {"log_id": "0Rg9e0yl000", "error": "nats: no servers available for connection"}
Error: nats: no servers available for connection

The command I'm using to start is:

/usr/local/bin/influxd --engine-path=/ifdata/engine --bolt-path=/ifdata/influxd.bolt

The error does not happen if I don't pass my persistent engine-path as a parameter

__Environment info:__

* System info: Linux 4.18.0-193.14.3.el8_2.x86_64 x86_64
* InfluxDB version: InfluxDB 2.0.2 (git: 84496e507a) build_date: 2020-11-19T03:59:35Z

__Config:__
Only non-default variables are the engine path and bolt path:

--engine-path=/ifdata/engine --bolt-path=/ifdata/influxd.bolt

__Logs:__
2021-01-13T16:38:31.138603Z info Starting retention policy enforcement service {"log_id": "0Rg9e0yl000", "service": "retention", "check_interval": "30m"}
2021-01-13T16:38:31.138640Z info Starting precreation service {"log_id": "0Rg9e0yl000", "service": "shard-precreation", "check_interval": "10m", "advance_period": "30m"}
2021-01-13T16:38:31.138861Z info Starting query controller {"log_id": "0Rg9e0yl000", "service": "storage-reads", "concurrency_quota": 10, "initial_memory_bytes_quota_per_query": 9223372036854775807, "memory_bytes_quota_per_query": 9223372036854775807, "max_memory_bytes": 0, "queue_size": 10}
2021-01-13T16:38:31.139609Z info Configuring InfluxQL statement executor (zeros indicate unlimited). {"log_id": "0Rg9e0yl000", "max_select_point": 0, "max_select_series": 0, "max_select_buckets": 0}
2021-01-13T16:38:31.182037Z error Failed to start nats streaming server {"log_id": "0Rg9e0yl000", "error": "nats: no servers available for connection"}
Error: nats: no servers available for connection
See 'influxd -h' for help

Start by reproducing the failure with the influxd command and the persistent --engine-path and --bolt-path values shown in the report, then compare startup with those paths omitted. Use the reported startup logs and the nats streaming server error to trace the persistence-related startup path. Done means InfluxDB starts successfully after a reboot while using the persistent paths.

Written by the indexing model from the issue text.