I am able to run the InfluxDB2.0 daemon process “influxd” on a linux box and the port is configured to 8111. I see in the log that the daemon is listening to 8111, but I’m not able to launch “Influx setup” to create a database or any further operations to set up. Please let me know what I’m missing here?
I see the web page saying " This site can’t be reached"
“SYSWDL1832” refused to connect.
But we already have Influx-1.8 running on this box as well, where I can create database and measurements.
I’m not sure if the 2.0 Influxd process is running perfectly fine… below is all I see in its logs. Is this all that is required for daemon process?
Unfortunately no, the 9999 port is being used by another app in our environment which I do not have control on…
But can you please confirm if the daemon process logs are correct and they look as it should? Just want to make sure nothing is missing in the config for daemon…
Hi, thanks for the response… currently I see a problem with running the daemon process. We have influx1.8 running in parallel on the same machine…
when I start the command to bring up the daemon process > ./influxd
The influx2.0 isn’t coming up due to the below error.
ts=2020-08-03T01:52:53.296456Z lvl=error msg=“Failed opening bolt” log_id=0OOWBbTl000 error=“unable to open boltdb; is there a chronograf already running? timeout”
Error: unable to open boltdb; is there a chronograf already running? timeout
Not sure if I can suppress this one with a config…
Should be able to. This is what settled on. Although full disclosure I’m only running v2 instance, but I can’t see why it wouldn’t be possible to do what you’re wanting to
I met same error Error: failed to determine if instance has been configured.
My scenario is I use a script to run influxdb2.0 in docker and then call influx setup immediately.
I found the reason of this error is that the service is not ready when calling setup, the service self needs some time to launch before ready to receive traffic.
So I solved it by before calling setup, repeated to check the status of 127.0.0.1:8086/api/v2/setup until it returns a “true”.
I’m using an influx v2 with docker compose and it throws an error Failed opening bolt , unable to open boltdb: timeout. I can use influxdb UI without problem and telegraf but influx CLI has problems.
@dhinojosac the Failed opening bolt , unable to open boltdb: timeout is usually because the bolt file is already opened by another process.
In the linked docker compose file, it has two influxdb containers being created and both mounting the data directory. This would cause the second container to fail to open the bolt file and generate that error.
@Anaisdg I’m not 100% clear on the need to have two influxdb containers in the compose file - since the linked file is in your github, I’m assuming you are familiar with it . The the container with the DOCKER_INFLUXDB_INIT_MODE=setup should start up influxdb and do the initial configuration on first launch, and then on subsequent launches it will see that the instance is already set up and not do it again - you shouldn’t need a separate container to do the setup. Maybe I’m missing something though!
Hello @wbaker,
I don’t remember exactly to be completely honest, but I believe it was because I can create the influxdb container and the telegraf container simultaneously. There were problems with a lag in the containers running and authentication and cert issues because of timing. I remember I needed a second one, the influxdb-cli, to get setup first and then configure the influxdb container first. The telegraf container depends on the influxdb-cli container when depends on the influxdb one. To ensure that a each step, running the container and setting up influxdb happens successfully before setting up and running telegraf.