I happened again. It had actually only survived for half an hour, then the blockexplorer node was offline again, because it had crashed again with a "panic: runtime error: index out of range":
I0208 22:18:58.707726 10883 downloader.go:288] Block synchronisation started
I0208 22:19:20.323027 10883 blockchain.go:1230] imported 87 block(s) (0 queued 0 ignored) including 0 txs in 8.65759476s. #1822401 [e022f6b1 / 2848295b]
I0208 22:19:26.974903 10883 blockchain.go:1230] imported 256 block(s) (0 queued 0 ignored) including 0 txs in 6.51036203s. #1822657 [9b38bfc6 / 6d5506a7]
I0208 22:19:32.260438 10883 blockchain.go:1230] imported 256 block(s) (0 queued 0 ignored) including 0 txs in 5.280125215s. #1822913 [0d3f1d6d / 79be460a]
...
I0208 22:53:03.373333 10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 6.292147ms. #1825228 [dc2d8a82 / dc2d8a82]
I0208 22:53:41.866656 10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 37.473429ms. #1825229 [aff98a9f / aff98a9f]
I0208 22:53:48.124703 10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 15.644022ms. #1825230 [85e4e08a / 85e4e08a]
I0208 22:53:52.288943 10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 14.348147ms. #1825231 [d32527f6 / d32527f6]
panic: runtime error: index out of range
Anyone understands possible reasons for this?
http://pastebin.com/xSMWS7wxThanks for switching off the new-code nodes for now. I only see these here, all with older versions:
cat peers-20170209.txt | grep "name\|peers"
admin.peers
name: "Gsoil/v1.3.3-b62bb712/linux/go1.5",
name: "Gsoil/v1.4.0/windows/go1.6",
name: "Gsoil/v1.4.0/windows/go1.6",
name: "Gsoil/v1.4.0-9174da70/linux/go1.7.1",
Please keep the new-code nodes off the mainchain, at least until this weekend. Thanks.
I restarted the node. When the
blockexplorer chain page does not show numbers but a pop up notification instead, the gsoil node has crashed again.