🌱[ANN] SOIL | Environmental | Agriculture | Smart Contracts | Sustainable

[Dubrovin]

Hello! I have left the coins on the old wallet! What will happen to them? how to get them back?

[holgerkpedersen]

Hello! I have left the coins on the old wallet! What will happen to them? how to get them back?

I guess, you just let the coins be where they are, until we go live with the homestead version of gsoil.exe. They will reappear when the network returns to normal mining on the main net.

Always make a copy of your gsoil/keystore folder to a safe place; if you want to be able to keep the existing wallet.

[altsheets]

Again.

Code:

panic: runtime error: index out of range

I am restarting it now, but I cannot keep manually restarting the gsoil node of the block explorer every few hours.

Anyone ever had that?

My gsoil node of the blockexplorer crashed.

First time I see this, after years, literally:

Code:

...

This ^ is part of the end of the logfile (if you need the full logfile, just tell me).


This is the node version I am running:

Code:

gsoil version

Gsoil
Version: 1.4.0
Git Commit: 9f893c8dd8f80b4be52c7019069d00bfa49a945a
Protocol Versions: [63 62 61]
Network Id: 42
Go Version: go1.4.2
OS: linux
GOPATH=/root/go
GOROOT=/usr/local/go

Just to make sure that it has really never happened before: I have logfiles back to May 2016, and I checked them:

Code:

 cat nohup.out_2016* | grep  goroutine

- none of them has such an error message.

And it happened again.

This time full error log:   http://pastebin.com/xSMWS7wx

Anyone understands this?


Could this be the reason for the sudden crashes?

Those of you who are trying the new homestead code ...

Code:

...

... could you please do tests first: On the testnet, please try out mixing old and new gsoil code versions. Thanks.

?

For testing: Could you please switch off all nodes which are trying to run the new code on mainnet, just to see if it then still happens?

[altsheets]

WTB 100k soil @ 35 sat

WTB 100k soil @ 35 sat

WTS 98k @ 150 sat each

See WTB/WTS soil.

[holgerkpedersen]

I am in now

admin.addNode("enode://a623eadd411ab6d612e091716706a22de86a9d01e932bcd170463e46920073be04e0c9263a3c2720bb18a446d1a95d39e9a90f903e954514ea530296a462d637@2.105.196.29:39340");

[altsheets]

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":

Code:

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/xSMWS7wx


Thanks for switching off the new-code nodes for now.  I only see these here, all with older versions:

Code:

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.

[holgerkpedersen]

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":

Code:

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/xSMWS7wx


Thanks for switching off the new-code nodes for now.  I only see these here, all with older versions:

Code:

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.

I have no clue; why you get an error, but something is indexing into an illegal location in some sort of collection. There could be some misunderstandings related to intermixing of testnet and mainnet addressing. IMO; it's likely causing trouble.

Are you preparing the homestead explorer?

[altsheets]

Anyone understands possible reasons for this? http://pastebin.com/xSMWS7wx
...
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.

I have no clue; why you get an error, but something is indexing into an illegal location in some sort of collection. There could be some misunderstandings related to intermixing of testnet and mainnet addressing. IMO; it's likely causing trouble.

Are you preparing the homestead explorer?

I am a bit reluctant to trust the new code, unless we can 100% exclude the possibility that it might be creating transactions or p2p communications that crashed my node - which had been running fine for almost a year, until block 1820081.

[apolo11]

I am a bit reluctant to trust the new code, unless we can 100% exclude the possibility that it might be creating transactions or p2p communications that crashed my node - which had been running fine for almost a year, until block 1820081.

 maybe is coincidence but to my observation, errors occurs after a mining pool has been released (i mined before at that pool, was good)   
 is it possible to run a test version of gsoil at mainchain? because pools soil links , source description redirecting to github test code
 am i right?     
 i am not a tech guy, that's  just thoughts
 
 Cheers   

[Dunkelheit667]

I'm getting this on testnet, any hints?

Code:

E0210 17:45:00.776716    3691 blockchain.go:1384] Bad block #460001 (0x5edaeaebdf53887e1c93cccbb9115680b8991b416b0ce7216bfd3bc29eac22b6)
E0210 17:45:00.776844    3691 blockchain.go:1385] Difficulty check failed for header 5697432, 5151670
I0210 17:45:00.805252    3691 downloader.go:267] Synchronisation failed: Difficulty check failed for header 5697432, 5151670

