problems upgrading from 0.93.3 to 0.95.1 (stuck on Scanning transaction history)

Petete

newbie

Activity: 10

Merit: 0

Quote from: achow101 on April 24, 2017, 08:09:15 AM

You will need to start Bitcoin Core manually. In Armory, go to FIle > Settings and uncheck the box "Let Armory run Bitcoin Core in the background". Then stop Armory, start Bitcoin Core, and start Armory again.

Did that. On first run it took a long time and Armory produced a 92GB log file before I shut it down containing these messages:

Quote

-INFO - 1493045595: (BlockchainScanner.cpp:650) scanned from height #385622 to #386291
---::BlockchainScanner.cpp:433ch) Failed to create BlockDataMap for file/home/pete/.bitcoin/blocks/blk00601.dat

::BlockchainScanner.cpp:433ch) Failed to create BlockDataMap for file/home/pete/.bitcoin/blocks/blk00601.dat

::BlockchainScanner.cpp:433ch) Failed to create BlockDataMap for file/home/pete/.bitcoin/blocks/blk00601.dat

-WARN - 1493065874: (BlockDataMap.cpp:434) Trying again...
-WARN - 1493065876: (BlockDataMap.cpp:433) Failed to create BlockDataMap for file: /home/pete/.bitcoin/blocks/blk00601.dat
-WARN - 1493065876: (BlockDataMap.cpp:434) Trying again...
-WARN - 1493065876: (BlockDataMap.cpp:433) Failed to create BlockDataMap for file: /home/pete/.bitcoin/blocks/blk00601.dat

Then I deleted blocks back to blk00600.dat, did a "bitcoind -reindex" and started Armory again after blockchain was up to date.
This time, everything worked as expected. Had to close Armory again because it comsumed again all memory while showing no progress for hours, but now I can start it without a problem.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: Petete on April 24, 2017, 06:53:30 AM

New problem with the backup computer where I downloaded a fresh blockchain with BC 0.13.2. Now Armory hangs on "Initializing bitcoin engine" and ArmoryDB never gets started.

You will need to start Bitcoin Core manually. In Armory, go to FIle > Settings and uncheck the box "Let Armory run Bitcoin Core in the background". Then stop Armory, start Bitcoin Core, and start Armory again.

Quote from: Petete on April 24, 2017, 06:53:30 AM

armorylog.txt fills up with megabyted of this repeated error message:

That error is benign.

Petete

newbie

Activity: 10

Merit: 0

New problem with the backup computer where I downloaded a fresh blockchain with BC 0.13.2. Now Armory hangs on "Initializing bitcoin engine" and ArmoryDB never gets started. armorylog.txt fills up with megabyted of this repeated error message:

2017-04-23 16:27 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

I also installed Ubuntu 16.04 on that computer to check if it is a problem with the operating system. Same problem.
Any advice?

Petete

newbie

Activity: 10

Merit: 0

Thank you for answering!

Meanwhile, before your post I startet to download a new blockchain with BC 0.13.1 on the backup computer, so waiting for this to finish before trying again.

On the main computer which halfway worked before, I downgraded to BC 0.13.2 and started Armory up with deleted database folder. This time, I had to kill ArmoryDB because it was getting stuck at "Scanning transaction history". In detail, I closed Armory when nothing happened for some time, then CPU usage suddenly jumped up with ArmoryDB for some time, but it didn't terminate, so I killed it. After a restart, everything seems to work and total sum shows up fine.

Posting log files from the main computer:
https://pastebin.com/zQ2JBTvN
https://pastebin.com/bPxKrX8z

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

The invalid header size error is not related to the block parsing. Rather that is because you are probably using Bitcoin Core 0.14.0 which is incompatible with Armory 0.95.1. If you are using Bitcoin Core 0.14.0, you should downgrade to 0.13.2. Once you do that, try rebuilding the Armory databases as well (although it shouldn't matter). If it still fails after that, you may need to redownload the blockchain.

Petete

newbie

Activity: 10

Merit: 0

I have problems upgrading from 0.93.3 to 0.95.1 on Ubuntu 14.04.

What I do is:
- delete "databases" and "bittorrentcache" folders in .armory
- remove 0.93.3, install and start 0.95.1
- wait for the database being build (seems to work fine)
- see armory hanging at "Scanning transaction history" (showing no progress for hours)
- ArmoryDB will consume all available memory at this point
- close Armory, kill ArmoryDB process
- restart Armory
- it will finish to main screen, but this years transactions are missing, showing a wrong total sum of funds

This is on my backup computer. On my main computer, also with Ubuntu 14.04 and same wallets, ArmoryDB will also hang at "Scanning transaction history" but not consume all available memory. Also there are error messages when Armory is started from console. I can close Armory there with it shutting down ArmoryDB automatically. When I restart Armory, it completes and shows correct total funds.

armorylog.txt
https://pastebin.com/PmNGYg0m
dbLog.txt
https://pastebin.com/8Fb5P1jt

In dbLog.txt there are errors "invalid header size" and "raw data does not match expected block hash". Should I redownload BC blockchain and try again with database rebuild?

Topic: problems upgrading from 0.93.3 to 0.95.1 (stuck on Scanning transaction history) (Read 535 times)