0.96.1 testing build #4

[goatpig]

This DB never got really far. Are you using an anti virus too? Your blockchain data keeps getting corrupted after the fact.

[goatpig]

So I checked and I actually had clamav installed. I am pretty sure thought, that it didn't do anything, since I didn't let it delete anything.
I also have ufw installed, which also shouldn't do anything. Can I make Bitcoin Core check the blockchain maybe? I didn't find any option for that anywhere.

Not sure what the name of the arg is, something like "-checkchain". Make sure to delete your armory databases folder after that.

[Portnoy]

So I checked and I actually had clamav installed. I am pretty sure thought, that it didn't do anything, since I didn't let it delete anything.
I also have ufw installed, which also shouldn't do anything. Can I make Bitcoin Core check the blockchain maybe? I didn't find any option for that anywhere.

Not sure what the name of the arg is, something like "-checkchain". Make sure to delete your armory databases folder after that.

https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments

[Mr.Vice]

@goatpig: I just wanted to thank you for everything man, finally everything works with Armory 0.96.1-testing. There where multiple issues that have caused my unique problem.

1): McAfee AV was configured to (not only) real-time scanning, but also with the option of direct blocking "threats" before written on HDD.
2): Encrypted HDD with AES-CBC 256bit.
3): Custom bitcoin.conf with server=1 and the old rpcuser & rpcpasswords set that are deprecated now (cookie-auth).

Code:

## CONNECTION

#server=1

## Threshold for disconnecting misbehaving peers (default: 100)
banscore=80
 
## Number of seconds to keep misbehaving peers from reconnecting (default: 86400) 
bantime=1814400


## TOR & PROXY SERVER

listen=1

proxy=127.0.0.1:9050

torcontrol=127.0.0.1:9051

torpassword=***


## HIDDEN SERVICE (TOR)

#listenonion=1

## Seperate SOCKS5-Proxy for Tor Hidden Service
#onion=127.0.0.1:50959


## OTHER

#min=1

So many thanks for your help goatpig! I was able to run McAfee together with Armory now by deactivating some settings, but it was one of the reasons why it didn't work in the first place.

[goatpig]

@goatpig: I just wanted to thank you for everything man, finally everything works with Armory 0.96.1-testing. There where multiple issues that have caused my unique problem.

1): McAfee AV was configured to (not only) real-time scanning, but also with the option of direct blocking "threats" before written on HDD.
2): Encrypted HDD with AES-CBC 256bit.
3): Custom bitcoin.conf with server=1 and the old rpcuser & rpcpasswords set that are deprecated now (cookie-auth).

cookie auth replaces rpclogin/password

You need server=1 to enable the RPC though.

[creamers]

Hi !