Code:

instance: Gsoil_TNET/v1.4.3-f0475b8f/linux/go1.7.5
 datadir: /root/.soiltnet
coinbase: 0x5d575c05ab6462b0ff748a2f4e5cd4b0a0306e7c
at block: 460000 (Thu, 09 Feb 2017 21:14:41 CET)
modules: admin:1.0 db:1.0 debug:1.0 eth:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0

[ExEric3]

Anyone understands possible reasons for this? http://pastebin.com/xSMWS7wx
...
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.

I have no clue; why you get an error, but something is indexing into an illegal location in some sort of collection. There could be some misunderstandings related to intermixing of testnet and mainnet addressing. IMO; it's likely causing trouble.

Are you preparing the homestead explorer?

I am a bit reluctant to trust the new code, unless we can 100% exclude the possibility that it might be creating transactions or p2p communications that crashed my node - which had been running fine for almost a year, until block 1820081.

Try look now if it crashes. I put http://soil.miners-zone.net back to old code since that homestead gsoil looks unstable.

Code:

Starting Gsoil/Miners-Zone/v1.4.0-9174da70/linux/go1.7.5

Here are working peers which have opened ports. If you have syncing problems create in data directory of soil this file: static-nodes.json and inside it put this:

Code:

[
"enode://36667a60f555c254957b56aca013b507bb9e2a2f7b2484be7c70471dee268492907a11ee00329af761574ae2be57562660b95738654a2ca96bcf8ae88974033f@51.15.130.241:39420",
"enode://5aea33dbeacb10ad7df148947e17947c5ebb1ac0fedc7b4d65d01dd61907349830aa24961e2069e07f81ee4635acfd3c4cb4039da4f25d81455d8b7d2c78e4c5@173.254.234.18:39420",
"enode://77b71660f5cb025e337bfb9bebf0c71001849fab8786d7b13fe3e081841f35cbf463cfc46fd570ef09829553524806be76b051e4f16afa7daf77265eb9733335@192.241.129.165:39420",
"enode://d61c21eb1c83e60e31d8cb327d422a5fa4ca4a958aa6e7db260e742ebc9bfe696d6d68e416cfe445f2de724cd10c860b3ab1aaafac982363acd930642c71c67e@103.82.54.14:39420",
"enode://46fce6fdc328596df97c8c2e4d1744b9bf5bfd540ff8cf95e4880d797bd92e2cb52a81f38a9a49e51079f875c1adbdc2d4d6f503253e2d7188a494d421bd968b@178.62.133.174:39420",
"enode://5595675ef82cbc49ad2704096db7bee8fac221fcbf65c3ece75827e7078d10df99688946add3efd418712e9643633cbd40b3d9b403168050a2b011dd3260c9af@37.120.184.125:39420"
]

[martymcfly2015]

I'm getting this on testnet, any hints?

Code:

E0210 17:45:00.776716    3691 blockchain.go:1384] Bad block #460001 (0x5edaeaebdf53887e1c93cccbb9115680b8991b416b0ce7216bfd3bc29eac22b6)
E0210 17:45:00.776844    3691 blockchain.go:1385] Difficulty check failed for header 5697432, 5151670
I0210 17:45:00.805252    3691 downloader.go:267] Synchronisation failed: Difficulty check failed for header 5697432, 5151670

Code:

instance: Gsoil_TNET/v1.4.3-f0475b8f/linux/go1.7.5
 datadir: /root/.soiltnet
coinbase: 0x5d575c05ab6462b0ff748a2f4e5cd4b0a0306e7c
at block: 460000 (Thu, 09 Feb 2017 21:14:41 CET)
modules: admin:1.0 db:1.0 debug:1.0 eth:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0

Yes, the problem is that you have no peers - other connected clients - which are on the right chain.
Maybe this node is on the right chain:
admin.addPeer("enode://45ec3e9efbe74e7b6a4accd04ea003fca120e4fd812c6dba6a194e657a1060d0134e9b46462207b52e3ca9a796626fef127f26432f837964b5945f9581744e58@62.227.107.119:39340")
Restart soil and add the node. If this wont help - maybe holgerkpedersen can help with his node when he's back online.

