RAM-Reduction & Backup Center Testing (version 0.89.99.16)

[etotheipi]

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!

[1715299474]

1715299474

[1715299474]

1715299474

[1715299474]

1715299474

[1715299474]

1715299474

[Rogue Star]

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!

[Eylrid]

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.

[etotheipi]

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).

[goatpig]

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.

[Rogue Star]

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!

[els]

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.

[els]

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!

[Eylrid]

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.

[etotheipi]

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.   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, we might just have to wait it out). 

[picobit]

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

[goatpig]

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

[Eylrid]

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.

[goatpig]

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?

[Eylrid]

That worked.

Vista or XP?

Vista

[Portnoy]

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.

[pvz]

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!

[etotheipi]

Version 0.89.99.14-testing: Now with message signing and fragmented backup tester!

Ubuntu/Debian 32-bit
Ubuntu/Debian 64-bit
Mac/OSX (flaky with 10.9)
Windows (32- and 64-bit)

[Allaboutbit]

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?

[etotheipi]

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)