I've been using a cold armory wallet on my ubuntu pi version 94.x and a online version on server 2008R2 94.x.
Core is version 13.x (if I'm not mistaken)

Q: should I download en just install everything on the 'online' server without deinstalling stuff first ? What do you advice ?
Q: is my cold wallet still usable with the new versions ? When isnt it usable anymore?
Q: I assume my paper wallet is still usable on the new armory version?

Thanks in advance ... Hopefully it's gonna be a nice migration

[goatpig]

Q: should I download en just install everything on the 'online' server without deinstalling stuff first ? What do you advice ?

If you are updating from 0.94, you will need to delete your Armory database as it is not compatible with 0.95+. The installer just replace the binaries. Uninstalling does not wipe the user data (db/wallets/settings), so you will have to wipe the db data manually.

Q: is my cold wallet still usable with the new versions ? When isnt it usable anymore?

No difference with 0.95. 0.96 default settings are backwards compatible with up to 0.92. If you use the new scripts types (deviate from the defaults), you will need a 0.96+ signer.

Q: I assume my paper wallet is still usable on the new armory version?

This stuff will always be supported.

[creamers]

I first updated bitcoin core to the latest version. This went without problem.
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -datadir="D:\Bitcoin Core Database"

After this I removed the old armory database and installed armory. (not deinstalled the armory client)

I started armory:
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="D:\Armory Database" --satoshi-datadir="D:\Bitcoin Core Database"

After a while I got this error:
http://i65.tinypic.com/10r7g1t.png

Code:

(ERROR) ArmoryUtils.pyc:3744 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:395 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="D:\Bitcoin Core Database\blocks" --datadir="D:\Armory Database" --dbdir="D:\Armory Database\databases"

armorylog.txt https://pastebin.com/Q7CaghHj
dblog.txt https://pastebin.com/XVCK9Qyv

Then I saw this in eventlog on server 2008R2:

Windows cannot access the file D:\Bitcoin Core Database\blocks\blk00646.dat for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program ArmoryDB.exe because of this error.

Strange reason. There is no virusscanner installed and the file is accessible.

What should be the next step.? Should I try again or are there things you need to know before I do, so you can solve this for future updates?

[goatpig]

Is D: a USB drive?

[creamers]

Is D: a USB drive?

No, a second (raid 1) volume/disk. (same disk where bitcoin core stores it's database)

I'll try to start bitcoin core again and see if it syncs up. Then I'll try armory again.

*EDIT:  so far so good the second time around:   http://imgur.com/a/0b9fS

[creamers]

Unfortunately it crashed again at a higher % but the application eventlog says it has to do with the same file (blk00646.dat).
http://imgur.com/a/XitHD

After closing the crash notification window if found some more info in the logfiles. Maybe this clears things up?

The strange thing about this is that I've been using the old version and the old bitcoin core already for a long time on this server, there should be something that causes this. If we find it, it will be beneficial for others and new users.

-INFO  - 19:28:30.643: (..\DatabaseBuilder.cpp:268) parsed block file #647
-INFO  - 19:29:02.015: (..\DatabaseBuilder.cpp:268) parsed block file #649
-INFO  - 19:33:55.406: (..\DatabaseBuilder.cpp:268) parsed block file #651
-INFO  - 19:34:11.584: (..\DatabaseBuilder.cpp:268) parsed block file #653
-ERROR - 22:04:06.118: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10022
-ERROR - 22:04:06.211: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in writeToSocket: 10022
-INFO  - 22:04:06.320: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

2017-05-31 19:34:11 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-31 22:04:29 (INFO) -- ArmoryQt.py:5389 - BDM state is scanning -- force shutdown BDM
2017-05-31 22:04:29 (INFO) -- SDM.pyc:456 - Called stopBitcoind
2017-05-31 22:04:31 (ERROR) -- ArmoryQt.py:5402 - Strange error during shutdown
Traceback (most recent call last):
  File "ArmoryQt.py", line 5393, in closeForReal
  File "SDM.pyc", line 482, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 828, in LOGERROR
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
2017-05-31 22:04:31 (INFO) -- ArmoryQt.py:5404 - Attempting to close the main window!

Restarted the 2008R2 server and running armory for the third time to see what happens.

[Betatester]

--------------

Linux users:

If the build fails to run on your setup (unknown instructions), it means your CPU is missing SSE4/AES/PCLMUL instructions. There will be a fail safe gcc4.7 build without any of those instructions for the actual release, but for the testing phase, you'll want to build the code directly on your machine. The build process has been fixed so you should have an easy time with it.

--------------

So what setup (Distro, CPU, RAM) did you use for those builds? I will buy such a machine to get my coins sent.

[creamers]

Restarted the 2008R2 server and running armory for the third time to see what happens.

Same problem again at the same percentage.

any suggestions ?

[Mr.Vice]

@goatpig:
server=1 and cookie auth works fine... actually everything essential works well! :-D
There are only some minor bugs left regarding the property window (address explorer like I call it). E.g. in the offline version the right click options don't work and the pop-up window when clicking on specific addresses does not show up. And when you are in the sending dialoge and open the address book you can not select addresses. You have to right click and copy/paste the address in order to select it.

[Mr.Vice]

Unfortunately it crashed again at a higher % but the application eventlog says it has to do with the same file (blk00646.dat).
http://imgur.com/a/XitHD

After closing the crash notification window if found some more info in the logfiles. Maybe this clears things up?

The strange thing about this is that I've been using the old version and the old bitcoin core already for a long time on this server, there should be something that causes this. If we find it, it will be beneficial for others and new users.

-INFO  - 19:28:30.643: (..\DatabaseBuilder.cpp:268) parsed block file #647
-INFO  - 19:29:02.015: (..\DatabaseBuilder.cpp:268) parsed block file #649
-INFO  - 19:33:55.406: (..\DatabaseBuilder.cpp:268) parsed block file #651
-INFO  - 19:34:11.584: (..\DatabaseBuilder.cpp:268) parsed block file #653
-ERROR - 22:04:06.118: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10022
-ERROR - 22:04:06.211: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in writeToSocket: 10022
-INFO  - 22:04:06.320: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

@creamers:
I think I know what's causing your problem. I've gotten a similar issue when I was upgrading to Core (0.14+) and Armory (0.96+). The Bitcoin Core versions since 0.14 can cause a right management bug on Windows machines, which does not affect BitcoinQt, but every software that runs on top of it.

Could you please check the properties of your Bitcoin folder by right clicking on the folder, selecting properties, tab security and go to extended or additional (I'm not sure how that button is called in English, it's the last one at the bottom). Now you'll see another pop-up window where it says "owner:". When it says "SYSTEM" you have to change that into your local user's account, otherwise you'll ran into the same issue over and over.

Afterwards start BitcoinQt only and let it completely sync the blockchain. Then exit BitcoinQt, go to your Bitcoin folder and modify your bitcoin.conf file. Remove the lines with rpcuser and rpcpassword, add the following line "server=1" and save it. Now let Armory do a rebuild & rescan and everything should work fine.

[creamers]

Thx mr Vice, but unfortunately it didnt work out for me. I'm logged in as administrator and it was already owner of the folder and has full permissions.
I did change it to server=1. Still crashing at some %.

I also copied everything from the bitcoincore database folder to a new folder to make sure windows hasnt a problem with the file.
Bitcoin core also hasnt a problem with it's own database.

armorylog since the beginning with all the errors in it:
https://pastebin.com/QUSgMCd5

dblog since:
https://pastebin.com/DaDhxH63

Bitcoincore is now catching up and I'm running armory with an unchecked 'let armory run bitcoind in background' to see what happens.

Hope someone can make sence out of the logfiles to solve this for me and others who want to update from older versions.


*EDIT:

• For it's further than before with unchecked 'let armory run bitcoind in background' and server=1 and having bitcoin core running next to it: https://ibb.co/ecE1oF
• 100% and now it's Organizing chain: https://ibb.co/iA8fFv
• Now finished: https://ibb.co/d9KCvv
• BUT, after closing both bitcoin core and armory, I see the armorydb.exe still running under processes taking up 100% on one core?
• Starting armory with the armorydb.exe left behind and still running, nothing happens.
• Killed the armorydb.exe and restarted armory.
• Seems like it's going again but waiting for it to get 'online'
• ONLINE and Working
• somehow it worked to disable the bitcoind background option, but closing Armory isnt going well cause armorydb.exe stays behind...
• Balance ended into zero !  I forced rebalance after restart, but it began building databases again )-:

[goatpig]

Ima push another build tomorrow, try with that then.

[creamers]

Thank you.

It ran all night, but after importing a paper backup, armorydb.exe was very busy and finally it crashed with the following in the logfiles:

armorylog

2017-06-04 08:34:08 (INFO) -- qtdialogs.pyc:10895 - Wallet Restore Complete!

armorycpplog

Log file opened at 18:42:54.000: D:\Armory Database\armorycpplog.txt
-ERROR - 17:27:46.070: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 17:38:34.000: D:\Armory Database\armorycpplog.txt
-ERROR - 22:04:07.928: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 22:09:55.000: D:\Armory Database\armorycpplog.txt
-ERROR - 14:58:31.580: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 11:18:23.000: D:\Armory Database\armorycpplog.txt
Log file opened at 12:33:37.000: D:\Armory Database\armorycpplog.txt
Log file opened at 16:26:35.000: D:\Armory Database\armorycpplog.txt
-ERROR - 16:26:42.942: (c:\users\goat\code\armory3\cppforswig\DataObject.h:286) exhausted entries in Arguments object
-ERROR - 16:26:42.942: (..\SwigClient.cpp:61) exhausted entries in Arguments object
Log file opened at 16:30:31.000: D:\Armory Database\armorycpplog.txt
Log file opened at 19:22:08.000: D:\Armory Database\armorycpplog.txt
-ERROR - 21:47:03.277: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 21:47:58.000: D:\Armory Database\armorycpplog.txt
Log file opened at 22:02:54.000: D:\Armory Database\armorycpplog.txt
Log file opened at 23:46:04.000: D:\Armory Database\armorycpplog.txt

dblog

-INFO  - 09:00:01.737: (..\BlockchainScanner.cpp:650) scanned from height #430571 to #431600
-INFO  - 09:00:15.183: (..\BlockchainScanner.cpp:650) scanned from height #431601 to #432267
-INFO  - 09:00:30.488: (..\BlockchainScanner.cpp:650) scanned from height #432268 to #432970
-INFO  - 09:00:43.452: (..\BlockchainScanner.cpp:650) scanned from height #432971 to #433637
-INFO  - 09:00:44.981: (..\BlockchainScanner.cpp:650) scanned from height #433638 to #433787
-INFO  - 09:00:44.293: (..\BlockchainScanner.cpp:225) scanned transaction history in 1596.52s
-INFO  - 09:00:45.698: (..\BlockchainScanner.cpp:1560) resolving txhashes
-INFO  - 09:02:22.824: (..\BlockchainScanner.cpp:1616) 11 blocks hit by tx filters
-ERROR - 09:02:24.696: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:24.712: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR - 09:02:24.712: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:24.712: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:24.728: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR - 09:02:24.728: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.005: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.005: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR - 09:02:26.021: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.021: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.036: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR - 09:02:26.036: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.348: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.364: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR - 09:02:26.364: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.364: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.395: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR - 09:02:26.395: (..\BlockchainScanner.cpp:1407) Skipping this block

Here it crashed!  

469666 blocks are shown in BitcoinCore and it's uptodate, but Armory only shows 433xxx blocks and is online ?!
That's probably also the reason that I don't have a correct end balance and missing transactions.

I'll try 0.96.2 , let me know what you want me to do/test.

[Mr.Vice]

Thx mr Vice, but unfortunately it didnt work out for me. I'm logged in as administrator and it was already owner of the folder and has full permissions.
I did change it to server=1. Still crashing at some %.

@creamers: I'm sorry to hear that :-/
Actually I've been undergoing quite similar issues like you are with Core (0.14+) and Armory (0.96+). These issues where mostly caused by AntiVirus software (McAfee), to be specific it was due to the real-time scanner. I'm not sure if I remember it right that Windows Server R2 2008 has a buildt in Windows Defender? Because from what I know WinDef hasn't really changed over the years (Win10 has practically no difference with the ones in Vista, 7 etc.).

What I've done was first uninstalling all McAfee AV files and so on and tried running Core and Armory only with WinDef. But that hasn't worked verry well either. To prevent it from interfering you have two options: deactivate real-time scanner or set up exceptions for specific directories. For me that worked, so I really hope you can solve it the same way.

1) Exceptions for the following paths:
C:\Users\..\AppData\Roaming\Bitcoin (or your specific Core folder)
C:\Users\..\AppData\Roaming\Armory (like above)