[Dunkelheit667]

...
Maybe this node is on the right chain:
admin.addPeer("enode://45ec3e9efbe74e7b6a4accd04ea003fca120e4fd812c6dba6a194e657a1060d0134e9b46462207b52e3ca9a796626fef127f26432f837964b5945f9581744e58@62.227.107.119:39340")

Restart soil and add the node. If this wont help - maybe holgerkpedersen can help with his node when he's back online.

That's funny, the node above is my node. However, I've restarted testnet soil, added my node as a peer and it synced.

[ExEric3]

Network Status is installed here: http://soil.miners-zone.net:9090/

If anyone wanna put his node stats on this page pm me for password.

[holgerkpedersen]

I'm getting this on testnet, any hints?

Code:

E0210 17:45:00.776716    3691 blockchain.go:1384] Bad block #460001 (0x5edaeaebdf53887e1c93cccbb9115680b8991b416b0ce7216bfd3bc29eac22b6)
E0210 17:45:00.776844    3691 blockchain.go:1385] Difficulty check failed for header 5697432, 5151670
I0210 17:45:00.805252    3691 downloader.go:267] Synchronisation failed: Difficulty check failed for header 5697432, 5151670

Code:

instance: Gsoil_TNET/v1.4.3-f0475b8f/linux/go1.7.5
 datadir: /root/.soiltnet
coinbase: 0x5d575c05ab6462b0ff748a2f4e5cd4b0a0306e7c
at block: 460000 (Thu, 09 Feb 2017 21:14:41 CET)
modules: admin:1.0 db:1.0 debug:1.0 eth:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0

Yes, the problem is that you have no peers - other connected clients - which are on the right chain.
We had a fork to homestead on block #460000 on the testnet with client version "Gsoil_TNET/v1.4.3" and I we have old testnet clients online (TNET_v1.4.1) which are on it's on chain now.

Maybe this node is on the right chain:
admin.addPeer("enode://45ec3e9efbe74e7b6a4accd04ea003fca120e4fd812c6dba6a194e657a1060d0134e9b46462207b52e3ca9a796626fef127f26432f837964b5945f9581744e58@62.227.107.119:39340")

Restart soil and add the node. If this wont help - maybe holgerkpedersen can help with his node when he's back online.

I have same problem as you guys.

I've started my node just a few minutes ago.

My node has the following properties:

admin.addPeer("enode://a623eadd411ab6d612e091716706a22de86a9d01e932bcd170463e46920073be04e0c9263a3c2720bb18a446d1a95d39e9a90f903e954514ea530296a462d637@2.105.196.29:39340")


> admin.peers
[{
    caps: ["eth/61", "eth/62", "eth/63"],
    id: "45ec3e9efbe74e7b6a4accd04ea003fca120e4fd812c6dba6a194e657a1060d0134e9b46462207b 52e3ca9a796626fef127f26432f837964b5945f9581744e58",
    name: "Gsoil_TNET/v1.4.3-f0475b8f/linux/go1.7.5",
    network: {
      localAddress: "192.168.0.16:39340",
      remoteAddress: "62.227.107.119:54268"
    },
    protocols: {
      eth: {
        difficulty: 174846653126,
        head: "f870969d8d16b7b7b3188b637ea3cfe680b17bdab85d2c691e77a318c7f8bb2e",
        version: 63
      }
    }
}, {
    caps: ["eth/61", "eth/62", "eth/63"],
    id: "e042fbe55beaff48ffbb0c1caabd224267260b660c738f2fd33e53d3b18ef984734323fe7be5be2 3e3faa3d9358aa32c8d02337bfb921fc4abd2fac36e041b4a",
    name: "Gsoil_TNET/v1.4.3/windows/go1.5.4",
    network: {
      localAddress: "192.168.0.16:39340",
      remoteAddress: "77.78.26.74:50353"
    },
    protocols: {
      eth: {
        difficulty: 174856467025,
        head: "ea301f1bfd2b167a597824fb15f8bd8c7d3b17376023884a5d3aaee1a55be348",
        version: 63
      }
    }
}]

I am also cpu mining, therefore I use  ">miner.start(1)", to keep things moving. If nobody is mining; we won't get far, and it explains, the missing blocks to be imported.

