Bitcoin Forum

Bitcoin => Armory => Topic started by: etotheipi on September 22, 2013, 06:50:41 PM



Title: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on September 22, 2013, 06:50:41 PM
Armory version 0.89.99.16-testing:

On my Linux system, I have 2,300 addresses and probably 1,000-2,000 transactions.  It takes 24 sec to startup Armory on mainnet when I manage Bitcoin-Qt myself and it's already sync'd.  And 290 MB of RAM at steady-state.  

Latest version contains fragmented backup tester and Bitcoin-Qt-compatible message signing!  (and verification).

----- GPG-signed hashes of all installers (using the Armory Offline Signing Key (http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x4AB16AEA98832223))

   Armory 0.89.99.16-testing: Signed hashes of all installers  (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_sha256sum.txt.asc)

----- WINDOWS

  Armory 0.89.99.16-testing for Windows Vista, 7, 8 (Both 32- and 64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_win32.exe)

----- Mac/OSX

  Armory 0.89.99.16-testing for Mac/OSX 10.8 and 10.9 (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OSX.app.tar.gz)

----- Ubuntu/Debian (packages are signed directly with offline GPG key using dpkg-sig)

  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_i386.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_i386.deb)

----- Ubuntu/Debian Offline Bundles

  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-64bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-64bit.tar.gz)





Thanks to picobit, we have a working testing release for OSX.  It appears like it might work on a much wider set of OSX systems, too!   (For reference, picobit basically gave me a recipe for building a portable Armory app, he didn't actually build it himself -- the package was built on my OSX system).  [note: there are bugs (https://groups.google.com/forum/#!topic/eventandtaskmanager/L636sUwZudY) in 10.9/Mavericks that may make it unusable...gotta wait for Apple to fix it]



New features in 0.89.99.X (to be 0.90-beta when released):

  • RAM usage and startup time reduction: RAM reduced to less than 300MB, and startup time typically under 60 seconds after initial DB build!
  • Persistent database: Armory now maintains its own blockchain database for fast startup.  Make sure you have space to duplicate the blockchain (will be reduced in a subsequent version; this way was easier for now).
  • Full MacOSX support*: thanks to picobit for the builder, though the Apple+PyQt bugs (https://groups.google.com/forum/#!topic/eventandtaskmanager/L636sUwZudY) prevent full usability in 10.9.  Until Apple pushes an update, it may not be very usable on 10.9.
  • New Backup Center:  Better organization and description of backup options.  Includes unencrypted digital backups, now.
  • Fragmented Backups:  Shamir's Secret Sharing (M-of-N secret splitting); balance your physical security and redundancy.  Create up to 5-of-6 backups in Standard & Advanced modes.  Up to 8-of-12 in Expert mode.  Fragments are also deterministic for a given M value.  For example, if you make a 3-of-5 backup, you can later make a 3-of-7 and the first 5 will be the same as the 3-of-5 (but you will get different fragments if you do 2-of-N or 4-of-N!)
  • SecurePrint: Paper backups optionally encrypted with code on screen to prevent private key exposure to printer and other network devices.  SecurePrint code should be identical across all backup types for a given wallet
  • Half-sized paper backups:  The chaincode is now derived from the private key, meaning only two lines of data for wallets created with the new version of Armory.  Yet, all backup features work with older wallet without a hitch -- they'll all show four lines (if you don't believe me, prove me wrong and collect your 0.04 BTC!)
  • Paper backup tester: test any kind of paper backup before you bury it in your backyard.  Includes subset testing of fragmented backups. (https://bitcointalk.org/index.php?topic=299684.msg3560071#msg3560071)
  • Message Sign & Verify: Finally Bitcoin-Qt-compatible signing and verification.  Will have a new ASCII-armored version like PGP signing, soon
  • Fixed broadcasting non-std signatures:  Older versions of Armory produced signatures that have non-standard padding.  If an older version is used on your offline system, you can't broadcast those signed transactions with 0.88.1 online.  This version will fix the padding and broadcast successfully
  • Improve *nix Makefile:  Improved Makefile that should work out of the box on most Linux distros once the proper depedencies are installed.  See the osx_picobit directory for compiling on OSX.





The new sequence of operations executed by Armory (with auto-bitcoind) is outlined below.  The times are what I've observed in my testing on Linux Mint 64-bit with regular HDD (no SSD), and a Windows 7-64bit VM running on that same HDD.

  • (1) Start bitcoind (using "--datadir" supplied on the command line)
  • (2) Download/update blockchain (same as previous version, may take 4-16 hours)
  • (3) Process all headers and determine longest chain ("headers-first" is new feature of Armory, will help with lite-node implementation later)
  • (4) Build database of raw blockchain data from the blk*.dat files produced by bitcoind/-qt (30-90 min).
  • (5) Scan database for transaction data relevant to your wallets (Linux: 5-20 min, Windows: 20-45 min)

Step 4 (building the DB) is done only once.  There is no reason to do it again (besides updating for new blocks), unless the user explicitly requests it using the " --rebuild" flag.
Step 5 also is only done once, unless you import or restore addresses or wallets.  Doing so will initiate a rescan of the blockchain to find the transaction history.  You can force a rescan using the "--rescan" flag.


Known Issues:

  • Unicode everything :(  Ugh.  Will work on that after it works for US users.  The next version will get some unicode-TLC (it will mostly be a bug-fix and polishing release, with nothing major except for message signing)
  • There are some DB consistency issues that may lead to a lot of DB rescanning and sometimes rebuilding.  If you always shutdown cleanly and don't interrupt Armory while it is updating, you will avoid that and it will start up quickly.  However, there does not appear to be any danger in having this happen, it's just inconvenient.
  • Occasionally a zero-confirmation tx disappears when it is included in a block, instead of sticking around and getting one confirmation.  Restarting should fix it (even without a rescan!)
  • Occasionally a crash with a "Partial StoredTx" error in the log file.  Please PM me if you observe this error.  I suspect I know the problem, but it would help to have someone who actively has it so I can test fixes

Instructions for building on Ubuntu/Debian:

This is just a copy of the build instructions on the website (http://bitcoinarmory.com/download/building-armory-from-source/), but has an extra step to check out the "testing" branch instead of the "master" branch (which is still 0.88.1).

Just copy the following commands into a terminal one-by-one.  In Linux, you can simply highlight text using the mouse, then middle-click in the terminal (and press enter after each one).  It works between just about any two applications running in Linux, but it's especially important in the Linux terminal because Ctrl-C has a different meaning there.  (NOTE: do not copy the '$' symbols)

Code:
$ sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil
$ git clone git://github.com/etotheipi/BitcoinArmory.git
$ cd BitcoinArmory
$ git checkout testing
$ make
$ python ArmoryQt.py


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: itsgoldbaby on September 22, 2013, 07:15:50 PM
I can't seem to get it to work. This is what appears in the text log:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

?

:(


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 22, 2013, 07:42:37 PM
I can't seem to get it to work. This is what appears in the text log:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

?

:(

Can you post system specs?  If others have this same problem, it would be nice to try to correlate it with specific system configurations.  I just tested it on one of my non-dev windows machines and it works.  But I also have python installed, which shouldn't matter (since this is a standalone package), but it might.   So I can half-verify it working on Windows 7-64bit with python pre-installed.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: itsgoldbaby on September 22, 2013, 07:46:08 PM
Windows XP PRO
AMD Athlon X2 5200+
300GB HDD
4 GB RAM

I know, it's kinda crappy. :P


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 22, 2013, 07:52:49 PM
Windows XP PRO
AMD Athlon X2 5200+
300GB HDD
4 GB RAM

I know, it's kinda crappy. :P

Well, I want it to be supported on such systems.  So this is a good test.  I wonder if it's an issue with Windows XP.  For instance, I bet if I setup the new build environment in Windows XP, it would be forward compatible with Win7 and Win8, but not the other way around (it's being built on Win7-64bit right now, but as a 32-bit app).

I assume your Windows XP system is 32-bit... correct?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: itsgoldbaby on September 22, 2013, 07:56:12 PM
Windows XP PRO
AMD Athlon X2 5200+
300GB HDD
4 GB RAM

I know, it's kinda crappy. :P

Well, I want it to be supported on such systems.  So this is a good test.  I wonder if it's an issue with Windows XP.  For instance, I bet if I setup the new build environment in Windows XP, it would be forward compatible with Win7 and Win8, but not the other way around (it's being built on Win7-64bit right now, but as a 32-bit app).

I assume your Windows XP system is 32-bit... correct?
Yes, sorry. :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: TierNolan on September 22, 2013, 08:06:13 PM
The update still suffers from that issue that I PM-ed you about a while back.  (Granted not a critical issue :) )

If the HOME environment variable is set incorrectly, then it can't start the reference client.

Code:
(ERROR) ArmoryQt.py:1271 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1267, in startBitcoindIfNecessary
  File "armoryengine.pyc", line 10827, in setupSDM
  File "armoryengine.pyc", line 10891, in findBitcoind
WindowsError: [Error 3] The system cannot find the path specified: 'e:\\cygwin\\home\\coding\\Desktop/*.*'

[edit]
Creating the Desktop directory in my alternative home direction seems to fix things
[/edit]

[edit2]
When I start, it says that I have started by clicking on a bitcoin: link, but should try again when Armory is online (since transactions are not possible).
[/edit2]

[edit3]
It crashes after around a minute

When it crashes, it doesn't kill the bitcoin daemon.  I have to manually use "bitcoind stop" to stop it (or kill the process).

guardian.exe doesn't appear to be in the .zip file.

Code:
(ERROR) armoryengine.pyc:10973 - Could not find guardian script: G:\armory testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\guardian.exe
(ERROR) ArmoryQt.py:1271 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1268, in startBitcoindIfNecessary
  File "armoryengine.pyc", line 11105, in startBitcoind
  File "armoryengine.pyc", line 10974, in getGuardianPath
FileExistsError
(ERROR) ArmoryQt.py:646 - 6 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 35672076, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (35672076)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(ERROR) ArmoryQt.py:646 - 7 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 3242000, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (3242000)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'

[/edit3]


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 22, 2013, 08:31:46 PM
[edit3]
It crashes after around a minute

When it crashes, it doesn't kill the bitcoin daemon.  I have to manually use "bitcoind stop" to stop it (or kill the process).

guardian.exe doesn't appear to be in the .zip file.

Code:
(ERROR) armoryengine.pyc:10973 - Could not find guardian script: G:\armory testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\guardian.exe
(ERROR) ArmoryQt.py:1271 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1268, in startBitcoindIfNecessary
  File "armoryengine.pyc", line 11105, in startBitcoind
  File "armoryengine.pyc", line 10974, in getGuardianPath
FileExistsError
(ERROR) ArmoryQt.py:646 - 6 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 35672076, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (35672076)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(ERROR) ArmoryQt.py:646 - 7 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 3242000, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (3242000)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'

[/edit3]

Okay, I left out guardian.exe by accident.  I just uploaded a new zip file right now with it in there.  If you download the zip file again, it should be there this time.  guardian.exe is responsible for killing bitcoind if Armory doesn't do it.   So that addresses two of your issues.

I'll look into the "SetBlkFileLocation" issue.  Could it be a unicode issue?  Do you have non-ASCII characters in your paths?  Unfortunately, the error does not explain what the expected and supplied data types were.  But it wouldn't surprise me if "type 'unicode'" was one of those...




Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: TierNolan on September 22, 2013, 08:50:41 PM
Could it be a unicode issue?  Do you have non-ASCII characters in your paths?  Unfortunately, the error does not explain what the expected and supplied data types were.  But it wouldn't surprise me if "type 'unicode'" was one of those...

The issue is that if the %HOME%/Desktop directory doesn't exist, then there is an error and it doesn't check any more locations.

I think the code here (https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine.py#L10514) needs to check if the path exists before checking if path/*.* exists.

I will try the re-download.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 22, 2013, 08:53:36 PM
Could it be a unicode issue?  Do you have non-ASCII characters in your paths?  Unfortunately, the error does not explain what the expected and supplied data types were.  But it wouldn't surprise me if "type 'unicode'" was one of those...

The issue is that if the %HOME%/Desktop directory doesn't exist, then there is an error and it doesn't check any more locations.

I think the code here (https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine.py#L10514) needs to check if the path exists before checking if path/*.* exists.

I will try the re-download.

There's two different problems.  The $(DESKTOP) issue is one that is a simple bug I can fix.  The app shouldn't crash because it can't find the desktop folder.

The other problem is it trying to set the new LevelDB directory, which it attempts to create as

Code:
os.path.join(ARMORY_HOME_DIR, 'databases')

It appears that the result of that operation is getting passed to the SWIG'd C++ code, and throwing an error.  Either because it's expecting a string and got something else, or we passed a string and it was expecting something else.  I would get it's the first problem, and that os.path.join is returning a unicode output that is not handled properly. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: TierNolan on September 22, 2013, 08:57:53 PM
There's two different problems.  The $(DESKTOP) issue is one that is a simple bug I can fix.  The app shouldn't crash because it can't find the desktop folder.

The other problem is it trying to set the new LevelDB directory, which it attempts to create as

Code:
os.path.join(ARMORY_HOME_DIR, 'databases')

It appears that the result of that operation is getting passed to the SWIG'd C++ code, and throwing an error.  Either because it's expecting a string and got something else, or we passed a string and it was expecting something else.  I would get it's the first problem, and that os.path.join is returning a unicode output that is not handled properly. 

Ahh ok.  I am still getting this error:

Code:
(ERROR) ArmoryQt.py:646 - 8 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 87485194, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (87485194)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(ERROR) ArmoryQt.py:646 - 9 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 43561706, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (43561706)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(ERROR) ArmoryQt.py:646 - 10 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 48373466, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (48373466)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'

I started the program with this shortcut

"G:\armory testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\ArmoryQt.exe" --datadir=G:\armory testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\datadir

Maybe, I need to use forward slashes?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 22, 2013, 09:54:34 PM

Ahh ok.  I am still getting this error:

Code:
(ERROR) ArmoryQt.py:646 - 8 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 87485194, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (87485194)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(ERROR) ArmoryQt.py:646 - 9 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 43561706, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (43561706)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(ERROR) ArmoryQt.py:646 - 10 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 48373466, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (48373466)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'

I started the program with this shortcut

"G:\armory testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\ArmoryQt.exe" --datadir=G:\armory testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\datadir

Maybe, I need to use forward slashes?

If you are modifying the target of a shortcut, I believe bot '/' and '\' are fine.  If you are running from a git/cygwin shell, you have to use forward slashes '/' or else it interprets the backslashes as escape characters.   

I'm still quite curious how that error is cropping up.  If you are ambitious, you can close Armory, unpack the library.zip file inside that directory, then modify armoryengine.py.  When you are done, re-zip it and overwrite library.zip.  Then it should use the new code when you run ArmoryQt.exe.   This works for everything except ArmoryQt.py which is the entry point for the app, so it treats that file differently.  But all the other python files should be modifiable in that way mentioned.

If you've got a problem with line 12808 in armoryengine.py, try adding the following to line 12807:

Code:
print '***blkdir var:', type(blkdir), len(blkdir), '"'+str(blkdir)+'"'

Also make sure you are running with --debug.  The next testing round, I should probably turn on all debugging output by default.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: TierNolan on September 22, 2013, 10:15:03 PM
If you are modifying the target of a shortcut, I believe bot '/' and '\' are fine.  If you are running from a git/cygwin shell, you have to use forward slashes '/' or else it interprets the backslashes as escape characters.   

I just unpacked the zip file and created a shortcut.  I am not running from within cygwin.

It is not impossible that the %HOME% issue is affecting things though.  Maybe some other directory reference is affected.

Quote
I'm still quite curious how that error is cropping up.  If you are ambitious, you can close Armory, unpack the library.zip file inside that directory, then modify armoryengine.py.  When you are done, re-zip it and overwrite library.zip.  Then it should use the new code when you run ArmoryQt.exe.   This works for everything except ArmoryQt.py which is the entry point for the app, so it treats that file differently.  But all the other python files should be modifiable in that way mentioned.

They are all .pyc files rather than .py files.  I assume there is some kind of compile step.

Do I need to set a home directory too?

Code:
(INFO) armoryengine.pyc:781 - 
(INFO) armoryengine.pyc:782 -
(INFO) armoryengine.pyc:783 -
(INFO) armoryengine.pyc:784 - ************************************************************
(INFO) armoryengine.pyc:785 - Invoked: G:\armory_testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\ArmoryQt.exe --datadir=G:\armory_testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\datadir --debug
(INFO) armoryengine.pyc:786 - ************************************************************
(INFO) armoryengine.pyc:787 - Loading Armory Engine:
(INFO) armoryengine.pyc:788 -    Armory Version        : 0.89.99.2
(INFO) armoryengine.pyc:789 -    PyBtcWallet  Version  : 1.35
(INFO) armoryengine.pyc:790 - Detected Operating system: Windows
(INFO) armoryengine.pyc:791 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
(INFO) armoryengine.pyc:792 -    User home-directory   : C:\Users\TN\AppData\Roaming
(INFO) armoryengine.pyc:793 -    Satoshi BTC directory : C:\Users\TN\AppData\Roaming\Bitcoin\
(INFO) armoryengine.pyc:794 -    Armory home dir       : C:\Users\TN\AppData\Roaming\Armory\
(INFO) armoryengine.pyc:795 - Detected System Specs    :
(INFO) armoryengine.pyc:796 -    Total Available RAM   : 16.00 GB
(INFO) armoryengine.pyc:797 -    CPU ID string         : Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
(INFO) armoryengine.pyc:798 -    Number of CPU cores   : 4 cores
(INFO) armoryengine.pyc:799 -    System is 64-bit      : False
(INFO) armoryengine.pyc:800 -    Preferred Encoding    : cp1252
(INFO) armoryengine.pyc:801 -
(INFO) armoryengine.pyc:802 - Network Name: Main Network
(INFO) armoryengine.pyc:803 - Satoshi Port: 8333
(INFO) armoryengine.pyc:804 - Named options/arguments to armoryengine.py:
(INFO) armoryengine.pyc:806 -     leveldbDir      : DEFAULT
(INFO) armoryengine.pyc:806 -     skipVerCheck    : False
(INFO) armoryengine.pyc:806 -     satoshiPort     : DEFAULT
(INFO) armoryengine.pyc:806 -     settingsPath    : C:\Users\TN\AppData\Roaming\Armory\ArmorySettings.txt
(INFO) armoryengine.pyc:806 -     logFile         : C:\Users\TN\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
(INFO) armoryengine.pyc:806 -     nettimeout      : 2
(INFO) armoryengine.pyc:806 -     rescan          : False
(INFO) armoryengine.pyc:806 -     doDebug         : True
(INFO) armoryengine.pyc:806 -     datadir         : G:\armory_testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\datadir
(INFO) armoryengine.pyc:806 -     netlog          : False
(INFO) armoryengine.pyc:806 -     keypool         : 100
(INFO) armoryengine.pyc:806 -     testnet         : False
(INFO) armoryengine.pyc:806 -     rpcport         : DEFAULT
(INFO) armoryengine.pyc:806 -     satoshiHome     : DEFAULT
(INFO) armoryengine.pyc:806 -     forceOnline     : False
(INFO) armoryengine.pyc:806 -     logDisable      : False
(INFO) armoryengine.pyc:806 -     offline         : False
(INFO) armoryengine.pyc:806 -     mtdebug         : False
(INFO) armoryengine.pyc:806 -     rebuild         : False
(INFO) armoryengine.pyc:806 -     interport       : 8223
(INFO) armoryengine.pyc:807 - Other arguments:
(INFO) armoryengine.pyc:810 - ************************************************************
(INFO) armoryengine.pyc:1016 - C++ block utilities loaded successfully
(INFO) armoryengine.pyc:13305 - Using the asynchronous/multi-threaded BlockDataManager.
(INFO) armoryengine.pyc:13306 - Blockchain operations will happen in the background. 
(INFO) armoryengine.pyc:13307 - Devs: check TheBDM.getBDMState() before asking for data.
(INFO) armoryengine.pyc:13308 - Registering addresses during rescans will queue them for
(INFO) armoryengine.pyc:13309 - inclusion after the current scan is completed.
(INFO) armoryengine.pyc:11405 - Using settings file: C:\Users\TN\AppData\Roaming\Armory\ArmorySettings.txt
(INFO) ArmoryQt.py:1505 - loadWalletsAndSettings
(INFO) ArmoryQt.py:1552 - Loading wallets...
(INFO) ArmoryQt.py:1600 - Number of wallets read in: 4
(INFO) ArmoryQt.py:1605 -    Wallet (27KXMC5Ao):   "VanityWallet                    "   (Encrypted)
(INFO) ArmoryQt.py:1605 -    Wallet (2Jg5gsaZV):   "Active                          "   (No Encryption)
(INFO) ArmoryQt.py:1605 -    Wallet (38vfGKavT):   "Primary Wallet (Watch)          "   (No Encryption)
(INFO) ArmoryQt.py:1605 -    Wallet (LC1iqeBy):    "Test Wallet1                    "   (No Encryption)
(INFO) ArmoryQt.py:1186 - Setting up networking...
(INFO) ArmoryQt.py:1239 - Internet connection is Available: True
(INFO) ArmoryQt.py:1240 - Bitcoin-Qt/bitcoind is Available: 0
(INFO) ArmoryQt.py:1247 - startBitcoindIfNecessary
(INFO) ArmoryQt.py:1277 - setSatoshiPaths
(INFO) armoryengine.pyc:10831 - Found bitcoind in the following places:
(INFO) armoryengine.pyc:10833 -    C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
(INFO) armoryengine.pyc:10835 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
(INFO) armoryengine.pyc:602 - Executing popen: ['icacls', u'F:\\bitcoin_data\\bitcoin.conf', '/inheritance:r', '/grant:r', 'TN:F']
(INFO) armoryengine.pyc:11004 - icacls returned: processed file: F:\bitcoin_data\bitcoin.conf Successfully processed 1 files; Failed processing 0 files
(INFO) armoryengine.pyc:11058 - Called startBitcoind
(INFO) armoryengine.pyc:602 - Executing popen: ['C:\\Program Files (x86)\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=F:\\bitcoin_data']
(INFO) armoryengine.pyc:11101 - PID of bitcoind: 5556
(INFO) armoryengine.pyc:11102 - PID of armory:   2876
(INFO) armoryengine.pyc:602 - Executing popen: ['G:\\armory_testing\\ArmoryStandalone_0.89.99.2_win_all\\ArmoryStandalone\\guardian.exe', '2876', '5556']
(INFO) ArmoryQt.py:773 - setupUriRegistration
(INFO) ArmoryQt.py:812 - Armory already registered for current user.  Done!
(INFO) armoryengine.pyc:11260 - Creating proxy in SDM: host=127.0.0.1, port=8332
(INFO) ArmoryQt.py:4214 - Dashboard switched to auto-InitSync
(INFO) ArmoryQt.py:3687 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
(INFO) ArmoryQt.py:3687 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
(INFO) ArmoryQt.py:3629 - Switching Armory functional mode to "Offline"
(INFO) ArmoryQt.py:529 - Usermode: Expert
(INFO) ArmoryQt.py:1019 - Changing usermode:
(INFO) ArmoryQt.py:1020 -    From: Expert
(INFO) ArmoryQt.py:1028 -      To: Expert
(INFO) armoryengine.pyc:10746 - Signature on signed data block is GOOD!
(INFO) ArmoryQt.py:1158 - Latest versions:
(INFO) ArmoryQt.py:1159 -    Satoshi: 0.8.1
(INFO) ArmoryQt.py:1160 -     Armory: 0.88
(INFO) ArmoryQt.py:1169 - You are running the latest version!
(INFO) ArmoryQt.py:4214 - Dashboard switched to auto-InitSync
(INFO) ArmoryQt.py:3687 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
(INFO) ArmoryQt.py:3687 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
(INFO) ArmoryQt.py:3629 - Switching Armory functional mode to "Offline"
(INFO) ArmoryQt.py:4497 - Starting load blockchain
(INFO) ArmoryQt.py:1300 - loadBlockchainIfNecessary
(ERROR) ArmoryQt.py:646 - 21 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.pyc:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.pyc:13245 - Go online requested
(INFO) armoryengine.pyc:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 62016481, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (62016481)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(INFO) armoryengine.pyc:10353 - Connection initiated.  Start handshake
(INFO) armoryengine.pyc:10442 - Received version message from peer:
(INFO) armoryengine.pyc:10443 -    Version:     70001
(INFO) armoryengine.pyc:10444 -    SubVersion:  /Satoshi:0.8.1/
(INFO) armoryengine.pyc:10445 -    TimeStamp:   1379887837
(INFO) armoryengine.pyc:10446 -    StartHeight: 259494
(INFO) armoryengine.pyc:10624 - Handshake finished, connection open!
(INFO) ArmoryQt.py:4497 - Starting load blockchain
(INFO) ArmoryQt.py:1300 - loadBlockchainIfNecessary
(ERROR) ArmoryQt.py:646 - 22 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.pyc:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.pyc:13245 - Go online requested
(INFO) armoryengine.pyc:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 45243962, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (45243962)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(INFO) armoryengine.pyc:10353 - Connection initiated.  Start handshake
(INFO) ArmoryQt.py:4497 - Starting load blockchain
(INFO) ArmoryQt.py:1300 - loadBlockchainIfNecessary
(ERROR) ArmoryQt.py:646 - 23 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.pyc:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.pyc:13245 - Go online requested
(INFO) armoryengine.pyc:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 76143845, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (76143845)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(INFO) armoryengine.pyc:10353 - Connection initiated.  Start handshake
(INFO) armoryengine.pyc:10442 - Received version message from peer:
(INFO) armoryengine.pyc:10443 -    Version:     70001
(INFO) armoryengine.pyc:10444 -    SubVersion:  /Satoshi:0.8.1/
(INFO) armoryengine.pyc:10445 -    TimeStamp:   1379887840
(INFO) armoryengine.pyc:10446 -    StartHeight: 259496
(INFO) armoryengine.pyc:10624 - Handshake finished, connection open!
(INFO) armoryengine.pyc:10498 - Received new block.  000000000000001be2ae056523401720da306758e54f2551153ac6a23c3dd01b
(INFO) ArmoryQt.py:4497 - Starting load blockchain
(INFO) ArmoryQt.py:1300 - loadBlockchainIfNecessary
(ERROR) ArmoryQt.py:646 - 24 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.pyc:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.pyc:13245 - Go online requested
(INFO) armoryengine.pyc:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 72244790, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (72244790)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(INFO) armoryengine.pyc:10353 - Connection initiated.  Start handshake
(INFO) armoryengine.pyc:10498 - Received new block.  0000000000000004cc3c8821fc424901030665fa1de9f3286525a8be31c954d0
(INFO) armoryengine.pyc:10442 - Received version message from peer:
(INFO) armoryengine.pyc:10443 -    Version:     70001
(INFO) armoryengine.pyc:10444 -    SubVersion:  /Satoshi:0.8.1/
(INFO) armoryengine.pyc:10445 -    TimeStamp:   1379887841
(INFO) armoryengine.pyc:10446 -    StartHeight: 259497
(INFO) armoryengine.pyc:10624 - Handshake finished, connection open!
(INFO) armoryengine.pyc:10498 - Received new block.  000000000000001be2ae056523401720da306758e54f2551153ac6a23c3dd01b
(INFO) armoryengine.pyc:10498 - Received new block.  0000000000000004cc3c8821fc424901030665fa1de9f3286525a8be31c954d0
(INFO) armoryengine.pyc:10442 - Received version message from peer:
(INFO) armoryengine.pyc:10443 -    Version:     70001
(INFO) armoryengine.pyc:10444 -    SubVersion:  /Satoshi:0.8.1/
(INFO) armoryengine.pyc:10445 -    TimeStamp:   1379887841
(INFO) armoryengine.pyc:10446 -    StartHeight: 259497
(INFO) armoryengine.pyc:10624 - Handshake finished, connection open!
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000243d5372d0e637f7b047c041af5f598a7accabeeba1a2cbf50
(INFO) ArmoryQt.py:4497 - Starting load blockchain
(INFO) ArmoryQt.py:1300 - loadBlockchainIfNecessary
(ERROR) ArmoryQt.py:646 - 25 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.pyc:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.pyc:13245 - Go online requested
(INFO) armoryengine.pyc:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 97531984, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (97531984)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(INFO) armoryengine.pyc:10353 - Connection initiated.  Start handshake
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000243d5372d0e637f7b047c041af5f598a7accabeeba1a2cbf50
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000243d5372d0e637f7b047c041af5f598a7accabeeba1a2cbf50
(INFO) armoryengine.pyc:10498 - Received new block.  0000000000000004cc3c8821fc424901030665fa1de9f3286525a8be31c954d0
(INFO) armoryengine.pyc:10442 - Received version message from peer:
(INFO) armoryengine.pyc:10443 -    Version:     70001
(INFO) armoryengine.pyc:10444 -    SubVersion:  /Satoshi:0.8.1/
(INFO) armoryengine.pyc:10445 -    TimeStamp:   1379887842
(INFO) armoryengine.pyc:10446 -    StartHeight: 259498
(INFO) armoryengine.pyc:10624 - Handshake finished, connection open!
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000243d5372d0e637f7b047c041af5f598a7accabeeba1a2cbf50
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000034ba3c3c3cf4660bdc0f4c7b17c2bbb9af0c1a0e6264a6df0
(INFO) ArmoryQt.py:4497 - Starting load blockchain
(INFO) ArmoryQt.py:1300 - loadBlockchainIfNecessary
(ERROR) ArmoryQt.py:646 - 26 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.pyc:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.pyc:13245 - Go online requested
(INFO) armoryengine.pyc:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 29566096, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (29566096)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(INFO) armoryengine.pyc:10353 - Connection initiated.  Start handshake
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000034ba3c3c3cf4660bdc0f4c7b17c2bbb9af0c1a0e6264a6df0
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000034ba3c3c3cf4660bdc0f4c7b17c2bbb9af0c1a0e6264a6df0
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000034ba3c3c3cf4660bdc0f4c7b17c2bbb9af0c1a0e6264a6df0
(INFO) armoryengine.pyc:10442 - Received version message from peer:
(INFO) armoryengine.pyc:10443 -    Version:     70001
(INFO) armoryengine.pyc:10444 -    SubVersion:  /Satoshi:0.8.1/
(INFO) armoryengine.pyc:10445 -    TimeStamp:   1379887843
(INFO) armoryengine.pyc:10446 -    StartHeight: 259499
(INFO) armoryengine.pyc:10624 - Handshake finished, connection open!
(INFO) armoryengine.pyc:10498 - Received new block.  00000000000000034ba3c3c3cf4660bdc0f4c7b17c2bbb9af0c1a0e6264a6df0
(INFO) armoryengine.pyc:10498 - Received new block.  000000000000001e0c0e2fda15f09f1ca1658e3b0f623d68f2db03e3f277b118
(INFO) ArmoryQt.py:4497 - Starting load blockchain
(INFO) ArmoryQt.py:1300 - loadBlockchainIfNecessary
(ERROR) ArmoryQt.py:646 - 27 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:651 - File mempool.bin does not exist. Nothing deleted.
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.pyc:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.pyc:13245 - Go online requested
(INFO) armoryengine.pyc:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.pyc:13270 - Error processing BDM input
(ERROR) armoryengine.pyc:13271 - Received inputTuple: GoOnlineRequested [13, 29892524, False]
(ERROR) armoryengine.pyc:13272 - Error processing ID (29892524)
(ERROR) armoryengine.pyc:13273 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13256, in run
  File "armoryengine.pyc", line 12808, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'
(INFO) armoryengine.pyc:10353 - Connection initiated.  Start handshake
(INFO) armoryengine.pyc:10498 - Received new block.  000000000000001e0c0e2fda15f09f1ca1658e3b0f623d68f2db03e3f277b118
(INFO) armoryengine.pyc:10498 - Received new block.  000000000000001e0c0e2fda15f09f1ca1658e3b0f623d68f2db03e3f277b118
(INFO) armoryengine.pyc:10498 - Received new block.  000000000000001e0c0e2fda15f09f1ca1658e3b0f623d68f2db03e3f277b118


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 22, 2013, 10:26:11 PM
Quote
I'm still quite curious how that error is cropping up.  If you are ambitious, you can close Armory, unpack the library.zip file inside that directory, then modify armoryengine.py.  When you are done, re-zip it and overwrite library.zip.  Then it should use the new code when you run ArmoryQt.exe.   This works for everything except ArmoryQt.py which is the entry point for the app, so it treats that file differently.  But all the other python files should be modifiable in that way mentioned.

They are all .pyc files rather than .py files.  I assume there is some kind of compile step.

Do I need to set a home directory too?


Ack, forgot about the .pyc thing.  I forgot that py2exe puts the already-byte-compiled python code in there.  However, it doesn't require .pyc files.  Simply copy in the pre-compiled armoryengine.py (https://raw.github.com/etotheipi/BitcoinArmory/rrld_planB/armoryengine.py) and delete the .pyc.  Make the modification to the .py file, and my previous instructions should work (sorry, it's been a while since I've done this).

If you want to spend any significant amount of time modifying code, etc, and you are a patient person, we just gave all the MSVS projects a complete overhaul and should be much easier to get working, now (and uses the free version of MSVS 2012).  Still not trivial, but if you have any interest in spending a lot of time in Armory source code (C++ or python), it would be worth the effort.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: TierNolan on September 22, 2013, 11:15:45 PM
Code:
print '***blkdir var:', type(blkdir), len(blkdir), '"'+str(blkdir)+'"'


It doesn't seem that print dumps the text into the log file and windows doesn't show the standard output stream (even if started from command line).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 22, 2013, 11:51:22 PM
Code:
print '***blkdir var:', type(blkdir), len(blkdir), '"'+str(blkdir)+'"'


It doesn't seem that print dumps the text into the log file and windows doesn't show the standard output stream (even if started from command line).


My bad.  Sorry for the scavenger hunt!  Put in LOGERROR calls, which will guarantee it gets written out to the log file:

Code:
      LOGERROR('***BLKDIR VARIABLE:')
      LOGERROR('***Type:  %s' % str(type(blkdir)))
      LOGERROR('***Size:  %d' % len(blkdir))
      LOGERROR('***Value: %s' % str(blkdir))

Breaking them out like that will also make sure the type() is printed even if len() or str() throws an error.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 23, 2013, 05:07:08 AM


Fixed rescan-on-every-load bug!

Version 0.89.99.3-testing (link is in the top post)

It turns out that it wasn't waiting for the block data manager to finish writing the wallet histories to the database before killing it.  The time between calling and killing was enough to write out a couple hundred addresses -- if you had more than that, it wouldn't finish in time, and Armory would detect a bunch of new addresses every load requiring a rescan. 

Therefore, all features I wanted to be in this release are implemented now.  I've pretty much decided to freeze the feature set, and just focus on bugs and polishing.

One other bug that I noticed: there's a pretty long freeze on every new block.  Again, it's one of those efficiencies/optimizations that can be improved later.  The "usability" impact of that bug is a lot less than requiring 6 GB of RAM!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 23, 2013, 06:31:38 AM
If I want to try it out on OS X I have to compile it myself.  I assume it is in a branch in git ?



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 23, 2013, 06:34:22 AM
If I want to try it out on OS X I have to compile it myself.  I assume it is in a branch in git ?



It's the "testing" branch.  There is Level DB source code in the project, though, no clue if it compiles on OSX...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 23, 2013, 06:37:30 AM
If I want to try it out on OS X I have to compile it myself.  I assume it is in a branch in git ?



It's the "testing" branch.  There is Level DB source code in the project, though, no clue if it compiles on OSX...

If it doesn't, then I will look at it in a few weeks.  If it does, I will report back here soon.  :-)
A quick google for "os x leveldb" looks like it should work, but that it in reality causes some amount of trouble ...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: simonk83 on September 23, 2013, 09:26:54 AM
Good stuff, looking forward to the OSX release :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: japerry on September 23, 2013, 03:25:53 PM

Armory version 0.89.99.3-testing:

Windows:  Download the standalone executable bundle (click here) (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmoryStandalone_0.89.99.3_win_all.zip)  
Just unpack and double-click on ArmoryQt.exe.  You may want to right-click and make a shortcut to it, in the same directory, then modify the properties->"Target:" to use non-standard "--datadir" and/or "--satoshi-datadir" paths (or any other flags you want, like "--testnet).


I'm trying to set up the new Armory and Bitcoin-QT to run completely off a flash drive. Oh!! BTW thanks for the new Armory! I actually can run it now!  ;D

So what is the difference between the --datadir and --satoshi-datadir command line calls?



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 23, 2013, 03:51:34 PM
I'm trying to set up the new Armory and Bitcoin-QT to run completely off a flash drive. Oh!! BTW thanks for the new Armory! I actually can run it now!  ;D

So what is the difference between the --datadir and --satoshi-datadir command line calls?

--datadir is the Armory home directory to use
--satoshi-datadir is the Bitcoin-Qt/bitcoind home directory to use (which should match the "-datadir" flag you give to Bitcoin software if run it manually)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: japerry on September 23, 2013, 04:31:46 PM
I'm trying to set up the new Armory and Bitcoin-QT to run completely off a flash drive. Oh!! BTW thanks for the new Armory! I actually can run it now!  ;D

So what is the difference between the --datadir and --satoshi-datadir command line calls?

--datadir is the Armory home directory to use
--satoshi-datadir is the [/i]Bitcoin-Qt/bitcoind[/i] home directory to use (which should match the "-datadir" flag you give to Bitcoin software if run it manually)

Thank you sir! I will report back to you soon on the totally flash drive test. BTW The flash drive is a TrueCrypt container.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 23, 2013, 05:03:57 PM
I'm trying to set up the new Armory and Bitcoin-QT to run completely off a flash drive. Oh!! BTW thanks for the new Armory! I actually can run it now!  ;D

So what is the difference between the --datadir and --satoshi-datadir command line calls?

--datadir is the Armory home directory to use
--satoshi-datadir is the [/i]Bitcoin-Qt/bitcoind[/i] home directory to use (which should match the "-datadir" flag you give to Bitcoin software if run it manually)

Thank you sir! I will report back to you soon on the totally flash drive test. BTW The flash drive is a TrueCrypt container.


What kind of flash drive are you using?  The Bitcoin and Armory directories together will probably consume 30 GB of disk space, and of course will grow with the blockchain.  Just a reminder.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: japerry on September 23, 2013, 05:09:06 PM
I'm trying to set up the new Armory and Bitcoin-QT to run completely off a flash drive. Oh!! BTW thanks for the new Armory! I actually can run it now!  ;D

So what is the difference between the --datadir and --satoshi-datadir command line calls?

--datadir is the Armory home directory to use
--satoshi-datadir is the [/i]Bitcoin-Qt/bitcoind[/i] home directory to use (which should match the "-datadir" flag you give to Bitcoin software if run it manually)

Thank you sir! I will report back to you soon on the totally flash drive test. BTW The flash drive is a TrueCrypt container.


What kind of flash drive are you using?  The Bitcoin and Armory directories together will probably consume 30 GB of disk space, and of course will grow with the blockchain.  Just a reminder.

Yes! I got too big for my britches!! LOL!! I'm testing it on a removable 1 TB drive with a 128G Truecrypt container now. LOL!! A 16G won't do the job! But at least the drive is removable.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: TierNolan on September 23, 2013, 05:23:38 PM
My bad.  Sorry for the scavenger hunt!  Put in LOGERROR calls, which will guarantee it gets written out to the log file:

Code:
      LOGERROR('***BLKDIR VARIABLE:')
      LOGERROR('***Type:  %s' % str(type(blkdir)))
      LOGERROR('***Size:  %d' % len(blkdir))
      LOGERROR('***Value: %s' % str(blkdir))

Breaking them out like that will also make sure the type() is printed even if len() or str() throws an error.

It didn't crash until bitcoind had downloaded the blockchain.

Code:
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.py:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.py:13249 - Go online requested
(INFO) armoryengine.py:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.py:12808 - ***BLKDIR VARIABLE:
(ERROR) armoryengine.py:12809 - ***Type:  <type 'unicode'>
(INFO) armoryengine.py:10353 - Connection initiated.  Start handshake
(ERROR) armoryengine.py:12810 - ***Size:  22
(ERROR) armoryengine.py:12811 - ***Value: F:\bitcoin_data\blocks
(ERROR) armoryengine.py:13274 - Error processing BDM input
(ERROR) armoryengine.py:13275 - Received inputTuple: GoOnlineRequested [13, 40873630, False]
(ERROR) armoryengine.py:13276 - Error processing ID (40873630)
(ERROR) armoryengine.py:13277 - ERROR:
Traceback (most recent call last):
  File "G:\armory_testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\library.zip\armoryengine.py", line 13260, in run
  File "G:\armory_testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\library.zip\armoryengine.py", line 12812, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'

So, it looks like the string is of the wrong type.  None of the characters are non-ASCII, so it shouldn't be that hard to convert.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.2)
Post by: etotheipi on September 23, 2013, 06:58:35 PM
My bad.  Sorry for the scavenger hunt!  Put in LOGERROR calls, which will guarantee it gets written out to the log file:

Code:
      LOGERROR('***BLKDIR VARIABLE:')
      LOGERROR('***Type:  %s' % str(type(blkdir)))
      LOGERROR('***Size:  %d' % len(blkdir))
      LOGERROR('***Value: %s' % str(blkdir))

Breaking them out like that will also make sure the type() is printed even if len() or str() throws an error.

It didn't crash until bitcoind had downloaded the blockchain.

Code:
(INFO) ArmoryQt.py:1346 - Setting netmode: 1
(INFO) armoryengine.py:12324 - Setting online mode: True (wait=False)
(INFO) armoryengine.py:13249 - Go online requested
(INFO) armoryengine.py:12766 - Called __startLoadBlockchain()
(ERROR) armoryengine.py:12808 - ***BLKDIR VARIABLE:
(ERROR) armoryengine.py:12809 - ***Type:  <type 'unicode'>
(INFO) armoryengine.py:10353 - Connection initiated.  Start handshake
(ERROR) armoryengine.py:12810 - ***Size:  22
(ERROR) armoryengine.py:12811 - ***Value: F:\bitcoin_data\blocks
(ERROR) armoryengine.py:13274 - Error processing BDM input
(ERROR) armoryengine.py:13275 - Received inputTuple: GoOnlineRequested [13, 40873630, False]
(ERROR) armoryengine.py:13276 - Error processing ID (40873630)
(ERROR) armoryengine.py:13277 - ERROR:
Traceback (most recent call last):
  File "G:\armory_testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\library.zip\armoryengine.py", line 13260, in run
  File "G:\armory_testing\ArmoryStandalone_0.89.99.2_win_all\ArmoryStandalone\library.zip\armoryengine.py", line 12812, in __startLoadBlockchain
  File "CppBlockUtils.pyc", line 1230, in SetBlkFileLocation
TypeError: in method 'BlockDataManager_LevelDB_SetBlkFileLocation', argument 2 of type 'string'

So, it looks like the string is of the wrong type.  None of the characters are non-ASCII, so it shouldn't be that hard to convert.

In fact, there was no error when it printed the value of "str(blkdir)" which means it was safely cast to a string.  I don't know why you ended up with a unicode value, but I do know that the simply putting in that cast is not a good general solution.  Though it should work for you right now...

For now just cast the "unicode" object to a string.  I'll put that in the next version, since it is strictly an improvement over the current code (which will fail unless it's a string, anyway).  But I need to put more effort into the unicode handling there... probably one of need to call "toPreferred()" to get it to work with arbitrary path vars. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 23, 2013, 07:44:31 PM
I can report that the new version compiled just fine on OS X.  I had previously used HomeBrew to install all dependencies of the old Armory client, and did not have to install anything new to compile the new version.  The first tests on testnet look good.  I will test offline wallets (on testnet) soon.

As for packaging this as an .app, that is going to be harder, but I will have a look at that too.  But not this week, and probably not next week.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 23, 2013, 07:50:39 PM
OK, first two strange behaviors:

I transferred some testnet coins from a testnet faucet.  When the first block arrived, Armory popped up a window saying that Bitcoin-QT was not up to date.  It also printed this around 10 times in the terminal.

At the same time this happened, I was transferring testnet coins from another faucet.  The amount appeared in the total, but this time the transaction did not appear in the list of transactions.  Restarting Armory made it appear (at 0 confirmations).  Restart was blazingly fast!


EDIT:
Quote
-INFO  - 1379965779: (BlockUtils.cpp:3748) Finished blockchain scan in 8e-06 seconds
I somehow doubt this timing :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: japerry on September 23, 2013, 08:16:13 PM

Armory version 0.89.99.3-testing:

Windows:  Download the standalone executable bundle (click here) (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmoryStandalone_0.89.99.3_win_all.zip)  
Just unpack and double-click on ArmoryQt.exe.  You may want to right-click and make a shortcut to it, in the same directory, then modify the properties->"Target:" to use non-standard "--datadir" and/or "--satoshi-datadir" paths (or any other flags you want, like "--testnet).


I'm trying to set up the new Armory and Bitcoin-QT to run completely off a flash drive. Oh!! BTW thanks for the new Armory! I actually can run it now!  ;D

So what is the difference between the --datadir and --satoshi-datadir command line calls?



OK! I have it running on a TrueCrypt container on a removable drive! So... what command line parameter specifies the location of the config file? My goal is to make a portable version with the command line parameters fully defined. Of course I want to read any docs explaining the parameters.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 23, 2013, 08:18:17 PM
OK! I have it running on a TrueCrypt container on a removable drive! So... what command line parameter specifies the location of the config file? My goal is to make a portable version with the command line parameters fully defined. Of course I want to read any docs explaining the parameters.



See the bottom of the "troubleshooting" page:  http://bitcoinarmory.com/download/troubleshooting/

Not sure how it ended up there.  It might've gotten reshuffled with the new website.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: japerry on September 23, 2013, 08:34:37 PM
OK! I have it running on a TrueCrypt container on a removable drive! So... what command line parameter specifies the location of the config file? My goal is to make a portable version with the command line parameters fully defined. Of course I want to read any docs explaining the parameters.



See the bottom of the "troubleshooting" page:  http://bitcoinarmory.com/download/troubleshooting/

Not sure how it ended up there.  It might've gotten reshuffled with the new website.

Wow! Thanks! That is exactly what I was looking for! I really appreciate your fast response time and I thank you for a wonderful program.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Mooshire on September 24, 2013, 02:34:20 AM
I check this subforum every once in a while, great work! I may finally be able to soon go back to using Armory!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 24, 2013, 02:34:55 AM
I check this subforum every once in a while, great work! I may finally be able to soon go back to using Armory!

Well, please try it!  I need more people trying it!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Mooshire on September 24, 2013, 02:45:26 AM
I check this subforum every once in a while, great work! I may finally be able to soon go back to using Armory!

Well, please try it!  I need more people trying it!

I'll do that now. Specs before I try:
Windows 8
8 GB RAM
AMD 8120 8-core
NVIDIA GT 640


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 24, 2013, 03:21:18 AM
So far, I've seen a pattern that 32-bit Windows versions don't seem to work.  But 64-bit OSes do work.  And this strange unicode issue from TierNolan.

I tested it on my fiancée's computer:  Win7-64bit w/ 4 GB of RAM.  About 5 years old.  It took forever to download the blockchain (probably 24 hours).  And it took about 2-3 hours to build the the DB.  But once it finished scanning (I don't know the timing), it only takes 1.5 minutes to start up.  And most of that is waiting for bitcoind to initialize.  And somehow uses even less RAM than the other systems:  215 MB.  Not too shabby.  

Also had someone report success on a system with 2 GB of RAM!  Slow of course.  There is no doubt that Armory is still a pretty heavy program...

Given the issues with Windows 32-bit that I've seen, I'm going to try to rebuild everything on a native 32-bit VM.  Unfortunately, I tried installing MSVS 2012 Express on WindowsXP-32bit, but I got all sorts of crazy errors.  If anyone else has WinXP-32bit and feels like donating some time, please try downloading and installing MSVS 2012 Express for Windows Desktop (http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-for-windows-desktop#product-express-desktop).  I ask because, I assume it's possible that there is something wrong with my WinXP system, but I also wouldn't be surprised if Windows XP is just too old at this point for such a new piece of software.

Instead, I'm going to install Windows7-32bit and repeat the build process there.  If it works there, it obviously has a better chance of working on any Win7-32bit and Win8-32bit.  Fat chance for Windows XP, but maybe we'll get lucky.

Known Issues:

  • Doesn't seem to work yet on 32-bit OS.  Haven't tried any *nix systems, yet.  But haven't heard any success stories from 32-bit Windows users.
  • Unicode everything :(  Ugh.  Will work on that after it works for US users.  The next version will get some unicode-TLC (it will mostly be a bug-fix and polishing release, with nothing major except for message signing)
  • About 10% of the time, I start the app and I get rapid disconnects/reconnects.  The log reports a huge string of "Marking Orphan Chain" messages (which indicates the headers are not being processed correctly).  I close it, and restart and it works fine.
  • Super-slow and no feedback when it's updating a couple days' history after being shut down for a while.  The feedback is technically there, telling it to update the GUI every 25 MB... but the update is usually less than 25 MB, and even if it is >25 MB, that can take a couple minutes.  Not only do I need to improve the GUI-update cycle, I need to figure out why the initial build is 10x faster than updating on restart (even though they should be using the same code to do it)
  • General speed:  Obviously some optimizations missed.  One of the reasons I picked levelDB was some testing early on where I found that doing a full blockchain scan was 30% faster than my super-optimized blockchain scanner.  Now it's 3x slower.  I have a good idea what it is -- I'll dedicate a day to tinkering and benchmarking, after the release


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: SimonBelmond on September 24, 2013, 04:43:58 AM
OK thanks for all the hard work Alan (and contributors and team):

Tested "Armory version 0.89.99.3-testing"
On: Windows 7 64 bit, 4 gb ram,
I had it scan the BC over night. This morning i got the message that bitcoin qt appears to be offline or something (sorry missed the screenshot). Armory was online though. I closed armory and reopened. I think it took even less than your 19 sec to download 1 block and go online straight away. very nice. Not a lot of testing apart from that. Will do more and also report on ram usage. First sight looks good.  ::)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 24, 2013, 04:49:53 AM
OK thanks for all the hard work Alan (and contributors and team):

Tested "Armory version 0.89.99.3-testing"
On: Windows 7 64 bit, 4 gb ram,
I had it scan the BC over night. This morning i got the message that bitcoin qt appears to be offline or something (sorry missed the screenshot). Armory was online though. I closed armory and reopened. I think it took even less than your 19 sec to download 1 block and go online straight away. very nice. Not a lot of testing apart from that. Will do more and also report on ram usage. First sight looks good.  ::)

There appears to be an issue right after it finishes the full DB build.  But it seems to be solved by a restart.  So far, I've seen a few issues with Armory getting into a bad state like that, but it always resolves itself.  So far, I haven't had to "--rebuild" the DBs once. That's a good sign (though --rescanning sometimes seems necessary).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: justusranvier on September 24, 2013, 06:11:43 AM
Leveldb/snappy is still broken:

Code:
(CRITICAL) armoryengine.py:1019 - C++ block utilities not available.
(CRITICAL) armoryengine.py:1020 -    Make sure that you have the SWIG-compiled modules
(CRITICAL) armoryengine.py:1021 -    in the current directory (or added to the PATH)
(CRITICAL) armoryengine.py:1022 -    Specifically, you need:
(CRITICAL) armoryengine.py:1023 -        CppBlockUtils.py     and
(CRITICAL) armoryengine.py:1025 -        _CppBlockUtils.so
(ERROR) Traceback (most recent call last):
  File "/usr/share/armory/ArmoryQt.py", line 30, in <module>
    from armoryengine import *
  File "/usr/share/armory/armoryengine.py",                                                                                                 line 1015, in <module>
    import CppBlockUtils as Cpp
  File "/usr/share/armory/CppBlockUtils.py", line 26, in <module>
    _CppBlockUtils = swig_import_helper()
  File "/usr/share/armory/CppBlockUtils.py", line 22, in swig_import_helper
    _mod = imp.load_module('_CppBlockUtils', fp, pathname, description)
ImportError: /usr/share/armory/_CppBlockUtils.so: undefined symbol: _ZN6snappy21GetUncompressedLengthEPKcmPm

Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/share/armory/armoryengine.py", line 595, in logexcept_override
    sys.__excepthook__(type, value, tback)
AttributeError: 'NoneType' object has no attribute '__excepthook__'

Original exception was:
Traceback (most recent call last):
  File "/usr/share/armory/ArmoryQt.py", line 30, in <module>
    from armoryengine import *
  File "/usr/share/armory/armoryengine.py", line 1015, in <module>
    import CppBlockUtils as Cpp
  File "/usr/share/armory/CppBlockUtils.py", line 26, in <module>
    _CppBlockUtils = swig_import_helper()                                                                                                
  File "/usr/share/armory/CppBlockUtils.py", line 22, in swig_import_helper                                                                                                                                                              
    _mod = imp.load_module('_CppBlockUtils', fp, pathname, description)                                                                                                                                                                  
ImportError: /usr/share/armory/_CppBlockUtils.so: undefined symbol: _ZN6snappy21GetUncompressedLengthEPKcmPm

The pull request I sent you on GitHub fixes the problem for me. With that patch applied, the time from starting the program until balances are displayed is about 28 seconds.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 24, 2013, 06:38:19 AM
So far, I've seen a pattern that 32-bit Windows versions don't seem to work.  But 64-bit OSes do work.  

I would not be too optimistic on a 32-bit version.  The real reason for 64-bit architectures is that you can easily handle more than 2GB of data in one block.  On a 32-bit architecture, that is going to be tough (but of course not impossible).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: justusranvier on September 24, 2013, 08:21:55 AM
Watching-only wallets contribute to the "Maximum Funds" and "Spendable Funds" totals even if they are configured as "Belongs to: Someone else."


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: TierNolan on September 24, 2013, 09:13:40 AM
And this strange unicode issue from TierNolan.

Adding the string cast seems to have fixed things.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: rkjnsn on September 24, 2013, 11:22:16 AM
Given the issues with Windows 32-bit that I've seen, I'm going to try to rebuild everything on a native 32-bit VM.  Unfortunately, I tried installing MSVS 2012 Express on WindowsXP-32bit, but I got all sorts of crazy errors.  If anyone else has WinXP-32bit and feels like donating some time, please try downloading and installing MSVS 2012 Express for Windows Desktop (http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-for-windows-desktop#product-express-desktop).  I ask because, I assume it's possible that there is something wrong with my WinXP system, but I also wouldn't be surprised if Windows XP is just too old at this point for such a new piece of software.

Instead, I'm going to install Windows7-32bit and repeat the build process there.  If it works there, it obviously has a better chance of working on any Win7-32bit and Win8-32bit.  Fat chance for Windows XP, but maybe we'll get lucky.

Visual Studio 2012 only supports running on Windows 7 SP1 and later. By default, the created executables will only run on Vista and later. It can build XP compatible executables, but you have to change the project's Platform Toolset to "Visual Studio 2012 - Windows XP (v110_xp)"


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Mooshire on September 24, 2013, 11:45:20 AM
Alan  mine worked like a charm, except for rapidly disconnecting/reconnecting while downloading the blockchain. Specs are above.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Mooshire on September 24, 2013, 03:26:14 PM
When starting it for the second time, after downloading what blocks it had to, it got stuck scanning on 1%. I found this in the log over and over, for a very long time.

-WARN  - 0: (..\BlockUtils.cpp:4865) Marking orphan chain
-WARN  - 0: (..\BlockUtils.cpp:4888) Done marking orphan chain


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 24, 2013, 05:27:45 PM
When starting it for the second time, after downloading what blocks it had to, it got stuck scanning on 1%. I found this in the log over and over, for a very long time.

-WARN  - 0: (..\BlockUtils.cpp:4865) Marking orphan chain
-WARN  - 0: (..\BlockUtils.cpp:4888) Done marking orphan chain

Mooshire, is it solved by restarting the app?  So far, I haven't seen it get into any permanent bad state.  I've seen that happen before, and then it goes away on a restart. (P.S. - I do plan to find and fix it, I just want to make sure that, for now, it doesn't leave anyone in an unusable state)

Watching-only wallets contribute to the "Maximum Funds" and "Spendable Funds" totals even if they are configured as "Belongs to: Someone else."

What is the wallet filter set to?  If it is "All wallets" it will include all wallets.  If you set the filter to "My Wallets" it has the behavior you expect.  Bottom-left corner of main window.

Leveldb/snappy is still broken:

...

The pull request I sent you on GitHub fixes the problem for me. With that patch applied, the time from starting the program until balances are displayed is about 28 seconds.

I have modified it in my source code and will commit it with the next version.  

Visual Studio 2012 only supports running on Windows 7 SP1 and later. By default, the created executables will only run on Vista and later. It can build XP compatible executables, but you have to change the project's Platform Toolset to "Visual Studio 2012 - Windows XP (v110_xp)"

I don't want to spend a ton of time on it... but now that the RAM issues are under control, and it previously worked on XP, I would be willing to spend a couple hours getting it work on XP.  Especially because some users might have old XP systems laying around they'd want to use for offline use (don't bash them, it's still better than an online computer :))


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: goatpig on September 24, 2013, 07:32:49 PM
I don't want to spend a ton of time on it... but now that the RAM issues are under control, and it previously worked on XP, I would be willing to spend a couple hours getting it work on XP.  Especially because some users might have old XP systems laying around they'd want to use for offline use (don't bash them, it's still better than an online computer :))

You can't install msvc11 on WinXP, you need .NET Framework 4.0, which is only compatible with Windows 6.0 (Vista) and above. I have built the LevelDB port using the WinXP tool, but haven't tested it. There are instructions for WinXP deployment with the port I sent you.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 24, 2013, 10:36:30 PM
Anyone tried this with Win7-32bit?  I'm running it right now, but I don't have a pre-sync'd version, so it might be a while before I can really run it.  I guess I could figure out how to bootstrap it...

Btw, I just executed a couple offline transactions using the new version on the online computer (offline computer is still using an ancient version).  Everything is smooth, so far.  Except for that occasional faulty startup thing.  That's my next task after I finish with the Windows LevelDB upgrade from goatpig (thanks goat!)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Mooshire on September 25, 2013, 01:07:37 AM
I started it up again, the visual indicator didn't change from 1% until it went straight to the wallet after a few minutes. Looking at the live log file, it stopped right after the completed handshake, also it said the armory version was 0.88 (ArmoryQt.py:1162) also, got this error. (WARNING) -- ArmoryQt.py:1838 - Memory pool file was corrupt.  Deleted. (no further action is needed)

Not sure if it's significant. Hope this helps.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 25, 2013, 01:25:02 AM
I started it up again, the visual indicator didn't change from 1% until it went straight to the wallet after a few minutes. Looking at the live log file, it stopped right after the completed handshake, also it said the armory version was 0.88 (ArmoryQt.py:1162) also, got this error. (WARNING) -- ArmoryQt.py:1838 - Memory pool file was corrupt.  Deleted. (no further action is needed)

Not sure if it's significant. Hope this helps.

So is it working?  It sounds like it's working and you're just reporting some inconsistencies in the log file.  Don't worry, both those things are normal.  I mean, not totally normal, but they happen.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Mooshire on September 25, 2013, 02:33:37 AM
I started it up again, the visual indicator didn't change from 1% until it went straight to the wallet after a few minutes. Looking at the live log file, it stopped right after the completed handshake, also it said the armory version was 0.88 (ArmoryQt.py:1162) also, got this error. (WARNING) -- ArmoryQt.py:1838 - Memory pool file was corrupt.  Deleted. (no further action is needed)

Not sure if it's significant. Hope this helps.

So is it working?  It sounds like it's working and you're just reporting some inconsistencies in the log file.  Don't worry, both those things are normal.  I mean, not totally normal, but they happen.

Yes, it's working.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: rkjnsn on September 25, 2013, 02:42:14 AM
Visual Studio 2012 only supports running on Windows 7 SP1 and later. By default, the created executables will only run on Vista and later. It can build XP compatible executables, but you have to change the project's Platform Toolset to "Visual Studio 2012 - Windows XP (v110_xp)"
I don't want to spend a ton of time on it... but now that the RAM issues are under control, and it previously worked on XP, I would be willing to spend a couple hours getting it work on XP.  Especially because some users might have old XP systems laying around they'd want to use for offline use (don't bash them, it's still better than an online computer :))
I mainly use Linux, myself, but I do have a fair amount of experience getting things to build on Windows for work. I'd be happy to help if you run into problems, time permitting.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Winterfrost on September 25, 2013, 04:43:18 AM
Everything synced fine from a fresh install (Win7 64-bit), but I did find an issue when I sent a transaction. It went through successfully and showed up in the receiving address as well as in the transactions list in Armory. However, when I went away from my computer and came back later, the transaction is no longer there and the wallet has reverted the balance to what it was before. So basically, it now says there are funds to spend even though in reality they've already been sent elsewhere. The bug also persisted across restarting.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 25, 2013, 04:46:33 AM
Everything synced fine from a fresh install (Win7 64-bit), but I did find an issue when I sent a transaction. It went through successfully and showed up in the receiving address as well as in the transactions list in Armory. However, when I went away from my computer and came back later, the transaction is no longer there and the wallet has reverted the balance to what it was before. So basically, it now says there are funds to spend even though in reality they've already been sent elsewhere. The bug also persisted across restarting.

Ack, I haven't seen that one before.  Are you sure it has confirmations?  Armory on Windows has always had an issue with the memory pool, for some reason it cannot persist through a restart (that's what all the "Memory pool file was corrupt.  Deleted. (no further action is needed)" messages are about.  But it should resolve itself after the transaction gets one confirmation.  If not, then that's a problem, for sure!  Does it have one confirmation yet?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Winterfrost on September 25, 2013, 05:10:11 AM
Everything synced fine from a fresh install (Win7 64-bit), but I did find an issue when I sent a transaction. It went through successfully and showed up in the receiving address as well as in the transactions list in Armory. However, when I went away from my computer and came back later, the transaction is no longer there and the wallet has reverted the balance to what it was before. So basically, it now says there are funds to spend even though in reality they've already been sent elsewhere. The bug also persisted across restarting.

Ack, I haven't seen that one before.  Are you sure it has confirmations?  Armory on Windows has always had an issue with the memory pool, for some reason it cannot persist through a restart (that's what all the "Memory pool file was corrupt.  Deleted. (no further action is needed)" messages are about.  But it should resolve itself after the transaction gets one confirmation.  If not, then that's a problem, for sure!  Does it have one confirmation yet?

Yes, this is the address (https://blockchain.info/address/15BtBEktTW7EBoo52vS6B8FxtLCorQqoNi) and this is the transaction (https://blockchain.info/tx/e5babbdd79b1dd24493b68c7e4136a690497c157cb3f6747263686e62d99e7c4).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 25, 2013, 05:21:51 AM
Everything synced fine from a fresh install (Win7 64-bit), but I did find an issue when I sent a transaction. It went through successfully and showed up in the receiving address as well as in the transactions list in Armory. However, when I went away from my computer and came back later, the transaction is no longer there and the wallet has reverted the balance to what it was before. So basically, it now says there are funds to spend even though in reality they've already been sent elsewhere. The bug also persisted across restarting.

Ack, I haven't seen that one before.  Are you sure it has confirmations?  Armory on Windows has always had an issue with the memory pool, for some reason it cannot persist through a restart (that's what all the "Memory pool file was corrupt.  Deleted. (no further action is needed)" messages are about.  But it should resolve itself after the transaction gets one confirmation.  If not, then that's a problem, for sure!  Does it have one confirmation yet?

Yes, this is the address (https://blockchain.info/address/15BtBEktTW7EBoo52vS6B8FxtLCorQqoNi) and this is the transaction (https://blockchain.info/tx/e5babbdd79b1dd24493b68c7e4136a690497c157cb3f6747263686e62d99e7c4).

Ugh.  Okay, definitely a bug.  And the saving-between loads is causing it to persist (it's one of the reasons I liked rescan-every-load, from a reliability perspective).   Can you do me a favor and close Armory, then restart it with the "--rescan" option?  I just realized, I need to put a button into the interface to do that...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 25, 2013, 05:25:00 AM
Winterfrost:  can you also send me a copy of your log file?  Use File->Export Log File.  Then attach it to an email to "bugs@bitcoinarmory.com".  This could be an ugly bug to track down because it's probably pretty difficult to reproduce it on demand.  Hopefully there's something in the logs that helps...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Winterfrost on September 25, 2013, 01:21:52 PM
I sent you the log file. I'll let you know what happens when the rescan finishes.

Update: rescan finished and balances are back to normal.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: cp1 on September 26, 2013, 05:12:08 PM
Finally got around to building it.  It worked fine without any makefile changes on Ubuntu 13.04 64-bit.  I think it took about 3 hours to build the database, but I wasn't watching very closely.  It loads instantly on a wallet with no balance :)  Very nice work.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: cp1 on September 26, 2013, 06:00:00 PM
When starting it for the second time, after downloading what blocks it had to, it got stuck scanning on 1%. I found this in the log over and over, for a very long time.

-WARN  - 0: (..\BlockUtils.cpp:4865) Marking orphan chain
-WARN  - 0: (..\BlockUtils.cpp:4888) Done marking orphan chain

I just added an empty wallet while it was loading and got this loop.  I closed and restarted and it's scanning transaction history again, says 20 minutes remaining.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 26, 2013, 06:07:49 PM
When starting it for the second time, after downloading what blocks it had to, it got stuck scanning on 1%. I found this in the log over and over, for a very long time.

-WARN  - 0: (..\BlockUtils.cpp:4865) Marking orphan chain
-WARN  - 0: (..\BlockUtils.cpp:4888) Done marking orphan chain

I just added an empty wallet while it was loading and got this loop.  I closed and restarted and it's scanning transaction history again, says 20 minutes remaining.

Ugh, that's been happening too much.  Typically a restart solves it.  Before I officially release this version, I'm going to figure out what's causing that and fix it.  But it will not finish loading in that state.  It thinks that every block is an orphan.  It has to be restarted.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: cp1 on September 26, 2013, 09:45:49 PM
I haven't seen that loop since I started running bitcoin-qt independent of armory.  But I've only open and closed it a few times, so it could just be a coincidence.

I know you're busy, but I have (hopefully) a quick question -- I'm trying to add an address to a wallet following the add 500k address in extras, but only adding 1 key (I took out the key reading loop and just used line = private key).  I'm not doing it right because armoryqt.py gives me a checksum error on keys that were already in the wallet: line 3245, in unserialize '('+hash160_to_addrStr(self.addrStr20)+')' armoryengine.UnserializeError: Checksum mismatch in PrivateKey (1LMsGerE3FmWmJig6e5DpmjctFar6RVR2L)

Code:
import os
import sys
sys.path.append('..')
from armoryengine import *


# Could use sys.argv but this script will be used, like, once.  Hardcode it!
wltID        = 'ydeMUhu' # this was the ID of the wallet I tested with
wltDir       = 'ydeMUhu' # this was the ID of the wallet I tested with
wltfile    = os.path.join(ARMORY_HOME_DIR, 'armory_%s_.wallet' % wltID)
wltfilebak = os.path.join(ARMORY_HOME_DIR, 'armory_%s_backup.wallet' % wltID)


if not os.path.exists(wltfile):
   print 'ERROR: Wallet does not exist:', wltfile
   exit(1)

# Remove the backup if it exists
if os.path.exists(wltfilebak):
   os.remove(wltfilebak)




# If you don't delete the backup, Armory will think the primary wallet
# is corrupted and restore the backup

exampleEntry = hex_to_binary( \
  '0047b8ad 0b1d6803 260ce428 d9e09e2c d99fd3b3 5947b8ad 0b1d6803 260ce428 '
  'd9e09e2c d99fd3b3 59fb1670 0860fecd 00030000 00000000 00ffffff ffffffff '
  'ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ff71ca50 49feffff '
  'ffffffff ffffffff ffffffff ff000000 00000000 00000000 00000000 005df6e0 '
  'e2eeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee '
  'eec93a79 dd04a706 ad8f7311 5f905002 66f273f7 571df942 9a4cfb4b bfbcd825 '
  '227202da bad1ba3d 35c73aec 698af852 b327ba1c 24e11758 936bb632 2fe93d74 '
  '69b182f6 6631727c 7072ffff ffff0000 00000000 00000000 0000ffff ffff0000 '
  '0000 '.replace(' ',''))

wltOut = open(wltfile, 'ab')

rawAddrEntry = exampleEntry[21:]
addr20 = rawAddrEntry[:24]
fixed1 = rawAddrEntry[ 24:108]
prvkey = rawAddrEntry[    108:144]
pubkey = rawAddrEntry[        144:213]
fixed2 = rawAddrEntry[            213:]

addrDataToWrite = []

line = "5KaPWnaXTLUdv5WdbwbiXbjDqUFXEUT1aAgSGrYHtzuGD5mooWv"

privBin = base58_to_binary(line[1:-4])
pubBin  = CryptoECDSA().ComputePublicKey(SecureBinaryData(privBin)).toBinStr()
addr20  = hash160(pubBin)
# Pre-PyBtcAddr Entry Header
addrDataToWrite.append('\x00')
addrDataToWrite.append(addr20)

# PyBtcAddr itself
addrDataToWrite.append(addr20)
addrDataToWrite.append(computeChecksum(addr20))

addrDataToWrite.append(fixed1)

addrDataToWrite.append(privBin)
addrDataToWrite.append(computeChecksum(privBin))

addrDataToWrite.append(pubBin)
addrDataToWrite.append(computeChecksum(pubBin))

addrDataToWrite.append(fixed2)

wltOut.write(''.join(addrDataToWrite))
wltOut.close()

Any ideas?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 26, 2013, 10:48:23 PM
I haven't seen that loop since I started running bitcoin-qt independent of armory.  But I've only open and closed it a few times, so it could just be a coincidence.

It really does only happen like once every 10 loads.  And then goes away.  Which will make it tough for me to track it down.  So it's more "expected" than "coincidence"...




I know you're busy, but I have (hopefully) a quick question -- I'm trying to add an address to a wallet following the add 500k address in extras, but only adding 1 key ...

Code:
...

Any ideas?

You just made me realize I should probably remove that example script... that script is actually "special" because someone had wanted to try running Armory with 500k addresses, and I said that it would be ridiculously slow to import them "the right way" (shown below).    So I recommended he manually modify the wallet files with the proper wallet format -- you should not import addresses that way!  

Instead, use the built-in function, and leave everything blank except for the privKey argument:

Code:
def importExternalAddressData(self, privKey=None, privChk=None, \
                                    pubKey=None,  pubChk=None, \
                                    addr20=None,  addrChk=None, \
                                    firstTime=UINT32_MAX,  firstBlk=UINT32_MAX, \
                                    lastTime=0,   lastBlk=0):

I haven't tested the following code, but it would look something like this (note that key data needs to be crammed into a "SecureBinaryData" object before being passed to any of these methods -- but still pretty simple)

Quote from: ExampleCode
# If run from extras dir, need to add parent dir to path
import sys
sys.path.append('..')
from armoryengine import *

# Create the SBD object for the private key which is "aaaaaaaa..."
hardcodedPrivKey = SecureBinaryData(hex_to_binary('aa'*32))

# Read the wallet file (it handles all the backup stuff automatically)
wlt = PyBtcWallet().readWalletFile('/path/to/my.wallet')

# Import the address using the built-in method
wlt.importExternalAddressData(privKey=hardcodedPrivKey)

# Nothing else needs to be done -- the wallet is closed after every operation already
print 'Done!'

# But let's verify it worked:
addr160 = convertKeyDataToAddress(hardcodedPrivKey)
addrStr = hash160_to_addrStr(addr160)
print 'The new address is', addrStr, 'and is in the wallet:', wlt.hasAddr(addr160)


Yeah, it's dead simple when you're using the right calls... sorry for the confusion!  

Edit updated the script with formatting and with the hex_to_binary() call which is needed if you are plugging in a hex private key.  Also, you may have damaged your previous wallet file trying the original script.  You might consider removing it and trying the new script on the original to make sure you're not mixing two different things.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: cp1 on September 27, 2013, 12:23:35 AM
Thanks, that worked great for a 32-byte hex key.  Is it possible to import from WIF?  I've tried:

wlt.importExternalAddressData(privKey=SecureBinaryData(base58_to_binary("5KaPWnaXTLUdv5WdbwbiXbjDqUFXEUT1aAgSGrYHtzuGD5mooWv")))

But I get: assert(plainPrivKey.getSize()==32)

Do I have to convert from WIF to 32-byte first?  Is there a function in armory?  I was snooping in bulkImportAddresses() and found snippets to deal with base-58 private key, but couldn't turn it into anything working.


Edit:  It must be in there somewhere because I think you can import WIF from armoryqt.  Now I'm on a hunt!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 27, 2013, 01:32:41 AM
Thanks, that worked great for a 32-byte hex key.  Is it possible to import from WIF?  I've tried:

wlt.importExternalAddressData(privKey=SecureBinaryData(base58_to_binary("5KaPWnaXTLUdv5WdbwbiXbjDqUFXEUT1aAgSGrYHtzuGD5mooWv")))

But I get: assert(plainPrivKey.getSize()==32)

Do I have to convert from WIF to 32-byte first?  Is there a function in armory?  I was snooping in bulkImportAddresses() and found snippets to deal with base-58 private key, but couldn't turn it into anything working.


Edit:  It must be in there somewhere because I think you can import WIF from armoryqt.  Now I'm on a hunt!

The "parsePrivateKeyData()" method autodetects basically every private key format, including Casascius' mini-private-keys.  You could manually read the keys using "base58_to_binary()", but the following will work just as well to convert the data into 32-byte hex that can imported per my previous example:

Code:
>>> encodePrivKeyBase58('\xaa'*32)
'5K7T2qR7K5MUMDmkJvCEPbUeALuPyc6LFEnBiwWLuKCEVdBp8qV'
>>> parsePrivateKeyData(_)
('\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa',
'Standard Base58 key with checksum')


Edit:  I just noticed you that your problem was actually that you crammed the whole 37 bytes into the import function.  The first byte is 0x80 which is the "network private key byte", and the last four bytes are a checksum: So you could've just done "base58_to_binary(...)[1:-4]" and that would've worked, too.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: cp1 on September 27, 2013, 04:25:51 AM
Success!  Thanks

parsePrivateKeyData worked great.  I still can't figure out base58_to_binary though (not a big deal).  I did try substringing at first using [1:-4], but it never worked for me, I always get too many bytes (and also the wrong answer).

For example:

line = "5JdeQ39z8NUkNVvB37tt74Cu2WSNVj7qb9PdY651UoQnqyCm937"
hardcodedPrivKey = base58_to_binary(line[1:-4])
print prettyHex(binary_to_hex(hardcodedPrivKey))

0x0000:  0d728779 7539eb09 87a0c18f 9e3fac6c 68dbe7f9 1eb106e5 0793d7b9 6e03697f
0x0020:  f673


But parsePrivateKeyData works perfect:

line = "5JdeQ39z8NUkNVvB37tt74Cu2WSNVj7qb9PdY651UoQnqyCm937"
pk = (parsePrivateKeyData(line)[0])
print prettyHex(binary_to_hex(pk))

0x0000:  6b88c087 247aa2f0 7ee1c595 6b8e1a9f 4c7f892a 70e324f1 bb3d161e 05ca107b

Ha, and funny enough it just loaded the transactions for this key in armoryqt and there was a small transaction in May.  People use the worst brainwallets.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 27, 2013, 07:09:12 AM
Hi etotheipi,

I have a strange crash when Armory quits on Mac OS.  LevelDB gives a segfault, the stack trace from gdb is below.

I am by the way almost done making a Mac OS X App.  But since this is not a race for a bounty, I prefer to sit on it for a few days to fix the worst issues  ;)  (No real testing yet, will it run on another machine?  It probably crashes on old hardware if built on new hardware.  The icon and other stuff is missing.  The app is beyond huge, 250M !!).  I think I know how to address all of them.

Anyway, here is the crash data.  It occurs when I quit the app, and it does not depend on whether I build a real app, or just compile Armory and run it from the command line.

Code:
-INFO  - 1380265090: (BlockUtils.cpp:3988) Saving wallet history for next load

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
[Switching to process 899 thread 0x1903]
0x0000000103e083c0 in InterfaceToLDB::commitBatch ()
(gdb) where
#0  0x0000000103e083c0 in InterfaceToLDB::commitBatch ()
#1  0x0000000103e5d064 in BlockDataManager_LevelDB::shutdownSaveScrAddrHistories ()
#2  0x00000001040250fe in _wrap_BlockDataManager_LevelDB_shutdownSaveScrAddrHistories ()
#3  0x000000010001d5a9 in PyEval_EvalFrameEx ()
#4  0x0000000100021869 in _PyEval_SliceIndex ()
#5  0x000000010001d63a in PyEval_EvalFrameEx ()
#6  0x0000000100021869 in _PyEval_SliceIndex ()
#7  0x000000010001d63a in PyEval_EvalFrameEx ()
#8  0x0000000100021869 in _PyEval_SliceIndex ()
#9  0x000000010001d63a in PyEval_EvalFrameEx ()
#10 0x0000000100021869 in _PyEval_SliceIndex ()
#11 0x000000010001d63a in PyEval_EvalFrameEx ()
#12 0x000000010001b147 in PyEval_EvalCodeEx ()
#13 0x0000000100054d7a in PyFunction_SetClosure ()
#14 0x00000001000136c6 in PyObject_Call ()
#15 0x00000001000309bf in PyMethod_New ()
#16 0x00000001000136c6 in PyObject_Call ()
#17 0x0000000100021018 in PyEval_CallObjectWithKeywords ()
#18 0x000000010007d7f6 in initthread ()
#19 0x00007fff96982772 in _pthread_start ()
#20 0x00007fff9696f1a1 in thread_start ()
(gdb) list
1 // algparam.cpp - written and placed in the public domain by Wei Dai
2
3 #include "pch.h"
4
5 #ifndef CRYPTOPP_IMPORTS
6
7 #include "algparam.h"
8
9 NAMESPACE_BEGIN(CryptoPP)
10
(gdb) up
#1  0x0000000103e5d064 in BlockDataManager_LevelDB::shutdownSaveScrAddrHistories () at basic_string.h:279
279       _M_data() const
Current language:  auto; currently c++
(gdb) list
274     private:
275       // Data Members (private):
276       mutable _Alloc_hider _M_dataplus;
277
278       _CharT*
279       _M_data() const
280       { return  _M_dataplus._M_p; }
281
282       _CharT*
283       _M_data(_CharT* __p)
(gdb) up
#2  0x00000001040250fe in _wrap_BlockDataManager_LevelDB_shutdownSaveScrAddrHistories ()
(gdb) list
284       { return (_M_dataplus._M_p = __p); }
285
286       _Rep*
287       _M_rep() const
288       { return &((reinterpret_cast<_Rep*> (_M_data()))[-1]); }
289
290       // For the internal use we have functions similar to `begin'/`end'
291       // but they do not call _M_leak.
292       iterator
293       _M_ibegin() const
(gdb) up
#3  0x000000010001d5a9 in PyEval_EvalFrameEx ()
(gdb) list
294       { return iterator(_M_data()); }
295
296       iterator
297       _M_iend() const
298       { return iterator(_M_data() + this->size()); }
299
300       void
301       _M_leak()    // for use in begin() & non-const op[]
302       {
303 if (!_M_rep()->_M_is_leaked())


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 27, 2013, 11:53:52 AM
I did a bit more debugging, putting a breakpoint in the crashing function and stepping line by line.  It looks like the call to KEY_NOT_IN_MAP triggers an exception in some python code.  It is a testnet wallet, so I could in principle send it to you.

Code:
Breakpoint 1, BlockDataManager_LevelDB::shutdownSaveScrAddrHistories (this=0x104ba23e0) at BlockUtils.cpp:3988
3988    LOGINFO << "Saving wallet history for next load";
(gdb) n
Current language:  auto; currently c++
-INFO  - 1380282523: (BlockUtils.cpp:3988) Saving wallet history for next load
3990    iface_->startBatch(BLKDATA);
(gdb) n
3992    uint32_t i=0;
(gdb) n
3993    set<BtcWallet*>::iterator wltIter;
(gdb)
3994    for(wltIter  = registeredWallets_.begin();
(gdb)
3995        wltIter != registeredWallets_.end();
(gdb)
3998       for(uint32_t a=0; a<(*wltIter)->getNumScrAddr(); a++)
(gdb)
4000          ScrAddrObj & scrAddr = (*wltIter)->getScrAddrObjByIndex(a);
(gdb)
4001          BinaryData uniqKey = scrAddr.getScrAddr();
(gdb)
4003          if(KEY_NOT_IN_MAP(uniqKey, registeredScrAddrMap_))
(gdb)
(ERROR) armoryengine.py:12189 - Waiting for BDM output that didn't come after 20s.
(ERROR) armoryengine.py:12190 - BDM state is currently: Uninitialized
(ERROR) armoryengine.py:12191 - Called from: armoryengine.py:12314 (83837112)
(ERROR) armoryengine.py:12192 - BDM currently doing: Shutdown (83837112)
(ERROR) armoryengine.py:12193 - Direct traceback
  File "ArmoryQt.py", line 4981, in <module>
    os._exit(QAPP.exec_())
  File "ArmoryQt.py", line 4835, in closeForReal
    TheBDM.execCleanShutdown(wait=True)
  File "/Users/schiotz/src/BitcoinArmory/armoryengine.py", line 12314, in execCleanShutdown
    return self.waitForOutputIfNecessary(expectOutput, rndID)
  File "/Users/schiotz/src/BitcoinArmory/armoryengine.py", line 12194, in waitForOutputIfNecessary
    traceback.print_stack()
(ERROR) armoryengine.py:12195 - Traceback:
Traceback (most recent call last):
  File "/Users/schiotz/src/BitcoinArmory/armoryengine.py", line 12185, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
4009          RegisteredScrAddr & rsa = registeredScrAddrMap_[uniqKey];


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: TitanBTC on September 27, 2013, 04:08:42 PM
Just wanted to report that this update is definitely Usable on our windows7 64-bit machine.  Typically we use ubuntu, but I've wanted to try out some watch only copies on windows.  While it does seem to hang regularly when closing the program, its been stable enough to test functionality and everything we typically use works great.  

Current RAM usage on this version is hovering around 315 Mb, which is at least an order of magnitude improvement.  I'll continue troubleshooting to provide more helpful feedback but for now I just wanted to say THANKS for this much needed fix and good luck in your troubleshooting.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 28, 2013, 03:54:15 AM
I did a bit more debugging, putting a breakpoint in the crashing function and stepping line by line.  It looks like the call to KEY_NOT_IN_MAP triggers an exception in some python code.  It is a testnet wallet, so I could in principle send it to you.

Code:
Breakpoint 1, BlockDataManager_LevelDB::shutdownSaveScrAddrHistories (this=0x104ba23e0) at BlockUtils.cpp:3988
3988   LOGINFO << "Saving wallet history for next load";
(gdb) n
Current language:  auto; currently c++
-INFO  - 1380282523: (BlockUtils.cpp:3988) Saving wallet history for next load
3990   iface_->startBatch(BLKDATA);
(gdb) n
3992   uint32_t i=0;
(gdb) n
3993   set<BtcWallet*>::iterator wltIter;
(gdb)
3994   for(wltIter  = registeredWallets_.begin();
(gdb)
3995       wltIter != registeredWallets_.end();
(gdb)
3998      for(uint32_t a=0; a<(*wltIter)->getNumScrAddr(); a++)
(gdb)
4000         ScrAddrObj & scrAddr = (*wltIter)->getScrAddrObjByIndex(a);
(gdb)
4001         BinaryData uniqKey = scrAddr.getScrAddr();
(gdb)
4003         if(KEY_NOT_IN_MAP(uniqKey, registeredScrAddrMap_))
(gdb)
(ERROR) armoryengine.py:12189 - Waiting for BDM output that didn't come after 20s.
(ERROR) armoryengine.py:12190 - BDM state is currently: Uninitialized
(ERROR) armoryengine.py:12191 - Called from: armoryengine.py:12314 (83837112)
(ERROR) armoryengine.py:12192 - BDM currently doing: Shutdown (83837112)
(ERROR) armoryengine.py:12193 - Direct traceback
  File "ArmoryQt.py", line 4981, in <module>
    os._exit(QAPP.exec_())
  File "ArmoryQt.py", line 4835, in closeForReal
    TheBDM.execCleanShutdown(wait=True)
  File "/Users/schiotz/src/BitcoinArmory/armoryengine.py", line 12314, in execCleanShutdown
    return self.waitForOutputIfNecessary(expectOutput, rndID)
  File "/Users/schiotz/src/BitcoinArmory/armoryengine.py", line 12194, in waitForOutputIfNecessary
    traceback.print_stack()
(ERROR) armoryengine.py:12195 - Traceback:
Traceback (most recent call last):
  File "/Users/schiotz/src/BitcoinArmory/armoryengine.py", line 12185, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
4009         RegisteredScrAddr & rsa = registeredScrAddrMap_[uniqKey];

Actually, that's a red herring.  "KEY_NOT_IN_MAP" is actually a macro that is pretty safe from seg faults.  The problem was you waiting 10+ seconds between calling "Shutdown" and letting it finish shutting down.  At least that's why you got that error message from python -- It's difficult for the app to determine whether the blockdatamanager is stuck in an infinite loop or not, and starts throwing errors if any wait=True operation takes more than 10s.   Shutting down should not take long.  

The registeredScrAddrMap_[uniqKey] is much more likely to throw the seg fault, but I call "KEY_NOT_IN_MAP()" to make sure the key actually exists before attempting to access it like that.  So again, that should be fairly safe.  Unless the uniqKey object had destroyed/cleared and it was attempting to access the data behind it...

I'm going to go on a hunt for this bug this weekend.  It seems frequent enough I should be able to catch it if I restart the app enough times.  Unfortunately, I can't get the project compiling in debug mode in Windows, where debugging would be quite a bit easier...  I'll figure it out, either way.

By the way, goatpig came through and got me a full Windows port of the latest LevelDB for MSVS.  He's pretty badass with this obscure windows stuff!  I have a bit of my own testing to do on the new code, but it looks like it's building the DB about the same speed as Linux now -- in under an hour.  If that's true, then it will rescan in 10-15 min, too.  

Glad to see that the app is mostly working for people.  My wedding and then honeymoon starts in exactly a week, so I will be getting these bugs cleaned up and do a release towards the end of the week.  So far everything seems to be smooth, and any lingering usability issues are far preferable to the old usability issues (as long as the integrity is there, which it is).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 28, 2013, 03:55:15 AM
P.S -- Has no one played with the new backup center?  Come on!  It's so badass!



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: SimonBelmond on September 28, 2013, 06:43:27 AM
P.S -- Has no one played with the new backup center?  Come on!  It's so badass!



One back from the conference I'll spend some time on it. Have some other things to to do also but I am also excited about the new features.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: picobit on September 28, 2013, 02:05:46 PM
OK, so tracing the bug is difficult if one cannot single-step through the function unless it is done in less than 10 sec :)

It seems that it sometimes cause corruption of the database, so that a rescan is necessary on the next restart.  Othewise transactions may be missing.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 28, 2013, 02:44:45 PM
OK, so tracing the bug is difficult if one cannot single-step through the function unless it is done in less than 10 sec :)

It seems that it sometimes cause corruption of the database, so that a rescan is necessary on the next restart.  Othewise transactions may be missing.


Modify the variable MT_WAIT_TIMEOUT_SEC (https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine.py#L966) in armoryengine.py.  Set it to UINT32_MAX or something.   That will help with the debugging.

Also, be aware that I explicitly try to avoid corrupting the wallet history by only saving it if there's a clean shutdown.  If you kill Armory, or you close it while it's scanning, offline, or dirty, it will not save any history and will require rescanning. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Kyune on September 28, 2013, 06:59:47 PM
P.S -- Has no one played with the new backup center?  Come on!  It's so badass!
Great to see a M of N paper backup implemented so smoothly.  I've really been looking forward to that as a GUI feature.
Been poking around 0.89.99.3 in a Ubuntu 12.04 VM.  No issues so far.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: cp1 on September 28, 2013, 07:36:42 PM
I look around in parsePrivateKeyData and figured out what I needed to add to my base58 conversion, thanks.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 28, 2013, 07:48:18 PM
I look around in parsePrivateKeyData and figured out what I needed to add to my base58 conversion, thanks.

So what was it?  I just did the same thing as you did at first and got a wacky answer.  I haven't looked at that in forever, so I'm curious what I forgot.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: P_Shep on September 28, 2013, 08:10:15 PM
It appeared to be working... started up, took forever to scan then showed my balance... but then I hit exit and my machine immediately BSOD'ed :/


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 28, 2013, 08:16:20 PM
It appeared to be working... started up, took forever to scan then showed my balance... but then I hit exit and my machine immediately BSOD'ed :/

Wtf?  Certainly haven't heard that one yet...

System specs?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: cp1 on September 28, 2013, 10:14:01 PM
I look around in parsePrivateKeyData and figured out what I needed to add to my base58 conversion, thanks.

So what was it?  I just did the same thing as you did at first and got a wacky answer.  I haven't looked at that in forever, so I'm curious what I forgot.

I had to take the substring of the hex instead of the substring of the private key and then it worked.

line = "5KJvsngHeMpm884wtkJNzQGaCErckhHJBGFsvd3VyK5qMZXj3hS"
binEntry = base58_to_binary(line)
print prettyHex(binary_to_hex(binEntry[1:33]))


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Kupsi on September 28, 2013, 11:46:56 PM
P.S -- Has no one played with the new backup center?  Come on!  It's so badass!

It's awesome!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: P_Shep on September 29, 2013, 12:06:48 AM
It appeared to be working... started up, took forever to scan then showed my balance... but then I hit exit and my machine immediately BSOD'ed :/

Wtf?  Certainly haven't heard that one yet...

System specs?


Sorry, was going to, but forgot... Win 8, 16Gb Ram, SSD + HDD, i7 Quad core 2.4GHz.

I'll try again tomorrow see what happens.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: Kupsi on September 29, 2013, 12:08:08 AM
A little bug?

https://i.imgur.com/yM7R31u.png


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: etotheipi on September 29, 2013, 12:46:14 AM
A little bug?

<IMG>


Meh.  It's not really a bug.  The backwards compatibility of the new backup features led to me breaking up the versions of the backups based on various factors.  Basically, the wallet is version 1.35, and the type of backup is "c" (vs "a" vs "").  I can see it being slightly confusing, but it's really because the wallet code hasn't changed, only the backup features did.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on September 29, 2013, 12:57:38 AM
Just pushed 0.89.99.5-testing.  Also updated the download link for Windows, which is now a NSIS installer courtesy of my new employee (Andy) :)  Try it out!  I did sign the .exe with my SSL Class 2 cert, but the signature is no shown when you double-click the .exe to run it.  I need to figure out why that is...  but you can still see it by right-clicking, going to "Properties" and then "Digital Signatures". 

By the way, the process of building the installer is now integrated into the MSVS build system, so every time I "Rebuild All", I get a properly named "ArmorySetup_<version>.exe" file.  This will dramatically improve my release process.  Thanks Andy!

As for code, this is really just an efficiency update for Windows, with a few tweaks.  "goatpig" has been awesome: he built me a completely native port of LevelDB, which seems to be totally absent everywhere else on the internet... because it's really hard.  Please test it especially if you were testing before.  That way you can compare speed for me, and know what did and did not work before. 

Also updated the progress meter to give better feedback while building and scanning.  And a few tiny things mentioned on this thread over the past few days.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: CircusPeanut on September 29, 2013, 02:04:00 AM
(This is Andy)

Alan, Glad to take some of the grunt work off of your hands.

Feel free to let me know any feedback you have about the windows installer.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: prezbo on September 29, 2013, 10:32:16 AM
It appeared to be working... started up, took forever to scan then showed my balance... but then I hit exit and my machine immediately BSOD'ed :/

I have a similar problem. The building databases stage takes forever (about an hour or so), it doesn't bsod when I quit but on the restart the preparing/building databases stage starts all over again. Also similar specs - win 7 64 bit, i5-2500k, 12 g of ram. Logs don't indicate anything to be wrong either.

Nevermind, problem on my end, works as intended. Awesome stuff!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.3)
Post by: P_Shep on September 29, 2013, 12:49:08 PM
It appeared to be working... started up, took forever to scan then showed my balance... but then I hit exit and my machine immediately BSOD'ed :/

Wtf?  Certainly haven't heard that one yet...

System specs?


Sorry, was going to, but forgot... Win 8, 16Gb Ram, SSD + HDD, i7 Quad core 2.4GHz.

I'll try again tomorrow see what happens.

Just upped to the latest. Quit OK now.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: Dabs on September 29, 2013, 01:16:16 PM
Wow, I missed all the action. I will begin testing this week. I still use Win XP SP3 32 bit with 2 gig of ram. Two old laptops. And dozens of new desktops with 4 gig ram but still old XP on them for work. (I run a clothes business, no need for new OS.)

I do have an updated blockchain of bitcoin-qt.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: picobit on September 29, 2013, 07:31:48 PM
Just pushed 0.89.99.5-testing. 
Looks like this fixed the crashing on exit bug on OS X!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: picobit on September 29, 2013, 07:36:45 PM
I have finally produced a script that creates a stand-alone OS X app of Armory.  Not a single line of higuys' script has been used (but I use his Info.plist), and I do many things in a different way.  Nevertheless, this is based on his work and it would have taken me at least ten times longer to do it without his work to build on! 

Some comments:

* I have only tested it slightly, and almost exclusively on Testnet.

* The building script is written in Python.  Perhaps that will make it easier for etotheipi to maintain it; it certainly made it easier for me to write it.   ;)

* The app is 64-bit only.  I doubt that Armory can fit into a 32-bit memory model.

* Higuys' script delegated most of the compiling to Homebrew, and copied the result into the App.  This script compiles things directly (although mostly the same way as Homebrew would have done it).  It looks like this solves the problem with the App crashing on Macs that are older than the one used to build the App.  Homebrew assumes that compiled code will be executed on the local machine, and tries to get a bit of extra performance by enabling the full instruction set of the actual CPU.  The usual building scripts are more conservative, and build for all 64-bit CPUs.

* The app claims to work on OS X 10.6 or later, but in reality I have no idea if it works on 10.6 and 10.7.  I suspect that if it declared 10.8 or later that alone would prevent it from working on older versions.

* The app is huge, 136 M.  This is because it contains the majority of a Python installation (mostly .pyc files, but still 65M) and a large part of Qt (51M).  I suspect I can shave off another 25-50 M.

* Command line arguments are ignored (so even if you know how to pass command line arguments to OS X apps, you cannot ask Armory to use e.g. testnet).  This is because I cannot just pass on command line arguments to the Python script as OS X adds its own extra arguments.

I will send this script by PM to etotheipi.  I hereby donate the script to the Armory project and transfer copyright etc.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: LogicalUnit on September 30, 2013, 01:53:17 AM
I just installed 0.89.99.5-beta, and was a little disappointed to see that the Message Signing functionality is only compatible with other versions of Armory. Will there ever be an Armory/Bitcoin-Qt cross-compatible signing mechanism?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cp1 on September 30, 2013, 03:21:02 AM
I just installed 0.89.99.5-beta, and was a little disappointed to see that the Message Signing functionality is only compatible with other versions of Armory. Will there ever be an Armory/Bitcoin-Qt cross-compatible signing mechanism?

What do you mean?  As far as I know there's only one way to sign something.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: picobit on September 30, 2013, 09:54:58 AM
I just installed 0.89.99.5-beta, and was a little disappointed to see that the Message Signing functionality is only compatible with other versions of Armory. Will there ever be an Armory/Bitcoin-Qt cross-compatible signing mechanism?

What do you mean?  As far as I know there's only one way to sign something.
No, he is right.  The mathematics may be (almost) the same, but armory signing and bitcoin-qt signing are not compatible.  He is working on it, but unsurprisingly getting the RAM problems solved has much higher priority.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: Dabs on October 01, 2013, 03:42:47 AM
I downloaded the windows msi file which is ArmorySetup-0.89.99.5-beta_win32.exe

Ran it. Installed. Clicked OK OK, Next, Etc. Clicked "Run Armory". Then I get this:

Quote
Errors occured
See the logfile 'C:\Program Files\Armory\ArmoryQT.exe.log' for details

Contents of that file:

Quote
Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

My system specs:
Windows XP SP3 (almost fresh install) 32 bit. (pro or corp, if that matters, not home)
2 gig ram
Intel Pentium T4400

Bitcoin-Qt is running in the background, version 0.8.5
Bitcoin-Qt is also not "installed", I run it from a different drive with -datadir. The blockchain data is in another drive.

*edit* I tried doing -datadir and -offline (there are also shortcuts after installation) and both did not work. I can't even run it offline mode.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: goatpig on October 01, 2013, 04:07:32 AM
Most likely an msvc11 build. Long story short, the tool used to build Armory for Windows doesn't natively creates .exe that can be run under WinXP. You'd have to select the specific build tool for XP to build XP compatible Armory. The task is simple, but that version of the binary is most likely not bundled in the package you got. You should ask for a WinXP build or build it yourself, although you'll need Win Vista or above to build it, since msvc11 needs .Net Framework 4.0, which is for Win 6.0 and above only


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: SimonBelmond on October 01, 2013, 04:44:44 AM
I also have problems with this latest version. I have Win7 64 4 gb ram and some quadcore processor. I installed and ran. The blockchain downloaded fine. The scan took forever and I finaly ended with aborting the scan after 14h. Progress bar was still showing 1%. With version 0.89.99.3 The scan was finished after 7h or maybe even earlier (i went to bed so I don't know exactly). Any sugestions? Should I have deleted some files or something before starting?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 01, 2013, 06:18:17 PM
There is still a problem where the app occasionally starts up like that and is filling the log with "Marking Orphan Chain" messages, but it looks like it's doing something or getting ready to do something.  This is one of the big bugs I have to fix before I can put out a real release.

After you've done the initial sync with Bitcoin-Qt, and Armory built the database, the most it should take is 10-20 minutes to do a rescan.  And if you've loaded it before and closed it in a good state, it won't even need to do that.  And when it is rescanning, it will tell you that it is.

Moral of the story:  if it stays at 1% for more than a couple minutes, it's hosed.  But restarting seems to fix it. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 01, 2013, 07:52:04 PM
I am trying to 'make' the Makefile in Ubuntu 13.04, but I have found this instruction from you Etotheipi:

Quote
...open the cppForSwig/Makefile and uncomment the LIBRARY_OPTS line around line 13 that includes "config-x86_64-linux" and also remove the STATICPYTHON variable (just use "STATICPYTHON =" without anything after it)...

What exactly does this mean? My makefile looks like this:

Code:
LIBRARY_OPTS += -lpthread -Lleveldb -L/usr/lib/python2.7/config-x86_64-linux-gnu/ -lpython2.7
SWIG_OPTS    += -c++ -python -classic -threads


UNAME := $(shell uname)

ifeq ($(UNAME), Darwin)
   # This configuration assumes you have setup your 10.X.X system like
   # Red Emerald in this thread:
   #    https://bitcointalk.org/index.php?topic=73648.msg976015#msg976015
# The makefile updates he shows are already tied into this if/else branch
   PYVER += `python -c 'import sys; print str(sys.version_info[0]) + "." + str(sys.version_info[1])'`
   SWIG_INC     += -I"/usr/include/python$(PYVER)"
   STATICPYTHON +=   "/usr/lib/python$(PYVER)/config/libpython$(PYVER).a"
else
   PYVER += `python2 -c 'import sys; print str(sys.version_info[0]) + "." + str(sys.version_info[1])'`
   SWIG_INC     += -I"$(DEPSDIR)/include/python$(PYVER)"
   #STATICPYTHON +=   "$(DEPSDIR)/lib/libpython$(PYVER).a"
   STATICPYTHON =

Which I believe does not have any comments on line LIBRARYOPTS, and also already has the line STATICPYTHON blank, so do I need to change this file before running 'make'?

Sorry if this is obvious.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cp1 on October 01, 2013, 08:17:03 PM
Did you try it without the changes?  I didn't need to make any, I think I'm using 13.04 xubuntu.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 01, 2013, 08:20:28 PM
I am trying to 'make' the Makefile in Ubuntu 13.04, but I have found this instruction from you Etotheipi:

Quote
...open the cppForSwig/Makefile and uncomment the LIBRARY_OPTS line around line 13 that includes "config-x86_64-linux" and also remove the STATICPYTHON variable (just use "STATICPYTHON =" without anything after it)...

What exactly does this mean? My makefile looks like this:

Code:
LIBRARY_OPTS += -lpthread -Lleveldb -L/usr/lib/python2.7/config-x86_64-linux-gnu/ -lpython2.7
SWIG_OPTS    += -c++ -python -classic -threads


UNAME := $(shell uname)

ifeq ($(UNAME), Darwin)
   # This configuration assumes you have setup your 10.X.X system like
   # Red Emerald in this thread:
   #    https://bitcointalk.org/index.php?topic=73648.msg976015#msg976015
# The makefile updates he shows are already tied into this if/else branch
   PYVER += `python -c 'import sys; print str(sys.version_info[0]) + "." + str(sys.version_info[1])'`
   SWIG_INC     += -I"/usr/include/python$(PYVER)"
   STATICPYTHON +=   "/usr/lib/python$(PYVER)/config/libpython$(PYVER).a"
else
   PYVER += `python2 -c 'import sys; print str(sys.version_info[0]) + "." + str(sys.version_info[1])'`
   SWIG_INC     += -I"$(DEPSDIR)/include/python$(PYVER)"
   #STATICPYTHON +=   "$(DEPSDIR)/lib/libpython$(PYVER).a"
   STATICPYTHON =

Which I believe does not have any comments on line LIBRARYOPTS, and also already has the line STATICPYTHON blank, so do I need to change this file before running 'make'?

Sorry if this is obvious.

It's not obvious.  And I'm frustrated that the Makefile is still so terrible.  I have gone to great lengths to make sure Armory is easy to compile on all *nix systems, and it is ... once you get the Makefile worked out.  I really need a better Makefile, but my Makefile skills are crap. 

What you posted looks right.  Did you install all the dependencies first?  See here:

http://bitcoinarmory.com/download/building-armory-from-source/

Quote
sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil

The "python-dev" pacakge should put libpython2.7.a into the /usr/lib/python2.7/config-x86_64-linux-gnu/ directory.  If it's not there, please post the output of: 

Code:
$ cd /usr
$ find . | grep libpython2


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 01, 2013, 08:25:32 PM
Yes, I installed dependencies:

Code:
~$ sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil
[sudo] password for will:
Reading package lists... Done
Building dependency tree      
Reading state information... Done
python-twisted is already the newest version.
libqt4-dev is already the newest version.
swig is already the newest version.
git-core is already the newest version.
libqtcore4 is already the newest version.
python-dev is already the newest version.
build-essential is already the newest version.
python-qt4 is already the newest version.
pyqt4-dev-tools is already the newest version.
python-psutil is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This is the result of my 'make' command (I tried with no edits to the Makefile):

Code:
make[2]: Leaving directory `/home/will/BitcoinArmory/cppForSwig/cryptopp'
cd leveldb; make libleveldb.a; mv libleveldb.a ..
make[2]: Entering directory `/home/will/BitcoinArmory/cppForSwig/leveldb'
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -fPIC -O2 -DNDEBUG        -c db/builder.cc -o db/builder.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -fPIC -O2 -DNDEBUG        -c db/c.cc -o db/c.o
db/c.cc: In function ‘bool SaveError(char**, const leveldb::Status&)’:
db/c.cc:141:42: error: ‘_strdup’ was not declared in this scope
db/c.cc:145:42: error: ‘_strdup’ was not declared in this scope
db/c.cc: In function ‘char* leveldb_property_value(leveldb_t*, const char*)’:
db/c.cc:250:30: error: ‘_strdup’ was not declared in this scope
make[2]: *** [db/c.o] Error 1
make[2]: Leaving directory `/home/will/BitcoinArmory/cppForSwig/leveldb'
mv: cannot stat ‘libleveldb.a’: No such file or directory
make[1]: *** [libleveldb.a] Error 1
make[1]: Leaving directory `/home/will/BitcoinArmory/cppForSwig'
make: *** [all] Error 2


Python is in /usr/ correctly I think:

Code:
will@ubuntu:/usr/lib/python2.7/config-x86_64-linux-gnu$ ls
config.c  config.c.in  install-sh  libpython2.7.a  libpython2.7-pic.a  libpython2.7.so  Makefile  makesetup  python.o  Setup  Setup.config  Setup.local

and this is the result of running

$ cd /usr
$ find . | grep libpython2

Code:
./lib/x86_64-linux-gnu/libpython2.7.so
./lib/x86_64-linux-gnu/libpython2.7.a
./lib/x86_64-linux-gnu/libpython2.7.so.1.0
./lib/x86_64-linux-gnu/libpython2.7.so.1
./lib/python2.7/config-x86_64-linux-gnu/libpython2.7.so
./lib/python2.7/config-x86_64-linux-gnu/libpython2.7.a
./lib/python2.7/config-x86_64-linux-gnu/libpython2.7-pic.a
./share/doc/libpython2.7
./share/doc/libpython2.7-stdlib
./share/doc/libpython2.7-minimal
./share/doc/libpython2.7-minimal/changelog.Debian.gz
./share/doc/libpython2.7-minimal/copyright
./share/doc/libpython2.7-minimal/README.Debian
./share/doc/libpython2.7-dev
./share/lintian/overrides/libpython2.7
./share/lintian/overrides/libpython2.7-stdlib
./share/lintian/overrides/libpython2.7-minimal
./share/lintian/overrides/libpython2.7-dev

Sorry for so much code in a single post!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cp1 on October 01, 2013, 09:19:18 PM
That's weird, I don't think it even tried to compile any directory except for cppforswig root directory.  I just did a make clean in the leveldb, cryptopp, and cppforswig directories and redid make in the root BitcoinArmory directory and it didn't do anything to leveldb or cryptopp.  I did get an a.out in cryptopp, not sure from what.

BTW I'm on Xubuntu 13.04, but this is with armory 0.89.99.3

Do you have libcrypto++-dev and qt4reactor.py?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 01, 2013, 10:13:07 PM
That's weird, I don't think it even tried to compile any directory except for cppforswig root directory.  I just did a make clean in the leveldb, cryptopp, and cppforswig directories and redid make in the root BitcoinArmory directory and it didn't do anything to leveldb or cryptopp.  I did get an a.out in cryptopp, not sure from what.

BTW I'm on Xubuntu 13.04, but this is with armory 0.89.99.3

Do you have libcrypto++-dev and qt4reactor.py?

Huh, well i didn't have either actually, had previously only run
Code:
sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil
On top of a completely fresh Ubuntu 13.04 (64bit) install to VMWare.

Now I installed libcrypto++-dev and also this package http://packages.ubuntu.com/precise/python-qt4reactor and all those related packages (just to be sure)...

Ran make again and just threw the exact same error?

http://pastebin.com/rHe2g9kU
(Full log from terminal)

I am officially out of my depth and stuck :/


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cp1 on October 01, 2013, 10:52:34 PM
Ah I tried the new version and got the same error as you.

From a diff of the two versions it looks like line 18 in leveldb/db/c.cc was added:  #define strdup _strdup.  Just delete that line and remake.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cryptomint on October 01, 2013, 11:16:15 PM
Ah I tried the new version and got the same error as you.

From a diff of the two versions it looks like line 18 in leveldb/db/c.cc was added:  #define strdup _strdup.  Just delete that line and remake.

I was having the same problem. Commenting out this line allowed it to compile for me (Debian testing/jessie)

Thanks!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: goatpig on October 01, 2013, 11:17:02 PM
#define strdup _strdup

This line is for the msvc11 build only. Sorry, it should be only defined for the Windows project:

Code:
#ifdef _MSC_VER
#define strdup _strdup
#endif


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 02, 2013, 06:26:30 AM
Great success, that sorted it.

Nicely spotted cp1! I guess 'diff' should be my next command to learn (if indeed it was a terminal command at all)...  ;D


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 02, 2013, 09:01:35 AM
etotheipi, and anyone else who wants to try this test branch (and is a bit of a terminal noob like myself) in my experience for Ubuntu 13.06 (64bit) you can use the following build instructions, for 0.89.99.5:

Code:
sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil libcrypto++-dev

git clone git://github.com/etotheipi/BitcoinArmory.git

cd BitcoinArmory

git checkout testing

cd BitcoinArmory/cppForSwig/leveldb/db/

gedit c.cc

// Comment out or delete line 18 (" #define strdup _strdup"), save and close c.cc

cd ~/BitcoinArmory

make

python ArmoryQt.py


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cp1 on October 02, 2013, 10:26:11 PM
I think you have to cd to the bitcoinarmory directory before switching the branch.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 07, 2013, 10:39:26 AM
I think you have to cd to the bitcoinarmory directory before switching the branch.

Right you are, corrected.

In other news, I have been using this build reasonably sucessfully now for a few days, until two days ago I wanted to move some coins to an online wallet.

I was not near my dedicated offline netbook which holds the private keys for my wallet so performed something of an emergency procedure: I downloaded armory (stable version 0.88.1 windoze) on the laptop I had access to, and restored my wallet (from paper backup).

I did not even download bitcoin qt/d as i just needed the privkeys, then, I exported the privkeys and swept the balances to my other wallet, so now, theoretically, the coins are not in an address in the armory address book...Right?

Wrong!

Although I can see that the funds have been moved to a new address, when I returned to my machine with the VM and armory 0.89.99.5 loaded on, the coins are apparently still in the wallet!?

I have checked the terminal and I seem to be synced up to the latest block; all the lights seem to be green on armory, anybody know what is going on?



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cp1 on October 07, 2013, 04:32:45 PM
If I read that right you tried to sweep a balance without having access to the blockchain.  You can't do that because it doesn't know anything about your transactions.

Edit:  It would be cool to have access to a blockchain.info type website where you could query unspent transactions, for this kind of emergency mode.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 07, 2013, 04:49:31 PM
cp1 sorry, I may not have made myself clear. I used a second (online) wallet to sweep the funds.

It is just the (online) Armory wallet running in a VM which does not seem to register that the funds have left all addresses controlled by it...

Edit: Fixed. Nevermind


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: winnetou on October 09, 2013, 04:34:21 PM
Is this version already safe to use for managing (creating & broadcasting) offline transactions?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: w00dy on October 10, 2013, 08:22:00 AM
There is still a problem where the app occasionally starts up like that and is filling the log with "Marking Orphan Chain" messages, but it looks like it's doing something or getting ready to do something.  This is one of the big bugs I have to fix before I can put out a real release.

After you've done the initial sync with Bitcoin-Qt, and Armory built the database, the most it should take is 10-20 minutes to do a rescan.  And if you've loaded it before and closed it in a good state, it won't even need to do that.  And when it is rescanning, it will tell you that it is.

Moral of the story:  if it stays at 1% for more than a couple minutes, it's hosed.  But restarting seems to fix it. 

Restarting does not fix it here.

BitconQT is up-to-date but the 0.89.99.5 beta is stuck with this problem every time i start it.

x64 W7, 8GB RAM, TC'ed System


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: SimonBelmond on October 10, 2013, 02:12:09 PM
same here. Worked with 0.89.99.3 version. Might it be the installer? Shall we send logs? which ones and from what location?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: HowlingMad on October 13, 2013, 01:25:26 AM
Is this version for Windows supposed to be 64 bit?  My Win7 installation saves it in the 32-bit subdir and states in TaskMan that it is 32-bit, along with bitcoind.
Thank you


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: DobZombie on October 14, 2013, 02:14:08 PM
bug -

armory 89.99.3 (the standalone windows version)

It crashed and left bitcoin.exe running.  When I attempted to restart armouryqt.exe nothing happened.  I had to open the task manager and close bitcoin.exe

Hope this helps!
======================================

Also, is there a way to automatically sweep the change back into the original address?  So if I'm using a vanity address I can happily use it on many devices.

and don't lecture me on security, I only keep BTC1 in there so I can make small purchases while I'm out and about : ;)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 14, 2013, 10:20:10 PM
Also, is there a way to automatically sweep the change back into the original address?  So if I'm using a vanity address I can happily use it on many devices.

You can use custom change behavior in Armory by switching to "Expert" usermode.  Then when you create a transaction, you can specify that you want the change to be sent back to the first input address, or specify another address.  You can also choose to have it remember the setting so you won't have to re-select it for each transaction.

Hope that helps!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: DobZombie on October 15, 2013, 01:24:04 PM
Also, is there a way to automatically sweep the change back into the original address?  So if I'm using a vanity address I can happily use it on many devices.

You can use custom change behavior in Armory by switching to "Expert" usermode.  Then when you create a transaction, you can specify that you want the change to be sent back to the first input address, or specify another address.  You can also choose to have it remember the setting so you won't have to re-select it for each transaction.

Hope that helps!

You the man! (you know that don't you) :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: winnetou on October 15, 2013, 06:42:41 PM
Is this version already safe to use for managing (creating & broadcasting) offline transactions?

Or should I wait until the final release!?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: DobZombie on October 16, 2013, 05:35:01 PM
The Build database and scan doesn't make it to 100%.

At some point, it crashes and I gotta start again :(

The stand alone version crashed a bit less

I'm running Windows 8 if that helps.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 16, 2013, 07:04:16 PM
The Build database and scan doesn't make it to 100%.

At some point, it crashes and I gotta start again :(

The stand alone version crashed a bit less

I'm running Windows 8 if that helps.

 
I don't know if this is the problem, but you can run it with "--rebuild" which will delete the database and start over from scratch (Bitcoin-Qt DB will still be there, so it will only take 1-2 hours to do a rebuild).  I'm curious if doing a full rebuild fixes it for you.  So far, I haven't seen any one need it yet, but if you have no other choice, you should try it.

Is this version already safe to use for managing (creating & broadcasting) offline transactions?

Or should I wait until the final release!?

It's safe to use for executing offline transactions.  I'm just not 100% confident that the backups will be the same as the final version.  I know it creates a frustrating dynamic, because I need people to help test the backups, but I have to tell them not to rely on them yet.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: SimonBelmond on October 16, 2013, 08:33:37 PM
I don't know if this is the problem, but you can run it with "--rebuild" which will delete the database and start over from scratch (Bitcoin-Qt DB will still be there, so it will only take 1-2 hours to do a rebuild).  I'm curious if doing a full rebuild fixes it for you.  So far, I haven't seen any one need it yet, but if you have no other choice, you should try it.

Seems to do the job for me. Tried 50 times before and always stuck at 1%. Now already at 3% after 3 min. Thanks for the advice.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 16, 2013, 08:37:48 PM
I don't know if this is the problem, but you can run it with "--rebuild" which will delete the database and start over from scratch (Bitcoin-Qt DB will still be there, so it will only take 1-2 hours to do a rebuild).  I'm curious if doing a full rebuild fixes it for you.  So far, I haven't seen any one need it yet, but if you have no other choice, you should try it.

Seems to do the job for me. Tried 50 times before and always stuck at 1%. Now already at 3% after 3 min. Thanks for the advice.

Thanks for identifying how much more work I have to do to get this version stable :-\

It's tough getting my brain back into the game after 2-3 weeks of vacation!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: SimonBelmond on October 16, 2013, 08:48:21 PM
I don't know if this is the problem, but you can run it with "--rebuild" which will delete the database and start over from scratch (Bitcoin-Qt DB will still be there, so it will only take 1-2 hours to do a rebuild).  I'm curious if doing a full rebuild fixes it for you.  So far, I haven't seen any one need it yet, but if you have no other choice, you should try it.

Seems to do the job for me. Tried 50 times before and always stuck at 1%. Now already at 3% after 3 min. Thanks for the advice.

Thanks for identifying how much more work I have to do to get this version stable :-\

It's tough getting my brain back into the game after 2-3 weeks of vacation!


I was going to write before that I wish that you had a nice honeymoon. Then I thought: I cant do that because I don't know if it was already over. Anyway. Hope you and your wife had a good wedding and enjoyed the time off.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: dserrano5 on October 16, 2013, 08:49:45 PM
It's tough getting my brain back into the game after 2-3 weeks of vacation!

Off topic if I may, but I'm curious: how did you learn of the SR news? :) (assuming you did!)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 16, 2013, 09:13:47 PM
There is no problem using the new/testing version to create transactions to be signed offline and then broadcast.  The nice thing about the offline system is that you can always keep an old, stable version on there, and it will notice if something is wrong.  For instance, if online Armory does not construct the addresses properly, the offline system will throw an error, or display a different address than you were expecting. 

The online-offline split provides an extra layer of protection against both malicious attacks, and bugs!   But so far I've used it for multiple online and offline transactions, and I have other people helping test with no reports of issues beyond the usability ones.  If you're really paranoid, just make sure you read the confirmation dialogs closely and verify the addresses match.  Those dialogs haven't changed at all, so they are reliable at reporting what is actually in the transaction you are about to execute.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: justmyname on October 17, 2013, 11:27:36 PM
I have 4G of Ram. Is their an online version of Armory that will work with 4G? Or should I just wait? 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: SimonBelmond on October 18, 2013, 03:54:11 AM
I have 4G of Ram. Is their an online version of Armory that will work with 4G? Or should I just wait? 

Works like a charm for me with 4GB.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: DobZombie on October 18, 2013, 09:25:38 AM
The Build database and scan doesn't make it to 100%.

At some point, it crashes and I gotta start again :(

The stand alone version crashed a bit less

I'm running Windows 8 if that helps.

 
I don't know if this is the problem, but you can run it with "--rebuild" which will delete the database and start over from scratch (Bitcoin-Qt DB will still be there, so it will only take 1-2 hours to do a rebuild).  I'm curious if doing a full rebuild fixes it for you.  So far, I haven't seen any one need it yet, but if you have no other choice, you should try it.


That did the job! Program hasn't crashed on me either.  I gotta say, I'm pretty happy!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 18, 2013, 09:51:06 AM
Is it possible to install 0.89.99.5 on an offline machine to use as the offline component, as I would like to generate backups using the new m of n backup system, but don't want to do this on my online machine...

My offline (netbook - very low power) is running Ubuntu 10.04 currently, but this could be changed if needed...

Would it just be a case of installing all the dependencies and then compiling and running the app from the terminal as I have been doing on my VM (which I talked about earlier in the this thread), or would I be able to compile on my (fast) online machine and then transfer the binaries over to the offline machine and run like that...?

Sorry if this doesn't make sense, I am learning a lot of this as I go along...  :D

So questions:
Will this run on ubuntu 10.04?
Can I precomplie on a different (more powerful) machine and transfer over binaries or .deb files or something to my crappy netbook


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: Kupsi on October 18, 2013, 11:40:07 AM
I'm just not 100% confident that the backups will be the same as the final version.  I know it creates a frustrating dynamic, because I need people to help test the backups, but I have to tell them not to rely on them yet.

When will you decide this? I would love to use the m-of-n paper backup.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: SimonBelmond on October 19, 2013, 07:09:58 AM
I'm just not 100% confident that the backups will be the same as the final version.  I know it creates a frustrating dynamic, because I need people to help test the backups, but I have to tell them not to rely on them yet.

When will you decide this? I would love to use the m-of-n paper backup.

I think the paper backup should have an option to have no identifying information other than the codes.  If someone finds the paper backup it clearly states it is a backup for a Bitcoin wallet.  If it is just a string of numbers of letters most people are not going to know what it is if they find it.

Should be configurable though. The backup slip which is going into the inheritance needs to be clear on beeing a cryptocurrency key backup.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: justmyname on October 19, 2013, 09:41:05 AM
I have 4G of Ram. Is their an online version of Armory that will work with 4G? Or should I just wait? 

Works like a charm for me with 4GB.

MY computer goes into hibernation when downloading the Block Chain for the first time. Unless I am using the computer. Then has to start over each time. Computer is so slow when running it.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: SimonBelmond on October 19, 2013, 10:16:51 AM
I have 4G of Ram. Is their an online version of Armory that will work with 4G? Or should I just wait? 

Works like a charm for me with 4GB.

MY computer goes into hibernation when downloading the Block Chain for the first time. Unless I am using the computer. Then has to start over each time. Computer is so slow when running it.

Adjust it in the power settings in your control panel.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: justmyname on October 19, 2013, 10:36:48 PM
I have 4G of Ram. Is their an online version of Armory that will work with 4G? Or should I just wait? 

Works like a charm for me with 4GB.

MY computer goes into hibernation when downloading the Block Chain for the first time. Unless I am using the computer. Then has to start over each time. Computer is so slow when running it.

Adjust it in the power settings in your control panel.

That seems to have worked. I was going to try that but I didn't know where it was on windows 7. Thanks.

I wonder if a Chrome book will work for an offline wallet? Their only $200. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 19, 2013, 10:52:22 PM
I have 4G of Ram. Is their an online version of Armory that will work with 4G? Or should I just wait? 

Works like a charm for me with 4GB.

MY computer goes into hibernation when downloading the Block Chain for the first time. Unless I am using the computer. Then has to start over each time. Computer is so slow when running it.

Adjust it in the power settings in your control panel.

That seems to have worked. I was going to try that but I didn't know where it was on windows 7. Thanks.

I wonder if a Chrome book will work for an offline wallet? Their only $200. 


We will eventually have something that works on the Android platform.  Until then, it's not going to work.  But it is a natural fit:  I was able to get the Craig 10" Chromebook, CLP281 (http://www.amazon.com/Craig-Wireless-Netbook-Android-2-2/dp/B006P0TX16) for $40!  I haven't seen a deal that good since then, but it looks like you can still get one for $80-$100.  That might end up being cheaper than a HW wallet too (Trezor, BitSafe).  More flexibility, but not quite as convenient.

Btw, I'm not currently using it:  I impulse purchased it assuming I could wipe it and put linux on it, but it turned out to be a royal PITA to do that.  Instead, I'll just have to use its presence in my house as motivation to work on the Android app :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: justmyname on October 19, 2013, 11:59:11 PM
I have 4G of Ram. Is their an online version of Armory that will work with 4G? Or should I just wait?  

Works like a charm for me with 4GB.

MY computer goes into hibernation when downloading the Block Chain for the first time. Unless I am using the computer. Then has to start over each time. Computer is so slow when running it.

Adjust it in the power settings in your control panel.

That seems to have worked. I was going to try that but I didn't know where it was on windows 7. Thanks.

I wonder if a Chrome book will work for an offline wallet? Their only $200.  


We will eventually have something that works on the Android platform.  Until then, it's not going to work.  But it is a natural fit:  I was able to get the Craig 10" Chromebook, CLP281 (http://www.amazon.com/Craig-Wireless-Netbook-Android-2-2/dp/B006P0TX16) for $40!  I haven't seen a deal that good since then, but it looks like you can still get one for $80-$100.  That might end up being cheaper than a HW wallet too (Trezor, BitSafe).  More flexibility, but not quite as convenient.

Btw, I'm not currently using it:  I impulse purchased it assuming I could wipe it and put linux on it, but it turned out to be a royal PITA to do that.  Instead, I'll just have to use its presence in my house as motivation to work on the Android app :)


This looks pretty close. It has windows 7 but it might not be 64 bit

http://www.ebay.com/itm/10-1-inch-Windows-7-Notebook-1-5GHz-LCD-4GB-ROM-Camera-WiFi-Pink-White-black-/331035876688?pt=Laptops_Nov05&var=&hash=item4d13469d50


I could probably just put an operating system on a thumb drive like others are doing instead. If it goes bad it won't matter. just reload onto another thumb drive  and use back ups.  


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: DobZombie on October 20, 2013, 01:02:15 PM
Version 0.89.99.5 has been running for 2 days now without crashing.

Gentleman, congratulations!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 22, 2013, 05:54:55 PM
Hey guys, sorry for the lack of updates recently.  I am still trying to get my brain back on track now that my in-laws have left :)  So I haven't had a chance to fix any of the startup bugs, but goatpig did make me a nice script for fixing the build issues.  It has been tested on a couple versions of Linux and seems to work great.  

Basically, it's a script that is run as part of the makefile, which attempts to locate the correct libpython dependencies and writes the correct values to a pypaths.txt file.  That file is then included in the Makefile.  I mention those details, because if it doesn't work, you'll probably have to manually set the paths in pypaths.txt, and then comment out the line in the Makefile (near the top) that executes the "whereispy.sh" script.  But hopefully no one will have to do that :)

If you are a linux user, especially one that had compile issues with 0.89.99.5, please try it again.  Checkout a fresh copy and try building.   The last build issue to be resolved on Linux is a redefinition error in log.h, where two functions appear to be the same when compiled on 32-bit systems.  I just have to find the right preprocessor for it and that should be resolved, too.  

So if you are on 64-bit Linux, the new Makefile should work, on all versions of Ubuntu, and I think goatpig tested Fedora, too.  If you are on 32-bit linux, you might have to comment out three "redefined" functions in log.h, but then it should compile fine.  


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 22, 2013, 07:36:16 PM
Oh this is fun (for you C++ Linux devs)!  I didn't know this existed:

Code:
touch foo.c ; g++ -dM -E foo.c; rm foo.c;

That prints a full list of all pre-processor symbols defined by default in your g++ compiler.  I noticed a bunch of things I didn't know were normally compiler defined.  Just some samples from my system (Linux Mint 15, 64-bit):

Code:
#define __BYTE_ORDER__ __ORDER_LITTLE_ENDIAN__
#define __INT_LEAST32_TYPE__ int
#define __INT32_TYPE__ int
#define __UINT64_TYPE__ long unsigned int
#define __SIZE_TYPE__ long unsigned int
#define __DBL_EPSILON__ double(2.22044604925031308085e-16L)
#define __DBL_MIN_EXP__ (-1021)
#define __FLT_MIN__ 1.17549435082228750797e-38F
#define __VERSION__ "4.7.3"
#define __SIZEOF_SIZE_T__ 8
#define __SIZEOF_INT__ 4
#define __SIZEOF_POINTER__ 8
#define __SIZE_TYPE__ long unsigned int
#define __x86_64__ 1
#define __LP64__ 1
#define __FLT_HAS_INFINITY__ 1



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: pvz on October 22, 2013, 08:29:37 PM
On my Ubuntu 13.04 i368 running Armory for the first time this error hits every 10 - 15 blocks:

Quote
-INFO  - 1382470521: (BlockUtils.cpp:3693) Parsing blockchain file: /home/xxx/.bitcoin/blocks/blk00033.dat
-INFO  - 1382470522: (BlockUtils.cpp:3787) /home/xxx/.bitcoin/blocks/blk00033.dat is 134,217,728 bytes
Unhandled Error
Traceback (most recent call last):
  File "ArmoryQt.py", line 4981, in <module>
    os._exit(QAPP.exec_())
  File "/home/xxx/Downloads/armory/BitcoinArmory/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 805, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "ArmoryQt.py", line 4482, in Heartbeat
    sdmState = TheSDM.getSDMState()
  File "/home/xxx/Downloads/armory/BitcoinArmory/armoryengine.py", line 11181, in getSDMState
    state = self.getSDMStateLogic()
  File "/home/xxx/Downloads/armory/BitcoinArmory/armoryengine.py", line 11234, in getSDMStateLogic
    elif not self.bitcoindIsResponsive():
  File "/home/xxx/Downloads/armory/BitcoinArmory/armoryengine.py", line 11169, in bitcoindIsResponsive
    return satoshiIsAvailable(self.bitconf['host'], self.bitconf['rpcport'])
  File "/home/xxx/Downloads/armory/BitcoinArmory/armoryengine.py", line 10703, in satoshiIsAvailable
    s = socket.socket()
  File "/usr/lib/python2.7/socket.py", line 187, in __init__
    _sock = _realsocket(family, type, proto)
socket.error: [Errno 24] Te veel open bestanden (translation: to many open files)
-INFO  - 1382470673: (BlockUtils.cpp:3693) Parsing blockchain file: /home/xxx/.bitcoin/blocks/blk00034.dat
-INFO  - 1382470673: (BlockUtils.cpp:3787) /home/xxx/.bitcoin/blocks/blk00034.dat is 134,217,728 bytes
Armory continues to run without any dump or GUI error (in the case above until block 83 because of error below) and after restart started from block 33.

The second error:
Quote
-INFO  - 1382468790: (BlockUtils.cpp:3693) Parsing blockchain file: /home/xxx/.bitcoin/blocks/blk00087.dat
-INFO  - 1382468790: (BlockUtils.cpp:3787) /home/xxx/.bitcoin/blocks/blk00087.dat is 134,089,409 bytes
-INFO  - 1382468834: (BlockUtils.cpp:3693) Parsing blockchain file: /home/xxx/.bitcoin/blocks/blk00088.dat
-INFO  - 1382468834: (BlockUtils.cpp:3787) /home/xxx/.bitcoin/blocks/blk00088.dat is 33,554,432 bytes
-INFO  - 1382468842: (BlockUtils.cpp:3707) Processed 77978 raw blocks DB (3180 seconds)
-INFO  - 1382468844: (BlockUtils.cpp:3736) Starting scan from block height: 0
-ERROR - 1382468844: (StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!
-ERROR - 1382468844: (BlockUtils.cpp:757) Passed uninitialized STX to regAddrScan
-ERROR - 1382468846: (StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!
-ERROR - 1382468846: (StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!
Segmentatiefout (geheugendump gemaakt [translation: memmorydump created] )
Please let me know if I can do some more tests.
Armory keep up the good work!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 22, 2013, 08:33:27 PM
This looks eerily similar to teh guy that just posted here:

https://bitcointalk.org/index.php?topic=316312.0

I wonder if the recent update did something... because so far I haven't ever seen that error until I committed the tiny update a couple hours ago... at least it should be easy to track down what happened...

Can you please try --rebuild.  It will take a while to rebuild the database, but it sounds like your DB is corrupted.  There's some transactions in the DB that were only partially written.  That's bad.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: pvz on October 22, 2013, 08:42:54 PM
Can you please try --rebuild.  
I'll do that. Should it be default for the first time or a database check before start?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 22, 2013, 08:49:10 PM
Can you please try --rebuild. 
I'll do that. Should it be default for the first time or a database check before start?

It is.  The default behavior is to rebuild if the DB doesn't exist.  Just like I mentioned in that other thread, it looks like you might've interrupted the DB build process in the middle and then it restarted (hence only 77k blocks processed, not 260k).  It's worked on my system before but it may not be reliable yet (to interrupt and then restart the build).



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: wheeler on October 22, 2013, 09:26:48 PM
This looks eerily similar to teh guy that just posted here:

https://bitcointalk.org/index.php?topic=316312.0


Just to update on progress from that thread...

The --rebuild progressed for me until the 18th block file, then raised the same socket error just reported.  Armory GUI was still responsive, but stopped processing further blocks.

Not had chance to look in detail at the satoshiIsAvailable() method, but perhaps socket creation should be within the try block?  Might hack that myself and give it a go.







Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 22, 2013, 09:32:48 PM
This looks eerily similar to teh guy that just posted here:

https://bitcointalk.org/index.php?topic=316312.0


Just to update on progress from that thread...

The --rebuild progressed for me until the 18th block file, then raised the same socket error just reported.  Armory GUI was still responsive, but stopped processing further blocks.

Not had chance to look in detail at the satoshiIsAvailable() method, but perhaps socket creation should be within the try block?  Might hack that myself and give it a go.

Are you running a 32-bit OS?  I just committed the first version that should build on 32-bit *nix, but haven't had much chance to test online mode (only tested offline mode).  pvz appears to be in 32-bit as well, and I wonder if that's related...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: pvz on October 22, 2013, 09:34:42 PM
--rebuild does not work.
Deleted .armory directory, started armory again (latest testing branch from a few minutes ago) with this result:

Quote
laptop:~/Downloads/armory/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.89.99.6
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   OS Variant            : ('Ubuntu', '13.04', 'raring')
   User home-directory   : /home/xxx
   Satoshi BTC directory : /home/xxx/.bitcoin/
   Armory home dir       : /home/xxx/.armory/
   LevelDB directory     : /home/xxx/.armory/databases
   Armory settings file  : /home/xxx/.armory/ArmorySettings.txt
   Armory log file       : /home/xxx/.armory/armorylog.txt
Log file doesn't exist [yet]
(WARNING) armoryengine.py:11197 - Overriding not-available message. This should happen 0-5 times
-INFO  - 1382477339: (BlockUtils.cpp:1582) Set home directory:
-INFO  - 1382477339: (BlockUtils.cpp:1604) Set blkfile dir: /home/xxx/.bitcoin/blocks
-INFO  - 1382477339: (BlockUtils.cpp:1614) Set leveldb dir: /home/xxx/.armory/databases
-INFO  - 1382477339: (BlockUtils.cpp:1570) SetBtcNetworkParams
-INFO  - 1382477339: (BlockUtils.cpp:3542) Executing: doInitialSyncOnLoad
-INFO  - 1382477339: (BlockUtils.cpp:3582) Number of registered addr: 0
-INFO  - 1382477340: (BlockUtils.cpp:1709) Current Top block in HEADERS DB:  0
-INFO  - 1382477340: (BlockUtils.cpp:1710) Current Top block in BLKDATA DB:  0
-INFO  - 1382477340: (BlockUtils.cpp:1711) Current Applied blocks up to hgt: 0
-INFO  - 1382477340: (BlockUtils.cpp:3606) Clearing databases for clean build
-WARN  - 1382477340: (BlockUtils.cpp:3507) Destroying databases;  will need to be rebuilt
pthread lock: Ongeldig argument
Afgebroken (geheugendump gemaakt)
Question: how can I make a fresh Armory restart?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: wheeler on October 22, 2013, 09:38:39 PM
Are you running a 32-bit OS?

Yes:
Ubuntu 12.04 (precise) 32-bit
AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ × 2
2GB RAM

Will look further tomorrow (on London time here  ;) )

Thanks for your help so far!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 22, 2013, 09:39:05 PM
--rebuild does not work.
Deleted .armory directory, started armory again (latest testing branch from a few minutes ago) with this result:

Quote
laptop:~/Downloads/armory/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.89.99.6
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   OS Variant            : ('Ubuntu', '13.04', 'raring')
   User home-directory   : /home/xxx
   Satoshi BTC directory : /home/xxx/.bitcoin/
   Armory home dir       : /home/xxx/.armory/
   LevelDB directory     : /home/xxx/.armory/databases
   Armory settings file  : /home/xxx/.armory/ArmorySettings.txt
   Armory log file       : /home/xxx/.armory/armorylog.txt
Log file doesn't exist [yet]
(WARNING) armoryengine.py:11197 - Overriding not-available message. This should happen 0-5 times
-INFO  - 1382477339: (BlockUtils.cpp:1582) Set home directory:
-INFO  - 1382477339: (BlockUtils.cpp:1604) Set blkfile dir: /home/xxx/.bitcoin/blocks
-INFO  - 1382477339: (BlockUtils.cpp:1614) Set leveldb dir: /home/xxx/.armory/databases
-INFO  - 1382477339: (BlockUtils.cpp:1570) SetBtcNetworkParams
-INFO  - 1382477339: (BlockUtils.cpp:3542) Executing: doInitialSyncOnLoad
-INFO  - 1382477339: (BlockUtils.cpp:3582) Number of registered addr: 0
-INFO  - 1382477340: (BlockUtils.cpp:1709) Current Top block in HEADERS DB:  0
-INFO  - 1382477340: (BlockUtils.cpp:1710) Current Top block in BLKDATA DB:  0
-INFO  - 1382477340: (BlockUtils.cpp:1711) Current Applied blocks up to hgt: 0
-INFO  - 1382477340: (BlockUtils.cpp:3606) Clearing databases for clean build
-WARN  - 1382477340: (BlockUtils.cpp:3507) Destroying databases;  will need to be rebuilt
pthread lock: Ongeldig argument
Afgebroken (geheugendump gemaakt)
Question: how can I make a fresh Armory restart?

Ack, this is really not going well on Ubuntu 32-bit (that's what you're in, right?).  You can remove the /home/xxx/.armory/databases directory to retry from scratch.  Though, "--rebuild" should do exactly that.

I noticed the line "pthread lock:  Ongeldig argument", I assume that means "Invalid Argument"?  If so, that may be the source of the problem, perhaps the way leveldb is being compiled here is not playing nicely with the 32-bit libraries.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 23, 2013, 02:00:38 AM
@pvz and @wheeler:

I just ran into the segfault issue when using --rebuild.  It turns out that i screwed up some pointer cleanup, and that was causing the segfaults.  Luckily, the last update was so tiny that it was obvious what did it!  I just fixed it and committed it.  Please do a "git pull origin testing" and then try the --rebuild again.

It might also have been responsible for the other issues you observed, though I won't be sure until you try it. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: wheeler on October 23, 2013, 05:48:24 AM
@pvz and @wheeler:

I just ran into the segfault issue when using --rebuild.  It turns out that i screwed up some pointer cleanup, and that was causing the segfaults.  Luckily, the last update was so tiny that it was obvious what did it!  I just fixed it and committed it.  Please do a "git pull origin testing" and then try the --rebuild again.

It might also have been responsible for the other issues you observed, though I won't be sure until you try it. 


Thanks, will give this a try tonight.  FWIW, the last run (not your latest code) failed due to exhausting file handles.  lsof lists lots of ~/.armory/databases/leveldb_blkdata/*.sst files open.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: pvz on October 23, 2013, 05:56:46 AM
A first quick test seems to work. Because it is not my computer I can't do more tests... to bad...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cp1 on October 23, 2013, 04:25:02 PM

Thanks, will give this a try tonight.  FWIW, the last run (not your latest code) failed due to exhausting file handles.  lsof lists lots of ~/.armory/databases/leveldb_blkdata/*.sst files open.



If the problem isn't the code, you can always increase the max # of files open, that's a pretty common problem.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 23, 2013, 07:57:41 PM
Okay, I just ran into a problem on windows that wheeler originally observed.   Luckily, this one is isolated, so I should be able to catch it easily.  It causes the "cannot get tx copy" message.  I thought it was a DB-corruption issue, but instead it looks like it has to do with orphan blocks in the block files under certain conditions. 

For me, it keeps triggering at the same block, so I should have no problem isolating it.

One day, this stuff will work...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: wheeler on October 23, 2013, 09:30:33 PM
Quick update on my attempts:  Got the latest testing branch 0.89.99.6, and also boosted the ulimit on files to 4096 (from 1024).  This time I got much further in the database rebuild (to the 48th block file), but it eventually fell over with a "Bus Error" (OS error, not a Python Exception).  Trying to restart now without the --rebuild option and it seems to have continued from where it left off, so hopefully after a couple of attempts I'll get fully synced!

@etotheipi: Let me know if you want me to e-mail you any cores or logs?

Thanks.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: cypherdoc on October 24, 2013, 04:26:10 PM
is 0.89.99.5 still the latest Windows version?

i need to try and reinstall since it now refuses to open after about 1 mo of successful usage  :(


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 27, 2013, 08:05:56 PM
OK so I am having some difficulty again getting the latest testing branch (0.89.99.6 I believe) to run on Ubuntu 13.10 VM...

I can't actually get past the splash "Armory" splash screen, and I don't think I am throwing any errors, so a bit stuck here... http://imgur.com/CAQNyaD (http://imgur.com/CAQNyaD)

Here is my logfile http://pastebin.com/hPVigcDn (http://pastebin.com/hPVigcDn) which I don't see anything wrong with. If anyone could offer me some info on how to troubleshoot this I would appreciate it.

Thanks.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 27, 2013, 08:48:21 PM
OK so I am having some difficulty again getting the latest testing branch (0.89.99.6 I believe) to run on Ubuntu 13.10 VM...

I can't actually get past the splash "Armory" splash screen, and I don't think I am throwing any errors, so a bit stuck here... http://imgur.com/CAQNyaD

Here is my logfile http://pastebin.com/hPVigcDn which I don't see anything wrong with. If anyone could offer me some info on how to troubleshoot this I would appreciate it.

Thanks.

Run it with --debug to get more output


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: etotheipi on October 28, 2013, 12:48:48 AM
OK so I am having some difficulty again getting the latest testing branch (0.89.99.6 I believe) to run on Ubuntu 13.10 VM...

I can't actually get past the splash "Armory" splash screen, and I don't think I am throwing any errors, so a bit stuck here... http://imgur.com/CAQNyaD

Here is my logfile http://pastebin.com/hPVigcDn which I don't see anything wrong with. If anyone could offer me some info on how to troubleshoot this I would appreciate it.

Thanks.

Oh, I didn't even look at the log file before responding.  It looks like maybe there's some kind of interactive message that is blocking on the gconftool command (which is used for setting up Armory as your default URI handler).  I wonder if that's it.

Can you open a terminal and run the following command and tell me what it spits out?

Code:
gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 28, 2013, 07:11:07 AM
that command returns:

Code:
python /usr/share/armory/ArmoryQt.py %s

here is a pastebin of my --debug log (once it made it past splash screen and I set up a wallet, but it could not leave offline mode and twice it did not make it past splash screen)

python /usr/share/armory/ArmoryQt.py %s

Edit: Damnit, that is of course not a pastebin link, this is what happens when VM and native OS use different copy/paste shortcuts and you use both OSs at the same time early in the morning without checking your work quickly.
Will be able to provide tonight when I am home from work


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: e4xit on October 28, 2013, 07:18:01 PM
Problem is persisting...

Here is my debug output. Note, this is the result of a few (about 3) startup attempts...

http://pastebin.com/AMkcVKJG


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 05:18:15 AM


UPDATE:  0.89.99.8-testing

Windows:  download from my dropbox folder (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.8-beta_win32.exe)
Linux/OSX:  Checkout the "testing" branch

What's different compared to 0.89.99.5:
--Fixed a major bug which might be responsible for the orphan chain issues.  I'm not sure, because I haven't been able to reliably reproduce it.  But the bug I found could very well cause such issues.  If you had the "Marking Orphan Chain" issues, please try the new version!
--Windows appears to run much faster.  Now it only takes about 50% longer to do its operations compared to the Linux runtimes
--Closing the app in offline mode no longer seg faults
--Issues with uninitialized zero-conf transactions getting into the mempool have been fixed.  This does not fix the zero-conf-disappearing bug (I don't think).  That is still on my list to track down and fix. 
--Zero-conf-disappearing bug:  it is still a problem, but I have put in a fix that should cause it to correct itself on a restart.  If you can reliably reproduce that bug, please tell me if restarting fixes it. 

What's the same:
--Zero-conf-disappearing bug is still there. 
--Restarting Armory in the middle of the original DB build still resets the progress meter.  To be clear:  progress picks up from where it left off, it's just that the meter tells you progress between where it started and the end, instead of the overall progress, so it looks like it restarted.
--I had run into an unrecoverable "Cannot copy partial StoredTx" bug (or something like that).  Unfortunately, I destroyed the DB I had that exposed that bug, so I'll have to go hunting it down again.  Luckily, I got a lot of information about it before I did, so I might be able to hunt it down without catching it in the debugger.

Thanks again to goatpig for all his help in improving the speed on windows, getting the unit tests working on Windows, and getting a full MSVS debugging environment working when running the full app (I used to only be able to debug the pure-C++ unit tests projects, now I can debug a full instance of ArmoryQt).  And about 300 other little things. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 05:22:25 AM
I forgot to mention that if you were previously having problems, you might have to start it with " --rebuild" to rebuild the database before the bug fixes become apparent.  Strong possibility you don't have to, but doing a " --rebuild" will also give you a chance to test the new speed in Windows.  Please let me know if it seems faster...

EDIT:  Alternatively, if you don't know what I mean when I say "start with --rebuild", you can just delete the databases directory in the Armory home dir.  It will rebuild the next time you start it.  You can find the databases dir at:

Windows:  C:\Users\<user>\AppData\Roaming\Armory\databases
Linux:  /home/<user>/.armory/databases


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Dabs on October 30, 2013, 06:02:42 AM
Still doesn't work at all or even run on my Windows XP SP3 (32 bit) machine. Same errors.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 02:09:17 PM
Still doesn't work at all or even run on my Windows XP SP3 (32 bit) machine. Same errors.

Okay, I think lack of working on XP is expected.  I don't have the right compiler installed for it.  Maybe goatpig can repeat (for me, but also everyone who might want to compile it) what is needed to build with Windows XP support.  I sounds like it's not hard, I just have to have the right packages installed on my windows machine.   I think.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 30, 2013, 03:08:00 PM
Still doesn't work at all or even run on my Windows XP SP3 (32 bit) machine. Same errors.

Okay, I think lack of working on XP is expected.  I don't have the right compiler installed for it.  Maybe goatpig can repeat (for me, but also everyone who might want to compile it) what is needed to build with Windows XP support.  I sounds like it's not hard, I just have to have the right packages installed on my windows machine.   I think.

On a Win Vista+ machine, download and install Microsoft Visual Studio 2012 express and Microsoft Visual C++ 2010 express. Grab the Armory source from Github, open BitcoinArmory.sln from the cppForSwig folder with MSVS2012.

In Build > Configuration Manager, pick Release as the active configuration and Win32 as the active platform.

Lastly, right click the BitcoinArmory_SwigDLL project in the Solution Explorer. Pick Properties at the very bottom. In Configuration Properties > General, change the line Platform Toolset from "Visual Studio 2012 (v110)" to "Visual Studio 2012 - Windows XP (v110_xp)"

Edit

A point I forgot to mention: You need to build every dependency with the winxp toolset, so do this step on every project =P

/Edit

Apply and close the properties window. Press F7 and let it build away. Note: You'll need Python installed in order to build. If you don't want to change path linking in the MSVS project, you'll have to install Python 2.7 in C:\Python27. Obviously you'll need all the Python related packages to run, afterwards.

You'll also need pthread_win32: ftp://sourceware.org/pub/pthreads-win32/pthreads-w32-2-9-1-release.zip
Expand this archive in the cppForSwig folder. Don't forget to copy the dll into the same folder as ArmoryQt.py to run.

I'll update the projects to support WinXP and pull request so that Alan can't have an excuse anymore =P


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 03:11:04 PM
Still doesn't work at all or even run on my Windows XP SP3 (32 bit) machine. Same errors.

Hey Dabs, try this out:

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.8-beta_win32_xp.exe

EDIT:  As for building on Windows, CircusPeanut prepared some instructions.  We have a few Windows guinea pigs testing it out for us right now, so we can iron out the instructions.  We'll post them on the website when we're done.  I'll make sure he adds the steps for WindowsXP to it (it's basically :  download and install VS2012 update 3, then select the vs110_xp toolset).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 03:16:31 PM
Whoops, I just realized that I didn't build all the projects with the new compiler settings. 

I'm about 10 min late for something, so I'll have to do it right in later this evening.  Sorry about that!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 06:16:38 PM
Just updated the link above with all sub-projects built with the vs110_xp toolset.  I have no way to test it currently, so I'm looking at Dabs :)

Here's the link again:

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.8-beta_win32_xp.exe


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: superbit on October 30, 2013, 06:42:38 PM
I just checked my version and it is 0.88.1, what is the proper procedure to update?  I do have a paper backup created already but it's locked away and ideally I don't need it to update.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 06:44:38 PM
I just checked my version and it is 0.88.1, what is the proper procedure to update?  I do have a paper backup created already but it's locked away and ideally I don't need it to update.

Just uninstall it from the Control Panel and install the new package.  That's it.  All your wallets and settings will be untouched through an uninstall-reinstall cycle.  And since the beginning of time, Armory has not [yet] modified the wallet design, so all your backups are still good, etc, even if you later go back.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: e4xit on October 30, 2013, 07:27:24 PM
etotheipi,

I am still hanging on
Code:
2013-10-30 18:59 (INFO) -- armoryengine.py:602 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command

I have to manually close terminal window or otherwise kill the process to end being frozen on the Armory splash screen.
pastebin of log:
http://pastebin.com/L4jhd3RD (http://pastebin.com/L4jhd3RD)

The second time starting up to program (nothing changed) I can reach the main "Wallet management" window, and if the first time starting up am prompted to create a new wallet etc., which works fine.

So now I have a wallet, but Armory will not go into online mode, as it says "Bitcoin QT is still running. Armory cannot start until it is closed, would you like Armory to close it for you?"

If I choose 'yes' here, Armory will freeze indefinately.

If I choose no, and manually kill bitcoind using 'top' command in a new terminal window, then wait a bit and then hit "Check again" in Armory, the program will darken as in "it's frozen", and will then have to be killed via the terminal again.
pastebin of log:
http://pastebin.com/LZuUeqMJ (http://pastebin.com/LZuUeqMJ)

I'm really not sure entirely where I am falling down with this...?

My system specs are:
Ubuntu 13.10 running in VMware Fusion 6.01 (completely fresh install of both, over a completely fresh install of Mavericks GM2)
Latest (testing) build of Armory (version announced 30.10.2013)

Any help, pointers or avenues of exploration to fix these issues much appreciated.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: cp1 on October 30, 2013, 08:54:41 PM
Is there an option to disable the registration for url?  Maybe that could be a temporary workaround for you.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 09:32:13 PM
Is there an option to disable the registration for url?  Maybe that could be a temporary workaround for you.

I'm not convinced the URL registration is the issue.  It's probably what happens right afterwards.

I see the "bitcoind is no more" message which I don't even remember putting in there, and haven't seen that in log files recently (or ever).  I'll do some digging...

Have you been using (or able to use) Bitcoin-Qt or bitcoind by itself?  This might actually be a Bitcoin-Qt problem.  If you close Armory and run Bitcoin-Qt by itself, does it load and run fine?  Any error messages?   


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: e4xit on October 30, 2013, 10:30:07 PM
I think the "bitcoind is no more" is when I manually close the Armory terminal window.

Now, without changing anything  except deleting  the folder ~ /.armory/ and then re-running 'python ArmoryQt.py --debug' I seem to be reaching the mail "wallet management" window everytime, where it is asking me to creat a new wallet.

Still stuck as it is telling me to close Bitcoin-Qt (except I can see that it has started bitcoind itself in the terminal and there is no Bitcoin-Qt running).

pastebin log of the process with where it is hanging now (without me manually killing bitcoind)
http://pastebin.com/jYeE513k (http://pastebin.com/jYeE513k)

This was happening also when I did not even have Bitcoin-Qt installed (only bitcoind version 80500 ). I have since installed Bitcoin-Qt v0.8.5.0-gef14a26-beta to see if this would in some way mitigate the error but had no luck.

Again, thanks for helping, but not really sure how to progress from here... The whole install was completely fresh on a fresh VM (which exists solely for the purpose of running Armory) so don't think uninstalling/re-installing would help much...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 30, 2013, 10:42:19 PM
Stupid question: are you using a manually edited bitcoin.conf?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: e4xit on October 30, 2013, 11:24:51 PM
Stupid question: are you using a manually edited bitcoin.conf?

Goatpig, you hero. It was indeed a faulty conf file. Top detective work and shame on me!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 30, 2013, 11:30:25 PM
Stupid question: are you using a manually edited bitcoin.conf?

Goatpig, you hero. It was indeed a faulty conf file. Top detective work and shame on me!

Awesome!  I will add that to the troubleshooting page.  At least a couple problems people have had, turned out to be bitcoin.conf issues, but not enough that I remember it as a common troubleshooting tip.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 30, 2013, 11:50:44 PM
Stupid question: are you using a manually edited bitcoin.conf?

Goatpig, you hero. It was indeed a faulty conf file. Top detective work and shame on me!

I'm actually relieved it was the .conf, I was running out of places to look at o.o


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Dabs on October 31, 2013, 12:05:17 AM
Quote
Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

Still not working for me. Sorry.

Just to be clear, my machines (I have 2 laptops) are both on Win XP SP3 updated with ms update to this month, with almost nothing else installed. (2 gig ram only.)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 31, 2013, 03:12:09 AM
Quote
Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

Still not working for me. Sorry.

Just to be clear, my machines (I have 2 laptops) are both on Win XP SP3 updated with ms update to this month, with almost nothing else installed. (2 gig ram only.)

Unfortunately, I think the issue is that there are system DLLs being passed along with Armory that are not compatible with Windows XP, even though all the Armory code itself was compiled with the XP toolset.   Unless goatpig has a recommendation for this, I'm not sure I see a way around it.   I would have to compile directly on Windows XP, but you can't even get MSVS 2012 installed on XP.

Ugh.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Dabs on October 31, 2013, 03:36:50 AM
Quote
Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

Still not working for me. Sorry.

Just to be clear, my machines (I have 2 laptops) are both on Win XP SP3 updated with ms update to this month, with almost nothing else installed. (2 gig ram only.)

Unfortunately, I think the issue is that there are system DLLs being passed along with Armory that are not compatible with Windows XP, even though all the Armory code itself was compiled with the XP toolset.   Unless goatpig has a recommendation for this, I'm not sure I see a way around it.   I would have to compile directly on Windows XP, but you can't even get MSVS 2012 installed on XP.

Ugh.

Thanks for trying. I will eventually upgrade OS... I'm just one of those who like to stick it out for as long as I can. (The end of life support for XP is April 2014.)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 31, 2013, 03:50:03 AM

Unfortunately, I think the issue is that there are system DLLs being passed along with Armory that are not compatible with Windows XP, even though all the Armory code itself was compiled with the XP toolset.   Unless goatpig has a recommendation for this, I'm not sure I see a way around it.   I would have to compile directly on Windows XP, but you can't even get MSVS 2012 installed on XP.

Ugh.

I don't have anything on this. I have compiled simple code and successfully had it work on WinXP with this toolset before. I can't give you more info without looking at the behavior myself. I'll set up a WinXP guest at some point and give it a look.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 31, 2013, 03:52:58 AM

Unfortunately, I think the issue is that there are system DLLs being passed along with Armory that are not compatible with Windows XP, even though all the Armory code itself was compiled with the XP toolset.   Unless goatpig has a recommendation for this, I'm not sure I see a way around it.   I would have to compile directly on Windows XP, but you can't even get MSVS 2012 installed on XP.

Ugh.

I don't have anything on this. I have compiled simple code and successfully had it work on WinXP with this toolset before. I can't give you more info without looking at the behavior myself. I'll set up a WinXP guest at some point and give it a look.

It might be possible to merge the .dlls from the old 0.88.1 release which was compatible with WinXP, with the new version with all the Armory code compiled using the XP toolset.  But that could be a mess and might not end up working.  I'm afraid that our move to MSVS 2012 may have shut out Windows XP users. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 31, 2013, 03:57:48 AM
Give me a couple days and I'll investigate to code in a WinXP environment. Just don't pull the plug yet!

Last but not least, I can port the atomic types and operations to WinAPI calls. That would let you compile in MSVS 2008/10 and would entirely go around the whole issue. This is the only part of the code that isn't backwards compatible with earlier compilers.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 31, 2013, 04:01:30 AM
Give me a couple days and I'll investigate to code in a WinXP environment. Just don't pull the plug yet!

Last but not least, I can port the atomic types and operations to WinAPI calls. That would let you compile in MSVS 2008/10 and would entirely go around the whole issue. This is the only part of the code that isn't backwards compatible with earlier compilers.

No offense to Dabs (sorry Dabs!), but I'm not convinced there's a reasonable cost-to-benefit ratio for this past a couple hours of work.  For every day that we spend on it, the number of potential XP users in the world shrinks by 2%...


EDIT:  To be clear, please take a shot at doing it.  I just don't want to spend a lot of resources working on it, because there's other priorities.   Well, assuming your priorities are aligned with mine :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 31, 2013, 04:19:48 AM
assuming your priorities are aligned with mine :)

Try to take over the world? I think there's a quick fix to turn on LevelDB internal atomic ports


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 31, 2013, 04:49:58 AM
I don't know if Alan got my email as gmail decided to stop working right when I figured out the trick. I'll update the projects and push it to the repo tomorrow. That one should get Armory working on WinXP.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Dabs on October 31, 2013, 04:57:18 AM
No offense to Dabs (sorry Dabs!)
None taken.

But you have to understand, a lot of corporate environments tend to stick to really really old ancient operating systems and other software. I'm not exactly there, since this is personal usage, but I understand enough to know that I can do almost anything on an older OS like XP while taking up less resources.

I do think, a bitcoin wallet should be able to work on something like XP. (well, QT still works on 32 bit XP, so I'm not complaining.)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 31, 2013, 03:23:41 PM
Has anyone else had issues with Armory in the new Mavericks update for OS X?
Is there any update for it?
I'm currently running the latest version of armory and mine just does not run at all...I've got around 20 or so bitcoins stuck in there and I really do hope I haven't lost them all.
I did research seeing if OSX 10.9 wasn't compatible Armory though didn't find anything, until it happened to me.
anyone know what I can do?
I tried editing the info.plist's to change max versions and still didn't work no matter what I did :/

Yeah, so far everything has broken on 10.9.  Picobit gave me a script for building a more-standalone version of Armory on OSX, which should hopefully resolve this problem on most versions of OSX, and hopefully Mavericks, too.  And hopefully we'll get a new guy soon that will be better experienced with OSX in order to battle these OSX problems.

I just caught the "Marking Orphan Chain" bug in the debugger, which I've been hoping to do for days!  If I fix that bug, then I'll be under a lot less stress and can maybe take a shot at this.  Stay tuned and thanks for being patient!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on October 31, 2013, 03:37:06 PM
No offense to Dabs (sorry Dabs!)
None taken.

But you have to understand, a lot of corporate environments tend to stick to really really old ancient operating systems and other software. I'm not exactly there, since this is personal usage, but I understand enough to know that I can do almost anything on an older OS like XP while taking up less resources.

I do think, a bitcoin wallet should be able to work on something like XP. (well, QT still works on 32 bit XP, so I'm not complaining.)

Can you install this: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en

Then try again to run the last win_xp build Alan gave you.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on October 31, 2013, 07:07:54 PM
No offense to Dabs (sorry Dabs!)
None taken.

But you have to understand, a lot of corporate environments tend to stick to really really old ancient operating systems and other software. I'm not exactly there, since this is personal usage, but I understand enough to know that I can do almost anything on an older OS like XP while taking up less resources.

I do think, a bitcoin wallet should be able to work on something like XP. (well, QT still works on 32 bit XP, so I'm not complaining.)

Can you install this: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en

Then try again to run the last win_xp build Alan gave you.

i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: picobit on October 31, 2013, 08:39:54 PM
Yeah, so far everything has broken on 10.9.  Picobit gave me a script for building a more-standalone version of Armory on OSX, which should hopefully resolve this problem on most versions of OSX, and hopefully Mavericks, too.  And hopefully we'll get a new guy soon that will be better experienced with OSX in order to battle these OSX problems.

I just caught the "Marking Orphan Chain" bug in the debugger, which I've been hoping to do for days!  If I fix that bug, then I'll be under a lot less stress and can maybe take a shot at this.  Stay tuned and thanks for being patient!

And I have been very passive recently due to being busy with other things.  I have an issue or two with my build script and the latest changes to Armory, but they are Makefile related and I will have a look at it in the weekend.  I will still be using Mountain Lion for a few weeks, but should then soon be able to test with Maverick too.

There is a vexing issue with OS X: If the database is messed up (and that happens too often), it is hard to call Armory with --rescan.  Passing command line arguments to OS X apps is possible (but not elegant), but the actual app is a script that calls Python, and that script does not pass through command line arguments.  If it did, Armory would refuse to start, since OS X per default sets some strange command line arguments (windows position, perhaps), and Armory cannot parse them.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on October 31, 2013, 08:52:14 PM
Yeah, so far everything has broken on 10.9.  Picobit gave me a script for building a more-standalone version of Armory on OSX, which should hopefully resolve this problem on most versions of OSX, and hopefully Mavericks, too.  And hopefully we'll get a new guy soon that will be better experienced with OSX in order to battle these OSX problems.

I just caught the "Marking Orphan Chain" bug in the debugger, which I've been hoping to do for days!  If I fix that bug, then I'll be under a lot less stress and can maybe take a shot at this.  Stay tuned and thanks for being patient!

And I have been very passive recently due to being busy with other things.  I have an issue or two with my build script and the latest changes to Armory, but they are Makefile related and I will have a look at it in the weekend.  I will still be using Mountain Lion for a few weeks, but should then soon be able to test with Maverick too.

There is a vexing issue with OS X: If the database is messed up (and that happens too often), it is hard to call Armory with --rescan.  Passing command line arguments to OS X apps is possible (but not elegant), but the actual app is a script that calls Python, and that script does not pass through command line arguments.  If it did, Armory would refuse to start, since OS X per default sets some strange command line arguments (windows position, perhaps), and Armory cannot parse them.

At one point I added rescan and rebuild buttons, but they didn't behave properly.  I decided that they needed to occur before the app loaded.  With some luck, these upcoming bug fixes will require that a lot less frequently.  Or I'll find another mechanism to do it.

The makefile was updated by goatpig to do a more-intelligent search for the python dependencies.  It's very possible that you may need to just branch that whole section if compiling on OSX/Darwin.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Mooshire on November 01, 2013, 02:26:09 AM
Coming back to the good clients, what do you reccommend right now for a 64-bit win8 user with 8 GB of RAM?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 01, 2013, 02:42:43 AM
Coming back to the good clients, what do you reccommend right now for a 64-bit win8 user with 8 GB of RAM?

Still 0.88.1 from the website.  Feel free to help test this version, but I'm fairly certain that the crashing bugs are bit too much for most people.  I finally caught the biggest one in the debugger, but it doesn't look like it's going to be easy to fix.  So it may still be a few days...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: e4xit on November 01, 2013, 08:47:42 AM
Stupid question: are you using a manually edited bitcoin.conf?

Goatpig, you hero. It was indeed a faulty conf file. Top detective work and shame on me!

Awesome!  I will add that to the troubleshooting page.  At least a couple problems people have had, turned out to be bitcoin.conf issues, but not enough that I remember it as a common troubleshooting tip.


etotheipi,

If it helps your FAQ/troubleshooting page, my conf file (which didn't work) was the result of just downloading the 'bitcoind' package via the terminal
Code:
sudo apt-get install bitcoind
and then simply running
Code:
bitcoind
which presents you with an error saying that you must create a bitcoin.conf file with
Code:
server = 1
rpcuser = your_username
rpcpassword = your_unique_password
which I duely did...This seemed to be causing the errors (perhaps I wrote the .conf file wrong; it was written by hand but bitcoind seemed to run with no errors on its own from the terminal).

Then in response to goatpig's suggestion that it could be the .conf file causing the non-reported errors, I visited
https://en.bitcoin.it/wiki/Running_Bitcoin#Sample_Bitcoin.conf (https://en.bitcoin.it/wiki/Running_Bitcoin#Sample_Bitcoin.conf)
and copy/pasted the "sample" .conf file, which I then uncommented only 'server', 'rpcuser' and 'rpcpassword' fields and set to '1', 'myusername' and 'mypassword' respectively.

Which got everything working again. Hope this help explain how/where I got stuck and how it was fixed.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: picobit on November 01, 2013, 08:48:24 AM
The makefile was updated by goatpig to do a more-intelligent search for the python dependencies.  It's very possible that you may need to just branch that whole section if compiling on OSX/Darwin.

Yes.  It looks very complicated considering that Python normally knows where its stuff is (e.g. os.path.join(sys.prefix, "include/python2.7") for the include files).  On the other hand, Python can actually get confused and report the wrong place perhaps goatpig's script is more reliable.  When it comes to building an OSX app, it looks like I can quite easily use goatpig's makefile stuff to point to the Python installation inside the app, so that is one less complication.  :)



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on November 01, 2013, 01:25:23 PM
i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?

Have you installed the MSVC9 redist from the link I gave? If you did, can you copy msvcp90.dll and put in your Armory installation folder? It's should be in Program Files/Visual Studio 9.0/VC/Redist/X86


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Portnoy on November 01, 2013, 05:01:30 PM
i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?

Have you installed the MSVC9 redist from the link I gave? If you did, can you copy msvcp90.dll and put in your Armory installation folder? It's should be in Program Files/Visual Studio 9.0/VC/Redist/X86

I am trying to get this running on XP 32bit as well. 

I found msvcp90.dll in another place ( I don't have a Program Files/Visual Studio 9.0/  dir. ).
I put it in the Armory folder and still get the same error message above as els.

Thanks for helping out with this... I think there may be others like him and me who want to use an old XP system for an offline wallet.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on November 01, 2013, 05:09:17 PM
i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?

Have you installed the MSVC9 redist from the link I gave? If you did, can you copy msvcp90.dll and put in your Armory installation folder? It's should be in Program Files/Visual Studio 9.0/VC/Redist/X86

I am trying to get this running on XP 32bit as well.  

I found msvcp90.dll in another place ( I don't have a Program Files/Visual Studio 9.0/  dir. ).
I put it in the Armory folder and still get the same error message above as els.

Thanks for helping out with this... I think there may be others like him and me who want to use an old XP system for an offline wallet.

It needs to be the msvcp90.dll from the package I linked. There are several versions of this DLL distributed by MS and py2exe only links against the one from that package. Regardless, I've concluded this path is too convoluted. I've found a simple way to build the entire project with msvc9/10 toolsets, that still support WinXP. I'll update the msvs projects once I'm back home, push them to my branch and have Alan build and distribute a test version with these. So this'll have to wait till Monday, sorry.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Portnoy on November 01, 2013, 05:40:39 PM
i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?

Have you installed the MSVC9 redist from the link I gave? If you did, can you copy msvcp90.dll and put in your Armory installation folder? It's should be in Program Files/Visual Studio 9.0/VC/Redist/X86

I am trying to get this running on XP 32bit as well.  

I found msvcp90.dll in another place ( I don't have a Program Files/Visual Studio 9.0/  dir. ).
I put it in the Armory folder and still get the same error message above as els.

Thanks for helping out with this... I think there may be others like him and me who want to use an old XP system for an offline wallet.

It needs to be the msvcp90.dll from the package I linked. There are several versions of this DLL distributed by MS and py2exe only links against the one from that package. Regardless, I've concluded this path is too convoluted. I've found a simple way to build the entire project with msvc9/10 toolsets, that still support WinXP. I'll update the msvs projects once I'm back home, push them to my branch and have Alan build and distribute a test version with these. So this'll have to wait till Monday, sorry.

Judging by the time stamp displayed in the filemanager the msvcp90.dll I used was the one I installed just yesterday from that link you provided.

Looking forward to that new update you talk about above... I can wait til Monday. 

( Over the weekend I was going to install a version of linux in virtualbox and install armory in there... so maybe I can use that, for at least a temporary location for an offline wallet. I hope there are no security issues in doing something like that, as long as I don't allow networking. )

Thanks for your efforts.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 01, 2013, 10:44:24 PM
i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?

Have you installed the MSVC9 redist from the link I gave? If you did, can you copy msvcp90.dll and put in your Armory installation folder? It's should be in Program Files/Visual Studio 9.0/VC/Redist/X86

Are you referring to this?  If not, I've missed another link somewhere.

> Can you install this: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en

> Then try again to run the last win_xp build Alan gave you.

Yes, I installed the above.  Can't find an instance of the .dll from it though....


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Portnoy on November 01, 2013, 10:59:18 PM
i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?

Have you installed the MSVC9 redist from the link I gave? If you did, can you copy msvcp90.dll and put in your Armory installation folder? It's should be in Program Files/Visual Studio 9.0/VC/Redist/X86

Are you referring to this?  If not, I've missed another link somewhere.

> Can you install this: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en

> Then try again to run the last win_xp build Alan gave you.

Yes, I installed the above.  Can't find an instance of the .dll from it though....

You'll have to use XP's search feature ( select Start, then Search, then "All files and folders", and then type in the name of the file... )
you will probably find a few different files of that name in different places.

Check the date to make sure you grab the one you just installed.  You might not have much luck getting it to work,
like me, but let us know how you do.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 01, 2013, 11:05:12 PM
i tried this on XP Pro SP3 32-bit (with nothing else special installed), then installed the xp build from earlier in this thread.  still getting the same errors in logfile upon running:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

did i miss another implied step somewhere in this?

Have you installed the MSVC9 redist from the link I gave? If you did, can you copy msvcp90.dll and put in your Armory installation folder? It's should be in Program Files/Visual Studio 9.0/VC/Redist/X86

Are you referring to this?  If not, I've missed another link somewhere.

> Can you install this: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en

> Then try again to run the last win_xp build Alan gave you.

Yes, I installed the above.  Can't find an instance of the .dll from it though....

You'll have to use XP's search feature ( select Start, then Search, then "All files and folders", and then type in the name of the file... )
you will probably find a few different files of that name in different places.

Check the date to make sure you grab the one you just installed.  You might not have much luck getting it to work,
like me, but let us know how you do.



thanks.  tried searching again, per above.  i do find a few, but attributable to other programs and not with current date.  i also am not finding the path Program Files/Visual Studio 9.0/ or anything like it, though i did reinstall the package to be sure there were no errors.  oh well.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Carlton Banks on November 02, 2013, 12:06:29 AM
Give me a couple days and I'll investigate to code in a WinXP environment. Just don't pull the plug yet!

Last but not least, I can port the atomic types and operations to WinAPI calls. That would let you compile in MSVS 2008/10 and would entirely go around the whole issue. This is the only part of the code that isn't backwards compatible with earlier compilers.

No offense to Dabs (sorry Dabs!), but I'm not convinced there's a reasonable cost-to-benefit ratio for this past a couple hours of work.  For every day that we spend on it, the number of potential XP users in the world shrinks by 2%...


EDIT:  To be clear, please take a shot at doing it.  I just don't want to spend a lot of resources working on it, because there's other priorities.   Well, assuming your priorities are aligned with mine :)

That increasingly shrinking proportion of XP users are increasingly going to be comprised of the people with (seemingly) no choice but XP; the poor (as well as those with poor opportunities to get hold of machines capable of running modern OS's, which are mostly still the economically poor). I know, I know, with a bit of work they could install a nice undemanding Linux distro that would be a much better all ways round, but that underestimates how protective the less computer savvy sort of individual would be over their only working PC. The extent to which such a machine, in a known working order, is valued by such a person perhaps cannot be overestimated; they might depend on it for a current system to receive foreign remittances, for instance.

I'd be very amused to hear of Nepalese or Zimbabwean Armory users making successful use of Armory on a 384 Mb 1Ghz XP machine! If they could even thrive with such a setup, then that would really be something. (has anyone ever tested it on Windows 2000?  :P)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on November 02, 2013, 12:12:44 AM
Ok sorry about the folder. I'm in front of a XP machine right now and can't really find the folder. Not my machine though as I'm not home, so I'm not gonna install anything on it. I've given up on the xp toolset and will iron out a msvc9 toolset build as I get back home.

I have personally run msvc9 toolset built code on Win2k. From what I've seen of the Armory source, I think there's a 2/3rd chance it could run on Win2k. I'm 99% positive I can get the current Armory code to run on XP. Just a matter of testing the build first hand.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 02, 2013, 06:08:45 PM
That increasingly shrinking proportion of XP users are increasingly going to be comprised of the people with (seemingly) no choice but XP; the poor (as well as those with poor opportunities to get hold of machines capable of running modern OS's, which are mostly still the economically poor). I know, I know, with a bit of work they could install a nice undemanding Linux distro that would be a much better all ways round, but that underestimates how protective the less computer savvy sort of individual would be over their only working PC. The extent to which such a machine, in a known working order, is valued by such a person perhaps cannot be overestimated; they might depend on it for a current system to receive foreign remittances, for instance.

I'd be very amused to hear of Nepalese or Zimbabwean Armory users making successful use of Armory on a 384 Mb 1Ghz XP machine! If they could even thrive with such a setup, then that would really be something. (has anyone ever tested it on Windows 2000?  :P)

To be clear, I have nothing against accommodating those OSes.  It's just a matter of priorities.  If we can support it, I'd be happy to, but I need to get some of the more critical usability issues out of the way, first.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Carlton Banks on November 02, 2013, 06:45:14 PM
That increasingly shrinking proportion of XP users are increasingly going to be comprised of the people with (seemingly) no choice but XP; the poor (as well as those with poor opportunities to get hold of machines capable of running modern OS's, which are mostly still the economically poor). I know, I know, with a bit of work they could install a nice undemanding Linux distro that would be a much better all ways round, but that underestimates how protective the less computer savvy sort of individual would be over their only working PC. The extent to which such a machine, in a known working order, is valued by such a person perhaps cannot be overestimated; they might depend on it for a current system to receive foreign remittances, for instance.

I'd be very amused to hear of Nepalese or Zimbabwean Armory users making successful use of Armory on a 384 Mb 1Ghz XP machine! If they could even thrive with such a setup, then that would really be something. (has anyone ever tested it on Windows 2000?  :P)

To be clear, I have nothing against accommodating those OSes.  It's just a matter of priorities.  If we can support it, I'd be happy to, but I need to get some of the more critical usability issues out of the way, first.

Agreed. It makes no sense to concentrate any effort into backwards compatibility when the trend is that the very PC's I'm referring to will eventually die in the heat of a desert somewhere, and this notional hard-up Bitcoin user ends up with a cast off Vista machine in replacement. If it can be done for the low cost of an experienced developer's pre-existing comprehensive knowledge of compatibility of compiling, as is the case with goatpig, then it's good to have.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: gweedo on November 03, 2013, 02:15:17 AM
That increasingly shrinking proportion of XP users are increasingly going to be comprised of the people with (seemingly) no choice but XP; the poor (as well as those with poor opportunities to get hold of machines capable of running modern OS's, which are mostly still the economically poor). I know, I know, with a bit of work they could install a nice undemanding Linux distro that would be a much better all ways round, but that underestimates how protective the less computer savvy sort of individual would be over their only working PC. The extent to which such a machine, in a known working order, is valued by such a person perhaps cannot be overestimated; they might depend on it for a current system to receive foreign remittances, for instance.

I'd be very amused to hear of Nepalese or Zimbabwean Armory users making successful use of Armory on a 384 Mb 1Ghz XP machine! If they could even thrive with such a setup, then that would really be something. (has anyone ever tested it on Windows 2000?  :P)

To be clear, I have nothing against accommodating those OSes.  It's just a matter of priorities.  If we can support it, I'd be happy to, but I need to get some of the more critical usability issues out of the way, first.
your priority should be Mac at the moment...many users use the armory for mac and I myself have A LOT of bitcoin stuck in it...

I have to agree, I think Alan is spread a little too thin, doing so much cool stuff, while trying to make it multi-OS usable. That will never work, I think Alan should be trying to get a good build process that will be able to output windows, linux and Mac binaries. Until then development has to be paused otherwise it will always be a rat race with new developments and OS binaries.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 03, 2013, 03:21:51 AM
Mac is definitely a high priority right now.  I also should put in an informational channel to communicate with users like "Armory does not yet work with OSX 10.9.  If you upgrade you may temporarily lose access to your Armory wallet". 

Things like Windows XP and obscure (err... less-popular) flavors of Linux will be lower priority for now.   Luckily, goatpig has helped out tremendously with Windows in general, so I'm down to just a couple bugs left (though one is going to be a pain to fix), and then OSX support.  I'm going to make it my mission to try to get picobit's OSX solution working before the end of the weekend.   We'll see where it goes from there.

It sounds like goatpig might have a decent XP solution, but I will leave it to those who really want it to try to get it working.  Too many other things for me to worry about right now.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: cp1 on November 03, 2013, 03:22:16 AM
your priority should be Mac at the moment...many users use the armory for mac and I myself have A LOT of bitcoin stuck in it...

If you have coins you can't access because of the Mac OS then just dual boot linux or run it in a virtual machine.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 03, 2013, 06:03:24 AM
i've been doing testing in linux and windows, but as a mac user i am really excited to report that a pkg picobit was kind enough to share with me installed cleanly on both OS X 10.8 & 10.9.  on 10.9 i have a full blockchain so i can see the balance from a small test transaction in the wallet; no other testing as of yet.

i know there are issues to be worked out such as command line arguments not passing and needing to get a formal build process for this, but this is sweet even as it is.

thanks picobit!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: HowlingMad on November 03, 2013, 12:13:21 PM
Linux n00b and dangerous so .....

I am trying to compile from source on  Debian.  When I do "git clone testing" Debian craps out
 bob@debian:~/BitcoinArmory$ git clone testing
Cloning into testing...
warning: You appear to have cloned an empty repository.

I had already ran the original git command as noted in "Building Armory from source"
Thanks in advance.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: e4xit on November 03, 2013, 12:32:43 PM
Linux n00b and dangerous so .....

I am trying to compile from source on  Debian.  When I do "git clone testing" Debian craps out
 bob@debian:~/BitcoinArmory$ git clone testing
Cloning into testing...
warning: You appear to have cloned an empty repository.

I had already ran the original git command as noted in "Building Armory from source"
Thanks in advance.


Disclaimer: I too am I Linux n00b, but here are the steps I used to compile (successfully) on Ubuntu:

Install dependencies:
Code:
sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil libcrypto++-dev

Clone Armory Git:
Code:
git clone git://github.com/etotheipi/BitcoinArmory.git

Change to newly created directory of git repo:
Code:
cd ~/BitcoinArmory

Switch to the 'testing' branch:
Code:
git checkout testing

Change to folder which is home to a file which needs editing:
Code:
cd ~/BitcoinArmory/cppForSwig/leveldb/db/

Open the file which needs editing in a text editor:
Code:
gedit c.cc

// Comment out or delete line 18 (" #define strdup _strdup"), save and close c.cc

Switch back to the root directory:
Code:
cd ~/BitcoinArmory

Compile:
Code:
make

Run the program (you will have to run this command to open Armory each time you want to open it, make sure you have 'cd' into 'BitcoinArmory' directory first each time though!:
Code:
python ArmoryQt.py


Notes:
gedit is a simple text editor which is installed by default in Ubuntu, if this is different in Debian you might have to change the step "gedit c.cc" but IDK.

Also, I guess some of the packages/dependencies required (first line of code) might differ in Debian, but I think Debian & Ubuntu are pretty similar in that way.

Hope this helps.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: HowlingMad on November 03, 2013, 01:29:16 PM

Also, I guess some of the packages/dependencies required (first line of code) might differ in Debian, but I think Debian & Ubuntu are pretty similar in that way.
Thanks all of the instructions were exactly the same.  Armory is running now and I learned a couple new things.  Have a great day!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: cp1 on November 03, 2013, 03:41:22 PM
Linux n00b and dangerous so .....

I am trying to compile from source on  Debian.  When I do "git clone testing" Debian craps out
 bob@debian:~/BitcoinArmory$ git clone testing
Cloning into testing...
warning: You appear to have cloned an empty repository.

I had already ran the original git command as noted in "Building Armory from source"
Thanks in advance.


You want to checkout instead of clone for that part.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 03, 2013, 06:27:06 PM
Yay picobit!

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.app.0.89.99.9-testing.tar.gz

That 40 MB tar.gz unpacks into a 136 MB Armory.app directory, which should be double-clickable to run Armory.  I successfully compiled it on my MacMini, after review the build-app.py script that picobit gave me, and then successfully running it.  There was a few hiccups in the build process, but it ultimately worked.  And kudos to picobit for not only giving me a script, but being diligent about creating and sorting log files for each command so I could easily figure out what went wrong.  

Please test it on your OSX system.  Especially on 10.9, and especially on any systems where the download from the webpage didn't work.  I want to find out if this .app works better than the one we originally got from higuys.  I'm hopeful based on els' statements that it worked on both 10.8 and 10.9, but I definitely need more empirical evidence.  

By the way, this is actually 0.89.99.9.  This has a feature merged in from CircusPeanut that fixes the broadcast issue people experience when using older versions of Armory on the offline computer.  The issue was that the core devs implemented a soft-rule requiring normalized signature padding, and older versions of Armory didn't do that.  Thus when you sign with the older version, the tx will be rejected if you are running Bitcoin-Qt/bitcoin 0.8.2 or newer.  This version works around that by exploiting the same transaction malleability that the core devs were trying to reduce!  It adjusts the signature padding of the already-signed transaction -- it changes the hash of the transaction but makes the transaction not only valid, but isStandard() so it will broadcast correctly.  

If you are experiencing that broadcast issue, you can:  (Linux) Pull the latest testing branch and use that (OSX) Use this .app (Windows) Wait for the next testing release.  


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 03, 2013, 06:42:52 PM
It is working for me on OSX 10.9, it is says "preparing database" so once is it finished I will reply, but it started! That is big plus!

Well just because it works on OSX, doesn't mean that the database/build/scan bugs are fixed.  I still have a lot of work to do on that front, but at least I have the tools now to debug it easier...

Unfortunately, one of the caveats of picobit's solution is the difficulty of passing command-line arguments.  I might "hack" something that will work from the menu:  Armory will check for a "rebuild.txt" or "rescan.txt" file at startup, if it finds it, it will delete it and then do the rebuild or rescan.  The menu option will simply write the file and then close the app.  This makes it fairly simple to force the rebuild or rescan, and also make it easy to induce it from within the app (I had problems before, trying to force this to happen after the app was already running). 

I'll make sure that's in the next version.  Unfortunately, we'll still need a real solution to the CLI-argument issue, since you can't set the --datadir this way. Though, for everything else, I suppose I could use an armory.conf file just like the bitcoin.conf file...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Missionary on November 03, 2013, 06:48:52 PM
I'll download and try that version on 10.9. Should I empty my Armory Library folder or just install the app using the old files?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 03, 2013, 08:36:40 PM
Just to clarify about the OSX version I just made available through dropbox: that version was built by me, not picobit.  I used his script to do the building, but I reviewed it and confirmed that it's building directly from the github repo and downloads the build dependencies from standard locations. 

If this version is like the previous version, it should work 100% when it works (besides the fact that it's the new testing version with a few usability bugs).  I'll let people report their experiences with it, but I would guess it can be trusted as much as the Linux or Windows testing versions.   Those versions are pretty solid, besides the usability issues. 

So usual caveats about "testing version: use at your own risk", but I don't see a reason to trust this version less than the other ones already being tested.





Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Red Emerald on November 03, 2013, 08:45:57 PM
I'm testing out the .app now.  Awesome work!  I haven't had any time to play with Armory recently.  Hopefully bitcoind works for me without crashing and corrupting the block chain like it was last time I tried bitcoin on OSX.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 03, 2013, 09:39:43 PM
Yay picobit!

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.app.0.89.99.9-testing.tar.gz

That 40 MB tar.gz unpacks into a 136 MB Armory.app directory, which should be double-clickable to run Armory.  I successfully compiled it on my MacMini, after review the build-app.py script that picobit gave me, and then successfully running it.  There was a few hiccups in the build process, but it ultimately worked.  And kudos to picobit for not only giving me a script, but being diligent about creating and sorting log files for each command so I could easily figure out what went wrong.  

Please test it on your OSX system.  Especially on 10.9, and especially on any systems where the download from the webpage didn't work.  I want to find out if this .app works better than the one we originally got from higuys.  I'm hopeful based on els' statements that it worked on both 10.8 and 10.9, but I definitely need more empirical evidence.  

By the way, this is actually 0.89.99.9.  This has a feature merged in from CircusPeanut that fixes the broadcast issue people experience when using older versions of Armory on the offline computer.  The issue was that the core devs implemented a soft-rule requiring normalized signature padding, and older versions of Armory didn't do that.  Thus when you sign with the older version, the tx will be rejected if you are running Bitcoin-Qt/bitcoin 0.8.2 or newer.  This version works around that by exploiting the same transaction malleability that the core devs were trying to reduce!  It adjusts the signature padding of the already-signed transaction -- it changes the hash of the transaction but makes the transaction not only valid, but isStandard() so it will broadcast correctly.  

If you are experiencing that broadcast issue, you can:  (Linux) Pull the latest testing branch and use that (OSX) Use this .app (Windows) Wait for the next testing release.  

It is working for me on OSX 10.9, it is says "preparing database" so once is it finished I will reply, but it started! That is big plus!

EDIT: Now it is Building the database!

this new (0.89.99.9) build is also working well for me on OS X 10.9.  awesome; very promising!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Red Emerald on November 03, 2013, 09:42:11 PM
I can't manage to get bitcoind built on OSX 10.9 :(  My tap (https://github.com/WyseNynja/homebrew-bitcoin) doesn't seem to be working anymore.

I've downloaded the official bitcoin-qt binary and am getting the blockchain with it now.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: HowlingMad on November 03, 2013, 11:01:26 PM
I dowloaded the Linux client and the version states 0.88.1-beta.  Is that right?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Missionary on November 03, 2013, 11:47:37 PM
I dowloaded the Linux client and the version states 0.88.1-beta.  Is that right?

That's the current stable version. If you want to use the test version, check the first post in this thread for instructions.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Missionary on November 03, 2013, 11:51:28 PM
I am happy to report that I have had success in running the OS X version posted by etotheipi. It rebuilt the database and I have successfully imported several wallets. The rescans still take about 20 minutes for each wallet import. However, after the initial import the client launches and syncs within 10-20 seconds!

The one bug I have found, is that during import I check the option for digital wallet import and then hit continue, but sometimes that does nothing. It's not until I hit cancel that the import is initiated. If I had clicked on continue several times, and thus chosen the same wallet file several times, it will give me an error saying that the wallet is already imported when I hit cancel.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: nnimmo on November 04, 2013, 02:03:06 AM
Yay picobit!

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.app.0.89.99.9-testing.tar.gz

That 40 MB tar.gz unpacks into a 136 MB Armory.app directory, which should be double-clickable to run Armory.  I successfully compiled it on my MacMini, after review the build-app.py script that picobit gave me, and then successfully running it.  There was a few hiccups in the build process, but it ultimately worked.  And kudos to picobit for not only giving me a script, but being diligent about creating and sorting log files for each command so I could easily figure out what went wrong.  

Please test it on your OSX system.  Especially on 10.9, and especially on any systems where the download from the webpage didn't work.  I want to find out if this .app works better than the one we originally got from higuys.  I'm hopeful based on els' statements that it worked on both 10.8 and 10.9, but I definitely need more empirical evidence.  

By the way, this is actually 0.89.99.9.  This has a feature merged in from CircusPeanut that fixes the broadcast issue people experience when using older versions of Armory on the offline computer.  The issue was that the core devs implemented a soft-rule requiring normalized signature padding, and older versions of Armory didn't do that.  Thus when you sign with the older version, the tx will be rejected if you are running Bitcoin-Qt/bitcoin 0.8.2 or newer.  This version works around that by exploiting the same transaction malleability that the core devs were trying to reduce!  It adjusts the signature padding of the already-signed transaction -- it changes the hash of the transaction but makes the transaction not only valid, but isStandard() so it will broadcast correctly.  

If you are experiencing that broadcast issue, you can:  (Linux) Pull the latest testing branch and use that (OSX) Use this .app (Windows) Wait for the next testing release.  
I have been succeeded to install it on OSX 10.9. Thank you etotheipi.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: gweedo on November 04, 2013, 03:16:44 AM
Just an update from me, I have built most the database, it says I have about 13mins but considering how long this took, I would say about ~4 more hours. But it is going and no problems so far!

OSX 10.9


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 04, 2013, 03:19:42 AM
Just an update from me, I have built most the database, it says I have about 13mins but considering how long this took, I would say about ~4 more hours. But it is going and no problems so far!

OSX 10.9

Interesting.  What's your system specs?  A few others have reported 30 minutes to build the database on OSX, which is actually faster than it's been working on my Linux system!  (about 40-50 min).  There's also a scanning operation after that, which is 10-20 min.  After that, it shouldn't need to rebuild or rescan again and should start up pretty quickly (unless you restore wallets or import private keys).



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 04, 2013, 04:19:48 AM
I think I found an issue from my log, it doesn't really detect my system specs correctly.
Code:
2013-11-03 23:01 (INFO) -- armoryengine.py:800 - Detected System Specs    : 
2013-11-03 23:01 (INFO) -- armoryengine.py:801 -    Total Available RAM   : -1.00 GB
2013-11-03 23:01 (INFO) -- armoryengine.py:802 -    CPU ID string         : Unknown
2013-11-03 23:01 (INFO) -- armoryengine.py:803 -    Number of CPU cores   : -1 cores
2013-11-03 23:01 (INFO) -- armoryengine.py:804 -    System is 64-bit      : Unknown
2013-11-03 23:01 (INFO) -- armoryengine.py:805 -    Preferred Encoding    : US-ASCII

I have 4gb and my number of cpu cores is a negative number.

Actually that's expected.  I didn't know how to query system specs in OSX so I just skipped it and left the sentinel -1 values.  It doesn't actually affect performance.  It's really just there to assist with troubleshooting when someone sends a log file, and not important for any actual runtime operations.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 04, 2013, 04:23:17 AM
WOO! it works and got my little stash recovered, thank you so much!


Fwhew!  What a huge weight off my shoulders!  Having a reliable OSX package has been on my TODO list forever, and I had no idea where to start with it, or who to recruit to help with it.  If anyone feels inspired to donate based on the availability of OSX support, I ask that you send your donations to picobit.  ATI (Armory Tech, Inc) will also be sending him some BTC whether he wants it or not!  (in exchange for a copyright release on the build script) 



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Rampion on November 04, 2013, 03:00:54 PM
Just tried new Armory on OSX, building database took aprox 30 minutes, next loads just a few seconds (5-10s)

I've been testing it and everything works fine, only problem is that some fonts are cut (see pics below). This problem existed on my system on all previous OSX builds/versions of Armory. Did any OSX user find a fix for this?

https://i.imgur.com/H6wfr73.png

https://i.imgur.com/taJgdNR.png

https://i.imgur.com/mb36p3b.png


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: picobit on November 04, 2013, 03:19:01 PM

I've been testing it and everything works fine, only problem is that some fonts are cut (see pics below). This problem existed on my system on all previous OSX builds/versions of Armory. Did any OSX user find a fix for this?


Yes, it is somewhat annoying.  It usually goes away if you grab one of the corners of the window, then it resizes.  I looks like all fonts grow in size the first time the window gets focus, some windows (those with scrollbars) handle it better than others.


Just an update from me, I have built most the database, it says I have about 13mins but considering how long this took, I would say about ~4 more hours. But it is going and no problems so far!

OSX 10.9
Yes, it took many hours for me too (three or four year old MacBook, OS X 10.8).

But then restarting is much faster than it used to be - except that today it looks like it decided to rescan all the transactions (estimated: 30 min).

Edit:  That smiley was supposed to be version 10.8 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 04, 2013, 03:33:23 PM
Yes, it took many hours for me too (three or four year old MacBook, OS X 10.8).

But then restarting is much faster than it used to be - except that today it looks like it decided to rescan all the transactions (estimated: 30 min).

Edit:  That smiley was supposed to be version 10.8 

I've designed it so that it only saves the wallet history on clean shutdowns while synchronized.  Otherwise it will have to rescan.  It is probably too aggressive in requiring rescanning when probably not necessary... but it's one of those things that can be really messy if it's doesn't work right... frustration is guaranteed, and someone could also lose coins (i.e. because Armory tells them they have X coins, when they actually have X+Y coins and they do something like delete the wallet thinking it's empty).  I'd rather require the rescan too much than deal with "missing" coins, etc.





Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: HowlingMad on November 04, 2013, 07:19:09 PM
I dowloaded the Linux client and the version states 0.88.1-beta.  Is that right?

That's the current stable version. If you want to use the test version, check the first post in this thread for instructions.
Huh, I followed the instructions with "checkout testing" etc...  If I do "git checkout testing" I get the response "you are already using testing". 

I'll uninstall and try it again.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 04, 2013, 07:20:38 PM
I dowloaded the Linux client and the version states 0.88.1-beta.  Is that right?

That's the current stable version. If you want to use the test version, check the first post in this thread for instructions.
Huh, I followed the instructions with "checkout testing" etc...  If I do "git checkout testing" I get the response "you are already using testing". 

I'll uninstall and try it again.

Then you're fine.  It's just to make sure you're on the branch with the latest testing code.  Once you're there, you can follow the rest of the instructions no problem. 

The only thing is that if you don't see "Version 0.89.99.9", you may not be up to date.  You can type "git pull origin testing", and then type "make" again and "python ArmoryQt.py".


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 05, 2013, 03:58:16 AM
trying out the ArmorySetup-0.89.99.8-beta_win32 install on a virgin install of Win 7 Home Premium 64-bit (SP1 + all updates).

it installs fine, but when run it fails with logfile errors.   anybody know if the _win32 means it won't work with 64-bit, or perhaps if i am missing some prerequisite installs?  (i had an earlier testing version working on another instance of win7, where i get the same errors with this version).

logfile output:

(CRITICAL) armoryengine.pyc:1019 - C++ block utilities not available.
(CRITICAL) armoryengine.pyc:1020 -    Make sure that you have the SWIG-compiled modules
(CRITICAL) armoryengine.pyc:1021 -    in the current directory (or added to the PATH)
(CRITICAL) armoryengine.pyc:1022 -    Specifically, you need:
(CRITICAL) armoryengine.pyc:1023 -        CppBlockUtils.py     and
(CRITICAL) armoryengine.pyc:1027 -        _CppBlockUtils.pyd
(ERROR) Traceback (most recent call last):
  File "ArmoryQt.py", line 30, in <module>
  File "armoryengine.pyc", line 1015, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.

Error in sys.excepthook:
Traceback (most recent call last):
  File "armoryengine.pyc", line 595, in logexcept_override
AttributeError: 'NoneType' object has no attribute '__excepthook__'

Original exception was:
Traceback (most recent call last):
  File "ArmoryQt.py", line 30, in <module>
  File "armoryengine.pyc", line 1015, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on November 05, 2013, 04:01:04 AM
is pthreadVC2.dll in the install folder?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 05, 2013, 04:03:24 AM
trying out the ArmorySetup-0.89.99.8-beta_win32 install on a virgin install of Win 7 Home Premium 64-bit (SP1 + all updates).

it installs fine, but when run it fails with logfile errors.   anybody know if the _win32 means it won't work with 64-bit, or perhaps if i am missing some prerequisite installs?  (i had an earlier testing version working on another instance of win7, where i get the same errors with this version).


The win32 means that it is built as a 32-bit application, but 64-bit windows can still run 32-bit applications.  So far, I think most people have been testing the 32-bit app on 64-bit (and I've been using it on my 64-bit Win7 VM).  If there's a problem, perhaps it has to do with installing different versions and jumping around.  I would recommend removing it via control panel, and then remove all C:\Program Files\Armory and C:\Program Files (x86)\Armory.  Then reinstall.  There may still be a problem with the installer not deleting/overwriting everything.

P.S. - Your wallets are not in those directories, so there's no risk of losing your wallets or settings when uninstalling or reinstalling Armory.  For reference, the wallets are in C:\Users\<username>\AppData\Roaming\Armory (do not delete that directory!).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Rogue Star on November 05, 2013, 04:15:18 AM
trying out the ArmorySetup-0.89.99.8-beta_win32 install on a virgin install of Win 7 Home Premium 64-bit (SP1 + all updates).

it installs fine, but when run it fails with logfile errors.   anybody know if the _win32 means it won't work with 64-bit, or perhaps if i am missing some prerequisite installs?  (i had an earlier testing version working on another instance of win7, where i get the same errors with this version).


The win32 means that it is built as a 32-bit application, but 64-bit windows can still run 32-bit applications.  So far, I think most people have been testing the 32-bit app on 64-bit (and I've been using it on my 64-bit Win7 VM).  If there's a problem, perhaps it has to do with installing different versions and jumping around.  I would recommend removing it via control panel, and then remove all C:\Program Files\Armory and C:\Program Files (x86)\Armory.  Then reinstall.  There may still be a problem with the installer not deleting/overwriting everything.
this is the same problem i reported to you by email a few weeks ago. i haven't been able to get it working since. i've tried uninstalling and removing the obvious files like the folder in Program Files and AppData\Roaming Data, but no dice. unfortunately I don't have any VM snapshots without Armory installed. i'm currently using the standalone edition (0.89.99.3) as a workaround since it still works just fine.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 05, 2013, 04:34:31 AM
trying out the ArmorySetup-0.89.99.8-beta_win32 install on a virgin install of Win 7 Home Premium 64-bit (SP1 + all updates).
it installs fine, but when run it fails with logfile errors....

The win32 means that it is built as a 32-bit application, but 64-bit windows can still run 32-bit applications.  So far, I think most people have been testing the 32-bit app on 64-bit (and I've been using it on my 64-bit Win7 VM).  If there's a problem, perhaps it has to do with installing different versions and jumping around.  I would recommend removing it via control panel, and then remove all C:\Program Files\Armory and C:\Program Files (x86)\Armory.  Then reinstall.  There may still be a problem with the installer not deleting/overwriting everything.
...

as i was having trouble with this in a win7 instance where i had a prior Armory install, i made the above referenced attempt in a completely new instance of win7 will all updates and nothing else installed.  (it is a VM on a Mac, not a native install).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 05, 2013, 04:41:18 AM
is pthreadVC2.dll in the install folder?

yes, it is...i am assuming the question is regarding the prior post:

"trying out the ArmorySetup-0.89.99.8-beta_win32 install on a virgin install of Win 7 Home Premium 64-bit (SP1 + all updates). it installs fine, but when run it fails with logfile errors. "



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: e4xit on November 05, 2013, 09:18:01 AM
etotheipi (or anyone else),

1. Is it possible to restore the m of n backups using version 0.88.1? As this is the version I have on my (offline) netbook and it defeats the purpose of it being offline if I have to restore to an online machine, kind of...

2. Conversely, and this is a little long winded, but would I be able to install 0.89.99.8/9 onto (an offline) Ubuntu 10.04? Would I simply have to download:
Code:
git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil libcrypto++-dev
as .deb packages, transfer them accross to the netbook and install them on-by-one.

Then also copy accross the cloned Armory git, and make and run as I have been doing on Ubuntu 13.10? Or is there something about this which would not work?

Then I could create m of n wallets on my network-neutered machine, and also be able to restore to them directly from there... But I am only speculating about this with my basic understanding of it all....


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: e4xit on November 06, 2013, 10:56:55 AM
Etotheipi, this may come as no surprise seeing as it runs perfectly on ubuntu 13.10, but 0.89.99.8 is running perfectly (in offline mode) on a low-powered Intel Atom EeePC netbook running Lubuntu 13.10 (Saucy Salamander).

Tested the backup center (various backup types, including the m-of-n GUI) and signing transactions, which all seems to work.

If anyone is wondering, the combination of lightweight Ubuntu and the Eee PC running Armory is ideal.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 06, 2013, 08:00:10 PM
...
If anyone is wondering, the combination of lightweight Ubuntu and the Eee PC running Armory is ideal.

absolutely!  any currently available models to recommend?  best i've found to-date is ASUS 1015E-DS03 going for about $230.  ships with Ubuntu not windows so you save a little.  this is not optimal (could be smaller w/fewer features, has spinning disk...) but is decent for this application.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on November 06, 2013, 08:58:30 PM
WinXP users: better late than never!

Note: this is my build (goatpig), not an official ATI (Armory Technologies Inc.) build. I'm offering this build to willing WinXp testers in order to iron out the WinXP building process.

This file is a rar archive containing compiled binaries that hopefully will run in WinXP. Succeeding to start Armory in offline mode is enough to confirm the binaries are WinXP compatible. Use it online at your own risk!

https://mega.co.nz/#!xQIgyIwT!LixQalxUuStJhNUYao217WVVRY0bjNuxMxUzliuUIAk



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 06, 2013, 09:13:17 PM
etotheipi (or anyone else),

1. Is it possible to restore the m of n backups using version 0.88.1? As this is the version I have on my (offline) netbook and it defeats the purpose of it being offline if I have to restore to an online machine, kind of...

2. Conversely, and this is a little long winded, but would I be able to install 0.89.99.8/9 onto (an offline) Ubuntu 10.04? Would I simply have to download:
Code:
git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil libcrypto++-dev
as .deb packages, transfer them accross to the netbook and install them on-by-one.

Then also copy accross the cloned Armory git, and make and run as I have been doing on Ubuntu 13.10? Or is there something about this which would not work?

Then I could create m of n wallets on my network-neutered machine, and also be able to restore to them directly from there... But I am only speculating about this with my basic understanding of it all....

If you've already installed an offline bundle on your offline machine, it already has all the dependencies needed to run the new version (though, occasionally new dependencies crop up in new versions, but I don't think that happened for this update).  Given that, you should be able to checkout the repo and build it on an online computer, then take the built directory to the offline computer and run it there.  As long as it has been built already,  and dependencies installed, you're good. 

The offline bundle has all the dependencies needed for 10.04.  However, it doesn't have the dependencies for building the package, which is a bit more work.  Technically, you can use synaptic on the offline machine to generate and offline download script, but that's a bit of work.  I don't recommend it unless you're patient.

No, you can't recover the fragmented backups in 0.88.1.  Ultimately, you'll have to switch to the new version for the offline computer.  However, I added a backup-testing window, which should help calm any nerves about trusting new technology :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Portnoy on November 06, 2013, 11:07:27 PM
WinXP users: better late than never!

Note: this is my build (goatpig), not an official ATI (Armory Technologies Inc.) build. I'm offering this build to willing WinXp testers in order to iron out the WinXP building process.

This file is a rar archive containing compiled binaries that hopefully will run in WinXP. Succeeding to start Armory in offline mode is enough to confirm the binaries are WinXP compatible. Use it online at your own risk!

https://mega.co.nz/#!xQIgyIwT!LixQalxUuStJhNUYao217WVVRY0bjNuxMxUzliuUIAk



Doesn't work for me.  Still the same error messages in the log as before:

Traceback (most recent call last):
  File "ArmoryQt.py", line 21, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: goatpig on November 06, 2013, 11:57:41 PM
WinXP users: second attempt =O

Same disclaimer as before: this is my build (goatpig), not ATI's. Use at your own risk. Just getting Armory to start in offline mode is enough to confirm the build is WinXP compatible.

https://mega.co.nz/#!xQwT0TRD!FgRbBD6vPAaoZulqHqe5qByy1d4sgRpqjmrShEKCZCU



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Portnoy on November 07, 2013, 01:21:57 AM
WinXP users: second attempt =O

Same disclaimer as before: this is my build (goatpig), not ATI's. Use at your own risk. Just getting Armory to start in offline mode is enough to confirm the build is WinXP compatible.

https://mega.co.nz/#!xQwT0TRD!FgRbBD6vPAaoZulqHqe5qByy1d4sgRpqjmrShEKCZCU



No change. Same error message.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 07, 2013, 04:42:40 AM
WinXP users: second attempt =O

Same disclaimer as before: this is my build (goatpig), not ATI's. Use at your own risk. Just getting Armory to start in offline mode is enough to confirm the build is WinXP compatible.

https://mega.co.nz/#!xQwT0TRD!FgRbBD6vPAaoZulqHqe5qByy1d4sgRpqjmrShEKCZCU



No change. Same error message.

i also get the same errors


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 08, 2013, 06:11:13 AM
Someone just reported a problem with "Too many open files" when running on Ubuntu 12.04, 32-bit.  This is only printed to the terminal, though, so it doesn't show up in any log files.  Its symptoms are all sorts of weird behavior on your system, outside of Armory.

He ran "cat /proc/sys/fs/file-max" and it returned a number around 700k.  On my 64-bit system it returns 3.2M.  I wouldn't expect that to be exhausted from our "little" blockchain database, but I guess it is (bitcoin-qt/bitcoind is also running a leveldb database, as well...).  I also found mention of systems with large databases running out of files.

The solution (still being tested)

(1) Reboot.  You're kind of hosed once you get to here
(2) Remove the database which probably go corrupted "rm -rf ~/.armory/databases"
(3) Increase the number of files:  "sudo sysctl -w fs.file-max=5000000"
(4) Restart Armory

If this works, you can make it permanent on reboot by appending the following line to /etc/sysctl.conf

Code:
fs.file-max = 5000000

Hopefully that helps.  Though it does concern me that this is even a problem...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: cp1 on November 08, 2013, 03:58:57 PM
Hopefully that helps.  Though it does concern me that this is even a problem...

I've had to increase this on a number of ubuntu systems for various reasons, I think it's just set way too low for non-desktop work.  So don't worry.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: pvz on November 09, 2013, 09:31:30 PM
Someone just reported a problem with "Too many open files" when running on Ubuntu 12.04, 32-bit

Solution above did not do the trick.

During parsing blockchain files the number of unclosed files increase.
Running the command below gives me a higher number during (re)building:
Code:
lsof | grep python | wc -l

The code and (possible) solution is mentioned on:
http://stackoverflow.com/questions/16386678/too-many-open-files-python-multiprocess-tcp-server
Mentioned solution: "The problem solved. File descriptor assotiated with socket must be manually closed. os.close(fd)"

Hopefully you can reproduce this, or maybe it is only a problem in Ubuntu 12.04, 32-bit.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 10, 2013, 12:03:03 AM
Update:  0.89.99.10-testing

Windows 0.89.99.10-testing:  Download the NSIS installer (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.10-testing_win32.exe)
Ubuntu 0.89.99.10-testing:  checkout and build "testing" branch (see instruction in first post)
Mac/OSX 0.89.99.10-testing:  Download the ArmoryQt.app for OSX (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.OSX.app.0.89.99.10-testing.tar.gz)

What's new:

  • (1) For my life, I cannot figure out the orphan chain bug.  It is very complicated to debug even with the tools I've got right now.  Instead, I work around it by detecting it and rebuilding the databases when it happens.  This won't solve it for everyone, but it does happen most often if a build/update is interrupted, so perhaps it won't be an issue if you're nice to Armory :)  For now, I don't see another way that gets me to a release in the near future.
  • (2) Thanks to CircusPeanut, this version of Armory detects non-standard signature padding and corrects it before broadcasting!  If you had trouble broadcasting transactions from an offline computer runnning an old version of Armory, updating the online computer to this version will allow your offline tx to work again!
  • (3) Goatpig helped update the "bitcoin:" URI-handling in both Linux and Windows.  I have no idea if it works:  try it!  (both with Armory open, and without)
  • (4) Added three new items to the "Help" menu:
        "Clear Unconfirmed Transactions" (mempoool.bin)
        "Rescan Databases"
        "Rebuild and Rescan Databases"
    All three operations require restarting Armory, and signal to it by touching a file in the ARMORY_HOME_DIR -- meaning you can do it yourself externally.  You can simply touch "clearmempool.txt", 'rebuild.txt' or "rescan.txt".  The file will trigger the appropriate behave and then be deleted so it doesn't trigger on the next load.
  • (5) Added a popup to warn users about sending money to their Armory wallet without ever getting online first.  This should prevent users dumping money in before they realize that it doesn't work on their system.
  • (6) Fixed the "memory pool file is corrupt" messages on Windows.  It should now successfully save zero-conf transactions between loads.
  • (7) If a rebuild operation is interrupted, Armory usually picks up where it left off when it restarted... but the meter would reset to 0% giving the user the impression it is starting from scratch.  That has been fixed.

News on OSX:

The OSX recipe prepared by picobit that i used to compile the OSX testing version, appears to be pretty unreliable on some systems, with lots of crashing.  It appears that, with enough effort, you can eventually get out of Armory what you need, but will likely involve lots of restarting and rescanning.  

The good news is that it appears this is a known problem affecting the combo of PyQt4 & OSX 10.9.  Not sure when there will be a fix, but even without fixed PyQt4 binaries, I might be able to work around it (it has to do with nested modal dialogs).  Therefore, I suspect the issue is not picobit's recipe -- even if I rebuilt higuys' package for 10.9, it would likely still be unreliable.

Message Signing!
Almost... should be in the next testing version.  I hadn't planned on including it in this release, but getting this release out has taken so long that it gave me time to delegate that integration to CircusPeanut.  Will include a Bitcoin-Qt compatible version, as well as an Armory-specific version that is based on RFC2440, so I'm hoping that others will feel inspired to support it (it's makes much more sense than the bare signatures).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 10, 2013, 12:24:29 AM
Update:  0.89.99.10-testing

Windows 0.89.99.10-testing:  Download the NSIS installer (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.10-testing_win32.exe)
....
as with the .8 version, i get errors trying to run on a fresh install of win 7 home premium w/sp1 and all updates.  (nothing else installed at all).  this is a VM (which shouldn't matter, but who knows).

anybody know if there is something else i must install first (as perhaps implied by the logfile errors below)?

(CRITICAL) armoryengine.pyc:1041 - C++ block utilities not available.
(CRITICAL) armoryengine.pyc:1042 -    Make sure that you have the SWIG-compiled modules
(CRITICAL) armoryengine.pyc:1043 -    in the current directory (or added to the PATH)
(CRITICAL) armoryengine.pyc:1044 -    Specifically, you need:
(CRITICAL) armoryengine.pyc:1045 -        CppBlockUtils.py     and
(CRITICAL) armoryengine.pyc:1049 -        _CppBlockUtils.pyd
(ERROR) Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.

Error in sys.excepthook:
Traceback (most recent call last):
  File "armoryengine.pyc", line 617, in logexcept_override
AttributeError: 'NoneType' object has no attribute '__excepthook__'

Original exception was:
Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: els on November 10, 2013, 12:39:04 AM
Update:  0.89.99.10-testing

Mac/OSX 0.89.99.10-testing:  Download the ArmoryQt.app for OSX (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.OSX.app.0.89.99.10-testing.tar.gz)

a quick check of this build looks good on my OS X 10.9!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 10, 2013, 01:23:42 AM
as with the .8 version, i get errors trying to run on a fresh install of win 7 home premium w/sp1 and all updates.  (nothing else installed at all).  this is a VM (which shouldn't matter, but who knows).

anybody know if there is something else i must install first (as perhaps implied by the logfile errors below)?

(CRITICAL) armoryengine.pyc:1041 - C++ block utilities not available.
(CRITICAL) armoryengine.pyc:1042 -    Make sure that you have the SWIG-compiled modules
(CRITICAL) armoryengine.pyc:1043 -    in the current directory (or added to the PATH)
(CRITICAL) armoryengine.pyc:1044 -    Specifically, you need:
(CRITICAL) armoryengine.pyc:1045 -        CppBlockUtils.py     and
(CRITICAL) armoryengine.pyc:1049 -        _CppBlockUtils.pyd
(ERROR) Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.

Error in sys.excepthook:
Traceback (most recent call last):
  File "armoryengine.pyc", line 617, in logexcept_override
AttributeError: 'NoneType' object has no attribute '__excepthook__'

Original exception was:
Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.


Perhaps there's some kind of MSVC redistributable to be installed.  In the past, there was a couple users that needed the MSVC 2008 Redistributable installed, when I was still compiling with MSVS 2005.  Perhaps goatpig has some ideas...?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 10, 2013, 05:26:08 AM
Oh, I haven't been building the Debian packages, but it's actually pretty easy, so I don't know why not.  I just built the package and put it in Dropbox:

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/armory_0.89.99.10-testing_amd64.deb

It is signed by my online GPG key (not the offline key, but better than nothing).  Use "dpkg-sig --verify armory_0.89.99.10-testing_amd64.deb" and check that the signature is valid for key FB596985 (http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x11DEE9BEFB596985).  You may have to install the "dpkg-sig" package first ("sudo apt-get install dpkg-sig").

If you are on 64-bit Ubuntu-Debian, please try it and let me know if it works for you the same as building it yourself.



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Rogue Star on November 10, 2013, 05:32:57 AM
I'm seeing the same error as "els", for Win7 Ultimate x64, also a VM with all Windows updates.

I have the following MS VS related entries listed in Programs and Features

Microsoft .NET Framework 4 Client Profile
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 10, 2013, 07:11:50 AM
Rogue Star & els,

I just dumped a "standalone" version into dropbox.  It should be exactly the same as the installed version, but it hasn't gone through the NSIS installer-builder process.  I want to see if that makes a difference.

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmoryStandalone_0.89.99.10-testing.zip

Just unzip and double-click on ArmoryQt.exe.  Let me know if that works. 

P.S. - I wonder if maybe the presence of 2008 redistributable is actually hurting you.  Total longshot, but possible.  Since I changed compilers, I doubt having that installed would benefit you (though there may be other reasons you have it installed)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Rogue Star on November 10, 2013, 07:33:32 AM
I just dumped a "standalone" version into dropbox.  It should be exactly the same as the installed version, but it hasn't gone through the NSIS installer-builder process.  I want to see if that makes a difference.
It was a nice thought, but the standalone version has the same error. One slightly odd thing about the standalone is it logs in both the User\App Data folder and the Standalone folder, but I think that may be normal. The Standalone log had a slightly more detailed stack.

Code:
(CRITICAL) armoryengine.pyc:1041 - C++ block utilities not available.
(CRITICAL) armoryengine.pyc:1042 -    Make sure that you have the SWIG-compiled modules
(CRITICAL) armoryengine.pyc:1043 -    in the current directory (or added to the PATH)
(CRITICAL) armoryengine.pyc:1044 -    Specifically, you need:
(CRITICAL) armoryengine.pyc:1045 -        CppBlockUtils.py     and
(CRITICAL) armoryengine.pyc:1049 -        _CppBlockUtils.pyd
(ERROR) Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.

Error in sys.excepthook:
Traceback (most recent call last):
  File "armoryengine.pyc", line 617, in logexcept_override
AttributeError: 'NoneType' object has no attribute '__excepthook__'

Original exception was:
Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.

[EDIT] Removing the redistributable and .NET Framework 4 Client Profile didn't have any impact. Is there any particular versions that should be installed? From what I understand about VS, it's normal to have multiple distributable versions installed and the app should select the appropriate one automatically. I don't know much about VS, so I could be totally wrong.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: Rampion on November 10, 2013, 10:57:19 AM
Update:  0.89.99.10-testing

Windows 0.89.99.10-testing:  Download the NSIS installer (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.10-testing_win32.exe)
Ubuntu 0.89.99.10-testing:  checkout and build "testing" branch (see instruction in first post)
Mac/OSX 0.89.99.10-testing:  Download the ArmoryQt.app for OSX (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.OSX.app.0.89.99.10-testing.tar.gz)

What's new:

  • (1) For my life, I cannot figure out the orphan chain bug.  It is very complicated to debug even with the tools I've got right now.  Instead, I work around it by detecting it and rebuilding the databases when it happens.  This won't solve it for everyone, but it does happen most often if a build/update is interrupted, so perhaps it won't be an issue if you're nice to Armory :)  For now, I don't see another way that gets me to a release in the near future.
  • (2) Thanks to CircusPeanut, this version of Armory detects non-standard signature padding and corrects it before broadcasting!  If you had trouble broadcasting transactions from an offline computer runnning an old version of Armory, updating the online computer to this version will allow your offline tx to work again!
  • (3) Goatpig helped update the "bitcoin:" URI-handling in both Linux and Windows.  I have no idea if it works:  try it!  (both with Armory open, and without)
  • (4) Added three new items to the "Help" menu:
        "Clear Unconfirmed Transactions" (mempoool.bin)
        "Rescan Databases"
        "Rebuild and Rescan Databases"
    All three operations require restarting Armory, and signal to it by touching a file in the ARMORY_HOME_DIR -- meaning you can do it yourself externally.  You can simply touch "clearmempool.txt", 'rebuild.txt' or "rescan.txt".  The file will trigger the appropriate behave and then be deleted so it doesn't trigger on the next load.
  • (5) Added a popup to warn users about sending money to their Armory wallet without ever getting online first.  This should prevent users dumping money in before they realize that it doesn't work on their system.
  • (6) Fixed the "memory pool file is corrupt" messages on Windows.  It should now successfully save zero-conf transactions between loads.
  • (7) If a rebuild operation is interrupted, Armory usually picks up where it left off when it restarted... but the meter would reset to 0% giving the user the impression it is starting from scratch.  That has been fixed.

News on OSX:

The OSX recipe prepared by picobit that i used to compile the OSX testing version, appears to be pretty unreliable on some systems, with lots of crashing.  It appears that, with enough effort, you can eventually get out of Armory what you need, but will likely involve lots of restarting and rescanning.  

The good news is that it appears this is a known problem affecting the combo of PyQt4 & OSX 10.9.  Not sure when there will be a fix, but even without fixed PyQt4 binaries, I might be able to work around it (it has to do with nested modal dialogs).  Therefore, I suspect the issue is not picobit's recipe -- even if I rebuilt higuys' package for 10.9, it would likely still be unreliable.

Message Signing!
Almost... should be in the next testing version.  I hadn't planned on including it in this release, but getting this release out has taken so long that it gave me time to delegate that integration to CircusPeanut.  Will include a Bitcoin-Qt compatible version, as well as an Armory-specific version that is based on RFC2440, so I'm hoping that others will feel inspired to support it (it's makes much more sense than the bare signatures).

Wow, the last OSX version works even better than the previous one. On 10.8.5 (no Mavericks for me, it screws up my system) with 8GB RAM it takes only a few seconds to boot up! The screwed fonts are also gone.

One question Alan: are these testing version safe to be used to manage our funds, or are they supposed to be used for pure testing only on testnet? I wouldn't like to screw up :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: etotheipi on November 10, 2013, 04:47:22 PM
Wow, the last OSX version works even better than the previous one. On 10.8.5 (no Mavericks for me, it screws up my system) with 8GB RAM it takes only a few seconds to boot up! The screwed fonts are also gone.

One question Alan: are these testing version safe to be used to manage our funds, or are they supposed to be used for pure testing only on testnet? I wouldn't like to screw up :)

I wonder if maybe things were updated on OSX 10.9 between the last version and now.  Because I didn't really do anything differently.  The only thing was that I installed the latest updates on 10.9...

As for reliability of this version:  I have to give the usual caveats about it being a testing version of beta software.  But it has proven to be quite reliable.  And I've been using it exclusively for the past month.  However, the backup system is still only 99% complete.  I've got some more testing to do on it before an official release, but I'm fairly confident it won't change (but we have some more tests to run, and I want to implement a way to test all fragments at once).

I am comfortable using it for offline transactions, for sure... because the offline computer (running a stable version) would  catch any issues with the tx created by the new version -- but so far there hasn't even been a hint of a problem with hot wallets, etc.

I have one more major bug to catch, which results in zero-conf transactions disappearing from the interface when they are included in a block.  It doesn't happen to all tx, and they should reappear when you restart.  But it can lead to incorrect balances which can be somewhat dangerous.  It seems that all the other bugs are simply usability issues, which I'll have to live with for now.  I think the combined usability problems of this version still sum to something far less than the problems with the old version with the RAM consumption...

Also, if you run across the following error in your logfile:

Code:
 Cannot get tx copy, because don't have full StoredTx

please stop Armory and make a backup of your database directory.  Then rebuild.  I will find a way to get a copy of the DB from you so that I can debug it.  But doing a rebuild should fix it in the short-run.  (sadly, I even caught this bug in my windows debugger, but accidentally did a rebuild over it.  D'oh!),


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 10, 2013, 10:28:42 PM
Windows Builds:

Try the MSVS 2012 redist, that's the only one I can think off that may be missing. This is the same issues as the WinXP builds I've distributed recently and I have to investigate the error on a clean install to find it out.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Rogue Star on November 11, 2013, 01:00:47 AM
Windows Builds:

Try the MSVS 2012 redist, that's the only one I can think off that may be missing. This is the same issues as the WinXP builds I've distributed recently and I have to investigate the error on a clean install to find it out.
I installed the MSVS 2012 redist, which added "Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.60610" as an entry to Programs and Features.

Unfortunately, I still get the same error. Thanks for the suggestion goatpig.

Is there also a .NET Framework that should be installed along side it?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 11, 2013, 01:25:29 AM
Windows Builds:

Try the MSVS 2012 redist, that's the only one I can think off that may be missing. This is the same issues as the WinXP builds I've distributed recently and I have to investigate the error on a clean install to find it out.
I installed the MSVS 2012 redist, which added "Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.60610" as an entry to Programs and Features.

Unfortunately, I still get the same error. Thanks for the suggestion goatpig.

Is there also a .NET Framework that should be installed along side it?

I'm now 99% sure this issue stems from a file missing in the package. Give it until Alan gets back and confirms this, he'll build a new installer with the fix.

This build shouldn't require those runtimes nor .NET framework binaries that aren't already packed with stock Win7


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Dabs on November 11, 2013, 02:50:45 AM
Okay. Mr. goatpig, let me know if you have a new XP build for me and others to test. I have a (almost) clean install of XP SP3, and I keep it that way.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Portnoy on November 11, 2013, 02:58:08 AM
Is there anything that can be done when it is stuck at "Build Databases and Scan - 62% 15 seconds"?
The 'Transactions' tab is greyed out; the lower right status bar says connected and seems to show
the correct number of blocks; the wallets all display the correct balances( haven't tried any
transactions to see if they update correctly ).

I shut it down and restarted it several times and each time soon after starting it gets to a point where
it is displaying properly; the transaction tab is accessible and scrollable and everything seems to be
working properly and then after a short while it switches to the Dashboard tab and says it is not
connected ( even though the text in the status bar still says it is ) and then after a few minutes it goes
back to that "Build Databases and Scan - 62% 15 seconds", like I describe above, and just stays like that...

This is with ArmorySetup-0.89.99.8-beta_win32.exe
on Windows 7 64-bit.

The latest test version starts for me but never even gets to displaying wallet balances or saying connected in the status bar...

Thanks


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 11, 2013, 02:59:53 AM
Is there anything that can be done when it is stuck at "Build Databases and Scan - 62% 15 seconds"?
The 'Transactions' tab is greyed out; the lower right status bar says connected and seems to show
the correct number of blocks; the wallets all display the correct balances( haven't tried any
transactions to see if they update correctly ).

I shut it down and restarted it several times and each time soon after starting it gets to a point where
it is displaying properly; the transaction tab is accessible and scrollable and everything seems to be
working properly and then after a short while it switches to the Dashboard tab and says it is not
connected ( even though the text in the status bar still says it is ) and then after a few minutes it goes
back to that "Build Databases and Scan - 62% 15 seconds", like I describe above, and just stays like that...

This is with ArmorySetup-0.89.99.8-beta_win32.exe
on Windows 7 64-bit.

The latest test version starts for me but never even gets to displaying wallet balances or saying connected in the status bar...

Thanks

Since I messed a bit with the DB ops, go ahead and do a rebuild if you don't mind waiting for it.  From the help menu "Rebuild and Rescan Databases".  Let me know if you have the same problem after that.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Portnoy on November 11, 2013, 03:02:25 AM
Is there anything that can be done when it is stuck at "Build Databases and Scan - 62% 15 seconds"?
The 'Transactions' tab is greyed out; the lower right status bar says connected and seems to show
the correct number of blocks; the wallets all display the correct balances( haven't tried any
transactions to see if they update correctly ).

I shut it down and restarted it several times and each time soon after starting it gets to a point where
it is displaying properly; the transaction tab is accessible and scrollable and everything seems to be
working properly and then after a short while it switches to the Dashboard tab and says it is not
connected ( even though the text in the status bar still says it is ) and then after a few minutes it goes
back to that "Build Databases and Scan - 62% 15 seconds", like I describe above, and just stays like that...

This is with ArmorySetup-0.89.99.8-beta_win32.exe
on Windows 7 64-bit.

The latest test version starts for me but never even gets to displaying wallet balances or saying connected in the status bar...

Thanks

Since I messed a bit with the DB ops, go ahead and do a rebuild if you don't mind waiting for it.  From the help menu "Rebuild and Rescan Databases".  Let me know if you have the same problem after that.

I don't see that option under the help menu. Do I have to be in expert mode?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 11, 2013, 03:03:00 AM
Is there anything that can be done when it is stuck at "Build Databases and Scan - 62% 15 seconds"?
The 'Transactions' tab is greyed out; the lower right status bar says connected and seems to show
the correct number of blocks; the wallets all display the correct balances( haven't tried any
transactions to see if they update correctly ).

I shut it down and restarted it several times and each time soon after starting it gets to a point where
it is displaying properly; the transaction tab is accessible and scrollable and everything seems to be
working properly and then after a short while it switches to the Dashboard tab and says it is not
connected ( even though the text in the status bar still says it is ) and then after a few minutes it goes
back to that "Build Databases and Scan - 62% 15 seconds", like I describe above, and just stays like that...

This is with ArmorySetup-0.89.99.8-beta_win32.exe
on Windows 7 64-bit.

The latest test version starts for me but never even gets to displaying wallet balances or saying connected in the status bar...

Thanks

Did you install 0.89.99.10?  It was just posted yesterday.

Since I messed a bit with the DB ops, go ahead and do a rebuild if you don't mind waiting for it.  From the help menu "Rebuild and Rescan Databases".  Let me know if you have the same problem after that.

I don't see that option under the help menu. Do I have to be in expert mode?



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 11, 2013, 03:05:07 AM
Okay. Mr. goatpig, let me know if you have a new XP build for me and others to test. I have a (almost) clean install of XP SP3, and I keep it that way.

Working to resolve the current Windows issue, this should give me a clue as off what's wrong with the WinXP build.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Portnoy on November 11, 2013, 03:07:04 AM
Is there anything that can be done when it is stuck at "Build Databases and Scan - 62% 15 seconds"?
The 'Transactions' tab is greyed out; the lower right status bar says connected and seems to show
the correct number of blocks; the wallets all display the correct balances( haven't tried any
transactions to see if they update correctly ).

I shut it down and restarted it several times and each time soon after starting it gets to a point where
it is displaying properly; the transaction tab is accessible and scrollable and everything seems to be
working properly and then after a short while it switches to the Dashboard tab and says it is not
connected ( even though the text in the status bar still says it is ) and then after a few minutes it goes
back to that "Build Databases and Scan - 62% 15 seconds", like I describe above, and just stays like that...

This is with ArmorySetup-0.89.99.8-beta_win32.exe
on Windows 7 64-bit.

The latest test version starts for me but never even gets to displaying wallet balances or saying connected in the status bar...

Thanks

Did you install 0.89.99.10?  It was just posted yesterday.

Since I messed a bit with the DB ops, go ahead and do a rebuild if you don't mind waiting for it.  From the help menu "Rebuild and Rescan Databases".  Let me know if you have the same problem after that.

I don't see that option under the help menu. Do I have to be in expert mode?


Yes I installed 0.89.99.10 and tried it and then uninstalled it using the control panel
and reinstalled 0.89.99.8.

I am now in expert mode and under the help menu it still just lists the 3 choices:
About Armory
Armory Version...
Revert All Settings


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 11, 2013, 03:20:31 AM
Yes I installed 0.89.99.10 and tried it and then uninstalled it using the control panel
and reinstalled 0.89.99.8.

I am now in expert mode and under the help menu it still just lists the 3 choices:
About Armory
Armory Version...
Revert All Settings

Those three options were added in 0.89.99.10. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Portnoy on November 11, 2013, 03:37:04 AM
Yes I installed 0.89.99.10 and tried it and then uninstalled it using the control panel
and reinstalled 0.89.99.8.

I am now in expert mode and under the help menu it still just lists the 3 choices:
About Armory
Armory Version...
Revert All Settings

Those three options were added in 0.89.99.10. 

Hmm...
Well I reinstalled 0.89.99.8 and that is what displays in the left side of the client now: "Armory 0.89.99.8 / Expert"
When I choose that 'About Armory' option it displays 0.89.99.8-beta as well.
When I choose 'Armory Version' it says I am in offline mode and can't retrieve the version from the internet, even though the status bar says I am "Connected (268942 blocks)". 

Now, after another restart it seems stuck at "Initializing Bitcoin Engine"... but all the wallets display their balances and the status bar saying what it says above:
"Connected (268942 blocks)"




Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 11, 2013, 03:39:31 AM
Yes I installed 0.89.99.10 and tried it and then uninstalled it using the control panel
and reinstalled 0.89.99.8.

I am now in expert mode and under the help menu it still just lists the 3 choices:
About Armory
Armory Version...
Revert All Settings

Those three options were added in 0.89.99.10. 

Hmm...
Well I reinstalled 0.89.99.8 and that is what displays in the left side of the client now: "Armory 0.89.99.8 / Expert"
When I choose that 'About Armory' option it displays 0.89.99.8-beta as well.
When I choose 'Armory Version' it says I am in offline mode and can't retrieve the version from the internet, even though the status bar says I am "Connected (268942 blocks)". 

Now, after another restart it seems stuck at "Initializing Bitcoin Engine"... but all the wallets display their balances and the status bar saying what it says above:
"Connected (268942 blocks)"


Very strange behavior, can you send me a log file?  Personally I've never seen it show connected & balances, but not also say "Armory is Online" on the dashboard.  It's almost like you somehow have a mixture of multiple versions...

Also, you should consider running Bitcoin-Qt yourself, and uncheck the first checkbox in the settings (about letting Armory run it for you).  Then try again -- sometimes it just doesn't do the auto-bitcoind well..


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: eid on November 11, 2013, 03:48:31 AM

If you are on 64-bit Ubuntu-Debian, please try it and let me know if it works for you the same as building it yourself.




It installed and works fine on my Ubuntu 64.


Thanks for all the work.    :)




eid


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Portnoy on November 11, 2013, 03:51:28 AM
Yes I installed 0.89.99.10 and tried it and then uninstalled it using the control panel
and reinstalled 0.89.99.8.

I am now in expert mode and under the help menu it still just lists the 3 choices:
About Armory
Armory Version...
Revert All Settings

Those three options were added in 0.89.99.10. 

Hmm...
Well I reinstalled 0.89.99.8 and that is what displays in the left side of the client now: "Armory 0.89.99.8 / Expert"
When I choose that 'About Armory' option it displays 0.89.99.8-beta as well.
When I choose 'Armory Version' it says I am in offline mode and can't retrieve the version from the internet, even though the status bar says I am "Connected (268942 blocks)". 

Now, after another restart it seems stuck at "Initializing Bitcoin Engine"... but all the wallets display their balances and the status bar saying what it says above:
"Connected (268942 blocks)"


Very strange behavior, can you send me a log file? 

Where would you like me to send it?

Quote
Personally I've never seen it show connected & balances, but not also say "Armory is Online" on the dashboard.  It's almost like you somehow have a mixture of multiple versions...

Also, you should consider running Bitcoin-Qt yourself, and uncheck the first checkbox in the settings (about letting Armory run it for you).  Then try again -- sometimes it just doesn't do the auto-bitcoind well..

I did that and it seemed to start okay and quicker than it ever has before. It has been running for close to 10 minutes now and everything seems to be displayed correctly ( transaction tab accessible and scrollable ) but that Help menu still has those 3 choices you said are from the latest version.

Now that it seems to be running alright I am kinda reluctant to uninstall this version and try 0.89.99.10 again.   :-\

Thanks for the assistance, hope my feedback helps.
 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 11, 2013, 06:19:28 AM
If anyone has experienced the disappearing tx behavior, where a zero-conf tx shows up in the history but then disappears when it it's included in a block... please send me your log file!  And especially if you remember when it happened, so I can try to locate an error message in the log file.  The problem is that I'm not sure there even is an error message at all.  So, if I don't know where to look I don't know for sure if it's there or not.

I have some strong leads on this bug.  But I'll have to reproduce it eventually, to know for sure if I fixed it!  If anyone can reproduce it reliably, any info about that would be fantastic.  (I've definitely seen it once before, but hoped it might be fixed with some of the other DB updates).

Send all log files to:  support@bitcoinarmory.com


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: jbreher on November 11, 2013, 07:09:05 AM

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.app.0.89.99.9-testing.tar.gz

Please test it on your OSX system.  

Nope.

I was one of the folk who was experiencing silent termination. I'm on 10.7.5. At least now I get a failure indication. Let me know if you can use the contents of what I got in Mac's Problem Report tool.

Are there any particular logs that may be of interest?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: jbreher on November 11, 2013, 07:23:39 AM
Update:  0.89.99.10-testing

Mac/OSX 0.89.99.10-testing:  Download the ArmoryQt.app for OSX (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory.OSX.app.0.89.99.10-testing.tar.gz)
spired to support it (it's makes much more sense than the bare signatures).

Wasn't immediately clear to me if this was the same. So I dl'd and installed it. It fails the same as my email of an hour or so ago.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: runeks on November 11, 2013, 03:01:37 PM
So I just updated to version 0.89.99.11 (4bd0919d0872f783928189917812c62ce7a02654 on "testing" branch) and I'm still experiencing the problem below. Figured I'd post it in here as well since I haven't gotten a response in the big Armory thread:

The issue is that the "Spendable/Maximum Funds" number doesn't include the coins in my offline (watching-only) wallet. It only counts the coins in my online "pocket change" wallet. If I double click the offline/watching-only wallet, I can see the correct amount for "Spendable/Maximum Funds", but they are not included in the main window.

I just tried transferring 0.5 BTC from my offline wallet to my online wallet, and it worked fine, so there are no issues there. The balance of the offline wallet just isn't showing up in the main window of Online Armory. Here's the log (for version .11):

Code:
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: free -m
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: ['cat', '/proc/cpuinfo']
2013-11-11 15:47 (INFO) -- armoryengine.py:804 -
2013-11-11 15:47 (INFO) -- armoryengine.py:805 -
2013-11-11 15:47 (INFO) -- armoryengine.py:806 -
2013-11-11 15:47 (INFO) -- armoryengine.py:807 - ************************************************************
2013-11-11 15:47 (INFO) -- armoryengine.py:808 - Invoked: /home/rune/Programming/BitcoinArmory/ArmoryQt.py
2013-11-11 15:47 (INFO) -- armoryengine.py:809 - ************************************************************
2013-11-11 15:47 (INFO) -- armoryengine.py:810 - Loading Armory Engine:
2013-11-11 15:47 (INFO) -- armoryengine.py:811 -    Armory Version        : 0.89.99.11
2013-11-11 15:47 (INFO) -- armoryengine.py:812 -    PyBtcWallet  Version  : 1.35
2013-11-11 15:47 (INFO) -- armoryengine.py:813 - Detected Operating system: Linux
2013-11-11 15:47 (INFO) -- armoryengine.py:814 -    OS Variant            : Ubuntu-13.04-raring
2013-11-11 15:47 (INFO) -- armoryengine.py:815 -    User home-directory   : /home/rune
2013-11-11 15:47 (INFO) -- armoryengine.py:816 -    Satoshi BTC directory : /home/rune/.bitcoin/
2013-11-11 15:47 (INFO) -- armoryengine.py:817 -    Armory home dir       : /home/rune/.armory/
2013-11-11 15:47 (INFO) -- armoryengine.py:818 - Detected System Specs    :
2013-11-11 15:47 (INFO) -- armoryengine.py:819 -    Total Available RAM   : 5.83 GB
2013-11-11 15:47 (INFO) -- armoryengine.py:820 -    CPU ID string         : Intel(R) Core(TM)2 Quad  CPU   Q9550  @ 2.83GHz
2013-11-11 15:47 (INFO) -- armoryengine.py:821 -    Number of CPU cores   : 4 cores
2013-11-11 15:47 (INFO) -- armoryengine.py:822 -    System is 64-bit      : True
2013-11-11 15:47 (INFO) -- armoryengine.py:823 -    Preferred Encoding    : UTF-8
2013-11-11 15:47 (INFO) -- armoryengine.py:824 -
2013-11-11 15:47 (INFO) -- armoryengine.py:825 - Network Name: Main Network
2013-11-11 15:47 (INFO) -- armoryengine.py:826 - Satoshi Port: 8333
2013-11-11 15:47 (INFO) -- armoryengine.py:827 - Named options/arguments to armoryengine.py:
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     nettimeout      : 2
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     rescan          : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     leveldbDir      : DEFAULT
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     port            : None
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     interport       : 8223
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     coverageOutputDir: None
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     rebuild         : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     datadir         : DEFAULT
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     offline         : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     satoshiPort     : DEFAULT
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     netlog          : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     keypool         : 100
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     coverageInclude : None
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     forceOnline     : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     logDisable      : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     mtdebug         : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     skipVerCheck    : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     settingsPath    : /home/rune/.armory/ArmorySettings.txt
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     verbosity       : None
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     doDebug         : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     testnet         : False
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     rpcport         : DEFAULT
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     satoshiHome     : DEFAULT
2013-11-11 15:47 (INFO) -- armoryengine.py:829 -     logFile         : /home/rune/.armory/ArmoryQt.py.log.txt
2013-11-11 15:47 (INFO) -- armoryengine.py:830 - Other arguments:
2013-11-11 15:47 (INFO) -- armoryengine.py:833 - ************************************************************
2013-11-11 15:47 (INFO) -- armoryengine.py:1039 - C++ block utilities loaded successfully
2013-11-11 15:47 (INFO) -- armoryengine.py:13426 - Using the asynchronous/multi-threaded BlockDataManager.
2013-11-11 15:47 (INFO) -- armoryengine.py:13427 - Blockchain operations will happen in the background. 
2013-11-11 15:47 (INFO) -- armoryengine.py:13428 - Devs: check TheBDM.getBDMState() before asking for data.
2013-11-11 15:47 (INFO) -- armoryengine.py:13429 - Registering addresses during rescans will queue them for
2013-11-11 15:47 (INFO) -- armoryengine.py:13430 - inclusion after the current scan is completed.
2013-11-11 15:47 (INFO) -- armoryengine.py:11480 - Using settings file: /home/rune/.armory/ArmorySettings.txt
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1640 - loadWalletsAndSettings
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1687 - Loading wallets...
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1735 - Number of wallets read in: 2
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1740 -    Wallet (6QZdwscT):    "offline (Watch)                 "   (No Encryption)
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1740 -    Wallet (2uyc3aSdm):   "new pocket change               "   (Encrypted)
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1318 - Setting up networking...
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1371 - Internet connection is Available: True
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1372 - Bitcoin-Qt/bitcoind is Available: 0
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1373 - The first blk*.dat was Available: True
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1374 - Online mode currently possible:   0
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1381 - startBitcoindIfNecessary
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1412 - setSatoshiPaths
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: ['whereis', 'bitcoind']
2013-11-11 15:47 (INFO) -- armoryengine.py:10998 - "whereis" returned: ['/usr/bin/bitcoind', '/usr/bin/X11/bitcoind']
2013-11-11 15:47 (INFO) -- armoryengine.py:10888 - Found bitcoind in the following places:
2013-11-11 15:47 (INFO) -- armoryengine.py:10890 -    /usr/bin/bitcoind
2013-11-11 15:47 (INFO) -- armoryengine.py:10890 -    /usr/bin/bitcoind
2013-11-11 15:47 (INFO) -- armoryengine.py:10890 -    /usr/bin/X11/bitcoind
2013-11-11 15:47 (INFO) -- armoryengine.py:10892 - Using: /usr/bin/bitcoind
2013-11-11 15:47 (INFO) -- armoryengine.py:11044 - Reading bitcoin.conf file
2013-11-11 15:47 (INFO) -- armoryengine.py:11070 - Setting permissions on bitcoin.conf
2013-11-11 15:47 (INFO) -- armoryengine.py:11125 - Called startBitcoind
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: ['/usr/bin/bitcoind', '-datadir=/home/rune/.bitcoin/']
2013-11-11 15:47 (INFO) -- armoryengine.py:11168 - PID of bitcoind: 24190
2013-11-11 15:47 (INFO) -- armoryengine.py:11169 - PID of armory:   24124
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: ['python', '/home/rune/Programming/BitcoinArmory/guardian.py', '24124', '24190']
2013-11-11 15:47 (INFO) -- ArmoryQt.py:884 - setupUriRegistration
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2013-11-11 15:47 (INFO) -- armoryengine.py:624 - Executing popen: find /home/rune -type f -name "mimeTypes.rdf"
2013-11-11 15:47 (INFO) -- armoryengine.py:11330 - Creating proxy in SDM: host=127.0.0.1, port=8332
2013-11-11 15:47 (INFO) -- ArmoryQt.py:4371 - Dashboard switched to auto-InitSync
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Offline"
2013-11-11 15:47 (INFO) -- ArmoryQt.py:532 - Usermode: Advanced
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1151 - Changing usermode:
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1152 -    From: Advanced
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1160 -      To: Advanced
2013-11-11 15:47 (INFO) -- armoryengine.py:10801 - Signature on signed data block is GOOD!
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1290 - Latest versions:
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1291 -    Satoshi: 0.8.1
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1292 -     Armory: 0.88
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1301 - You are running the latest version!
2013-11-11 15:47 (INFO) -- armoryengine.py:10801 - Signature on signed data block is GOOD!
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1290 - Latest versions:
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1291 -    Satoshi: 0.8.1
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1292 -     Armory: 0.88
2013-11-11 15:47 (WARNING) -- armoryengine.py:11253 - Overriding not-available message. This should happen 0-5 times
2013-11-11 15:47 (WARNING) -- armoryengine.py:11253 - Overriding not-available message. This should happen 0-5 times
2013-11-11 15:47 (WARNING) -- armoryengine.py:11253 - Overriding not-available message. This should happen 0-5 times
2013-11-11 15:47 (INFO) -- ArmoryQt.py:4371 - Dashboard switched to auto-InitSync
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Offline"
2013-11-11 15:47 (INFO) -- ArmoryQt.py:4652 - Starting load blockchain
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1435 - loadBlockchainIfNecessary
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1481 - Setting netmode: 1
2013-11-11 15:47 (INFO) -- armoryengine.py:12445 - Setting online mode: True (wait=False)
2013-11-11 15:47 (INFO) -- armoryengine.py:13366 - Go online requested
2013-11-11 15:47 (INFO) -- armoryengine.py:12887 - Called __startLoadBlockchain()
2013-11-11 15:47 (INFO) -- armoryengine.py:10408 - Connection initiated.  Start handshake
2013-11-11 15:47 (INFO) -- ArmoryQt.py:4480 - Dashboard switched to "Scanning" mode
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-11 15:47 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Scanning"
2013-11-11 15:47 (INFO) -- armoryengine.py:10497 - Received version message from peer:
2013-11-11 15:47 (INFO) -- armoryengine.py:10498 -    Version:     70001
2013-11-11 15:47 (INFO) -- armoryengine.py:10499 -    SubVersion:  /Satoshi:0.8.5/
2013-11-11 15:47 (INFO) -- armoryengine.py:10500 -    TimeStamp:   1384181265
2013-11-11 15:47 (INFO) -- armoryengine.py:10501 -    StartHeight: 269045
2013-11-11 15:47 (INFO) -- armoryengine.py:10679 - Handshake finished, connection open!
2013-11-11 15:47 (INFO) -- armoryengine.py:10801 - Signature on signed data block is GOOD!
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1290 - Latest versions:
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1291 -    Satoshi: 0.8.1
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1292 -     Armory: 0.88
2013-11-11 15:47 (INFO) -- ArmoryQt.py:1301 - You are running the latest version!
2013-11-11 15:47 (INFO) -- ArmoryQt.py:4572 - Satoshi Version: Curr: 805000, Latest: 801000
2013-11-11 15:48 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online"
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-11 15:48 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online"
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-11 15:48 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 6QZdwscT
2013-11-11 15:48 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 2uyc3aSdm
2013-11-11 15:48 (INFO) -- ArmoryQt.py:1926 - Current block number: 269046
2013-11-11 15:48 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online"
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-11 15:48 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online"
2013-11-11 15:48 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 11, 2013, 03:30:51 PM
So I just updated to version 0.89.99.11 (4bd0919d0872f783928189917812c62ce7a02654 on "testing" branch) and I'm still experiencing the problem below. Figured I'd post it in here as well since I haven't gotten a response in the big Armory thread:

The issue is that the "Spendable/Maximum Funds" number doesn't include the coins in my offline (watching-only) wallet. It only counts the coins in my online "pocket change" wallet. If I double click the offline/watching-only wallet, I can see the correct amount for "Spendable/Maximum Funds", but they are not included in the main window.

I just tried transferring 0.5 BTC from my offline wallet to my online wallet, and it worked fine, so there are no issues there. The balance of the offline wallet just isn't showing up in the main window of Online Armory. Here's the log (for version .11):


runeks, I probably forgot to respond to your other post.  Sorry about that. 

The problem is either

(1) Change the "filter" in the bottom-left of the main window to show "All wallets" instead of "My wallets"
(2) Go into wallet properties, and changed the "Belongs to" field and check that the wallet is "mine"

This is to avoid users importing malicious wallets and thinking the balance belongs to them.  They have to do a little bit of work for Armory to show them the balance.  Hope that's the issue.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: runeks on November 11, 2013, 05:07:35 PM
So I just updated to version 0.89.99.11 (4bd0919d0872f783928189917812c62ce7a02654 on "testing" branch) and I'm still experiencing the problem below. Figured I'd post it in here as well since I haven't gotten a response in the big Armory thread:

The issue is that the "Spendable/Maximum Funds" number doesn't include the coins in my offline (watching-only) wallet. It only counts the coins in my online "pocket change" wallet. If I double click the offline/watching-only wallet, I can see the correct amount for "Spendable/Maximum Funds", but they are not included in the main window.

I just tried transferring 0.5 BTC from my offline wallet to my online wallet, and it worked fine, so there are no issues there. The balance of the offline wallet just isn't showing up in the main window of Online Armory. Here's the log (for version .11):


runeks, I probably forgot to respond to your other post.  Sorry about that. 

The problem is either

(1) Change the "filter" in the bottom-left of the main window to show "All wallets" instead of "My wallets"
(2) Go into wallet properties, and changed the "Belongs to" field and check that the wallet is "mine"

This is to avoid users importing malicious wallets and thinking the balance belongs to them.  They have to do a little bit of work for Armory to show them the balance.  Hope that's the issue.
Thanks. That was exactly it.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Dragooon on November 11, 2013, 05:13:40 PM
Awesome! This version is actually opening up in OS X Mavericks (previous one was giving me some system python library problems), seems to be okay so far (a few crashes but it works)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.8)
Post by: pvz on November 11, 2013, 08:41:57 PM
Someone just reported a problem with "Too many open files" when running on Ubuntu 12.04, 32-bit.

I have the problems on a 13.04 32-bit Ubuntu system.
As mentioned before the "sudo sysctl -w fs.file-max=5000000" still gives the error: "socket.error: [Errno 24] Too many open files".

Side note: when it breaks the GUI (Qt) still keeps running without any notification. I expect a notification is desirable.

After a lot of search and a lot of trying I found out that ulimit did the trick for me.
Add to /etc/security/limits.conf:
*                soft    nofile          65535
*                hard    nofile          65535
Reboot.
Start Armory again (now without the socket.error)

On my intel i5 with Ubuntu 13.10 64-bit the problem does not arise, even with the standard (ulimit -n = 1024).

Reference: http://posidev.com/blog/2009/06/04/set-ulimit-parameters-on-ubuntu/

If you have a fix for this and want to run some tests, please let me know.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 11, 2013, 09:07:43 PM
@els & anyone else having problems with the windows build:

I just noticed I file missing from the package.  Both in the installer and the standalone.  I have added that file (msvcp90.dll) to the standalone directory and re-zipped it up for you:

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmoryStandalone_0.89.99.10_w_msvcp90.zip

Please try again.  I actually have a strong feeling that will resolve it.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Rogue Star on November 12, 2013, 01:10:47 AM
@els & anyone else having problems with the windows build:

I just noticed I file missing from the package.  Both in the installer and the standalone.  I have added that file (msvcp90.dll) to the standalone directory and re-zipped it up for you:

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmoryStandalone_0.89.99.10_w_msvcp90.zip

Please try again.  I actually have a strong feeling that will resolve it.

I tried the updated package. The file you added is there, but still no dice. Thanks for the effort Alan.

Code:
(CRITICAL) armoryengine.pyc:1041 - C++ block utilities not available.
(CRITICAL) armoryengine.pyc:1042 -    Make sure that you have the SWIG-compiled modules
(CRITICAL) armoryengine.pyc:1043 -    in the current directory (or added to the PATH)
(CRITICAL) armoryengine.pyc:1044 -    Specifically, you need:
(CRITICAL) armoryengine.pyc:1045 -        CppBlockUtils.py     and
(CRITICAL) armoryengine.pyc:1049 -        _CppBlockUtils.pyd
(ERROR) Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.

Error in sys.excepthook:
Traceback (most recent call last):
  File "armoryengine.pyc", line 617, in logexcept_override
AttributeError: 'NoneType' object has no attribute '__excepthook__'

Original exception was:
Traceback (most recent call last):
  File "ArmoryQt.py", line 31, in <module>
  File "armoryengine.pyc", line 1037, in <module>
  File "CppBlockUtils.pyc", line 26, in <module>
  File "CppBlockUtils.pyc", line 18, in swig_import_helper
  File "_CppBlockUtils.pyc", line 12, in <module>
  File "_CppBlockUtils.pyc", line 10, in __load
ImportError: DLL load failed: The specified module could not be found.

FYI, there is a log file in the package which threw me for a bit of loop since it had some error lines that I thought were new.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 12, 2013, 02:28:23 AM
Windows users: The load error was due to the use of pthread_win32 to support pthreads on Windows (pthreadVC2.dll). The DLL is built on some dependencies found in the .NET Framework SDK. As a result I ported pthreads myself and the error is fixed.

I am now in quite a predicament with WinXP, as it doesn't support condition variables (gg MS). I'll have to hack my way through it, and I still have a lot on my queue, so WinXP users, you'll have to wait some more ='(.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Dabs on November 12, 2013, 03:46:19 AM
I'm patient. :) I can wait.

BTW, how hard is this to port to an alt-coin?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 12, 2013, 04:11:17 AM
BTW, how hard is this to port to an alt-coin?

As in mod Armory to run on an alt coin?

Depends on much the txn and block rules have been modified. There's also the matter of the client API. Assuming they don't use bitcoind like JSON packets, you need to port that part too.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Dabs on November 12, 2013, 04:27:23 AM
Specifically, I'm looking at TagCoin. An exchange opened up in my country and I plan to hold a bunch of it. Dunno if I want it all in cold storage though, as it has a Proof of Stake mining part, where it's a good idea to just keep the client running.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 12, 2013, 04:59:26 AM
Never heard of that coin, can't really help you there =O


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Dabs on November 12, 2013, 05:42:27 AM
Never heard of that coin, can't really help you there =O
Yeah, it's new. But it's being backed by some rich bald dude who now lives in my country. He's running a business around it, but he's letting the coin grow on it's own and won't mine it. It's scrypt.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 12, 2013, 04:36:58 PM
Due to popular demand and the fact that I needed more tests for the fragmented backups, anyway:

https://dl.dropboxusercontent.com/u/1139081/BitcoinImg/dlgFragTester_sm.png

I refactored some of our unit-test code so that it could be used directly into the fragmented backup tester. Should have this implemented along with message sign&verify very soon!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 12, 2013, 10:43:54 PM
Windows users!

Thanks again to goatpig.  He made us a custom port of one of the leveldb DB dependencies and it appears it may have fixed the loading issues.

els & Rogue Star:  please try again!

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.12-beta_win32.exe


P.S. - This version also includes the fragmented backup tester.  Try it out!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Rogue Star on November 13, 2013, 12:02:40 AM
Windows users!

Thanks again to goatpig.  He made us a custom port of one of the leveldb DB dependencies and it appears it may have fixed the loading issues.
Looks good so far, it was great to see the splash screen come up. It's starting at 98% sync with the network now, I'll update my post if I run into any problems or have any additional comments. Thanks goatpig and Alan!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Eylrid on November 13, 2013, 01:05:59 AM
Windows users!

Thanks again to goatpig.  He made us a custom port of one of the leveldb DB dependencies and it appears it may have fixed the loading issues.

els & Rogue Star:  please try again!

https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.12-beta_win32.exe


P.S. - This version also includes the fragmented backup tester.  Try it out!

I'm on Windows Vista 32-bit. I'm still getting this error:

Code:
Traceback (most recent call last):
  File "ArmoryQt.py", line 22, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: A dynamic link library (DLL) initialization routine failed.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 13, 2013, 02:04:47 AM
Windows users!

Thanks again to goatpig.  He made us a custom port of one of the leveldb DB dependencies and it appears it may have fixed the loading issues.
Looks good so far, it was great to see the splash screen come up. It's starting at 98% sync with the network now, I'll update my post if I run into any problems or have any additional comments. Thanks goatpig and Alan!

By the way, you might have to use "Help"->"Rebuild and Rescan Databases".  Some of the database behavior changed ever so slightly since 0.89.99.3.  It may not be necessary, but I wouldn't be surprised if it cleared up any weird/buggy behavior in the app.

I'm on Windows Vista 32-bit. I'm still getting this error:

Code:
Traceback (most recent call last):
  File "ArmoryQt.py", line 22, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: A dynamic link library (DLL) initialization routine failed.

Unfortunately, I don't think this is going to work on Vista.   The same effort required to get it working on XP would be required by Vista (goat: correct me if that's wrong).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 13, 2013, 02:14:18 AM
Unfortunately, I don't think this is going to work on Vista.   The same effort required to get it working on XP would be required by Vista (goat: correct me if that's wrong).

There was explicit notes on the lack of WinXP compatibility with the code I used, but nothing about Windows Vista. Please install .NET framework 4.5 and tell me if it works. I'll investigate that matter.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Rogue Star on November 13, 2013, 04:00:46 AM
By the way, you might have to use "Help"->"Rebuild and Rescan Databases".  Some of the database behavior changed ever so slightly since 0.89.99.3.  It may not be necessary, but I wouldn't be surprised if it cleared up any weird/buggy behavior in the app.
I did have a built database in my app data I was keeping around for when Armory was fixed. It looks like it decided to rebuild it automatically. The reason I know this aside from the progress bar starting at 0% is because my virtual disk was starting to get full and when I was checking to see if I was running out of space and a lot of space was suddenly available.

Here are some stats in case you are interested. First run took 33 mins to sync to the network from 98% and the database took over an hour to rebuild the database (I wasn't able to finish timing it accurately). The second run took a little over 2 minutes to sync the 1 incoming block and scan the DB. I have 4 AMD cores at 4GHz allocated to the VM. I didn't see the memory usage go over 300 MB while I was watching it.

I feel as though the Bitcoin sync was primarily network bound, but the database build & scan seemed like it might have been IO bound and benefited from residing in memory a bit more. At least the 4 cores were never running full tilt perhaps varying between 35%-65% across all 4. Then again, I'm not sure I trust task manager, it seems threads jumping across cores cause it to average out the utilization on the graphs.

Looks like a good build for Win7 users, thanks again!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: els on November 13, 2013, 06:49:00 AM
Windows users!

Thanks again to goatpig.  He made us a custom port of one of the leveldb DB dependencies and it appears it may have fixed the loading issues.
Looks good so far, it was great to see the splash screen come up. It's starting at 98% sync with the network now, I'll update my post if I run into any problems or have any additional comments. Thanks goatpig and Alan!

same for me on Win 7 Home Premium.  looking good!  will report when sync'd up.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: els on November 13, 2013, 08:08:32 AM
Windows users!

Thanks again to goatpig.  He made us a custom port of one of the leveldb DB dependencies and it appears it may have fixed the loading issues.
Looks good so far, it was great to see the splash screen come up. It's starting at 98% sync with the network now, I'll update my post if I run into any problems or have any additional comments. Thanks goatpig and Alan!

same for me on Win 7 Home Premium.  looking good!  will report when sync'd up.

online, with balances, quick check looks great!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Eylrid on November 13, 2013, 03:46:28 PM
There was explicit notes on the lack of WinXP compatibility with the code I used, but nothing about Windows Vista. Please install .NET framework 4.5 and tell me if it works. I'll investigate that matter.

I tried that. It didn't work.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 14, 2013, 01:32:34 AM


Linux 32-bit Users:

I just built a version that I believe works on 32-bit Linux without the "Too many open files" error.  Either build the latest "testing" branch, or download the debian package (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/armory_0.89.99.13-testing_i386.deb).   If you still get the error, you can manually set the number of files LevelDB is allowed to open using the --maxfiles=X argument when you run it.  I have set it to 75 for (Linux && 32bit), but I suppose it might actually need to be lower for some systems (though I doubt it).    My testing shows that it doesn't make a huge difference in terms of speed of database building or scanning.  I was tempted to just do it for all OS/arch.  Meh.  Please let me know if it works. 

Tomorrow i should 0.89.99.14 which includes CircusPeanut's integration message signing&verifiaction (created under a bounty by JackJack).  That may be one of the last testing versions, unless more people pop up with serious issues.  It appears to work pretty reliably on all OS except OSX, and there's nothing I can do about that right now (it appears to be a a problem with OSX 10.9 + PyQt (https://groups.google.com/forum/#!topic/eventandtaskmanager/L636sUwZudY), we might just have to wait it out). 



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: picobit on November 14, 2013, 07:44:20 AM
There also seems to be an issue with LevelDB and OS X.  Armory crashed, and could not restart, it claimed that the database was corrupted.  It could start in offline mode, and I could ask it to rebuild the database, but unfortunately Armory looks at the database before rebuilding it, and it then crashes.  Removing the database directory works, of course.

Code:
-INFO  - 1384414404: (BlockUtils.cpp:1570) SetBtcNetworkParams
-INFO  - 1384414404: (BlockUtils.cpp:3580) Executing: doInitialSyncOnLoad_Rebuild
-INFO  - 1384414404: (BlockUtils.cpp:3604) Number of registered addr: 998
-WARN  - 1384414404: (leveldb_wrapper.cpp:31) ***LevelDB Error: Corruption: no meta-nextfile entry in descriptor
-ERROR - 1384414404: (leveldb_wrapper.cpp:168) Failed to open database! DB: 1

I suspect it is a LevelDB problem rather than an Armory problem, for Bitcoin-Qt had reported database corruption a few hours earlier, and I have also seen Bitcoin-Qt report that on my previous MacBook.


EDIT:  Yes, there are leveldb corruption problems:
https://code.google.com/p/leveldb/issues/detail?id=197


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 14, 2013, 10:11:15 AM
Here's a new tentative build to try and get Armory running on Vista and XP.

Disclaimer: This my build (goatpig), not etotheipi's. This is only for testing purpose on older Windows platforms. A lot of optimizations have been taken out in an attempt to achieve a failsafe build, so this will be slow. Starting Armory in offline mode is enough to prove compatibility. Adventurous ones, you may wanna try and build the DB (at your own risk)

https://mega.co.nz/#!0chE2J4C!RoE8WUfmPPqU1HStumsfh3bKGtJPu-toxzRhcM7_zVY


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Eylrid on November 14, 2013, 03:56:21 PM
Here's a new tentative build to try and get Armory running on Vista and XP.

Disclaimer: This my build (goatpig), not etotheipi's. This is only for testing purpose on older Windows platforms. A lot of optimizations have been taken out in an attempt to achieve a failsafe build, so this will be slow. Starting Armory in offline mode is enough to prove compatibility. Adventurous ones, you may wanna try and build the DB (at your own risk)

https://mega.co.nz/#!0chE2J4C!RoE8WUfmPPqU1HStumsfh3bKGtJPu-toxzRhcM7_zVY

That worked.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: goatpig on November 14, 2013, 03:58:44 PM
Here's a new tentative build to try and get Armory running on Vista and XP.

Disclaimer: This my build (goatpig), not etotheipi's. This is only for testing purpose on older Windows platforms. A lot of optimizations have been taken out in an attempt to achieve a failsafe build, so this will be slow. Starting Armory in offline mode is enough to prove compatibility. Adventurous ones, you may wanna try and build the DB (at your own risk)

https://mega.co.nz/#!0chE2J4C!RoE8WUfmPPqU1HStumsfh3bKGtJPu-toxzRhcM7_zVY

That worked.

Vista or XP?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Eylrid on November 14, 2013, 04:09:42 PM

Vista


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: Portnoy on November 14, 2013, 06:09:34 PM
Here's a new tentative build to try and get Armory running on Vista and XP.

Disclaimer: This my build (goatpig), not etotheipi's. This is only for testing purpose on older Windows platforms. A lot of optimizations have been taken out in an attempt to achieve a failsafe build, so this will be slow. Starting Armory in offline mode is enough to prove compatibility. Adventurous ones, you may wanna try and build the DB (at your own risk)

https://mega.co.nz/#!0chE2J4C!RoE8WUfmPPqU1HStumsfh3bKGtJPu-toxzRhcM7_zVY

Still not working on XP. Same error message in the log.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: pvz on November 14, 2013, 06:21:40 PM
Linux 32-bit Users
Works! Not any noticeable difference in time.
Also adding (read-only) wallets (rescan) works without any errors.
Noticed the message during startup stating max 75 connections.
Thank you Allan!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: etotheipi on November 14, 2013, 06:58:06 PM
Version 0.89.99.14-testing: Now with message signing and fragmented backup tester!

Ubuntu/Debian 32-bit (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/armory_0.89.99.14-testing_i386.deb)
Ubuntu/Debian 64-bit (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/armory_0.89.99.14-testing_amd64.deb)
Mac/OSX (flaky with 10.9) (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/Armory_0.89.99.14-testing_OSX.app.tar.gz)
Windows (32- and 64-bit) (https://dl.dropboxusercontent.com/u/1139081/ArmoryTestingReleases/ArmorySetup-0.89.99.14-testing.exe)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Allaboutbit on November 14, 2013, 08:16:37 PM
I've been running armory on osx for awhile now. Initially before there was a pre built app, I built it from the testing source on github following the instructions on the site. It worked fine. Then v9 and v10 came out as pre built app. It still worked fine. Now with v14 and armory will not load. Here is a paste from the log:

2013-11-14 14:44 (INFO) -- armoryengine.py:625 - Executing popen: sysctl hw.memsize
2013-11-14 14:44 (INFO) -- armoryengine.py:625 - Executing popen: sysctl -n machdep.cpu.brand_string
2013-11-14 14:44 (INFO) -- armoryengine.py:806 -
2013-11-14 14:44 (INFO) -- armoryengine.py:807 -
2013-11-14 14:44 (INFO) -- armoryengine.py:808 -
2013-11-14 14:44 (INFO) -- armoryengine.py:809 - ************************************************************
2013-11-14 14:44 (INFO) -- armoryengine.py:810 - Invoked: /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py
2013-11-14 14:44 (INFO) -- armoryengine.py:811 - ************************************************************
2013-11-14 14:44 (INFO) -- armoryengine.py:812 - Loading Armory Engine:
2013-11-14 14:44 (INFO) -- armoryengine.py:813 -    Armory Version        : 0.89.99.14
2013-11-14 14:44 (INFO) -- armoryengine.py:814 -    PyBtcWallet  Version  : 1.35
2013-11-14 14:44 (INFO) -- armoryengine.py:815 - Detected Operating system: MacOSX
2013-11-14 14:44 (INFO) -- armoryengine.py:816 -    OS Variant            : ('10.8.5', ('', '', ''), 'x86_64')
2013-11-14 14:44 (INFO) -- armoryengine.py:817 -    User home-directory   : /Users/xxxx/Library/Application Support
2013-11-14 14:44 (INFO) -- armoryengine.py:818 -    Satoshi BTC directory : /Users/xxxx/Library/Application Support/Bitcoin/
2013-11-14 14:44 (INFO) -- armoryengine.py:819 -    Armory home dir       : /Users/xxxx/Library/Application Support/Armory/
2013-11-14 14:44 (INFO) -- armoryengine.py:820 - Detected System Specs    :
2013-11-14 14:44 (INFO) -- armoryengine.py:821 -    Total Available RAM   : 16.00 GB
2013-11-14 14:44 (INFO) -- armoryengine.py:822 -    CPU ID string         : Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz

2013-11-14 14:44 (INFO) -- armoryengine.py:823 -    Number of CPU cores   : 8 cores
2013-11-14 14:44 (INFO) -- armoryengine.py:824 -    System is 64-bit      : True
2013-11-14 14:44 (INFO) -- armoryengine.py:825 -    Preferred Encoding    : US-ASCII
2013-11-14 14:44 (INFO) -- armoryengine.py:826 -
2013-11-14 14:44 (INFO) -- armoryengine.py:827 - Network Name: Main Network
2013-11-14 14:44 (INFO) -- armoryengine.py:828 - Satoshi Port: 8333
2013-11-14 14:44 (INFO) -- armoryengine.py:829 - Named options/arguments to armoryengine.py:
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     maxOpenFiles    : 0
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     nettimeout      : 2
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     rescan          : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     leveldbDir      : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     port            : None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     interport       : 8223
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     coverageOutputDir: None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     rebuild         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     datadir         : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     offline         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     satoshiPort     : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     netlog          : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     keypool         : 100
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     coverageInclude : None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     forceOnline     : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     logDisable      : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     mtdebug         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     skipVerCheck    : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     settingsPath    : /Users/xxxx/Library/Application Support/Armory/ArmorySettings.txt
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     verbosity       : None
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     doDebug         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     testnet         : False
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     rpcport         : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     satoshiHome     : DEFAULT
2013-11-14 14:44 (INFO) -- armoryengine.py:831 -     logFile         : /Users/xxxx/Library/Application Support/Armory/ArmoryQt.py.log.txt
2013-11-14 14:44 (INFO) -- armoryengine.py:832 - Other arguments:
2013-11-14 14:44 (INFO) -- armoryengine.py:835 - ************************************************************
2013-11-14 14:44 (INFO) -- armoryengine.py:1041 - C++ block utilities loaded successfully
2013-11-14 14:44 (INFO) -- armoryengine.py:13507 - Using the asynchronous/multi-threaded BlockDataManager.
2013-11-14 14:44 (INFO) -- armoryengine.py:13508 - Blockchain operations will happen in the background. 
2013-11-14 14:44 (INFO) -- armoryengine.py:13509 - Devs: check TheBDM.getBDMState() before asking for data.
2013-11-14 14:44 (INFO) -- armoryengine.py:13510 - Registering addresses during rescans will queue them for
2013-11-14 14:44 (INFO) -- armoryengine.py:13511 - inclusion after the current scan is completed.
2013-11-14 14:44 (ERROR) -- Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 42, in <module>
    from dialogs.toolsDialogs import MessageSigningVerificationDialog
ImportError: No module named dialogs.toolsDialogs

Can you please help me figure out why it's not working anymore now?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 14, 2013, 08:18:04 PM
Ack!  The installer script didn't copy over all the files, whoops!

I'll work on that...

(updated the first post with the old 0.89.99.10 OSX app until I fix that)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 14, 2013, 08:48:01 PM
Ack!  The installer script didn't copy over all the files, whoops!

I'll work on that...

(updated the first post with the old 0.89.99.10 OSX app until I fix that)

Well that was easy.  Just rebuilt 0.89.99.14-testing on OSX with the updated Makefile and re-posted it to the main thread.  Please try it again!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Allaboutbit on November 14, 2013, 08:59:21 PM
Ack!  The installer script didn't copy over all the files, whoops!

I'll work on that...

(updated the first post with the old 0.89.99.10 OSX app until I fix that)

Well that was easy.  Just rebuilt 0.89.99.14-testing on OSX with the updated Makefile and re-posted it to the main thread.  Please try it again!

Awesome. Thanks it works perfect now and loads in less than 30 seconds.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Rampion on November 14, 2013, 09:32:58 PM
So happy that OSX builds are included by default... Great job Alan, godspeed!!!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: pvz on November 14, 2013, 10:03:02 PM
Linux 64bit .deb does not start.
Next error after manual start:
Code:
sudo python /usr/lib/armory/ArmoryQt.py %u

(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 42, in <module>
    from dialogs.toolsDialogs import MessageSigningVerificationDialog
ImportError: No module named dialogs.toolsDialogs

EDIT: same error like reported a few posts earlier.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 14, 2013, 10:04:26 PM
Linux 64bit .deb do not start.
Next error after manual start:
Code:
sudo python /usr/lib/armory/ArmoryQt.py %u

(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 42, in <module>
    from dialogs.toolsDialogs import MessageSigningVerificationDialog
ImportError: No module named dialogs.toolsDialogs


Argh, same problem as on OSX.  I must've accidentally tested the new version in the development directory instead of through the installer.

Fix coming in 3... 2...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 14, 2013, 10:14:18 PM
Fix coming in 3... 2...

... 1!

Top post links now link to the fixed .deb installers!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: pvz on November 14, 2013, 10:18:40 PM
Top post links now link to the fixed .deb installers!
Check! Works.
Thanks Alan!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 15, 2013, 03:00:52 AM
New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug] (https://bitcointalk.org/index.php?topic=334263.msg3587171#msg3587171)

Help me test, make money!  


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.10)
Post by: els on November 15, 2013, 07:08:46 AM
Here's a new tentative build to try and get Armory running on Vista and XP.

Disclaimer: This my build (goatpig), not etotheipi's. This is only for testing purpose on older Windows platforms. A lot of optimizations have been taken out in an attempt to achieve a failsafe build, so this will be slow. Starting Armory in offline mode is enough to prove compatibility. Adventurous ones, you may wanna try and build the DB (at your own risk)

https://mega.co.nz/#!0chE2J4C!RoE8WUfmPPqU1HStumsfh3bKGtJPu-toxzRhcM7_zVY

Still not working on XP. Same error message in the log.

(finally got the download to complete and) got the same failure on XP 32-bit as well


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: chrisrico on November 15, 2013, 08:24:54 AM
Wow. This latest version is super fast on Windows 7. Like, 15-30 second startup time fast.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: RoadStress on November 16, 2013, 12:10:35 AM
New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug] (https://bitcointalk.org/index.php?topic=334263.msg3587171#msg3587171)

Help me test, make money!  

While i know the risks of using Beta software i just want to be sure of something. Having a paper backup makes me safe from any Armory/wallet problems/bugs/disasters right? Also please tell me how paper wallets work. If i make a paper backup of an encrypted wallet will it require the password when importing the backup or not?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 16, 2013, 12:16:55 AM
New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug] (https://bitcointalk.org/index.php?topic=334263.msg3587171#msg3587171)

Help me test, make money!  

While i know the risks of using Beta software i just want to be sure of something. Having a paper backup makes me safe from any Armory/wallet problems/bugs/disasters right? Also please tell me how paper wallets work. If i make a paper backup of an encrypted wallet will it require the password when importing the backup or not?

I can't go into technical details exactly about how the paper backup works (for time reasons).  The gist of it is that the wallet derives all its private keys in a deterministic (and secure!) manner from a seed.  That seed is what's on the paper backup: root key (and chaincode on wallets created with 0.88.1 and earlier).  That seed can be used to generate trillions of addresses.  You'll get the same trillion addresses the next time you restore from that seed.  The seed is all that matters.

So yes, you are totally protected from your coins being lost due to fire, HDD failure, and forgetting your password.  You do not need your password to use your paper backup.  That's by design: 95% of coin loss I've seen is due to forgetting your password and not having a paper backup.

The "risk of losing coins" is that perhaps Armory computes an address incorrectly and you send money to the wrong address.  Maybe one that can't be recovered by anyone.  I've never seen such a bug in Armory in its two-year history, but other people have done this with other apps and custom scripts.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: goatpig on November 16, 2013, 01:01:55 AM
Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: RoadStress on November 16, 2013, 02:40:09 PM
New bug-bounty thread!


[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug] (https://bitcointalk.org/index.php?topic=334263.msg3587171#msg3587171)

Help me test, make money!  

While i know the risks of using Beta software i just want to be sure of something. Having a paper backup makes me safe from any Armory/wallet problems/bugs/disasters right? Also please tell me how paper wallets work. If i make a paper backup of an encrypted wallet will it require the password when importing the backup or not?

I can't go into technical details exactly about how the paper backup works (for time reasons).  The gist of it is that the wallet derives all its private keys in a deterministic (and secure!) manner from a seed.  That seed is what's on the paper backup: root key (and chaincode on wallets created with 0.88.1 and earlier).  That seed can be used to generate trillions of addresses.  You'll get the same trillion addresses the next time you restore from that seed.  The seed is all that matters.

So yes, you are totally protected from your coins being lost due to fire, HDD failure, and forgetting your password.  You do not need your password to use your paper backup.  That's by design: 95% of coin loss I've seen is due to forgetting your password and not having a paper backup.

The "risk of losing coins" is that perhaps Armory computes an address incorrectly and you send money to the wrong address.  Maybe one that can't be recovered by anyone.  I've never seen such a bug in Armory in its two-year history, but other people have done this with other apps and custom scripts.

So i should keep an encrypted digital backup in hot medias and unencrypted digital backup and paper wallet on cold medias. Got it!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: picobit on November 16, 2013, 03:33:18 PM
So i should keep an encrypted digital backup in hot medias and unencrypted digital backup and paper wallet on cold medias. Got it!
+1

No, +1000 :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Eylrid on November 16, 2013, 06:34:41 PM
Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

This works on Win Vista 32-bit.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Portnoy on November 16, 2013, 09:28:44 PM
Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

This works on Win Vista 32-bit.

It also seems to be working on XP now.   :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: jbreher on November 17, 2013, 02:36:27 AM
Well that was easy.  Just rebuilt 0.89.99.14-testing on OSX with the updated Makefile and re-posted it to the main thread.  Please try it again!

I did. Sadly, same results. Immediate crash. OS X 10.7.5

Code:
Process:         Python [25536]
Path:            /Applications/Armory.app/Contents/MacOS/Python
Identifier:      com.armory.armory
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  bash [25532]

Date/Time:       2013-11-16 19:33:29.217 -0700
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version:  9

Interval Since Last Report:          145305 sec
Crashes Since Last Report:           1
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      2073DD49-7F33-4177-827A-9A4C34ABF7BA

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
-->
    __TEXT                 0000000100000000-0000000100001000 [    4K] r-x/rwx SM=COW  /Applications/Armory.app/Contents/MacOS/Python

Application Specific Information:
objc[25536]: garbage collection is OFF


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: RoadStress on November 17, 2013, 03:23:27 AM
I have installed the latest version 0.89.99.14 over my existing one 0.89.99.8 and now it just can't find my bitcoin installation. Double checked settings and everything seems ok. Suggestions?

Edit: I ran it with default settings(meaning that i'm running the bitcoin-qt client) seems to work just fine so there must be a problem with the "Let Armory run Bitcoin-Qt in the background"
And the loading time now just rock! Great job!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Dragooon on November 17, 2013, 06:44:46 AM
Just as a suggestion, it might be a good idea to not have the root key bolded in print backup for clarity or possible ink spillage. Or perhaps allow it to be customisable?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: goatpig on November 17, 2013, 09:56:01 AM
This works on Win Vista 32-bit.

It also seems to be working on XP now.   :)

Thanks for testing guys. Need a few more tests plz, Win7+ as well =)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: japerry on November 17, 2013, 12:52:34 PM
This works on Win Vista 32-bit.

It also seems to be working on XP now.   :)

Thanks for testing guys. Need a few more tests plz, Win7+ as well =)

And we have a winner! Armory now runs on my XP system also! Thanks Goatpig! Here I come cold wallets!



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: RoadStress on November 17, 2013, 04:07:08 PM
Nobody else having the issue that i have? I even reinstalled and still the same problem.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: goatpig on November 17, 2013, 07:33:04 PM
Nobody else having the issue that i have? I even reinstalled and still the same problem.

Reinstalled bitcoind or Armory? OS?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: RoadStress on November 17, 2013, 07:35:14 PM
Nobody else having the issue that i have? I even reinstalled and still the same problem.

Reinstalled bitcoind or Armory? OS?

Reinstalled Armory. OS: Win7 64bit.

Quote
Edit: I ran it with default settings(meaning that i'm running the bitcoin-qt client) seems to work just fine

I was wrong. I see that i am connected but 0 blocks.

Where can i find an earlier version? 0.89.99.8 was just much better for me :)

Edit: Forgot OS!

Second Edit: Ok now final version works ok if i run bitcoin-qt client! Finally!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: justusranvier on November 17, 2013, 07:52:47 PM
This might add some complexity to the release process, but can you start bundling bitcoind with the OSX version of Armory, since they don't have any other way of getting a precompiled version?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Zomdifros on November 17, 2013, 09:21:10 PM
Armory works great for me on Windows 7 64-bit. I did encounter a nuisance though: If Bitcoin-QT isn't installed in the C:\Program Files\, Armory had trouble locating it. I tried to give the correct location in settings, though that didn't seem to work. I also found it difficult to remove the blockchain from my C drive as Armory keeps it's own copy there (which is a problem when working from an SSD with limited space). The solution was to open command prompt and make symbolic links for both Armory and Bitcoin, though it would have been easier if this could be done from settings.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 17, 2013, 09:29:55 PM
Armory works great for me on Windows 7 64-bit. I did encounter a nuisance though: If Bitcoin-QT isn't installed in the C:\Program Files\, Armory had trouble locating it. I tried to give the correct location in settings, though that didn't seem to work. I also found it difficult to remove the blockchain from my C drive as Armory keeps it's own copy there (which is a problem when working from an SSD with limited space). The solution was to open command prompt and make symbolic links for both Armory and Bitcoin, though it would have been easier if this could be done from settings.

Since Armory doesn't save any registry settings, there's not a good way to signal to it that you want to change your --datadir.   If you move your --datadir, there's no way for Armory to know where it is when you start it.   The only way to do it is really to modify the shortcut as you did.  Technically, all other options could be put in a armory.conf file in the Armory --datadir, but haven't gotten to that yet.  Similarly, I could just write a registry setting for Windows.  Meh.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Dabs on November 18, 2013, 05:26:45 AM
Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

This one seems to be working on my production XP computer. It runs. Version 0.89.99.8-beta according to the about page.

I will test again on my other bare-bones XP laptop.

Now, all I need is to wait for importing and using compressed private keys.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: cp1 on November 18, 2013, 06:22:25 AM
Armory works great for me on Windows 7 64-bit. I did encounter a nuisance though: If Bitcoin-QT isn't installed in the C:\Program Files\, Armory had trouble locating it. I tried to give the correct location in settings, though that didn't seem to work. I also found it difficult to remove the blockchain from my C drive as Armory keeps it's own copy there (which is a problem when working from an SSD with limited space). The solution was to open command prompt and make symbolic links for both Armory and Bitcoin, though it would have been easier if this could be done from settings.

You can change your shortcut to point to your blockchain and where you want the database to be kept:
"C:\Program Files (x86)\Armory-testing\ArmoryQt.exe" --satoshi-datadir=I:\bitcoin --datadir=I:\armory


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: els on November 18, 2013, 06:50:59 AM
Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

This one seems to be working on my production XP computer. It runs. Version 0.89.99.8-beta according to the about page.

I will test again on my other bare-bones XP laptop.

Now, all I need is to wait for importing and using compressed private keys.

runs fine for me on win xp 32-bit and a very vanilla win 7.  both are syncing/building db.  will report if anything comes up, but looks great!!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: goatpig on November 18, 2013, 07:30:13 PM
Thanks for the testing guys =) Keep it up =P


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: itsgoldbaby on November 19, 2013, 06:21:05 PM
Thanks for the testing guys =) Keep it up =P
I just got around to trying out your Win XP build and it works! Thanks for your hard work mate. :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: xzempt on November 19, 2013, 06:23:12 PM
im getting stuck @ 77% scanning transaction history....


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 20, 2013, 07:15:07 AM
Please help me find the disappearing-tx bug!  
I'll give 0.2 BTC to someone who finds the pattern!

I need your help with this one!  I'm going insane trying to figure out the pattern behind this bug.  90% of my tx go through fine.  It seems to only happen when I'm not paying attention.  

Symptoms:

(1) Transaction is created and broadcast
(2) Tx shows up in ledger/history with zero-confirmations, wallet balance is reduced
(3) As soon as the tx is included in a block, the tx disappears completely.  Wallet balance returns to previous value, as if the tx never happened
(4) Restarting Armory doesn't help.  The only way to fix/find it is to do a rescan ("Help"->"Rescan Databases").


What I know about this bug:

(1) I'm fairly certain that the bug only occurs when the transaction has no outputs to any of your wallets.  Every time I've triggered it, has been with a tx that has a single output to an external address (i.e. the target address is not in any of your wallets, and there is no change output).  I suspect the number of inputs doesn't matter, but I think I've only seen it when there was a single input as well.

(2) I think it might be related to freshness of outputs: it may only happen when you are spending outputs that were just received a few confirmations ago.  And I think only without a restart between receiving and spending.

(3) It definitely happened before on a run where I did a rescan.  It may have to do with fresh-rescan-on-load vs read-stored-histories-from-last-load (but I'm somewhat certain this is not a requirement to trigger the bug).

(4) The fee does not appear to matter (seen it with

In order to test this, knowing that you need perfect-sized inputs, you'll need to use coin-control.  Deselect all but one address in the coin-control window, then use the "MAX" button to send the entire input to an external address not part of any of your wallets.  When the tx is in your ledger, you can double click on it to verify that there is only a single output and a blank in the "Wallet ID" column.

This is the last major bug that needs to be fixed before I can do a release.   Once I find a pattern and can reproduce it reliably, I can debug it and verify it's fixed.  Right now I can't reproduce or verify.  Tell me the pattern and you get 0.1 BTC!

P.S. if you want to run Armory on testnet, see the instructions here:  https://bitcointalk.org/index.php?topic=341252.0


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: CircusPeanut on November 20, 2013, 09:47:04 PM
Re: (2) I think it might be related to freshness of outputs: it may only happen when you are spending outputs that were just received a few confirmations ago.  And I think only without a restart between receiving and spending.

When I was able to reproduce it all of the outputs that I was working with were old.

Also, I reproduced the bug, on the first try, but then I had trouble making it happen again.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 20, 2013, 11:42:56 PM
POSTED SIGNED INSTALLERS:

https://bitcoinarmory.com/download/

Since the installers are now posted on the official website, I decided I should go through the effort of offline-signing everything, even though it's not the final release.    You can download the SHA256 hashes file here (now with a note to reduce confusion about which hash function to use):

https://s3.amazonaws.com/bitcoinarmory-releases/armory_sha256sum_hashes_0.89.99.14.txt.asc

Note that the .deb files changed hashes since yesterday, because I took the liberty to GPG-sign (using dpkg-sig) the .deb files.  You can use "dpkg-sig --verify *.deb" to check them.  If the signature is good, you don't need to mess with the hashes file.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 21, 2013, 06:48:06 AM
Please help me find the disappearing-tx bug!  
I'll give 0.2 BTC to someone who finds the pattern!

I need your help with this one!  I'm going insane trying to figure out the pattern behind this bug.  90% of my tx go through fine.  It seems to only happen when I'm not paying attention.  

FOUND!  Bounty off.

Sadly, I actually found this bug yesterday, but thought that its behavior would occur 100% of the time I did some specific behavior.  When I tested and it didn't happen, I assumed that wasn't actually a bug (or the bug).  It turns out that was it after all, but it only triggers under very specific, infrequent conditions.  Frustrating! 

Also, CircusPeanut fixed the restore-backup entry fields misbehaving (putting the cursor in the middle of the input mask fields, instead of at the beginning).  That should remove some extra confusion (a lot of people got really tripped up by that!).

Will be attending to some of the things found in the bug-bounty thread and then will release a final testing version before the official 0.90-beta release.  There are still problems with the release, but at some point I have to just release it.  And this version has more than enough usability to replace 0.88.1 on the website.  Exciting!



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: xephyr on November 22, 2013, 04:32:56 AM
I've been very pleased with 88.1 - no reason to update really - but got curious about the 0.89.99.14-testing version so downloaded it tonite to give it a spin. Wow this new version is fast - once installed with an up to date blockchain it took less than a minute to start up. And RAM used is minimal. Color me impressed:)



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: pvz on November 22, 2013, 06:28:05 AM
Ubuntu 10.4 LTS support.
Installing armory_0.89.99.12-testing_i386.deb gives dependency error: libstdc++6 >= 4.6
On 10.4 LTS the most recent available is 4.4.3
Maybe more dependencies will give this error, but no tools available on this offline machine.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 22, 2013, 06:32:05 AM
Ubuntu 10.4 LTS support.
Installing armory_0.89.99.12-testing_i386.deb gives dependency error: libstdc++6 >= 4.6
On 10.4 LTS the most recent available is 4.4.3
Maybe more dependencies will give this error, but no tools available on this offline machine.

Ack, I should've labeled those better!  Those are 12.04 installers.  I am actually in the process right now of upgrading my release process to include 10.04 and 12.04 installers by default.  AND name them appropriately!  Sorry about that.

Part of 0.89.99.16-testing will be testing the new release scripts, which sign all the debs, create all the offlien bundles, tag and sign the git repo, and compute all the hashes and signs them.  I'm hoping that once I get all the packages compiled and into one place, that it will be one command to do all that from the offline computer (with my GPG key password of course).

This whole release process used to take hours.  Now CircusPeanut got me a painless NSIS install script integrated into MSVS, and with the automatic offline-bundling, getting from compile to signed-release may be a lot faster now.  

Will have a 10.04 offline bundle for you tomorrow morning :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: pvz on November 22, 2013, 07:58:40 AM
...
I am actually in the process right now of upgrading my release process to include 10.04 and 12.04 installers by default.  
...
Will have a 10.04 offline bundle for you tomorrow morning :)
In my search process I just noticed there is only 10.04 support until 2013/05.
Are you sure you want to keep support on 10.04?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Missionary on November 22, 2013, 10:59:52 AM
...
I am actually in the process right now of upgrading my release process to include 10.04 and 12.04 installers by default.  
...
Will have a 10.04 offline bundle for you tomorrow morning :)
In my search process I just noticed there is only 10.04 support until 2013/05.
Are you sure you want to keep support on 10.04?

It does not really matter if the computer is never connected to the internet. However, 12.04 would have support for more devices. The main drawback with 10.04 is that it's not hosted on a very fast server anymore, and finding the ISO is not as straightforward as finding the 12.04.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Kyune on November 22, 2013, 06:14:44 PM
...
I am actually in the process right now of upgrading my release process to include 10.04 and 12.04 installers by default.  
...
Will have a 10.04 offline bundle for you tomorrow morning :)
In my search process I just noticed there is only 10.04 support until 2013/05.
Are you sure you want to keep support on 10.04?
One nice thing about 10.04 is that it will run on really old hardware, including non-PAE CPUs, which allows some otherwise obsolete machines to be used as the offline/cold storage piece of the Armory solution.  (Devices like IBM ThinkPads from the Windows 98 and Windows 2000 era.)  Because 12.04 switched over to using the PAE Linux kernel by default, it is non-trivial to get it to boot on a non-PAE CPU, so removing 10.04 support would probably, as a practical matter, reduce the universe of "spare" hardware that could be used for the Armory cold storage wallet.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 22, 2013, 06:18:42 PM
Also... at this point a lot of people are using 10.04 for their offline computers, and I don't want to tell them "sorry, gotta destroy and rebuild your super-secure system...have fun!"  (including one of my own offline systems :))


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Dabs on November 22, 2013, 09:42:00 PM
That's why I like XP. I've made my offline setup secure. My online version is not, but probably more secure than most other XPs, 7s and 8s.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 22, 2013, 11:09:54 PM
RELEASE SCRIPTS COMPLETE:

These things are bad-ass.  Not only do they sign everything, bundle everything, hash everything (offline), and then verify and upload everything to S3 (online), it prints out a bunch of forum-formatted and HTML links!   

Below I have raw copied the forum-formatted links here after a raw upload to S3.  This may not be perfect [yet], but it's pretty darned close.  Please download things, verify signatures, install and run, etc. 

The two things I'm not sure about:  Vista support, and offline-bundles properly bundled!  Please try it out! 



Try 0.89.99.16-testing!
All installers have offline-signatures, directly in the debs, and in the hashes file

  Armory 0.89.99.16-testing for Windows Vista, 7, 8 (Both 32- and 64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/ArmorySetup-0.89.99.16-beta_win32.exe)
  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_i386.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_i386.deb)
  Armory 0.89.99.16-testing for Mac/OSX 10.8 and 10.9 (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OSX.app.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-64bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-64bit.tar.gz)

  Armory 0.89.99.16-testing: Signed hashes of all installers  (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_sha256sum.txt.asc)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Keefe on November 23, 2013, 02:22:40 AM
RELEASE SCRIPTS COMPLETE:

These things are bad-ass.  Not only do they sign everything, bundle everything, hash everything (offline), and then verify and upload everything to S3 (online), it prints out a bunch of forum-formatted and HTML links!  

Below I have raw copied the forum-formatted links here after a raw upload to S3.  This may not be perfect [yet], but it's pretty darned close.  Please download things, verify signatures, install and run, etc.  

The two things I'm not sure about:  Vista support, and offline-bundles properly bundled!  Please try it out!  



Try 0.89.99.16-testing!
All installers have offline-signatures, directly in the debs, and in the hashes file

  Armory 0.89.99.16-testing for Windows Vista, 7, 8 (Both 32- and 64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/ArmorySetup-0.89.99.16-beta_win32.exe)
  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_i386.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_i386.deb)
  Armory 0.89.99.16-testing for Mac/OSX 10.8 and 10.9 (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OSX.app.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-64bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-64bit.tar.gz)

  Armory 0.89.99.16-testing: Signed hashes of all installers  (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_sha256sum.txt.asc)


The link text doesn't match the filenames for the 64bit offline bundles.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 23, 2013, 03:24:54 AM
The link text doesn't match the filenames for the 64bit offline bundles.

Yup.  I see that now!   Try again:

----- WINDOWS

  Armory 0.89.99.16-testing for Windows Vista, 7, 8 (Both 32- and 64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_win32.exe)

----- Mac/OSX

  Armory 0.89.99.16-testing for Mac/OSX 10.8 and 10.9 (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OSX.app.tar.gz)

----- Ubuntu/Debian

  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_i386.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_i386.deb)

----- Ubuntu/Debian Offline Bundles

  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-64bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-64bit.tar.gz)

----- Signed hashes

  Armory 0.89.99.16-testing: Signed hashes of all installers  (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_sha256sum.txt.asc)



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Keefe on November 23, 2013, 04:03:13 AM
The link text doesn't match the filenames for the 64bit offline bundles.

Yup.  I see that now!   Try again:

----- WINDOWS

  Armory 0.89.99.16-testing for Windows Vista, 7, 8 (Both 32- and 64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_win32.exe)

----- Mac/OSX

  Armory 0.89.99.16-testing for Mac/OSX 10.8 and 10.9 (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OSX.app.tar.gz)

----- Ubuntu/Debian

  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_10.04_i386.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_amd64.deb)
  Armory 0.89.99.16-testing for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_12.04_i386.deb)

----- Ubuntu/Debian Offline Bundles

  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 10.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_10.04-64bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-32bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-32bit.tar.gz)
  Armory 0.89.99.16-testing Offline Bundle for Ubuntu/Debian 12.04-64bit (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_OfflineBundle_12.04-64bit.tar.gz)

----- Signed hashes

  Armory 0.89.99.16-testing: Signed hashes of all installers  (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_sha256sum.txt.asc)



So is this intended to be the "final testing version before the official 0.90-beta release"?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 23, 2013, 04:06:30 AM
So is this intended to be last testing release prior to 0.90-beta?

Barring any showstopping issues, yes.  I plan to have it posted alongside 0.88.1, and if someone has enough RAM, they can still use the old one which may be more reliable for now.  But it seems that this version is working quite well for a lot of people, and 0.88.1 is getting more unreliable, so I have to release it sometime!

Version 0.91 will be tons of polishing, bug fixes, unicode fixes, and optimizations. I expect that that version will edge 0.88.1 on reliability.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: Eylrid on November 23, 2013, 04:34:54 AM

----- WINDOWS

  Armory 0.89.99.16-testing for Windows Vista, 7, 8 (Both 32- and 64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.89.99.16-testing_win32.exe)


Works beautifully on Windows Vista 32-bit.  ;D


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: jbreher on November 23, 2013, 04:54:49 AM
Well, I know you posted Mac OS X 10.8 & 10.9. And I am meager 10.7.5. But things are not improving on this. Seems to die even faster:

Code:
hostname:~ username$ /Applications/Armory.app/Contents/MacOS/Armory 
/Applications/Armory.app/Contents/MacOS/Armory: line 16:  3104 Segmentation fault: 11  $DIRNAME/Python $ARMORYDIR/ArmoryQt.py
hostname:~ username$


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: keewee on November 23, 2013, 06:01:32 AM
Yay! A new version to test. I was having a LOT of stability issues on OS X 10.9 with the .14 version. I'll save the bug report for this version


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: pvz on November 23, 2013, 06:52:15 AM
----- Ubuntu/Debian
Only 10.04 and 12.04 are mentioned.
Is the 12.04 deb/installer compatible with 13.10?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: shapemaker on November 23, 2013, 12:21:32 PM
I recently upgraded from the 0.88 stable to version 0.89.99.14-beta on Windows 7 64-bit.

Looks like the new version created the '%userdir%\AppData\Roaming\Armory\databases\leveldb_blkdata' directory, which now is larger than the original blockchain dir. What's the point in using double the HD space?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: goatpig on November 23, 2013, 01:25:06 PM
I recently upgraded from the 0.88 stable to version 0.89.99.14-beta on Windows 7 64-bit.

Looks like the new version created the '%userdir%\AppData\Roaming\Armory\databases\leveldb_blkdata' directory, which now is larger than the original blockchain dir. What's the point in using double the HD space?

So it doesn't have to hold the full blockchain in the ram. This is a "full implementation", intended for full nodes. This path was opted to reduce overhaul time and limit the code base to debug. There are plans for a lighter version of the DB now that this new code is solid.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: shapemaker on November 23, 2013, 01:59:40 PM
I recently upgraded from the 0.88 stable to version 0.89.99.14-beta on Windows 7 64-bit.

Looks like the new version created the '%userdir%\AppData\Roaming\Armory\databases\leveldb_blkdata' directory, which now is larger than the original blockchain dir. What's the point in using double the HD space?

So it doesn't have to hold the full blockchain in the ram. This is a "full implementation", intended for full nodes. This path was opted to reduce overhaul time and limit the code base to debug. There are plans for a lighter version of the DB now that this new code is solid.

I see. So that's already 28 gigabytes of HD space wasted. This is getting ridiculous.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: etotheipi on November 23, 2013, 04:24:44 PM
I see. So that's already 28 gigabytes of HD space wasted. This is getting ridiculous.

It is ridiculous, but it's what we had to do to get the new version working.  It also maximizes security and leaves open the possibility of having remote bitcoind/bitcoin-qt instances, etc.  And will be useful for heavyweight Armory servers in the future.  For now, it's what we gotta do.  We'll scale it back in future versions after this design is stable.


----- Ubuntu/Debian
Only 10.04 and 12.04 are mentioned.
Is the 12.04 deb/installer compatible with 13.10?

Good question!  I actually don't know.  Anyone want to make some VMs and try it out for me/us?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: justusranvier on November 23, 2013, 05:54:03 PM
If you've got enough Bitcoins to need Armory, then 28 GB of hard drive space shouldn't be an issue...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 23, 2013, 06:18:24 PM
I just tested on a fresh install of 13.10 online, and it works great.  I am not sure if the offline bundle will work with 13.10 offline though. 


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: shapemaker on November 23, 2013, 07:48:19 PM
I see. So that's already 28 gigabytes of HD space wasted. This is getting ridiculous.

It is ridiculous, but it's what we had to do to get the new version working.  It also maximizes security and leaves open the possibility of having remote bitcoind/bitcoin-qt instances, etc.

That I could live with. Remote instance would be most useful so I could just dump the bitcoind (and the blockchain) to my server. Please tell more.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.14)
Post by: K1773R on November 23, 2013, 08:42:04 PM
I see. So that's already 28 gigabytes of HD space wasted. This is getting ridiculous.

It is ridiculous, but it's what we had to do to get the new version working.  It also maximizes security and leaves open the possibility of having remote bitcoind/bitcoin-qt instances, etc.

That I could live with. Remote instance would be most useful so I could just dump the bitcoind (and the blockchain) to my server. Please tell more.
you can use a remote bitcoind already (with any armory version AFAIK):
mount the blockchain with NFS (for example)
expose RPC to public and limit to given ip (if you dont want that, no need for it) and use SSL on it (if this is possible with armory)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: DBordello on November 23, 2013, 08:57:09 PM
The link to the windows installer appears to be dead.

Edit:  Only in the first post.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 23, 2013, 09:03:51 PM
Ack, somehow that file didn't make it to S3.  I'll have to check the script to see if it was being excluded from the upload or if there was an error.

Thanks for catching that... the data behind the link is now there, so the previous link should work again.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: keewee on November 24, 2013, 12:01:05 AM
The .16 testing version, unfortunately, is pretty much unusable on my Mac. It's a recent model iMac (Core i5 3.2GHz, 8G RAM, no SSD). Scanning the blockchain brings the system to a crawl and makes doing anything else very frustrating. And this is exacerbated by the fact that once this completes Armory will usually crash within a short while so it has to rescan the blockchain every time it starts. I ran it from the command line and I can see something that I wonder could be part of the problem. There are leftover references to picobit's system in the errors it displays in Terminal. For example:

  File "/Users/joeschmoe/BitcoinArmory/osx_picobit/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Twisted-13.1.0-py2.7-macosx-10.4-x86_64.egg/twisted/internet/base.py", line 824, in runUntilCurrent


If there's any information I can provide to help fix this then I'd be glad to help


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 24, 2013, 12:53:27 AM
The .16 testing version, unfortunately, is pretty much unusable on my Mac. It's a recent model iMac (Core i5 3.2GHz, 8G RAM, no SSD). Scanning the blockchain brings the system to a crawl and makes doing anything else very frustrating. And this is exacerbated by the fact that once this completes Armory will usually crash within a short while so it has to rescan the blockchain every time it starts. I ran it from the command line and I can see something that I wonder could be part of the problem. There are leftover references to picobit's system in the errors it displays in Terminal. For example:

  File "/Users/joeschmoe/BitcoinArmory/osx_picobit/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Twisted-13.1.0-py2.7-macosx-10.4-x86_64.egg/twisted/internet/base.py", line 824, in runUntilCurrent


If there's any information I can provide to help fix this then I'd be glad to help

Interesting!  Each next version seems to work less and less reliably on OSX.  And for sure, that absolute path reference is ... not right. 

Luckily, picobit just messaged me to let me know that he may have a solution (a variant of the current build recipe).  I'm going to try it out tonight and see what happens.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: keewee on November 24, 2013, 12:58:36 AM
The .16 testing version, unfortunately, is pretty much unusable on my Mac. It's a recent model iMac (Core i5 3.2GHz, 8G RAM, no SSD). Scanning the blockchain brings the system to a crawl and makes doing anything else very frustrating. And this is exacerbated by the fact that once this completes Armory will usually crash within a short while so it has to rescan the blockchain every time it starts. I ran it from the command line and I can see something that I wonder could be part of the problem. There are leftover references to picobit's system in the errors it displays in Terminal. For example:

  File "/Users/joeschmoe/BitcoinArmory/osx_picobit/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Twisted-13.1.0-py2.7-macosx-10.4-x86_64.egg/twisted/internet/base.py", line 824, in runUntilCurrent


If there's any information I can provide to help fix this then I'd be glad to help

Interesting!  Each next version seems to work less and less reliably on OSX.  And for sure, that absolute path reference is ... not right. 

Luckily, picobit just messaged me to let me know that he may have a solution (a variant of the current build recipe).  I'm going to try it out tonight and see what happens.

Great! Looking forward to getting this working. The recent rise in the value of btc has me nervous every time I fire up Bitcoin-qt  ;D


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 24, 2013, 01:04:33 AM
Luckily, picobit's build script is pretty easy, so it's not too hard to make new releases when I update the code.  Though they will likely need extra testing, since OSX has a few quirks.  I'm hoping he'll see this and try scanning his own package for hardcoded directories and figure out what's wrong (though, he is a busy guy...)

I got a few more polishing activities (actually, mainly updating the website and replacing the dead links in the app), and then I'll at least release the Windows and Linux versions.  Perhaps early next week.  But I won't post the OSX packages to the website as-is, since they are basically unusable...


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Red Emerald on November 24, 2013, 05:37:49 AM
OS X app crashes for me on Mavericks after a few minutes of use, too :(


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: pvz on November 24, 2013, 08:18:06 AM
Install 12.10 deb on 13.10 works.
On my system Ubuntu 13.10 v.99.16 seems to have a 'wait/watch' issue in transition from updating blockchain (bitcoind) to scanning the blockchain.
This is already happening a number of builds ago.
If all the blocks are already downloaded and Armory is started, Armory continues after this check.
When there are new blocks and the 'wait/watch' issue seems to be there, the --debug last info is: "(INFO) ArmoryQt.py:3781 - Switching Armory functional mode to "Offline" ".
Visually: Qt states "Synchronizing with Network x blocks" with x > 0 and stays that way. Now more counting down. Just continue to display only this information.
When only <10 new blockchain blocks, Armory does continue, with 92 blocks (last time I got this error) Armory gets in the 'wait/watch' modus.
Maybe only happens when there is a new block file?

I can try a rescan or a reinstall of bitcoind and Armory, but maybe you prefer some more error analysis before I do that or to try another build first.

Please let me know.

[EDIT] Today (11/25) Armory did not stop when it started with 152 blocks to download (bitcoind). The number of blocks to download is not the variable triggering the freeze.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: sflicht on November 24, 2013, 09:20:51 PM
Hi,

Just a minor bug report. I'm running Ubuntu 13.04 64 bit. I managed to install 0.89.99.16 today (it's building the database now, and I'm looking forward to using the new version!). However I had a lot of headaches getting the installation to work. I downloaded the OfflineBundle but running the very simple install script f***ed up my package dependencies. I managed to resolve this by NOT installing the libqtwebkit4 in the bundle. I already had what I assume is the same version of this library, but installing the one in the bundle with dpkg somehow ran me into the following Launchpad bug: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-source/+bug/1175902 (https://bugs.launchpad.net/ubuntu/+source/qtwebkit-source/+bug/1175902). Ultimately I escaped from the resulting dependency hellhole by using  dpkg -i --force-overwrite to get back to the version of the deb in my apt cache.

I don't think this is an Armory bug per se, and I assume others have managed to install the 0.89.99.16 fine using the bundle on the website, but I thought I'd post this as a heads up in case anyone else runs into the same issue.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Zomdifros on November 25, 2013, 11:19:44 PM
I installed the Windows 64 bit .16 version over the .14, though not in C: but in a different drive. When I do this, the copy of the blockchain is deleted and I have to wait an hour for the database to build again. After this is done, my wallets are completely gone and I can't seem to find a good way of getting them back easily without resorting to paper backups. I'm not sure if this is default behaviour, but I can imagine this will scare the shit out of some people.

Edit: to clarify, it was originally installed in C:, the second time in a different drive. In both cased I had symbolic links made in AppData\Roaming\ to both the Armory and Bitcoin folders, located on a different drive. Oh and for some reason it takes about 15 minutes for Armory to get the database build each time I start it.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: gortonc on November 26, 2013, 12:17:50 AM
Windows 7 32bit lenovo T60 with 2 gig Ram. I am surprised that it runs at all! It does occasionally lock up, but it is usable.  I am using the same machine with a TAILS USB for offline use. It seems to work fine in that environment.

I am thrilled! I can drop my watching wallets on the hard drive directly into the Windows Armory and my TAILS USB never needs to touch the Windows OS.

At some point I hope to write up a tutorial on how I set it up. It is a little tedious as I have not been able to make Armory persistent in TAILS yet and am reinstalling as needed. I keep the .armory in the Persistent archive.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: cp1 on November 26, 2013, 12:26:39 AM
I installed the Windows 64 bit .16 version over the .14, though not in C: but in a different drive. When I do this, the copy of the blockchain is deleted and I have to wait an hour for the database to build again. After this is done, my wallets are completely gone and I can't seem to find a good way of getting them back easily without resorting to paper backups. I'm not sure if this is default behaviour, but I can imagine this will scare the shit out of some people.

Edit: to clarify, it was originally installed in C:, the second time in a different drive. In both cased I had symbolic links made in AppData\Roaming\ to both the Armory and Bitcoin folders, located on a different drive. Oh and for some reason it takes about 15 minutes for Armory to get the database build each time I start it.

You must not be doing the symlinks correctly.  It's probably best to avoid that, just use the satoshidir and datadir switches.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: goatpig on November 26, 2013, 07:34:38 AM
You must not be doing the symlinks correctly.  It's probably best to avoid that, just use the satoshidir and datadir switches.

Definitely this. Try with the command line arguments (make a shortcut if you have to) and let us know.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Zomdifros on November 26, 2013, 09:26:36 AM

You must not be doing the symlinks correctly.  It's probably best to avoid that, just use the satoshidir and datadir switches.

You mean the switches in the Armory settings themselves? I tried that, but it didn't work. See https://bitcointalk.org/index.php?topic=299684.msg3616125#msg3616125

I made the links following this instruction: https://bitcointalk.org/index.php?topic=63844.msg748224#msg748224


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: goatpig on November 26, 2013, 09:45:02 AM
Code:
parser.add_option("--settings",        dest="settingsPath",default='DEFAULT', type="str",          help="load Armory with a specific settings file")
parser.add_option("--datadir",         dest="datadir",     default='DEFAULT', type="str",          help="Change the directory that Armory calls home")
parser.add_option("--satoshi-datadir", dest="satoshiHome", default='DEFAULT', type='str',          help="The Bitcoin-Qt/bitcoind home directory")
parser.add_option("--satoshi-port",    dest="satoshiPort", default='DEFAULT', type="str",          help="For Bitcoin-Qt instances operating on a non-standard port")
parser.add_option("--dbdir",           dest="leveldbDir",  default='DEFAULT', type='str',          help="Location to store blocks database (defaults to --datadir)")
parser.add_option("--rpcport",         dest="rpcport",     default='DEFAULT', type="str",          help="RPC port for running armoryd.py")
parser.add_option("--testnet",         dest="testnet",     default=False,     action="store_true", help="Use the testnet protocol")
parser.add_option("--offline",         dest="offline",     default=False,     action="store_true", help="Force Armory to run in offline mode")
parser.add_option("--nettimeout",      dest="nettimeout",  default=2,         type="int",          help="Timeout for detecting internet connection at startup")
parser.add_option("--interport",       dest="interport",   default=-1,        type="int",          help="Port for inter-process communication between Armory instances")
parser.add_option("--debug",           dest="doDebug",     default=False,     action="store_true", help="Increase amount of debugging output")
parser.add_option("--nologging",       dest="logDisable",  default=False,     action="store_true", help="Disable all logging")
parser.add_option("--netlog",          dest="netlog",      default=False,     action="store_true", help="Log networking messages sent and received by Armory")
parser.add_option("--logfile",         dest="logFile",     default='DEFAULT', type='str',          help="Specify a non-default location to send logging information")
parser.add_option("--mtdebug",         dest="mtdebug",     default=False,     action="store_true", help="Log multi-threaded call sequences")
parser.add_option("--skip-online-check", dest="forceOnline", default=False,   action="store_true", help="Go into online mode, even if internet connection isn't detected")
parser.add_option("--skip-version-check", dest="skipVerCheck", default=False, action="store_true", help="Do not contact bitcoinarmory.com to check for new versions")
parser.add_option("--keypool",         dest="keypool",     default=100, type="int",                help="Default number of addresses to lookahead in Armory wallets")
parser.add_option("--rebuild",         dest="rebuild",     default=False,     action="store_true", help="Rebuild blockchain database and rescan")
parser.add_option("--rescan",          dest="rescan",      default=False,     action="store_true", help="Rescan existing blockchain DB")
parser.add_option("--maxfiles",        dest="maxOpenFiles",default=0,         type="int",          help="Set maximum allowed open files for LevelDB databases")

List of Armory switches, as seen in the source. I am currently working on unicode support in Windows and the 'dir' arguments work just fine.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: cp1 on November 26, 2013, 04:44:33 PM
You mean the switches in the Armory settings themselves? I tried that, but it didn't work. See https://bitcointalk.org/index.php?topic=299684.msg3616125#msg3616125

I made the links following this instruction: https://bitcointalk.org/index.php?topic=63844.msg748224#msg748224

No, sending them as arguments to the windows shortcut:

"C:\Program Files (x86)\Armory-testing\ArmoryQt.exe" --satoshi-datadir=I:\bitcoin --datadir=I:\armory


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Zomdifros on November 26, 2013, 10:57:23 PM
@goatpig, @cp1

I tried starting Armory using this command line, in settings the default dir was changed that way. Loading seemed somewhat faster in one instance, in others it was equally slow as starting Armory the regular way.

With a little patience I can get Armory to work however, so it isn't a pressing problem. I am worried though that other people might lose their wallet if they have moved the blockchain or install folder in a similar fashion, although I am not sure if a good solution is available.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: justusranvier on November 26, 2013, 11:09:33 PM
Just noticed that the version in git displays version 0.90 now. Is this the official release?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 27, 2013, 01:00:07 AM
Just noticed that the version in git displays version 0.90 now. Is this the official release?

Semi-official.  I'm going to let this release ferment silently for a few days, and make sure I got everything right, before pushing out notifications.  I was planning to push them out right away, but I've had too many instances of stupid things that need to be fixed and I don't want to spam users any more than necessary.

Probably push notifications and official announcement on Friday or Monday.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: HowlingMad on November 27, 2013, 02:00:04 AM
I have an interesting problem.  I am running 0.89.99... on Debian v2.26.32

I created a send transaction and after 70 minutes the status for the transaction "Not in the blockchain yet".  The transaction never gets sent.

What's up?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 27, 2013, 02:12:32 AM
Right-click on the transaction and "View on Blockchain.info".  If the transaction was broadcast properly, you'll see it on blockchain.info.  If not, go to "Help" -> "Clear all unconfirmed" and then send/broadcast your transaction again.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: Kupsi on November 28, 2013, 04:33:38 PM
I'm just not 100% confident that the backups will be the same as the final version.  I know it creates a frustrating dynamic, because I need people to help test the backups, but I have to tell them not to rely on them yet.

When will you decide this? I would love to use the m-of-n paper backup.

Have you decided this now?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: goatpig on November 28, 2013, 07:10:07 PM
I'm just not 100% confident that the backups will be the same as the final version.  I know it creates a frustrating dynamic, because I need people to help test the backups, but I have to tell them not to rely on them yet.

When will you decide this? I would love to use the m-of-n paper backup.

Have you decided this now?

M-of-N backups are available in the current testing release


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: Kyune on November 28, 2013, 09:17:28 PM
I'm just not 100% confident that the backups will be the same as the final version.  I know it creates a frustrating dynamic, because I need people to help test the backups, but I have to tell them not to rely on them yet.

When will you decide this? I would love to use the m-of-n paper backup.

Have you decided this now?

M-of-N backups are available in the current testing release
Yes, but the quoted statement from etotheipi suggested the possibility that the fragmented-backup format might yet change between testing version and release version.  That ambiguity hasn't been removed by a clear statement, although it seems unlikely that the format is going to change given how close we are to release of a new non-testing version.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: goatpig on November 28, 2013, 09:56:44 PM
Yes, but the quoted statement from etotheipi suggested the possibility that the fragmented-backup format might yet change between testing version and release version.  That ambiguity hasn't been removed by a clear statement, although it seems unlikely that the format is going to change given how close we are to release of a new non-testing version.

I think he was making reference to the new paper backup format, exporting only the root key instead of root key + chaincode. M of N backups were not available to public at the time of that post, if memory serves right.

Regardless, the current M of N backups are only available as part of test builds, you're better off waiting for a release build before shoving the GDP of Zimbabwe into one of those babies =P. You're welcome to abuse them with cheap change or testnet coins, however.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: Missionary on November 28, 2013, 10:00:53 PM
Yes, but the quoted statement from etotheipi suggested the possibility that the fragmented-backup format might yet change between testing version and release version.  That ambiguity hasn't been removed by a clear statement, although it seems unlikely that the format is going to change given how close we are to release of a new non-testing version.

I think he was making reference to the new paper backup format, exporting only the root key instead of root key + chaincode. M of N backups were not available to public at the time of that post, if memory serves right.

Regardless, the current M of N backups are only available as part of test builds, you're better off waiting for a release build before shoving the GDP of Zimbabwe into one of those babies =P. You're welcome to abuse them with cheap change or testnet coins, however.

I created a new wallet on my offline computer and printed a 5 of 6 backup. I then deleted the wallet and restored from the printed backups. There where no problems and the addresses that I created were the same as before. Are you saying that I have missed something and that I should not rely on that paper wallet for my small-country-sized-savings?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: goatpig on November 29, 2013, 10:02:42 AM
I created a new wallet on my offline computer and printed a 5 of 6 backup. I then deleted the wallet and restored from the printed backups. There where no problems and the addresses that I created were the same as before. Are you saying that I have missed something and that I should not rely on that paper wallet for my small-country-sized-savings?

Let me put it to you from our perspective. Recently we are getting a wave a new users who download Armory, shove their coins into it and then figure out they don't know how to use it, then spam us with emails like "help me please".

As with any new feature relating to wallets, please be sure to test it extensively, get familiar with the feature and acquire a solid understanding of how to use it before resorting to hold your funds with it.

While the testing phase on the M-of-N backups is satisfactory, even knowing that it'll be part of the next release, do not forget that the current builds are, as the name says, for testing purpose. I hope this clarifies the point.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.5)
Post by: Kupsi on November 29, 2013, 05:58:34 PM
Yes, but the quoted statement from etotheipi suggested the possibility that the fragmented-backup format might yet change between testing version and release version.  That ambiguity hasn't been removed by a clear statement, although it seems unlikely that the format is going to change given how close we are to release of a new non-testing version.

I think he was making reference to the new paper backup format, exporting only the root key instead of root key + chaincode. M of N backups were not available to public at the time of that post, if memory serves right.

M of N backups were available to the public at that time.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: thewayshegoes on November 29, 2013, 06:19:53 PM
Sorry if this is a stupid question, but is this version out of the testing phase now?

Asking this because I see a beta version 0.90 available for download on the Armory website, and don't recall seeing it there a couple days ago.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 29, 2013, 08:38:12 PM
https://bitcointalk.org/index.php?topic=299684.msg3729739#msg3729739


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: halfawake on November 30, 2013, 08:03:44 AM
I had been eagerly awaiting the new version, thinking that it wouldn't bog down my computer like the old one did, but it still seems to be doing that.  Granted, I only have 5 GB of RAM, which is why I essentially stopped using Armory for a while, but in theory that wasn't supposed to be an issue any more.

Is this just something that happens the first time it's loaded in a while, or is even a computer with 5 GB of RAM too slow to properly use Armory?  I waited until it finished building databases, but since I'm going to sleep soon and didn't want to wait another hour, I didn't wait to see how it'd behave after it finishes scanning transaction history.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: goatpig on November 30, 2013, 10:54:01 AM
I had been eagerly awaiting the new version, thinking that it wouldn't bog down my computer like the old one did, but it still seems to be doing that.  Granted, I only have 5 GB of RAM, which is why I essentially stopped using Armory for a while, but in theory that wasn't supposed to be an issue any more.

Is this just something that happens the first time it's loaded in a while, or is even a computer with 5 GB of RAM too slow to properly use Armory?  I waited until it finished building databases, but since I'm going to sleep soon and didn't want to wait another hour, I didn't wait to see how it'd behave after it finishes scanning transaction history.

The first time that new version starts (0.89+), it has to build its database. This is a heavy process. Once it is past that point, restarting Armory should take less than a minute + whatever time it'll take BitcoinQt to sync with the network (at this point the time it take to scan the new blocks is obsolete).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on November 30, 2013, 04:04:19 PM
I forgot to make the RAM usage for that first build configurable (or at least dynamically adjustable based on available RAM).  But right now it should only use 1 GB to build the DB.  However it is likely to slow things down because it's doing very heavy disk accessing. But after that process is done, it should only use 200-300 MB, and start up very quickly. And not station the system much at all.

Please let us know if your experience differs significantly.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: halfawake on December 01, 2013, 01:06:14 AM
I forgot to make the RAM usage for that first build configurable (or at least dynamically adjustable based on available RAM).  But right now it should only use 1 GB to build the DB.  However it is likely to slow things down because it's doing very heavy disk accessing. But after that process is done, it should only use 200-300 MB, and start up very quickly. And not station the system much at all.

Please let us know if your experience differs significantly.

Thanks for the update.  It was slow initially, but now that the scanning transaction history part is done, it's pretty quick again.  Good work.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Gryph on December 04, 2013, 08:23:16 AM
Hi!

Just installed the new version (0.90) but it keeps getting stuck at the "building databases" part with "15 seconds" left.

I tried "rebuild and rescan databases" in the help menu and it builds up to 99% again but keeps getting stuck with "15 seconds" left. I left it on for a full day but it never budged, then it started giving a crapload of "bitcoin-qt disconnected" errors.

I'm using windows 8 64-bit with 32GB of ram and a 256GB SSD.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on December 04, 2013, 04:37:32 PM
Hi!

Just installed the new version (0.90) but it keeps getting stuck at the "building databases" part with "15 seconds" left.

I tried "rebuild and rescan databases" in the help menu and it builds up to 99% again but keeps getting stuck with "15 seconds" left. I left it on for a full day but it never budged, then it started giving a crapload of "bitcoin-qt disconnected" errors.

I'm using windows 8 64-bit with 32GB of ram and a 256GB SSD.

Send a log file to support at bitcoinarmory com


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Gryph on December 04, 2013, 06:38:42 PM
Sent! :)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: seldon on December 04, 2013, 08:25:20 PM
I am currently switching to armory, used to have .88, now updated to .90

I use a second computer as offline wallet. Testing the offline transactions workd in .88, but the online version was eating up my ram - made the switch to .90 and this is fine now.

HOWEVER, when I try to make an offline transaction clicking the "create unsigned transaction" will not have an effect. When looking into the armory log I find this exception for each button click:

2013-12-04 21:15 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5225, in createOfflineTxDPAndDisplay
  File "qtdialogs.pyc", line 5514, in validateInputsGetTxDP
  File "armoryengine.pyc", line 6493, in createFromTxOutSelection
  File "armoryengine.pyc", line 6362, in createFromPyTx
  File "armoryengine.pyc", line 4274, in copy
  File "armoryengine.pyc", line 4263, in unserialize
  File "armoryengine.pyc", line 4111, in unserialize
UnserializeError

Any ideas?


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: seldon on December 04, 2013, 10:19:04 PM
Update, seems to be solved by reboot ..  ???


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: RoadStress on December 05, 2013, 12:33:08 AM
I don't know if this was posted or not, but i have a problem. I'm using Armory with the "--datadir=" command and it keeps crashing at 99% scanning transaction history with every version that i try. Using the default directory works, but what should i do to work with the "--datadir=" option?

Edit: I am thinking that using a .wallet file may pose some kind of security breach. How hard would it be to implement the use of custom named wallets? For examtle abc.jpg or abc.xyz? The format can be the same i assume, only the name changes.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: RoadStress on December 05, 2013, 11:30:39 AM
I don't know if this was posted or not, but i have a problem. I'm using Armory with the "--datadir=" command and it keeps crashing at 99% scanning transaction history with every version that i try. Using the default directory works, but what should i do to work with the "--datadir=" option?


Solved. Deleted the "databases" folder and now works like a charm.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on December 05, 2013, 04:31:34 PM
I don't know if this was posted or not, but i have a problem. I'm using Armory with the "--datadir=" command and it keeps crashing at 99% scanning transaction history with every version that i try. Using the default directory works, but what should i do to work with the "--datadir=" option?


Solved. Deleted the "databases" folder and now works like a charm.

This may have been the last major bug I never found before releasing

Code:
-ERROR - 1384746267: (..\StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!

It's in my plans to fix that for 0.91-beta.  I got a couple people to pass me their databases that have this error so I can debug it.  Will tend to it after I get back from the conference (in addition to fixing all the broken optimizations in the LevelDB code which causes it to scan so slowly!)


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: SimonBelmond on December 05, 2013, 06:13:44 PM
I had some fun with 0.9 lateley. The backup center is just mindblowingly awesome. All the safety questions are addressed. e.g. I was wondering if testing of backup is safe. Just then it tells me that no keys will be written to disk. Great stuff.

I noticed one little flaw though. Might have been mentioned before. Wehn printing a 1/1 (normal) paper backup the last block of of the chain key on each line does not stay within the given frame. two letters were just on top of the line. Does not happen with fragmented backups though. Let me know if you need a screenshot.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on December 05, 2013, 06:46:12 PM
I had some fun with 0.9 lateley. The backup center is just mindblowingly awesome. All the safety questions are addressed. e.g. I was wondering if testing of backup is safe. Just then it tells me that no keys will be written to disk. Great stuff.

I noticed one little flaw though. Might have been mentioned before. Wehn printing a 1/1 (normal) paper backup the last block of of the chain key on each line does not stay within the given frame. two letters were just on top of the line. Does not happen with fragmented backups though. Let me know if you need a screenshot.

:)   Thanks! 

I have battled with the text sizes and fonts on those backups, but Qt just does not want to obey me.  I think I'm missing something, and maybe it's somethign we should investigate for 0.91-beta... apparently your desktop DPI and default font affects it even though I explicitly tell Qt the exact size and font to use.  And on Mac it doesn't even use fixed-width font!

I'll make a note for the next version to do a bit more investigation of that (as well as spend some time on the Mac build, which got lost in the conference preparations)



Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Gryph on December 06, 2013, 01:21:10 AM
Hi!

Just installed the new version (0.90) but it keeps getting stuck at the "building databases" part with "15 seconds" left.

I tried "rebuild and rescan databases" in the help menu and it builds up to 99% again but keeps getting stuck with "15 seconds" left. I left it on for a full day but it never budged, then it started giving a crapload of "bitcoin-qt disconnected" errors.

I'm using windows 8 64-bit with 32GB of ram and a 256GB SSD.

Send a log file to support at bitcoinarmory com

I've been able to reproduce the error and fix the error.

When install Bitcoin-QT and reload the blockchain with bootstrap.dat the error pops up. But if i install the bitcoin-QT fresh and let it download the whole blockchain over two days, it works.

I hope this, along with the log files i sent you, help you solve problem.

Thanks again for such a great piece of software!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on December 06, 2013, 04:39:55 AM
I've been able to reproduce the error and fix the error.

When install Bitcoin-QT and reload the blockchain with bootstrap.dat the error pops up. But if i install the bitcoin-QT fresh and let it download the whole blockchain over two days, it works.

I hope this, along with the log files i sent you, help you solve problem.

Thanks again for such a great piece of software!

I'm starting to notice some patterns in this.  It may have to do with the version of Bitcoin-Qt that produces the blk*.dat files.  It's very possible that there are artifacts in the blk*.dat files that I don't handle gracefully. 

So where did your bootstrap file come from?  Do you know the version that created it? 

On the other hand, I'd like to move away from reading the blk*.dat files entirely, and just request it as a regular blockchain download via P2P (via localhost).  This would solve a lot of problems and should make the version of Bitcoin-Qt irrelevant, in addition to allowing remote Bitcoin-Qt instances.  In fact, I wanted to do this for 0.90-beta, but the change was too dramatic, and decided to keep it simple for now.  But now that this version is stabilizing, it may make sense to do that, especially if it wipes out these kinds of bugs, which may be elusive and difficult to debug (basically allow bitcoin-qt to read its own blk*.dat files properly, and pass us the data in standardized network messages).


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Dabs on December 06, 2013, 04:58:16 AM
So, Armory is going to turn into a SPV wallet? Or will it keep a copy of the blockchain? That would make sense, and besides I personally would still run a full node anyway, so I can have Armory pointed there.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Gryph on December 06, 2013, 05:15:07 AM
I've been able to reproduce the error and fix the error.

When install Bitcoin-QT and reload the blockchain with bootstrap.dat the error pops up. But if i install the bitcoin-QT fresh and let it download the whole blockchain over two days, it works.

I hope this, along with the log files i sent you, help you solve problem.

Thanks again for such a great piece of software!

I'm starting to notice some patterns in this.  It may have to do with the version of Bitcoin-Qt that produces the blk*.dat files.  It's very possible that there are artifacts in the blk*.dat files that I don't handle gracefully. 

So where did your bootstrap file come from?  Do you know the version that created it? 

On the other hand, I'd like to move away from reading the blk*.dat files entirely, and just request it as a regular blockchain download via P2P (via localhost).  This would solve a lot of problems and should make the version of Bitcoin-Qt irrelevant, in addition to allowing remote Bitcoin-Qt instances.  In fact, I wanted to do this for 0.90-beta, but the change was too dramatic, and decided to keep it simple for now.  But now that this version is stabilizing, it may make sense to do that, especially if it wipes out these kinds of bugs, which may be elusive and difficult to debug (basically allow bitcoin-qt to read its own blk*.dat files properly, and pass us the data in standardized network messages).

I swiped the file from this thread: https://bitcointalk.org/index.php?topic=145386.0

as for what version that created it, I have no idea.

Those changes to how it gets the blockchain sound like a great idea! Take all the time you need to implement it! :)

Great job again!


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: etotheipi on December 18, 2013, 05:46:51 AM



Now that the conference is over, I took a stab at OSX.  I finally got it compiling and running!  But, I don't have the full blockchain on my Mac, so I can't really test it...  Try it out!

https://s3.amazonaws.com/bitcoinarmory-releases/Armory_0.90-beta_OSX_test1.tar.gz


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: gweedo on December 18, 2013, 04:09:05 PM



Now that the conference is over, I took a stab at OSX.  I finally got it compiling and running!  But, I don't have the full blockchain on my Mac, so I can't really test it...  Try it out!

https://s3.amazonaws.com/bitcoinarmory-releases/Armory_0.90-beta_OSX_test1.tar.gz

It works for me, I am on maverick 10.9.0, not 10.9.1.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: Mashuri on December 19, 2013, 01:54:33 AM
Works well so far on MBP Retina 15" w/ OS 10.9.  Fully synched but haven't tried any transactions yet.


Title: Re: RAM-Reduction & Backup Center Testing (version 0.89.99.16)
Post by: e4xit on December 19, 2013, 08:53:47 AM



Now that the conference is over, I took a stab at OSX.  I finally got it compiling and running!  But, I don't have the full blockchain on my Mac, so I can't really test it...  Try it out!

https://s3.amazonaws.com/bitcoinarmory-releases/Armory_0.90-beta_OSX_test1.tar.gz


Woo-hoo! this what I've been waiting for. Will try out tonight and report back. Thanks!!