influxdata / influxdata/influxdb
influxdb 1.8.9 fails to load via systemctl script on existing DB
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
- stop the DB with systemctl stop influxdb
- start the DB with systemctl start influxdb
Expected behavior:
Database starting
Actual behavior:
Database fails to start with
"Failed to reach influxdb http endpoint at http://localhost:8086/health"
error
running
"/usr/lib/influxdb/scripts/influxd-systemd-start.sh"
script manually fails with same error. however database starts and connectable via http.
curl http://localhost:8086/health
{"checks":[],"message":"ready for queries and writes","name":"influxdb","status":"pass","version":"1.8.9"}
possibly due to loading shards time.
Environment info:
- System info: Run
uname -srmand copy the output here
Linux 4.15.0-154-generic x86_64 - InfluxDB version: Run
influxd versionand copy the output here
InfluxDB v1.8.9 (git: 1.8 d9b56321d579) - Other relevant environment details: Container runtime, disk info, etc
DB is about 250 GB
Logs:
Include snippet of errors in log.
nfluxd-systemd-start.sh[17616]: Failed to reach influxdb http endpoint at http://localhost:8086/health
systemd[1]: influxdb.service: Control process exited, code=exited status=1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /usr/lib/influxdb/scripts/influxd-systemd-start.sh and reproduce the failure using systemctl stop influxdb followed by systemctl start influxdb. Check how the script probes http://localhost:8086/health while the existing 250 GB database loads. Done means an existing InfluxDB 1.8.9 database starts successfully through systemd without the health-check control process failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100