Hi guys,
I am so confused right now because I have encountered this issue twice and don’t know how to fix it.
My problem is when I try to restart my influxdb with the “system service influxdb start” command. It showed the error "localhost:8086/ready unavailable after X attempt.
When I first installed it, I tried to start and stop the service and it worked fine. But this error happens when I let my service run for a while.
I am afraid that my log is very long and it is hard for you to read so I put my log in txt file.
I really need your help. Please give me some advice.
Thank you all so much.
Oct 25 091946 err08spc2 systemd[1].txt (46.6 KB)
Hello @vinh_lee ,
I’m seeing a “slice bounds out of range”
This can be due to a data corruption issue.
This person solved it by removing the WAL
I have had influxdb 0.10.0 running very well on Ubuntu 14.04 for over a year. I rebooted and now influx will not start.
I have searched here and googled but not managed to sort it. I found suggestions that it may be a corrupted file and that deleting the wal directory may help. I tried that to no avail.
I thought of upgrading to newer version to see if it gave better diagnostics but I believe I would first have to export the data, which can’t be done unless it is running.
I hope someone here…
And this
opened 09:58PM - 25 Apr 16 UTC
closed 07:33PM - 27 Apr 16 UTC
area/tsm
panic
### Bug report
__System info: __ [Linux: 3.10.0-327.13.1.el7.x86_64, influxdb-0… .12.2-1.x86_64]
**Steps to reproduce:**
1. I ran out of space in /var/lib/ (where I had influxdb).
2. Now I cannot start influxdb.
**Expected behavior:** [influxdb should start]
**Actual behavior:** [Cannot start influxdb]
**Additional info:** [Include gist of relevant config, logs, etc.]
influxdb.log states:
[tsm1] 2016/04/25 12:52:12 /d0/influxdb/data/_internal/monitor/23 database index loaded in 3.312297ms
[store] 2016/04/25 12:52:12 /d0/influxdb/data/_internal/monitor/23 opened in 15.019705488s
[tsm1] 2016/04/25 12:52:17 /d0/influxdb/data/regression/default/12 database index loaded in 20.03670118s
[store] 2016/04/25 12:52:17 /d0/influxdb/data/regression/default/12 opened in 20.087676684s
panic: runtime error: slice bounds out of range
goroutine 20 [running]:
github.com/influxdata/influxdb/tsdb/engine/tsm1.(_WriteWALEntry).UnmarshalBinary(0xc208139a68, 0xc20d8aa000, 0xb1, 0x100000, 0x0, 0x0)
/root/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/wal.go:593 +0x68f
github.com/influxdata/influxdb/tsdb/engine/tsm1.(_WALSegmentReader).Next(0xc2093560c0, 0xc20c9e1c00)
/root/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/wal.go:804 +0x7be
github.com/influxdata/influxdb/tsdb/engine/tsm1.func·001(0x0, 0x0)
/root/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/cache.go:444 +0x3a1
github.com/influxdata/influxdb/tsdb/engine/tsm1.(_CacheLoader).Load(0xc208146320, 0xc208082e80, 0x0, 0x0)
/root/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/cache.go:466 +0x10f
github.com/influxdata/influxdb/tsdb/engine/tsm1.(_Engine).reloadCache(0xc208176fd0, 0x0, 0x0)
/root/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/engine.go:663 +0xe2
github.com/influxdata/influxdb/tsdb/engine/tsm1.(_Engine).Open(0xc208176fd0, 0x0, 0x0)
/root/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/engine.go:159 +0x1dd
github.com/influxdata/influxdb/tsdb.func·004(0x0, 0x0)
/root/go/src/github.com/influxdata/influxdb/tsdb/shard.go:149 +0x26a
github.com/influxdata/influxdb/tsdb.(_Shard).Open(0xc208050fc0, 0x0, 0x0)
/root/go/src/github.com/influxdata/influxdb/tsdb/shard.go:159 +0x6f
github.com/influxdata/influxdb/tsdb.func·009(0xc208031c20, 0xc20801f952, 0xa, 0xc2080ecf1d, 0x7, 0xc2080ed165, 0x2)
/root/go/src/github.com/influxdata/influxdb/tsdb/store.go:162 +0x65f
created by github.com/influxdata/influxdb/tsdb.(*Store).loadShards
/root/go/src/github.com/influxdata/influxdb/tsdb/store.go:170 +0xac8
_Please note, the quickest way to fix a bug is to open a Pull Request._
I hope those help!
Hi @Anaisdg ,
I have tried to delete the WAL file. So what I did was, stopped the service and deleted WAL then started the service again. However, the WAL files were generated after I started the service.