Topic: [ANN][ARG] Argentum || A New Begining || UPDATE YOUR WALLET || - page 15. (Read 59642 times)

My client is also getting stuck constantly. I think the problem is something to do with the scrypt code:


crazy diff......

I've received the same errors, but keep restarting the client with -reindex. After several of those, I've now gotten up to block 2392566. When it gets stuck, I just do another -reindex.

Yesterday I had two clients with blocks and headers synced to 2390214. I created a scrypt and sha pool. When I found a sha block, it found a chain further along in block height started syncing with it. The same thing happened with the scrypt pool. After they synced, I continued mining and my windows client found the chain and synced up as well.

Here's the problem. Eventually I received this error on every client synced with the chain, and my windows client produced it's own error as well. This crashed every one of my clients that was synced with the blockchain at the time, mining or not.

:~/.argentum$ argentumd: main.cpp:4223: void ProcessGetData(CNode*): Assertion `!"cannot load block from disk"' failed

Debug.log

ERROR: CheckProofOfWork(): hash doesn't match nBits
2017-05-09 11:42:22 ERROR: CheckAuxPowProofOfWork : non-AUX proof of work failed
2017-05-09 11:42:22 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=5, nPos=122908179)

What I can't figure out is why it won't just reject the bad block and move on, like its supposed to do. It appears that its first writing the bad block to the blockchain then rejecting it, which corrupts your local copy of the blockchain until a reindex is done where it will finally discard the bad block as its supposed to. Until a reindex is done, i get the Assertion which crashed every client connected and synced with it.

Mine is stuck at 2385249 with 7-9 nodes, going no further. 

Hmm, I guess I'll have to wait then.

My sha256 node's debug.log is filled with this

2017-05-07 03:25:55 ERROR: CheckProofOfWork(): hash doesn't match nBits
2017-05-07 03:25:55 ERROR: CheckAuxPowProofOfWork : AUX proof of work failed
2017-05-07 03:25:55 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=11, nPos=21371058)
2017-05-07 03:25:55 ERROR: CheckProofOfWork(): hash doesn't match nBits
2017-05-07 03:25:55 ERROR: CheckAuxPowProofOfWork : AUX proof of work failed
2017-05-07 03:25:55 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=11, nPos=21371706)
2017-05-07 03:25:55 ERROR: CheckProofOfWork(): hash doesn't match nBits

My scrypt node at the exact same height shows no errors.

I am having the same issue with the bootstrap only indexing to 2,388,214. Once we fix the sha256 client errors, we can just continue the blockchain from there.

I attempted again with the following steps:
1. Moved all the files/folders in the blocks folder to a folder called old.bad
2. Moved all the files/folders in the chainstate folder to a folder called old.bad
3. Moved .lock, bootstrap.dat.old, and debug.log to a folder called old.bad
4. Downloaded a fresh copy of bootstrap.dat
5. Restarted v3.11.3.1-72cf1f3 with -reindex

Once again, the bootstrap.dat import failed after block 2,388,213:

Actually I'm pretty sure the bootstrap didn't import fine. I'm stuck at the same block after bootstrap, and reviewing my debug log I found this:


So, it looks like the bootstrap failed after block 2,388,213.

One of the nodes has progressed, but is still not fully synced.

Blocks: 2,390,231
Headers: 2,392,171

From debug.log
MapBlockIndex.size() = 2,398,140

So somebody is mining. I don't know why the blocks aren't being relayed.

Thank you protonn and aatheus for providing the bootstrap.  I really appreciate it!

The bootstrap imported just fine, but the wallet still will not sync despite 18 network connections (10 out / 8 in) and only being 8 days behind.

The wallet gets stuck at block 2,388,213 (which interestingly is about 2000 blocks behind the bootstrap block indicated by protonn).  Debug log is more of the same, just a bunch of dropped connections.  Total network traffic after one hour is only about 50KB in and out, so it's not even trying I don't think.  I did a reindex just for kicks, but it did not help.

Sorry I can't be more helpful in figuring this out. Let me know if I can provide any more info.

I compressed the file and uploaded it to my web server. Please feel free to download and use it. File size is ~ 707MB - sha256 sum 9c79237869d2d6be897dabad394d3c28fb9099f87a153a0872075c118511f671

http://www.taur.net/mirrors/argentum/bootstrap.dat.gz

Thanks! The file is downloading now. I'll give it a try. Would it be possible to get this new link added to the README.md on https://github.com/argentumproject/argentum/ ?

BOOTSTRAP

https://electrum-arg.org/bootstrap.dat
sha256 checksum 940f0a958ad79c311c90c899b1907c61668e23b9034f698e1174191a10428718

updated bootstrap May 15 2017
Block 2,400,684

Are any seed nodes, or any other v3 nodes, actually alive? I am seeing lots of connection refused/no route to host errors. Is anyone making a bootstrap.zip file available? argcurrency.org is long gone.


2017-05-03 19:40:42 Argentum version v3.11.3.1-72cf1f3 (2017-04-27 11:22:04 -0500)
2017-05-03 19:40:42 Using OpenSSL version OpenSSL 1.0.2g  1 Mar 2016
2017-05-03 19:40:42 Using BerkeleyDB version Berkeley DB 5.3.28: (September  9, 2013)
2017-05-03 19:40:42 Default data directory /home/aatheus/.argentum
2017-05-03 19:40:42 Using data directory /home/aatheus/.argentum
2017-05-03 19:40:42 Using config file /home/aatheus/.argentum/argentum.conf
2017-05-03 19:40:42 Using at most 125 connections (1024 file descriptors available)
2017-05-03 19:40:42 Using 8 threads for script verification
2017-05-03 19:40:42 scheduler thread start
2017-05-03 19:40:42 Binding RPC on address ::1 port 13581 (IPv4+IPv6 bind any: 0)
2017-05-03 19:40:42 Binding RPC on address 127.0.0.1 port 13581 (IPv4+IPv6 bind any: 0)
2017-05-03 19:40:42 scrypt: using scrypt-sse2 as built.
2017-05-03 19:40:42 Using wallet wallet.dat
2017-05-03 19:40:42 init message: Verifying wallet...
2017-05-03 19:40:42 CDBEnv::Open: LogDir=/home/aatheus/.argentum/database ErrorFile=/home/aatheus/.argentum/db.log
2017-05-03 19:40:42 Bound to [::]:13580
2017-05-03 19:40:42 Bound to 0.0.0.0:13580
2017-05-03 19:40:42 Cache configuration:
2017-05-03 19:40:42 * Using 2.0MiB for block index database
2017-05-03 19:40:42 * Using 39.5MiB for chain state database
2017-05-03 19:40:42 * Using 86.5MiB for in-memory UTXO set
2017-05-03 19:40:42 init message: Loading block index...
2017-05-03 19:40:42 Opening LevelDB in /home/aatheus/.argentum/blocks/index
2017-05-03 19:40:42 Opened LevelDB successfully
2017-05-03 19:40:42 Opening LevelDB in /home/aatheus/.argentum/chainstate
2017-05-03 19:40:42 Opened LevelDB successfully
2017-05-03 19:40:42 LoadBlockIndexDB: last block file = 0
2017-05-03 19:40:42 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2017-05-03 19:40:42 Checking all blk files are present...
2017-05-03 19:40:42 LoadBlockIndexDB: transaction index disabled
2017-05-03 19:40:42 LoadBlockIndexDB: address index disabled
2017-05-03 19:40:42 Initializing databases...
2017-05-03 19:40:42 Pre-allocating up to position 0x1000000 in blk00000.dat
2017-05-03 19:40:42 UpdateTip: new best=88c667bc63167685e4e4da058fffdfe8e007e5abffd6855de52ad59df7bb0bb2 height=0 algo=1 (scrypt) log2_work=20.000022 tx=1 date=2013-05-22 05:18:08 progress=0.000000 cache=0.0MiB(0tx)
2017-05-03 19:40:43 init message: Verifying blocks...
2017-05-03 19:40:43  block index             400ms
2017-05-03 19:40:43 init message: Loading wallet...
2017-05-03 19:40:43 nFileVersion = 3110301
2017-05-03 19:40:43 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total
2017-05-03 19:40:43  wallet                   50ms
2017-05-03 19:40:43 init message: Activating best chain...
2017-05-03 19:40:43 mapBlockIndex.size() = 1
2017-05-03 19:40:43 nBestHeight = 0
2017-05-03 19:40:43 setKeyPool.size() = 100
2017-05-03 19:40:43 mapWallet.size() = 0
2017-05-03 19:40:43 mapAddressBook.size() = 2
2017-05-03 19:40:43 init message: Loading addresses...
2017-05-03 19:40:43 ERROR: Read: Failed to open file /home/aatheus/.argentum/peers.dat
2017-05-03 19:40:43 Invalid or missing peers.dat; recreating
2017-05-03 19:40:43 Loaded 0 addresses from peers.dat  0ms
2017-05-03 19:40:43 dnsseed thread start
2017-05-03 19:40:43 Loading addresses from DNS seeds (could take a while)
2017-05-03 19:40:43 0 addresses found from DNS seeds
2017-05-03 19:40:43 dnsseed thread exit
2017-05-03 19:40:43 net thread start
2017-05-03 19:40:43 init message: Done loading
2017-05-03 19:40:43 addcon thread start
2017-05-03 19:40:43 opencon thread start
2017-05-03 19:40:43 msghand thread start
2017-05-03 19:40:43 connect() to 104.131.142.198:13580 failed after select(): Connection refused (111)
2017-05-03 19:40:43 connect() to 138.201.65.88:13580 failed after select(): No route to host (113)
2017-05-03 19:40:44 connect() to 149.210.234.234:13580 failed after select(): Connection refused (111)
2017-05-03 19:40:45 socket recv error Connection reset by peer (104)
2017-05-03 19:40:46 connect() to 172.98.67.62:13580 failed after select(): Connection refused (111)
2017-05-03 19:40:46 connect() to 173.199.65.54:13580 failed after select(): Connection refused (111)
2017-05-03 19:40:47 connect() to 173.212.202.33:13580 failed after select(): Connection refused (111)
2017-05-03 19:40:48 receive version message: /Argetoshi:3.11.3.1/: version 1070000, blocks=831724, us=96.95.217.5:19238, peer=3
2017-05-03 19:40:48 Added time data, samples 2, offset -34 (+0 minutes)
2017-05-03 19:40:48 receive version message: /Argetoshi:3.11.3.1/: version 1070000, blocks=1796710, us=96.95.217.5:18425, peer=4
2017-05-03 19:40:48 Added time data, samples 3, offset -2 (+0 minutes)
2017-05-03 19:40:55 receive version message: /Argetoshi:3.11.3.1/: version 1070000, blocks=2387736, us=96.95.217.5:6243, peer=5
2017-05-03 19:40:55 Added time data, samples 4, offset +0 (+0 minutes)
2017-05-03 19:41:18 receive version message: /Argetoshi:3.11.3.1/: version 1070000, blocks=2390189, us=96.95.217.5:34638, peer=7
2017-05-03 19:41:18 Added time data, samples 5, offset -1 (+0 minutes)
2017-05-03 19:41:18 nTimeOffset = -1  (+0 minutes)
2017-05-03 19:41:18 connect() to 69.64.35.244:13580 failed after select(): Connection refused (111)
2017-05-03 19:41:19 connect() to 72.13.188.130:13580 failed after select(): Connection refused (111)
2017-05-03 19:41:43 connect() to 82.29.4.122:13580 failed after select(): No route to host (113)
2017-05-03 19:41:44 Adding fixed seed nodes as DNS doesn't seem to be available.
2017-05-03 19:44:00 connect() to 104.131.142.198:13580 failed after select(): Connection refused (111)
2017-05-03 19:44:01 connect() to 138.201.65.88:13580 failed after select(): No route to host (113)
2017-05-03 19:44:01 connect() to 149.210.234.234:13580 failed after select(): Connection refused (111)
2017-05-03 19:44:02 socket recv error Connection reset by peer (104)
2017-05-03 19:44:02 socket recv error Connection reset by peer (104)
2017-05-03 19:44:03 connect() to 172.98.67.62:13580 failed after select(): Connection refused (111)
2017-05-03 19:44:04 connect() to 173.199.65.54:13580 failed after select(): Connection refused (111)
2017-05-03 19:44:04 connect() to 173.212.202.33:13580 failed after select(): Connection refused (111)
2017-05-03 19:44:33 connect() to 69.64.35.244:13580 failed after select(): Connection refused (111)
2017-05-03 19:44:34 connect() to 72.13.188.130:13580 failed after select(): Connection refused (111)
2017-05-03 19:44:57 connect() to 82.29.4.122:13580 failed after select(): No route to host (113)
2017-05-03 19:47:14 connect() to 104.131.142.198:13580 failed after select(): Connection refused (111)
2017-05-03 19:47:15 connect() to 138.201.65.88:13580 failed after select(): No route to host (113)
2017-05-03 19:47:17 connect() to 149.210.234.234:13580 failed after select(): Connection refused (111)
2017-05-03 19:47:17 socket recv error Connection reset by peer (104)
2017-05-03 19:47:19 connect() to 172.98.67.62:13580 failed after select(): Connection refused (111)
2017-05-03 19:47:19 connect() to 173.199.65.54:13580 failed after select(): Connection refused (111)
2017-05-03 19:47:20 connect() to 173.212.202.33:13580 failed after select(): Connection refused (111)
2017-05-03 19:47:49 connect() to 69.64.35.244:13580 failed after select(): Connection refused (111)
2017-05-03 19:47:49 connect() to 72.13.188.130:13580 failed after select(): Connection refused (111)
2017-05-03 19:48:15 connect() to 82.29.4.122:13580 failed after select(): No route to host (113)
2017-05-03 19:50:32 connect() to 104.131.142.198:13580 failed after select(): Connection refused (111)
2017-05-03 19:50:33 connect() to 138.201.65.88:13580 failed after select(): No route to host (113)
2017-05-03 19:50:33 connect() to 149.210.234.234:13580 failed after select(): Connection refused (111)
2017-05-03 19:50:34 socket recv error Connection reset by peer (104)
2017-05-03 19:50:35 socket recv error Connection reset by peer (104)
2017-05-03 19:50:35 connect() to 172.98.67.62:13580 failed after select(): Connection refused (111)
2017-05-03 19:50:36 connect() to 173.199.65.54:13580 failed after select(): Connection refused (111)
2017-05-03 19:50:37 connect() to 173.212.202.33:13580 failed after select(): Connection refused (111)
2017-05-03 19:51:05 connect() to 69.64.35.244:13580 failed after select(): Connection refused (111)
2017-05-03 19:51:06 connect() to 72.13.188.130:13580 failed after select(): Connection refused (111)
2017-05-03 19:51:21 connect() to 77.254.207.167:13580 failed after select(): Network is unreachable (101)
2017-05-03 19:53:49 connect() to 104.131.142.198:13580 failed after select(): Connection refused (111)
2017-05-03 19:53:49 connect() to 138.201.65.88:13580 failed after select(): No route to host (113)
2017-05-03 19:53:50 connect() to 149.210.234.234:13580 failed after select(): Connection refused (111)
2017-05-03 19:53:51 socket recv error Connection reset by peer (104)
2017-05-03 19:53:51 socket recv error Connection reset by peer (104)
2017-05-03 19:53:52 connect() to 172.98.67.62:13580 failed after select(): Connection refused (111)
2017-05-03 19:53:52 connect() to 173.199.65.54:13580 failed after select(): Connection refused (111)
2017-05-03 19:53:53 connect() to 173.212.202.33:13580 failed after select(): Connection refused (111)
2017-05-03 19:54:22 connect() to 69.64.35.244:13580 failed after select(): Connection refused (111)
2017-05-03 19:54:23 connect() to 72.13.188.130:13580 failed after select(): Connection refused (111)
2017-05-03 19:54:47 connect() to 82.29.4.122:13580 failed after select(): No route to host (113)

After the recent issue I decided to do a full re-download of the blockchain, but the new client v3.11.3.1-72cf1f3 will not seem to download from peers.  I have anywhere from 8-16 active connections, both outgoing and incoming, with up-to-date protocol and client versions, but no blocks will download.  I've tried the Windows QT client and building from source on Ubuntu, and both exhibit the same behavior.

The debug.log is not much help, but here's an excerpt.


Can anyone shed any light on this? Is there a bootstrap somewhere that might get me rolling?  Thank you.

 I was mining earlier for a while but my sha and scrypt kept crashing. I'm looking into it but could really use some help narrowing it down due personal time constraints.

17-04-28 19:27:29 ERROR: CheckProofOfWork(): hash doesn't match nBits
2017-04-28 19:27:29 ERROR: CheckAuxPowProofOfWork : non-AUX proof of work failed
2017-04-28 19:27:29 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=5, nPos=122908179)

In the case above, the client should simply reject the block and move on, but it seems like enough of this will crash the client.

Here's an error from another daemon. This came up as an echo, the debug.log shows the same output as above
argentumd: main.cpp:4221: void ProcessGetData(CNode*): Assertion `!"cannot load block from disk"' failed.

This leads back to readblockfromdisk i believe (I'm away from the code right now)

sha256 works now ( block 2.390.171 at the moment ), but scrypt crashes again on getblocktemplate!

Since updating my node to the latest source it is "Activating best chain..." since more than 2 days:


I hope it will eventually finish this process.

More nodes

addnode=69.64.35.244
addnode=173.199.65.54
addnode=45.76.27.218
addnode=73.148.18.80
addnode=95.218.209.141
addnode=52.58.50.77
addnode=66.56.61.161
addnode=149.210.234.234
addnode=158.69.245.58
addnode=158.69.245.58
addnode=138.201.65.88
addnode=45.76.89.17
addnode=52.14.92.197
addnode=173.212.202.33
addnode=172.98.67.62
addnode=46.105.63.132
addnode=82.176.15.68
addnode=72.13.188.130

Give these a try

addnode=45.76.27.218
addnode=45.76.89.17
addnode=52.58.50.77

Once everyone updates, and the nodes sync back up with each other, everything will stabilize. Nodes that are reindexing will not be available to serve blocks.