[martymcfly2015]

Anyone understands possible reasons for this? http://pastebin.com/xSMWS7wx
...
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.

I have no clue; why you get an error, but something is indexing into an illegal location in some sort of collection. There could be some misunderstandings related to intermixing of testnet and mainnet addressing. IMO; it's likely causing trouble.

Are you preparing the homestead explorer?

I am a bit reluctant to trust the new code, unless we can 100% exclude the possibility that it might be creating transactions or p2p communications that crashed my node - which had been running fine for almost a year, until block 1820081.

Fair enough. It might be that the new code interfere old client communication.
I think, if all would upgrade to the new client, problems would disappear.
I think the best is to play with the testnet for the moment - if doubts are gone - we can all upgrade to the new gsoil in the future if you want.

[holgerkpedersen]

It is moving, but try to start mining. I even get blocks, so I am not alone anymore

I0210 20:28:05.562993    4972 worker.go:447]    Mined 5 blocks back: block #460550
I0210 20:28:05.564504    4972 worker.go:569] commit new work on block 460556 with 0 txs & 0 uncles. Took 517.1µs
I0210 20:28:18.399951    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 4.0112ms. #460556 [adb3db4a / adb3db4a]
I0210 20:28:18.400429    4972 worker.go:569] commit new work on block 460557 with 0 txs & 0 uncles. Took 477.5µs
I0210 20:28:18.400929    4972 worker.go:447]    Mined 5 blocks back: block #460551
I0210 20:28:53.702442    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.517ms. #460557 [567f43c4 / 567f43c4]
I0210 20:28:53.702936    4972 worker.go:569] commit new work on block 460558 with 0 txs & 0 uncles. Took 0
I0210 20:30:09.724233    4972 worker.go:348]   Mined block (#460558 / ff1d7346). Wait 5 blocks for confirmation
I0210 20:30:09.725768    4972 worker.go:569] commit new work on block 460559 with 0 txs & 0 uncles. Took 1.5345ms
I0210 20:30:09.725768    4972 worker.go:447]    Mined 5 blocks back: block #460553
I0210 20:30:09.726239    4972 worker.go:569] commit new work on block 460559 with 0 txs & 0 uncles. Took 471.5µs
I0210 20:31:50.042980    4972 worker.go:348]   Mined block (#460559 / add1cb55). Wait 5 blocks for confirmation
I0210 20:31:50.043451    4972 worker.go:569] commit new work on block 460560 with 0 txs & 0 uncles. Took 471.2µs
I0210 20:31:50.043451    4972 worker.go:447]    Mined 5 blocks back: block #460554
I0210 20:31:50.044455    4972 worker.go:569] commit new work on block 460560 with 0 txs & 0 uncles. Took 0
I0210 20:32:02.218211    4972 worker.go:348]   Mined block (#460560 / be63621c). Wait 5 blocks for confirmation
I0210 20:32:02.218713    4972 worker.go:569] commit new work on block 460561 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:32:02.219750    4972 worker.go:447]    Mined 5 blocks back: block #460555
I0210 20:32:02.220440    4972 worker.go:569] commit new work on block 460561 with 0 txs & 0 uncles. Took 0
I0210 20:32:52.201073    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.0083ms. #460561 [24b739b5 / 24b739b5]
I0210 20:32:52.201575    4972 worker.go:569] commit new work on block 460562 with 0 txs & 0 uncles. Took 502.7µs
I0210 20:32:55.645297    4972 worker.go:348]   Mined block (#460562 / e7632c10). Wait 5 blocks for confirmation
I0210 20:32:55.645802    4972 worker.go:569] commit new work on block 460563 with 0 txs & 0 uncles. Took 505.7µs
I0210 20:32:55.646810    4972 worker.go:569] commit new work on block 460563 with 0 txs & 0 uncles. Took 0
I0210 20:33:38.127977    4972 worker.go:348]   Mined block (#460563 / a14412c9). Wait 5 blocks for confirmation
I0210 20:33:38.128952    4972 worker.go:569] commit new work on block 460564 with 0 txs & 0 uncles. Took 0
I0210 20:33:38.129473    4972 worker.go:447]    Mined 5 blocks back: block #460558
I0210 20:33:38.130457    4972 worker.go:569] commit new work on block 460564 with 0 txs & 0 uncles. Took 491.3µs
I0210 20:33:59.003788    4972 worker.go:348]   Mined block (#460564 / ce0e1bcf). Wait 5 blocks for confirmation
I0210 20:33:59.004289    4972 worker.go:569] commit new work on block 460565 with 0 txs & 0 uncles. Took 0
I0210 20:33:59.005291    4972 worker.go:447]    Mined 5 blocks back: block #460559
I0210 20:33:59.006298    4972 worker.go:569] commit new work on block 460565 with 0 txs & 0 uncles. Took 497µs
I0210 20:34:30.187160    4972 worker.go:348]   Mined block (#460565 / 392a4d14). Wait 5 blocks for confirmation
I0210 20:34:30.187663    4972 worker.go:569] commit new work on block 460566 with 0 txs & 0 uncles. Took 0
I0210 20:34:30.188730    4972 worker.go:447]    Mined 5 blocks back: block #460560
I0210 20:34:30.189735    4972 worker.go:569] commit new work on block 460566 with 0 txs & 0 uncles. Took 502.1µs
I0210 20:35:38.571857    4972 worker.go:348]   Mined block (#460566 / 855b71cf). Wait 5 blocks for confirmation
I0210 20:35:38.572332    4972 worker.go:569] commit new work on block 460567 with 0 txs & 0 uncles. Took 474.7µs
I0210 20:35:38.573334    4972 worker.go:569] commit new work on block 460567 with 0 txs & 0 uncles. Took 0
I0210 20:36:03.552134    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5086ms. #460567 [eff6e521 / eff6e521]
I0210 20:36:03.552607    4972 worker.go:569] commit new work on block 460568 with 0 txs & 0 uncles. Took 473.5µs
I0210 20:36:03.553656    4972 worker.go:447]    Mined 5 blocks back: block #460562
I0210 20:36:08.219405    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5095ms. #460568 [d57de49a / d57de49a]
I0210 20:36:08.220408    4972 worker.go:569] commit new work on block 460569 with 0 txs & 0 uncles. Took 501.4µs
I0210 20:36:08.220408    4972 worker.go:447]    Mined 5 blocks back: block #460563
I0210 20:36:19.500856    4972 worker.go:348]   Mined block (#460569 / 57cdfdaf). Wait 5 blocks for confirmation
I0210 20:36:19.501382    4972 worker.go:569] commit new work on block 460570 with 0 txs & 0 uncles. Took 0
I0210 20:36:19.502404    4972 worker.go:447]    Mined 5 blocks back: block #460564
I0210 20:36:19.502898    4972 worker.go:569] commit new work on block 460570 with 0 txs & 0 uncles. Took 0
I0210 20:36:32.566713    4972 worker.go:348]   Mined block (#460570 / dc6cf3b8). Wait 5 blocks for confirmation
I0210 20:36:32.567186    4972 worker.go:569] commit new work on block 460571 with 0 txs & 0 uncles. Took 473.5µs
I0210 20:36:32.567688    4972 worker.go:447]    Mined 5 blocks back: block #460565
I0210 20:36:32.568691    4972 worker.go:569] commit new work on block 460571 with 0 txs & 0 uncles. Took 501.1µs
I0210 20:37:31.435356    4972 worker.go:348]   Mined block (#460571 / 9d20b8e2). Wait 5 blocks for confirmation
I0210 20:37:31.435826    4972 worker.go:569] commit new work on block 460572 with 0 txs & 0 uncles. Took 469.6µs
I0210 20:37:31.436327    4972 worker.go:447]    Mined 5 blocks back: block #460566
I0210 20:37:31.437331    4972 worker.go:569] commit new work on block 460572 with 0 txs & 0 uncles. Took 492.2µs
I0210 20:38:27.147922    4972 worker.go:348]   Mined block (#460572 / ba62b87e). Wait 5 blocks for confirmation
I0210 20:38:27.148397    4972 worker.go:569] commit new work on block 460573 with 0 txs & 0 uncles. Took 475.4µs
I0210 20:38:27.149898    4972 worker.go:569] commit new work on block 460573 with 0 txs & 0 uncles. Took 500µs
I0210 20:38:29.277110    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.9777ms. #460573 [2c19f24a / 2c19f24a]
I0210 20:38:29.277617    4972 worker.go:569] commit new work on block 460574 with 0 txs & 0 uncles. Took 506.6µs
I0210 20:39:32.786290    4972 worker.go:348]   Mined block (#460574 / 332801c0). Wait 5 blocks for confirmation
I0210 20:39:32.786792    4972 worker.go:569] commit new work on block 460575 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:39:32.787795    4972 worker.go:447]    Mined 5 blocks back: block #460569
I0210 20:39:32.788769    4972 worker.go:569] commit new work on block 460575 with 0 txs & 0 uncles. Took 0
I0210 20:39:50.108510    4972 worker.go:348]   Mined block (#460575 / f61a9bee). Wait 5 blocks for confirmation
I0210 20:39:50.108985    4972 worker.go:569] commit new work on block 460576 with 0 txs & 0 uncles. Took 0
I0210 20:39:50.110001    4972 worker.go:447]    Mined 5 blocks back: block #460570
I0210 20:39:50.110489    4972 worker.go:569] commit new work on block 460576 with 0 txs & 0 uncles. Took 0
I0210 20:40:38.703360    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.9762ms. #460576 [6e291944 / 6e291944]
I0210 20:40:38.703871    4972 worker.go:569] commit new work on block 460577 with 0 txs & 0 uncles. Took 510.8µs
I0210 20:40:38.704864    4972 worker.go:447]    Mined 5 blocks back: block #460571
I0210 20:41:15.733660    4972 worker.go:348]   Mined block (#460577 / 53c06a5b). Wait 5 blocks for confirmation
I0210 20:41:15.734129    4972 worker.go:569] commit new work on block 460578 with 0 txs & 0 uncles. Took 0
I0210 20:41:15.735133    4972 worker.go:447]    Mined 5 blocks back: block #460572
I0210 20:41:15.736134    4972 worker.go:569] commit new work on block 460578 with 0 txs & 0 uncles. Took 500.6µs
I0210 20:41:16.276103    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5095ms. #460578 [eb7e9b91 / eb7e9b91]
I0210 20:41:16.277172    4972 worker.go:569] commit new work on block 460579 with 0 txs & 0 uncles. Took 568.2µs
I0210 20:41:31.213287    4972 worker.go:348]   Mined block (#460579 / 88c89cf3). Wait 5 blocks for confirmation
I0210 20:41:31.213790    4972 worker.go:569] commit new work on block 460580 with 0 txs & 0 uncles. Took 503µs
I0210 20:41:31.214291    4972 worker.go:447]    Mined 5 blocks back: block #460574
I0210 20:41:31.215293    4972 worker.go:569] commit new work on block 460580 with 0 txs & 0 uncles. Took 500.2µs
I0210 20:41:36.706483    4972 worker.go:348]   Mined block (#460580 / 5edc615c). Wait 5 blocks for confirmation
I0210 20:41:36.706984    4972 worker.go:569] commit new work on block 460581 with 0 txs & 0 uncles. Took 501.2µs
I0210 20:41:36.707485    4972 worker.go:447]    Mined 5 blocks back: block #460575
I0210 20:41:36.708489    4972 worker.go:569] commit new work on block 460581 with 0 txs & 0 uncles. Took 503µs
I0210 20:42:28.475823    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.039ms. #460581 [5313061e / 5313061e]
I0210 20:42:28.476307    4972 worker.go:569] commit new work on block 460582 with 0 txs & 0 uncles. Took 484.3µs
I0210 20:42:35.095066    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.0077ms. #460582 [5fd01cd2 / 5fd01cd2]
I0210 20:42:35.095567    4972 worker.go:569] commit new work on block 460583 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:42:35.096069    4972 worker.go:447]    Mined 5 blocks back: block #460577
I0210 20:42:43.569056    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5137ms. #460583 [2996ecbb / 2996ecbb]
I0210 20:42:43.569553    4972 worker.go:569] commit new work on block 460584 with 0 txs & 0 uncles. Took 497µs
I0210 20:42:45.680098    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.0383ms. #460584 [e38298bf / e38298bf]
I0210 20:42:45.680571    4972 worker.go:569] commit new work on block 460585 with 0 txs & 0 uncles. Took 472.4µs
I0210 20:42:45.681581    4972 worker.go:447]    Mined 5 blocks back: block #460579
I0210 20:42:48.626785    4972 worker.go:348]   Mined block (#460585 / 9fb68535). Wait 5 blocks for confirmation
I0210 20:42:48.627261    4972 worker.go:569] commit new work on block 460586 with 0 txs & 0 uncles. Took 0
I0210 20:42:48.628262    4972 worker.go:447]    Mined 5 blocks back: block #460580
I0210 20:42:48.628763    4972 worker.go:569] commit new work on block 460586 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:42:57.169952    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5405ms. #460586 [3452e42a / 3452e42a]
I0210 20:42:57.170423    4972 worker.go:569] commit new work on block 460587 with 0 txs & 0 uncles. Took 470.2µs
I0210 20:43:11.245575    4972 worker.go:348]   Mined block (#460587 / eeeeadd7). Wait 5 blocks for confirmation
I0210 20:43:11.246050    4972 worker.go:569] commit new work on block 460588 with 0 txs & 0 uncles. Took 474.7µs
I0210 20:43:11.247053    4972 worker.go:569] commit new work on block 460588 with 0 txs & 0 uncles. Took 501.2µs
I0210 20:43:14.748040    4972 worker.go:348]   Mined block (#460588 / 18a510f9). Wait 5 blocks for confirmation
I0210 20:43:14.748533    4972 worker.go:569] commit new work on block 460589 with 0 txs & 0 uncles. Took 0
I0210 20:43:14.750025    4972 worker.go:569] commit new work on block 460589 with 0 txs & 0 uncles. Took 505.6µs
I0210 20:43:24.068162    4972 worker.go:348]   Mined block (#460589 / 90f7f5bf). Wait 5 blocks for confirmation
I0210 20:43:24.068632    4972 worker.go:569] commit new work on block 460590 with 0 txs & 0 uncles. Took 470µs
I0210 20:43:24.070136    4972 worker.go:569] commit new work on block 460590 with 0 txs & 0 uncles. Took 489.5µs
I0210 20:43:46.582646    4972 worker.go:348]   Mined block (#460590 / a6860e2e). Wait 5 blocks for confirmation
I0210 20:43:46.583115    4972 worker.go:569] commit new work on block 460591 with 0 txs & 0 uncles. Took 469.6µs
I0210 20:43:46.584621    4972 worker.go:447]    Mined 5 blocks back: block #460585
I0210 20:43:46.585121    4972 worker.go:569] commit new work on block 460591 with 0 txs & 0 uncles. Took 500µs
I0210 20:44:16.008364    4972 worker.go:348]   Mined block (#460591 / 6d539f9b). Wait 5 blocks for confirmation
I0210 20:44:16.008867    4972 worker.go:569] commit new work on block 460592 with 0 txs & 0 uncles. Took 502.7µs
I0210 20:44:16.010379    4972 worker.go:569] commit new work on block 460592 with 0 txs & 0 uncles. Took 501.5µs

