Topic: Please Help Test Armory 0.91-beta! - page 9. (Read 21313 times)
Any help ?
2014-03-22 19:56 (INFO) -- ArmoryQt.py:585 - Usermode: Expert
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1343 - Changing usermode:
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1344 - From: Expert
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1352 - To: Expert
2014-03-22 19:56 (INFO) -- SDM.pyc:772 - Creating proxy in SDM: host=127.0.0.1, port=8332
2014-03-22 19:56 (INFO) -- ArmoryQt.py:5444 - Dashboard switched to auto-InitSync
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:InitializingLongTime
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline"
2014-03-22 19:56 (INFO) -- ArmoryQt.py:6293 - Another Armory instance just tried to open.
2014-03-22 19:56 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-03-22 19:56 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b
2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.4
2014-03-22 19:56 (WARNING) -- SDM.pyc:650 - bitcoind exited, bitcoind STDOUT:
2014-03-22 19:56 (WARNING) -- SDM.pyc:652 -
2014-03-22 19:56 (WARNING) -- SDM.pyc:653 - bitcoind exited, bitcoind STDERR:
2014-03-22 19:56 (WARNING) -- SDM.pyc:655 -
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (ERROR) -- ArmoryQt.py:5400 - BitcoindNotAvailable: should not happen...
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline"
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1343 - Changing usermode:
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1344 - From: Expert
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1352 - To: Expert
2014-03-22 19:56 (INFO) -- SDM.pyc:772 - Creating proxy in SDM: host=127.0.0.1, port=8332
2014-03-22 19:56 (INFO) -- ArmoryQt.py:5444 - Dashboard switched to auto-InitSync
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:InitializingLongTime
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline"
2014-03-22 19:56 (INFO) -- ArmoryQt.py:6293 - Another Armory instance just tried to open.
2014-03-22 19:56 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-03-22 19:56 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b
2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.4
2014-03-22 19:56 (WARNING) -- SDM.pyc:650 - bitcoind exited, bitcoind STDOUT:
2014-03-22 19:56 (WARNING) -- SDM.pyc:652 -
2014-03-22 19:56 (WARNING) -- SDM.pyc:653 - bitcoind exited, bitcoind STDERR:
2014-03-22 19:56 (WARNING) -- SDM.pyc:655 -
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times
2014-03-22 19:56 (ERROR) -- ArmoryQt.py:5400 - BitcoindNotAvailable: should not happen...
2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline"
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1009 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1010 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1011 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine:
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1016 - Armory Version : 0.90.99.4
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1017 - PyBtcWallet Version : 1.35
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1019 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1020 - User home-directory : C:\Users\x\AppData\Roaming
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1021 - Satoshi BTC directory : C:\Users\x\AppData\Roaming\Bitcoin\
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1022 - Armory home dir : C:\Users\x\AppData\Roaming\Armory\
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs :
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1024 - Total Available RAM : 7.94 GB
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1025 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1026 - Number of CPU cores : 4 cores
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1027 - System is 64-bit : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1028 - Preferred Encoding : cp1252
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1029 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py:
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - maxOpenFiles : 0
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - nettimeout : 2
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rescan : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - leveldbDir : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - ignoreAllZC : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - port : None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - interport : 8223
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageOutputDir: None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rebuild : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - datadir : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - offline : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - noWalletCheck : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiPort : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - netlog : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - keypool : 100
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageInclude : None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - forceOnline : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipAnnounceCheck: False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - redownload : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - disableTorrent : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testAnnounceCode: False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - mtdebug : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipVerCheck : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - settingsPath : C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - verbosity : None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - doDebug : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testnet : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rpcport : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiHome : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiRpcport : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logDisable : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logFile : C:\Users\x\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments:
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully
2014-03-22 19:56 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager.
2014-03-22 19:56 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background.
2014-03-22 19:56 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data.
2014-03-22 19:56 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for
2014-03-22 19:56 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed.
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:3006 - Using settings file: C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt
2014-03-22 19:56 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory:
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - announce : 88f1e5b41f0a828a1ae440c0490e4136a848b4fc79fa4d41809d309eefc87712
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - bootstrap : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - changelog : d4072bb5c0037ad4bd551dec85601ed8ef1eae04780c08e69e28d62932900441
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - downloads : cec3a5c4381a82860162d9d7d913bda75d88f7b531d6d528620a5464c0020b3d
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - notify : 20aa6e8a9d1f947c08f1b21a4c24d53e29b68c2d37b936a082d88192b2513fea
2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2211 - loadWalletsAndSettings
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2269 - Loading wallets...
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2318 - Number of wallets read in: 2
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (2vrvaaUvT): "Piotr " (No Encryption)
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (tNKjfKT5): "Offline (Watch) " (No Encryption)
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1758 - Setting up networking...
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1810 - Internet connection is Available: True
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1811 - Bitcoin-Qt/bitcoind is Available: 0
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1812 - The first blk*.dat was Available: True
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1813 - Online mode currently possible: 0
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1932 - startBitcoindIfNecessary
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1972 - setSatoshiPaths
2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB
2014-03-22 19:56 (INFO) -- SDM.pyc:299 - Found bitcoind in the following places:
2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2014-03-22 19:56 (INFO) -- SDM.pyc:303 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-22 19:56 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file
2014-03-22 19:56 (INFO) -- SDM.pyc:480 - Setting permissions on bitcoin.conf
2014-03-22 19:56 (INFO) -- SDM.pyc:483 - Setting permissions on bitcoin.conf
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['icacls', 'C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'x:F']
2014-03-22 19:56 (INFO) -- SDM.pyc:486 - icacls returned:
2014-03-22 19:56 (INFO) -- SDM.pyc:547 - Called startBitcoind
2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['C:\\Program Files (x86)\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\']
2014-03-22 19:56 (INFO) -- SDM.pyc:607 - PID of bitcoind: 3424
2014-03-22 19:56 (INFO) -- SDM.pyc:608 - PID of armory: 3760
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['.\\guardian.exe', '3760', '3424']
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1076 - setupUriRegistration
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1144 - Armory already registered for current user. Done!
Here is log can go online.....
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1009 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1010 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1011 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine:
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1016 - Armory Version : 0.90.99.4
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1017 - PyBtcWallet Version : 1.35
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1019 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1020 - User home-directory : C:\Users\x\AppData\Roaming
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1021 - Satoshi BTC directory : C:\Users\x\AppData\Roaming\Bitcoin\
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1022 - Armory home dir : C:\Users\x\AppData\Roaming\Armory\
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs :
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1024 - Total Available RAM : 7.94 GB
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1025 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1026 - Number of CPU cores : 4 cores
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1027 - System is 64-bit : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1028 - Preferred Encoding : cp1252
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1029 -
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py:
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - maxOpenFiles : 0
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - nettimeout : 2
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rescan : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - leveldbDir : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - ignoreAllZC : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - port : None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - interport : 8223
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageOutputDir: None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rebuild : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - datadir : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - offline : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - noWalletCheck : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiPort : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - netlog : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - keypool : 100
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageInclude : None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - forceOnline : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipAnnounceCheck: False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - redownload : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - disableTorrent : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testAnnounceCode: False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - mtdebug : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipVerCheck : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - settingsPath : C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - verbosity : None
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - doDebug : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testnet : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rpcport : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiHome : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiRpcport : DEFAULT
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logDisable : False
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logFile : C:\Users\x\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments:
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully
2014-03-22 19:56 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager.
2014-03-22 19:56 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background.
2014-03-22 19:56 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data.
2014-03-22 19:56 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for
2014-03-22 19:56 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed.
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:3006 - Using settings file: C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt
2014-03-22 19:56 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory:
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - announce : 88f1e5b41f0a828a1ae440c0490e4136a848b4fc79fa4d41809d309eefc87712
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - bootstrap : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - changelog : d4072bb5c0037ad4bd551dec85601ed8ef1eae04780c08e69e28d62932900441
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - downloads : cec3a5c4381a82860162d9d7d913bda75d88f7b531d6d528620a5464c0020b3d
2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - notify : 20aa6e8a9d1f947c08f1b21a4c24d53e29b68c2d37b936a082d88192b2513fea
2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2211 - loadWalletsAndSettings
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2269 - Loading wallets...
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2318 - Number of wallets read in: 2
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (2vrvaaUvT): "Piotr " (No Encryption)
2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (tNKjfKT5): "Offline (Watch) " (No Encryption)
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1758 - Setting up networking...
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1810 - Internet connection is Available: True
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1811 - Bitcoin-Qt/bitcoind is Available: 0
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1812 - The first blk*.dat was Available: True
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1813 - Online mode currently possible: 0
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1932 - startBitcoindIfNecessary
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1972 - setSatoshiPaths
2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB
2014-03-22 19:56 (INFO) -- SDM.pyc:299 - Found bitcoind in the following places:
2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2014-03-22 19:56 (INFO) -- SDM.pyc:303 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-22 19:56 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file
2014-03-22 19:56 (INFO) -- SDM.pyc:480 - Setting permissions on bitcoin.conf
2014-03-22 19:56 (INFO) -- SDM.pyc:483 - Setting permissions on bitcoin.conf
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['icacls', 'C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'x:F']
2014-03-22 19:56 (INFO) -- SDM.pyc:486 - icacls returned:
2014-03-22 19:56 (INFO) -- SDM.pyc:547 - Called startBitcoind
2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['C:\\Program Files (x86)\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\']
2014-03-22 19:56 (INFO) -- SDM.pyc:607 - PID of bitcoind: 3424
2014-03-22 19:56 (INFO) -- SDM.pyc:608 - PID of armory: 3760
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['.\\guardian.exe', '3760', '3424']
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1076 - setupUriRegistration
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1144 - Armory already registered for current user. Done!
Here is log can go online.....
Coinbase transactions no longer respond to "Show Details" in 0.90.99.4. Don't know if that was the case in previous 0.91 test versions, as this is the first I've tried.
I have Now wallet error found and armory fail to initiate bitcoin engine.
I just installed this version and Armory don't want go in to online mode, show armory offline mode and noting happend.
Finally! Thanks for the release, I will be testing it 
I'm getting this:
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Code:
Traceback (most recent call last):
File "armoryqt.py", line 38, in
from PyQt4.QtCore import *
ImportError: No module named PyQt4.QtCore
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Uhhh, gonna need more details. What OS and version? Did you build it yourself or use our package?
Duh, sorry my bad!
OSX (Mavericks), used the version in the first post of this thread.
I'm getting this:
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Code:
Traceback (most recent call last):
File "armoryqt.py", line 38, in
from PyQt4.QtCore import *
ImportError: No module named PyQt4.QtCore
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Uhhh, gonna need more details. What OS and version? Did you build it yourself or use our package?
I'm getting this:
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Code:
Traceback (most recent call last):
File "armoryqt.py", line 38, in
from PyQt4.QtCore import *
ImportError: No module named PyQt4.QtCore
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Quick bug report:
It appears as if I'm unable to open the "Transaction Info" popup on transactions that have a P2SH output as is standard in mastercoin transactions. In previous releases, the P2SH output was just marked as (I believe it was) "strange." It's not a huge deal considering that no wallet recognizes or can spend those outputs anyway, but it would be nice if the popup worked.
Here's an example:
https://blockchain.info/tx/cba042a1e4b4b072084c06e94f84843cdbd17a30f13dd038fabca67baeb20b53
It appears as if I'm unable to open the "Transaction Info" popup on transactions that have a P2SH output as is standard in mastercoin transactions. In previous releases, the P2SH output was just marked as (I believe it was) "strange." It's not a huge deal considering that no wallet recognizes or can spend those outputs anyway, but it would be nice if the popup worked.
Here's an example:
Code:
OP_1OP_2 OP_CHECKMULTISIG
https://blockchain.info/tx/cba042a1e4b4b072084c06e94f84843cdbd17a30f13dd038fabca67baeb20b53
@LOL
I just fixed the multisig display issue with a one-line change. All the code was already written and integrated, but I didn't account for the variable number of addresses/keys when analyzing a transaction with a multi-sig output.
Will push the update shortly to 0.91-dev (in case you're impatient
)
i found a bug in 0.90.99.4 :
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
My block count is updating just fine. Lemme see a log file. Can others confirm or infirm this behavior?
After updating to new version and having only run Armory once today, and leaving it open, I now show:
"Connected (291697 blocks)"
Update: My status is now "Connected (291699 blocks)"
Thus the Armor is updating
That's great Alan, we'll be eager to try it out!
Marshall Swatt
CTO - Coinsetter, Inc.
Marshall Swatt
CTO - Coinsetter, Inc.
i found a bug in 0.90.99.4 :
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
My block count is updating just fine. Lemme see a log file. Can others confirm or infirm this behavior?
After updating to new version and having only run Armory once today, and leaving it open, I now show:
"Connected (291697 blocks)"
i found a bug in 0.90.99.4 :
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
My block count is updating just fine. Lemme see a log file. Can others confirm or infirm this behavior?
Edit: This could be related to a spent output with the wallet. You should rescan the transactions. No need to rebuild though. I expect the balance will change after the rescan.
Yes, that solved it. I'm happy to report that every single issue I've had (and I've had many) is now resolved. https://blockchain.info/tx/dbeaf256a65a95d532ded05526e7eb874e02339f252124edc42cb3bdf2547bef
Thx for the tip =)
i found a bug in 0.90.99.4 :
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
Will take a look at this, thx for the report
My Armory wallet is finally working again!
Updated to the 0.90.99.4 Beta
Updated my BitcoinQT then started Armory
Building Databases took 7 minutes
Scanning Transaction History took 1 Hour
Odd behavior: Just before the 'Scanning Transaction History' completed it changed the time estimate to '16 years'.
Updated to the 0.90.99.4 Beta
Updated my BitcoinQT then started Armory
Building Databases took 7 minutes
Scanning Transaction History took 1 Hour
Odd behavior: Just before the 'Scanning Transaction History' completed it changed the time estimate to '16 years'.
During blockchain build and tx scan, the backend report it's progress to the front end. Now that the wallet ledger pre load is ran from the backend, it lacks the progress reporting. The front end then assumes it's gonna "that" long to get anywhere, as it's not seeing any reports further down the road.
My Armory wallet is finally working again!
Updated to the 0.90.99.4 Beta
Updated my BitcoinQT then started Armory
Building Databases took 7 minutes
Scanning Transaction History took 1 Hour
Odd behavior: Just before the 'Scanning Transaction History' completed it changed the time estimate to '16 years'.
Updated to the 0.90.99.4 Beta
Updated my BitcoinQT then started Armory
Building Databases took 7 minutes
Scanning Transaction History took 1 Hour
Odd behavior: Just before the 'Scanning Transaction History' completed it changed the time estimate to '16 years'.
i found a bug in 0.90.99.4 :
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
Thanks for the report!
Please go to Help -> Submit Bug Report
Armory will send us everything we need to investigate this bug.
i found a bug in 0.90.99.4 :
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync)
i make a tx and wonder why 0 confirms after 1 Hour.
on BC.i the tx confirm is 10
After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart.
Greets
Edit: This could be related to a spent output with the wallet. You should rescan the transactions. No need to rebuild though. I expect the balance will change after the rescan.
Yes, that solved it. I'm happy to report that every single issue I've had (and I've had many) is now resolved. https://blockchain.info/tx/dbeaf256a65a95d532ded05526e7eb874e02339f252124edc42cb3bdf2547bef
Jump to: