Turing on HTTPS slows influxdb startup and show multiple restarts in a loop!

#1

we have a 37 GB POC data store and I am testing turning on https.

After activating the https the influxdb restart taking a very long time

  # Determines whether HTTPS is enabled.
  https-enabled = true

  # The SSL certificate to use when HTTPS is enabled.
  https-certificate = "influxdb-selfsigned.crt"

  # Use a separate private key location.
  https-private-key = "influxdb-selfsigned.key"

  # The SSL certificate used to validate client certificates
  https-ca-certificate = "/etc/pki/CA/influx-rootCA.pem"

In output I see of the journalctl -u influxdb -f

I do see multiple restarts !

May 07 14:01:19 cricket influxd[2285]: ts=2018-05-07T19:01:19.183897Z lvl=info msg="Opened shard" log_id=07v~TmzW000 service=store trace_id=07v~TnOG000 op_name=tsdb_open path=/opt/influxdb/data/tickdata/autogen/55 duration=198.673ms
May 07 14:01:19 cricket systemd[1]: influxdb.service: main process exited, code=exited, status=1/FAILURE
May 07 14:01:19 cricket systemd[1]: Unit influxdb.service entered failed state.
May 07 14:01:19 cricket systemd[1]: influxdb.service failed.
May 07 14:01:19 cricket systemd[1]: influxdb.service holdoff time over, scheduling restart.
May 07 14:01:19 cricket systemd[1]: Started InfluxDB is an open-source, distributed, time series database.
May 07 14:01:19 cricket systemd[1]: Starting InfluxDB is an open-source, distributed, time series database...
May 07 14:01:19 cricket influxd[2306]: ts=2018-05-07T19:01:19.445540Z lvl=info msg="InfluxDB starting" log_id=07v~WaqG000 version=1.5.2 branch=1.5 commit=02d7d4f043b34ecb4e9b2dbec298c6f9450c2a32
May 07 14:01:19 cricket influxd[2306]: ts=2018-05-07T19:01:19.445573Z lvl=info msg="Go runtime" log_id=07v~WaqG000 version=go1.9.2 maxprocs=4
May 07 14:01:19 cricket influxd[2306]: ts=2018-05-07T19:01:19.547682Z lvl=info msg="Using data dir" log_id=07v~WaqG000 service=store path=/opt/influxdb/data
May 07 14:01:19 cricket influxd[2306]: ts=2018-05-07T19:01:19.547736Z lvl=info msg="Open store (start)" log_id=07v~WaqG000 service=store trace_id=07v~WbEl000 op_name=tsdb_open op_event=start
May 07 14:01:19 cricket influxd[2306]: ts=2018-05-07T19:01:19.571638Z lvl=info msg="Opened file" log_id=07v~WaqG000 engine=tsm1 service=filestore path=/opt/influxdb/data/_internal/monitor/1395/000000025-000000001.tsm id=3 duration=9.059ms
May 07 14:01:19 cricket influxd[2306]: ts=2018-05-07T19:01:19.573408Z lvl=info msg="Opened file" log_id=07v~WaqG000 engine=tsm1 service=filestore path=/opt/influxdb/data/_internal/monitor/1395/000000030-000000001.tsm id=7 duration=14.481ms

An I hitting some weird bug : uisng influxdb 1.5.2

Any help appreciated.

#2

I had bad config values
the path to cert files not correct had to add “/etc/ssl/” and that fixed the startup !

awesome !

#3

Might be worth filing a bug if there wasn’t an appropriate error message.

#4

Well " journalctl -u influxdb -f " did show errors but the issue was in the systemd file with service “restart” it continuously restarted with the error only in the first output!