influxdata / influxdata/influxdb
Influx 1.8.9 - the control process exited with error code
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Hi,
Influxdb 1.8.9 doesn't start. I have "Failed to connect to http://localhost:8086: Get http://localhost:8086/ping: dial tcp [::1]:8086: connect: connection refused Please check your connection settings and ensure 'influxd' is running."
After "systemctl status influxdb.service":
● influxdb.service - InfluxDB is an open-source, distributed, time series database
Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/influxdb.service.d
└─override.conf
Active: activating (start) since Tue 2021-08-24 20:00:33 CEST; 2s ago
Docs: https://docs.influxdata.com/influxdb/
Cntrl PID: 5866 (influxd-systemd)
Tasks: 14 (limit: 3292)
CGroup: /system.slice/influxdb.service
├─5866 /bin/bash -e /usr/lib/influxdb/scripts/influxd-systemd-start.sh
├─5867 /usr/bin/influxd -config /etc/influxdb/influxdb.conf
└─5907 sleep 1
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.007209Z lvl=info msg="Opened file" log_id=0WAKzEGW000 engine=tsm1 service=filestore path=/var/lib/influxdb/data/fronius/autogen/418/000000007-000000002.tsm id=0 duration=0.889ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.011883Z lvl=info msg="Opened file" log_id=0WAKzEGW000 engine=tsm1 service=filestore path=/var/lib/influxdb/data/fronius/autogen/406/000000011-000000002.tsm id=0 duration=0.252ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.017044Z lvl=info msg="Opened shard" log_id=0WAKzEGW000 service=store trace_id=0WAKzEg0000 op_name=tsdb_open index_version=inmem path=/var/lib/influxdb/data/fronius/autogen/394 duration=24.423ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.019269Z lvl=info msg="Opened file" log_id=0WAKzEGW000 engine=tsm1 service=filestore path=/var/lib/influxdb/data/fronius/autogen/43/000000007-000000002.tsm id=0 duration=0.262ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.033366Z lvl=info msg="Opened shard" log_id=0WAKzEGW000 service=store trace_id=0WAKzEg0000 op_name=tsdb_open index_version=inmem path=/var/lib/influxdb/data/fronius/autogen/406 duration=37.735ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.034983Z lvl=info msg="Opened file" log_id=0WAKzEGW000 engine=tsm1 service=filestore path=/var/lib/influxdb/data/fronius/autogen/430/000000009-000000002.tsm id=0 duration=0.234ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.037338Z lvl=info msg="Opened shard" log_id=0WAKzEGW000 service=store trace_id=0WAKzEg0000 op_name=tsdb_open index_version=inmem path=/var/lib/influxdb/data/fronius/autogen/418 duration=32.204ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.041009Z lvl=info msg="Opened file" log_id=0WAKzEGW000 engine=tsm1 service=filestore path=/var/lib/influxdb/data/fronius/autogen/442/000000009-000000002.tsm id=0 duration=1.506ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.151150Z lvl=info msg="Opened shard" log_id=0WAKzEGW000 service=store trace_id=0WAKzEg0000 op_name=tsdb_open index_version=inmem path=/var/lib/influxdb/data/fronius/autogen/43 duration=133.949ms
sie 24 20:00:35 raspberrypi influxd-systemd-start.sh[5866]: ts=2021-08-24T18:00:35.152599Z lvl=info msg="Opened file" log_id=0WAKzEGW000 engine=tsm1 service=filestore path=/var/lib/influxdb/data/fronius/autogen/454/000000007-000000002.tsm id=0 duration=0.384ms
Please help!
Michal
Contributor guide
Research direction
Start with the reported systemctl status output, /usr/lib/influxdb/scripts/influxd-systemd-start.sh, and /etc/influxdb/influxdb.conf; reproduce the startup failure and inspect the complete service logs beyond the shard-opening messages. Done means identifying a reproducible cause for influxd failing to become available on port 8086 and documenting or fixing it with verification on the affected setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100