panic: runtime error: slice bounds out of range

[Smiggel]

After upgrading yesterday to Hass.io 0.92.2 my InfluxDB crashed after weeks of running stable on my new installation.

When I upgraded yesterday, it crashed and I could not get it working. :-(

This was in my logs:
2019/05/03 23:15:32 Using configuration at: /etc/kapacitor/kapacitor.conf
panic: runtime error: slice bounds out of range
goroutine 229 [running]:
github.com/influxdata/influxdb/tsdb/cursors.(*StringArray).Include(0x7e7f758, 0x97b2d500, 0x15962722, 0x375fd406, 0x56650894)
/go/src/github.com/influxdata/influxdb/tsdb/cursors/arrayvalues.gen.go:693 +0x260
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*tsmBatchKeyIterator).combineString(0x34622d0, 0xf2fcf01, 0xf73348, 0xf2fcf00, 0x37)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.gen.go:1748 +0x63c
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*tsmBatchKeyIterator).mergeString(0x34622d0)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.gen.go:1691 +0x25c
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*tsmBatchKeyIterator).merge(0x34622d0)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.go:1815 +0xf4
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*tsmBatchKeyIterator).Next(0x34622d0, 0x75c28a)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.go:1676 +0xcf0
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*Compactor).write(0x31c07e0, 0x3e616d0, 0x47, 0xf76358, 0x34622d0, 0xe742401, 0x0, 0x0)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.go:1128 +0x148
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*Compactor).writeNewFiles(0x31c07e0, 0x11, 0x2, 0x34234c0, 0x6, 0x8, 0xf76358, 0x34622d0, 0x1, 0x0, ...)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.go:1032 +0x128
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*Compactor).compact(0x31c07e0, 0xe28b00, 0x34234c0, 0x6, 0x8, 0x0, 0x0, 0x0, 0x0, 0x0)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.go:940 +0x4a0
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*Compactor).CompactFull(0x31c07e0, 0x34234c0, 0x6, 0x8, 0x0, 0x0, 0x0, 0x0, 0x0)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/compact.go:958 +0x108
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*compactionStrategy).compactGroup(0x3423640)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/engine.go:2152 +0xaac
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*compactionStrategy).Apply(0x3423640)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/engine.go:2129 +0x2c
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*Engine).compactFull.func1(0xdcd73e0, 0x31be630, 0x3423640)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/engine.go:2098 +0xac
created by github.com/influxdata/influxdb/tsdb/engine/tsm1.(*Engine).compactFull
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/engine.go:2094 +0xd0
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

I read something about a broken a broken wal fragment file? Unfortunately there is no way to access the files of InfluxDB to remove the file.

I had to remove InfluxDB and do a new install losing the data from the last day.

Would be nice if the files would be accessible through the terminal, so you can fix this issue. Now the files are nowhere to be found.

I run Hass on a Raspberry Pi 2, using the Hassio Raspberry Pi 2 image.

[addons-assistant]

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

[addons-assistant]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[addons-assistant]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.