Monero: Genesis block hash mismatch on stagenet if --data-dir option is not set

Created on 29 Jun 2018  ยท  8Comments  ยท  Source: monero-project/monero

Reproduced with both 0.12.0 and 0.12.2.0 versions.

I'm trying to sync stagenet blockchain from scratch. At first, I have the following bitmonero-home directory structure:

/home/user/.bitmonero/
โ”œโ”€โ”€ bitmonero.log
โ”œโ”€โ”€ lmdb
โ”‚ย ย  โ”œโ”€โ”€ data.mdb
โ”‚ย ย  โ””โ”€โ”€ lock.mdb
โ”œโ”€โ”€ monero-blockchain-import.log
โ”œโ”€โ”€ monerod.conf
โ”œโ”€โ”€ monero-wallet-cli.log
โ”œโ”€โ”€ p2pstate.bin
โ””โ”€โ”€ testnet
    โ”œโ”€โ”€ 38080
    โ”‚ย ย  โ””โ”€โ”€ p2pstate.bin
    โ”œโ”€โ”€ 48080
    โ”‚ย ย  โ””โ”€โ”€ p2pstate.bin
    โ”œโ”€โ”€ 88080
    โ”‚ย ย  โ””โ”€โ”€ p2pstate.bin
    โ”œโ”€โ”€ bitmonero.log
    โ”œโ”€โ”€ lmdb
    โ”‚ย ย  โ”œโ”€โ”€ data.mdb
    โ”‚ย ย  โ””โ”€โ”€ lock.mdb
    โ””โ”€โ”€ p2pstate.bin

then i start my monerod as follows:

$ ./bitmonerod --stagenet --log-level=2

and a lot of errors like (full log is here - https://www.dropbox.com/s/jyte292csmvxj9c/bitmonero.log?dl=0):

2018-06-29 13:58:52.300 [P2P5]  ERROR   net.p2p src/cryptonote_core/blockchain.cpp:2011 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block mismatch: 
id: <96375dc8a8dd960c33f59190edf51a3f458d6e8d8a2c7bc7517c5dee26955174>, 
expected: <76ee3cc98646292206cd3e86f74d88b4dcc1d937088645e9b0cbca84b7ce74eb>,
 dropping connection

after deleting ~/.bitmonero/stagenet directory and restarting daemon with --data-dir option being set to default value it works just fine:

$ rm -rf ~/.bitmonero/stagenet && ./monerod --stagenet --log-level=2 --data-dir=/home/user/.bitmonero/stagenet
````
log:

2018-06-29 14:33:17.373 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1171 [18.191.223.168:38080 OUT] Synced 11600/107757
2018-06-29 14:33:18.110 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1171 [18.191.223.168:38080 OUT] Synced 11620/107757
2018-06-29 14:33:18.798 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1171 [18.191.223.168:38080 OUT] Synced 11640/107757
2018-06-29 14:33:19.607 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1171 [92.35.34.106:38080 OUT] Synced 11660/107757

```

invalid

All 8 comments

I'd want to see a level 2 log of the other nodes, the ones sending the apparently wrong block. AFAICT this is a problem on the other side, which is odd since there are many having it...

I accidentally noticed that if start daemon with option --data-dir=~/.bitmonero/stagenet it create directory ~ in cwd.

~ is a bash thing. If you use another shell, it won't replace it. Use $HOME instead.

but i use bash and apparently it doesn't expand the wildcard

This isn't the place to discuss how Bash works.

But drop the = if you want bash to see it.

+invalid

Was this page helpful?
0 / 5 - 0 ratings