influxdata / influxdata/influxdata-docker
init-influxdb.sh - influxdb init process failed.
- Dominant language
- Shell
- Stars
- 364
- Forks
- 255
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 7
Description
The influxdb fails to start after recreating the pod.
It seems as it cannot recover the data.
I am using AWS EFS as mount point.
Any suggestions how it can be solved?
[I] 2018-02-12T14:05:05Z InfluxDB starting, version 1.4.3, branch 1.4, commit 60d27e6995558f38a39e90b35a92cbac080310a3
[I] 2018-02-12T14:05:05Z Go version go1.9.2, GOMAXPROCS set to 4
[I] 2018-02-12T14:05:05Z Using configuration at: /etc/influxdb/influxdb.conf
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process in progress...
influxdb init process failed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with init-influxdb.sh and reproduce the initialization after recreating the pod with AWS EFS mounted. Use the provided InfluxDB startup output to trace where initialization stops; done means the container starts successfully and recovers its existing data after the pod is recreated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, shell
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100