15

I have both a macOS system and a Raspberry Pi 3 on the same home network. Both are having Monero release 0.10.1.0 installed. I stopped the daemon on macOS, and then copied the entire .bitmonero directory from macOS to the Raspberry Pi 3 (running Ubuntu MATE 16.04), because the LMDB blockchain database should be compatible according to this answer. The copy was made at block height 1202945. Unfortunately, I can't get the monerod on the Raspberry Pi to synchronize. Event though it regularly prints something in the log, it seems stuck and currently is 75 blocks behind already:

2016-Dec-17 02:12:23.986976 [P2P9][167.114.49.139:18080 OUT]Sync data returned a new top block candidate: 1202945 -> 1203019 [Your node is 74 blocks (0 days) behind] 
SYNCHRONIZATION started
2016-Dec-17 02:12:24.661208 [P2P0][45.32.187.175:18080 OUT]Sync data returned a new top block candidate: 1202945 -> 1203020 [Your node is 75 blocks (0 days) behind] 
SYNCHRONIZATION started
2016-Dec-17 02:12:25.103400 [P2P8][37.10.71.83:18080 OUT]Sync data returned a new top block candidate: 1202945 -> 1203020 [Your node is 75 blocks (0 days) behind] 
SYNCHRONIZATION started
2016-Dec-17 02:12:25.375142 [P2P0][85.194.238.130:18080 OUT]Sync data returned a new top block candidate: 1202945 -> 1203020 [Your node is 75 blocks (0 days) behind] 
SYNCHRONIZATION started

When I do a monerod status it shows this:

Creating the logger system
Height: 1202945/1203020 (99.9%) on mainnet, not mining, net hash 37.98 MH/s, v3 (next fork in 24.4 days), up to date, 6+0 connections

How can I resolve this?

Update

Started monerod with --add-exclusive-node 192.168.0.115, my internal node's IP address, to rule out any external connectivity issues.

2017-Jan-08 21:48:22.763516 [P2P9][192.168.0.115:18080 OUT]Sync data returned a new top block candidate: 1202945 -> 1219550 [Your node is 16605 blocks (23 days) behind] 
SYNCHRONIZATION started

After I did set_log 1, I got to see 19 of the following errors in bitmonero.log, and after that nothing:

2017-Jan-08 21:52:46.665384 Attempting to get output pubkey by global index (amount 30000000000000, index 46428, count 46423), but key does not exist
2017-Jan-08 21:52:46.698247 EXCEPTION: Attempting to get output pubkey by global index (amount 30000000000000, index 46428, count 46423), but key does not exist
2017-Jan-08 21:52:48.283107 Attempting to get output pubkey by global index (amount 20000000000000, index 75368, count 75366), but key does not exist
2017-Jan-08 21:52:48.322563 EXCEPTION: Attempting to get output pubkey by global index (amount 20000000000000, index 75368, count 75366), but key does not exist
2017-Jan-08 21:52:49.951894 Attempting to get output pubkey by global index (amount 10000000000000, index 914594, count 914594), but key does not exist
2017-Jan-08 21:52:49.952457 EXCEPTION: Attempting to get output pubkey by global index (amount 10000000000000, index 914594, count 914594), but key does not exist

When I do a status after this, I got an error because the monerod process seemed to be no longer there (pressumably crashed).

dpzz
  • 4,539
  • 4
  • 22
  • 46

1 Answers1

3

There was a bug in the ARMv7-specific source code, which was triggered when using newer versions of GCC to compile the code.

https://github.com/monero-project/monero/issues/1991

It has recently been fixed.

hyc
  • 4,253
  • 19
  • 21