2) Exceptions for the following processes:
C:\ProgramFiles\Armory\ArmoryQt.exe (please look up your installation path, it may differ from mine)
C:\ProgramFiles\Bitcoin\bitcoin-qt.exe (like above)
C:\ProgramFiles\Bitcoin\bitcoind.exe (like above)

But I would first recommend to just deactivate real-time scanner of WinDef to test if this is the cause (I do not want to hurt your security with my recommendations, so if you're not sure about that you should skip this and try the exceptions first). After that delete your database folder of the Armory directory to force a rebuild & rescan. Another thing I've noticed is that WinDef might interfer in the shut-down process of Armory, where some processes in background are still running even if you closed it properly. So to ensure that isn't the case I would also prefer to restart your server before you try to run Armory again (if restarting is possible for you - or if it has to be online 24/7).

[creamers]

@creamers: I'm sorry to hear that :-/
Actually I've been undergoing quite similar issues like you are with Core (0.14+) and Armory (0.96+). These issues where mostly caused by AntiVirus software (McAfee), to be specific it was due to the real-time scanner. I'm not sure if I remember it right that Windows Server R2 2008 has a buildt in Windows Defender? Because from what I know WinDef hasn't really changed over the years (Win10 has practically no difference with the ones in Vista, 7 etc.).

What I've done was first uninstalling all McAfee AV files and so on and tried running Core and Armory only with WinDef. But that hasn't worked verry well either. To prevent it from interfering you have two options: deactivate real-time scanner or set up exceptions for specific directories. For me that worked, so I really hope you can solve it the same way.

Good tip for others , but I don't have a virusscanner on my nas I see in the armory thread that others have crashes to, I'll wait for the .2 test version to help out testing this.