[martymcfly2015]

Testnet info:

The testnet has passed block 460000 and is on homestead code level now! The testnet is using a different home folder - so it's safe to use and will not interfere your mainnet folder. Please have a go and play with it.
linux:
git clone https://github.com/martymcfly2015/go-soil.git
cd go-soil
git checkout testnet
make
build/gsoil account new
build/gsoil console

The very good tutorials from AndreasKrueger:
https://github.com/drandreaskrueger/cryptomanuals/blob/master/SOIL/gsoiltestnet.md

windows:
https://github.com/martymcfly2015/go-soil/releases/download/1.4.3_testnet/gsoil_MMF_TESTNET_v1.4.3.zip

If you like my work please donate soil

[Dunkelheit667]

It is moving, but try to start mining. I even get blocks, so I am not alone anymore
...

I've tried, but unfortunately mining will crash the node instantly on my raspberry for any reason without throwing an error message. Even with a 4GB swap file. Sooo... thanks for keeping the chain going!

[holgerkpedersen]

It is moving, but try to start mining. I even get blocks, so I am not alone anymore
...

I've tried, but unfortunately mining will crash the node instantly on my raspberry for any reason without throwing an error message. Even with a 4GB swap file. Sooo... thanks for keeping the chain going!

Okay, small isn't always beautiful. Especially, when it crashes.