Latest posts of: etotheipi

Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 ... 186 »

381

Bitcoin / Armory / Re: Armory - Discussion Thread

on: April 19, 2014, 02:09:23 PM

Quote from: shoesman on April 19, 2014, 12:59:37 PM

ok after entering the following in the shortcut target

--satoshi-datadir=C:\Users\bob\AppData\Roaming\Bitcoin --satoshi-port=8331 --skip-online-check

still get offline

Code:

2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1009 - 
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1010 - 
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1011 - 
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine:
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1016 -    Armory Version        : 0.91
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1017 -    PyBtcWallet  Version  : 1.35
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1019 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1020 -    User home-directory   : C:\Users\bob\AppData\Roaming
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1021 -    Satoshi BTC directory : C:\Users\bob\AppData\Roaming\Bitcoin\
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1022 -    Armory home dir       : C:\Users\bob\AppData\Roaming\Armory\
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs    : 
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1024 -    Total Available RAM   : 15.99 GB
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1025 -    CPU ID string         : Intel64 Family 5 Model 24 Stepping 2, GenuineIntel
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1026 -    Number of CPU cores   : 6 cores
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1027 -    System is 64-bit      : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1028 -    Preferred Encoding    : cp1252
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1029 - 
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py:
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     maxOpenFiles    : 0
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     nettimeout      : 2
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     rescan          : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     leveldbDir      : DEFAULT
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     ignoreAllZC     : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     port            : None
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     interport       : 8223
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     coverageOutputDir: None
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     rebuild         : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     datadir         : DEFAULT
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     offline         : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     noWalletCheck   : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     satoshiPort     : DEFAULT
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     netlog          : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     keypool         : 100
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     coverageInclude : None
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     forceOnline     : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     skipAnnounceCheck: False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     redownload      : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     disableTorrent  : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     testAnnounceCode: False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     mtdebug         : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     skipVerCheck    : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     settingsPath    : C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     verbosity       : None
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     doDebug         : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     testnet         : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     rpcport         : DEFAULT
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     satoshiHome     : DEFAULT
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     satoshiRpcport  : DEFAULT
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     logDisable      : False
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1034 -     logFile         : C:\Users\bob\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments:
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************
2014-04-19 14:12 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully
2014-04-19 14:12 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager.
2014-04-19 14:12 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background.  
2014-04-19 14:12 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data.
2014-04-19 14:12 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for 
2014-04-19 14:12 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed.
2014-04-19 14:13 (INFO) -- ArmoryUtils.pyc:3007 - Using settings file: C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-19 14:13 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory:
2014-04-19 14:13 (INFO) -- announcefetch.pyc:92 -    announce         : 52b6e5624ed25b90d2d2a783ab87635b048aa8b7cb14b21a958ad052faee8691
2014-04-19 14:13 (INFO) -- announcefetch.pyc:92 -    bootstrap        : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7
2014-04-19 14:13 (INFO) -- announcefetch.pyc:92 -    changelog        : 00e39ea889395a7148dea87274ee60e484c97c67905b65c67782290dad945639
2014-04-19 14:13 (INFO) -- announcefetch.pyc:92 -    downloads        : b553c42962f36961f7ac56b85bdd8d6656a16a95c2ce0bc9d60670165825f786
2014-04-19 14:13 (INFO) -- announcefetch.pyc:92 -    notify           : 011ee87ce2b50a18a06ca4a05f95c5a8f7dc9d55cced2a4654c609eea2795f4c
2014-04-19 14:13 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-19 14:13 (INFO) -- ArmoryQt.py:2244 - loadWalletsAndSettings
2014-04-19 14:13 (INFO) -- ArmoryQt.py:2302 - Loading wallets...
2014-04-19 14:13 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-19 14:13 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-19 14:13 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-19 14:13 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-19 14:13 (ERROR) -- announcefetch.pyc:262 - Tried: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-19 14:13 (WARNING) -- announcefetch.pyc:275 - Error fetching announce digest
2014-04-19 14:13 (INFO) -- ArmoryQt.py:2351 - Number of wallets read in: 1
2014-04-19 14:13 (INFO) -- ArmoryQt.py:2356 -    Wallet (dgfhfgdhg):    "gdfhfgdhdfghgdhm"   (Encrypted)
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1786 - Setting up networking...
2014-04-19 14:13 (ERROR) -- ArmoryQt.py:1829 - Error checking for internet connection
Traceback (most recent call last):
  File "ArmoryQt.py", line 1827, in setupNetworking
  File "urllib2.pyc", line 127, in urlopen
  File "urllib2.pyc", line 404, in open
  File "urllib2.pyc", line 422, in _open
  File "urllib2.pyc", line 382, in _call_chain
  File "urllib2.pyc", line 1214, in http_open
  File "urllib2.pyc", line 1184, in do_open
URLError: <urlopen error [Errno 11004] getaddrinfo failed>
2014-04-19 14:13 (ERROR) -- ArmoryQt.py:1830 - Run --skip-online-check if you think this is an error
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1838 - Internet connection is Available: False
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1839 - Bitcoin-Qt/bitcoind is Available: 0
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1840 - The first blk*.dat was Available: True
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1841 - Online mode currently possible:   False
2014-04-19 14:13 (INFO) -- ArmoryQt.py:2028 - loadBlockchainIfNecessary
2014-04-19 14:13 (INFO) -- ArmoryQt.py:2074 - Setting netmode: 0
2014-04-19 14:13 (INFO) -- BDM.pyc:431 - Setting online mode: False (wait=False)
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1099 - setupUriRegistration
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1167 - Armory already registered for current user.  Done!
2014-04-19 14:13 (INFO) -- ArmoryQt.py:585 - Usermode: Expert
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1366 - Changing usermode:
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1367 -    From: Expert
2014-04-19 14:13 (INFO) -- ArmoryQt.py:1375 -      To: Expert
2014-04-19 14:13 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:OfflineNoSatoshiNoInternet
2014-04-19 14:13 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Offline"
2014-04-19 14:13 (INFO) -- ArmoryQt.py:698 - MinimizeOnOpen is True
2014-04-19 14:43 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-19 14:43 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-19 14:43 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-19 14:43 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-19 14:53 (INFO) -- ArmoryQt.py:6150 - BDM is safe for clean shutdown
2014-04-19 14:53 (INFO) -- BDM.pyc:1346 - Shutdown Requested
2014-04-19 14:53 (ERROR) -- BDM.pyc:1141 - Resetting BDM and all wallets
2014-04-19 14:53 (INFO) -- BDM.pyc:1393 - BDM is shutdown.
2014-04-19 14:53 (INFO) -- SDM.pyc:636 - Called stopBitcoind
2014-04-19 14:53 (INFO) -- SDM.pyc:638 - ...but bitcoind is not running, to be able to stop
2014-04-19 14:53 (INFO) -- ArmoryQt.py:6162 - Attempting to close the main window!
2014-04-19 14:53 (INFO) -- ArmoryQt.py:6435 - Resetting BlockDataMgr, freeing memory
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1009 - 
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1010 - 
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1011 - 
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine:
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1016 -    Armory Version        : 0.91
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1017 -    PyBtcWallet  Version  : 1.35
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1019 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1020 -    User home-directory   : C:\Users\bob\AppData\Roaming
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1021 -    Satoshi BTC directory : C:\Users\bob\AppData\Roaming\Bitcoin\
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1022 -    Armory home dir       : C:\Users\bob\AppData\Roaming\Armory\
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs    : 
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1024 -    Total Available RAM   : 15.99 GB
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1025 -    CPU ID string         : Intel64 Family 5 Model 24 Stepping 2, GenuineIntel
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1026 -    Number of CPU cores   : 6 cores
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1027 -    System is 64-bit      : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1028 -    Preferred Encoding    : cp1252
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1029 - 
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py:
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     maxOpenFiles    : 0
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     nettimeout      : 2
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     rescan          : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     leveldbDir      : DEFAULT
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     ignoreAllZC     : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     port            : None
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     interport       : 8223
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     coverageOutputDir: None
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     rebuild         : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     datadir         : DEFAULT
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     offline         : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     noWalletCheck   : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     satoshiPort     : DEFAULT
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     netlog          : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     keypool         : 100
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     coverageInclude : None
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     forceOnline     : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     skipAnnounceCheck: False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     redownload      : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     disableTorrent  : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     testAnnounceCode: False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     mtdebug         : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     skipVerCheck    : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     settingsPath    : C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     verbosity       : None
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     doDebug         : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     testnet         : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     rpcport         : DEFAULT
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     satoshiHome     : DEFAULT
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     satoshiRpcport  : DEFAULT
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     logDisable      : False
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1034 -     logFile         : C:\Users\bob\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments:
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully
2014-04-19 14:53 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager.
2014-04-19 14:53 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background.  
2014-04-19 14:53 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data.
2014-04-19 14:53 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for 
2014-04-19 14:53 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed.
2014-04-19 14:53 (INFO) -- ArmoryUtils.pyc:3007 - Using settings file: C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-19 14:53 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory:
2014-04-19 14:53 (INFO) -- announcefetch.pyc:92 -    announce         : 52b6e5624ed25b90d2d2a783ab87635b048aa8b7cb14b21a958ad052faee8691
2014-04-19 14:53 (INFO) -- announcefetch.pyc:92 -    bootstrap        : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7
2014-04-19 14:53 (INFO) -- announcefetch.pyc:92 -    changelog        : 00e39ea889395a7148dea87274ee60e484c97c67905b65c67782290dad945639
2014-04-19 14:53 (INFO) -- announcefetch.pyc:92 -    downloads        : b553c42962f36961f7ac56b85bdd8d6656a16a95c2ce0bc9d60670165825f786
2014-04-19 14:53 (INFO) -- announcefetch.pyc:92 -    notify           : 011ee87ce2b50a18a06ca4a05f95c5a8f7dc9d55cced2a4654c609eea2795f4c
2014-04-19 14:53 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-19 14:53 (INFO) -- ArmoryQt.py:2244 - loadWalletsAndSettings
2014-04-19 14:53 (INFO) -- ArmoryQt.py:2302 - Loading wallets...
2014-04-19 14:53 (INFO) -- ArmoryQt.py:2351 - Number of wallets read in: 1
2014-04-19 14:53 (INFO) -- ArmoryQt.py:2356 -    Wallet (dfghdfgh):    "gdfghfdghdfghfghddfgh"   (Encrypted)
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1786 - Setting up networking...
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1838 - Internet connection is Available: True
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1839 - Bitcoin-Qt/bitcoind is Available: 0
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1840 - The first blk*.dat was Available: True
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1841 - Online mode currently possible:   0
2014-04-19 14:53 (INFO) -- ArmoryQt.py:2028 - loadBlockchainIfNecessary
2014-04-19 14:53 (INFO) -- ArmoryQt.py:2074 - Setting netmode: 0
2014-04-19 14:53 (INFO) -- BDM.pyc:431 - Setting online mode: False (wait=False)
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1099 - setupUriRegistration
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1167 - Armory already registered for current user.  Done!
2014-04-19 14:53 (INFO) -- ArmoryQt.py:585 - Usermode: Expert
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1366 - Changing usermode:
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1367 -    From: Expert
2014-04-19 14:53 (INFO) -- ArmoryQt.py:1375 -      To: Expert
2014-04-19 14:53 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-19 14:53 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-19 14:53 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-19 14:53 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:OfflineNoSatoshi
2014-04-19 14:53 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Offline"
2014-04-19 14:53 (INFO) -- ArmoryQt.py:698 - MinimizeOnOpen is True
2014-04-19 14:53 (INFO) -- ArmoryQt.py:6334 - Another Armory instance just tried to open.

It looks like it's not finding bitcoin-qt but it did find the correct underlying directory. You set --satoshi-port to 8331, is Bitcoin port also set to 8331?

382

Bitcoin / Development & Technical Discussion / Re: Technical details on claim script/signatures - Help Please

on: April 19, 2014, 12:03:20 AM

You're getting confused by the generality of that diagram. It is showing how to do it for an ultra-complex script, but the vast majority will be much simpler, and no OP_CODESEPARATORs. For every standard script, and probably most of the useful scripts, the output of Step4 is just the script being spent. Whatever is the raw script of the TxOut being spent by this TxIn, is what's going to be inserted into that TxIn in Step8. In fact, there was some calls to remove OP_CODESEPARATOR, and it seems there's not really any reason to use it that can't be done without it. Therefore, just assume that Step8 is always just copying the raw script being spent, into the TxIn before signing.

383

Bitcoin / Armory / Re: Please Help Test Armory 0.91-beta!

on: April 18, 2014, 09:41:36 PM

Quote from: _r2h on April 18, 2014, 09:25:42 PM Any issues reported with the torrent download not working? Log reveals Quote 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it None 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it for hours on end. This is the first report we've heard of problems with torrent. It's been pretty reliable so far. It sounds like there's a corrupt block in the file being downloaded, and it's not recovering. I would close Armory, go into the Bitcoin homedir (C:\Users\<user>\AppData\Roaming\Bitcoin or /home/<user>/.bitcoin) and remove bootstrap.dat.partial and/or bootstrap.dat. Armory will restart the download next time you start it.

384

Bitcoin / Armory / Re: How long should it take to build database?

on: April 18, 2014, 04:25:42 AM

Feel free to try out the factory reset for us and see if it meets your expectations. Of course it's always a good idea to backup everything first. You especially might consider backing up the ArmorySettings.txt file and copy it back in after the reset. For some reason we didn't include a way to wipe the blk*.dat files without deleting the settings file...

385

Bitcoin / Armory / Re: How long should it take to build database?

on: April 18, 2014, 04:01:30 AM

Quote from: xe99 on April 18, 2014, 03:49:18 AM iv'e installed (upgraded) beta 0.91 from previous version and every time i run Armory it builds the data base which takes almost two hours. i let it run all night last night, turned it back on this evening, it downloaded 100 or so blocks and is rebuilding the data base all over again. i dont remember it taking this long before. is this normal rebuild time for one day of catchup on blockchain. i'm also gettting several disconnects during the process. i'm running ubuntu 12.04. also noticed system seriously lags like memory being all used up during this process but process explorer only showing a couple gigs memory being used. This happens when there is something wrong with your blk*.dat files, such as corruption. I have experienced it once myself and it went away after I re downloaded the blockchain. It's not pleasant but we're not sure of another way at the moment... At least you can do it with the speed of torrent now !

386

Bitcoin / Armory / Re: Armory - Discussion Thread

on: April 18, 2014, 12:04:35 AM

Quote from: shoesman on April 17, 2014, 07:52:24 PM ok ive set the switches as follows "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-port=8331 --satoshi-datadir="C:\Users\bob\AppData\Roaming\Bitcoin\blocks" as well have i tried this one "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-port=8331 --satoshi-datadir=C:\Users\bob\AppData\Roaming\Bitcoin\blocks both make no difference still offline as well has this been tested with online check enabled as well as disabled , nothing --satoshi-datadir should always be pointing at the base Bitcoin directory, i.e. Code: --satoshi-datadir=C:\Users\bob\AppData\Roaming\Bitcoin Also, it would help to know what the dashboard says when it's offline. It almost always tells you why it's offline. With what you're running right now, it probably can't find the blk*.dat files. Once that is fixed, it will tell you the next issue. You posted some logs that look like you intended to be passing these CLI args with it, but it doesn't show any arguments passed. Code: 2014-04-17 15:16 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe If the shortcut is setup right it will say: Code: 2014-04-17 15:16 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=C:\Users\bob\AppData\Roaming\Bitcoin --satoshi-port=8331 --skip-online-check

387

Bitcoin / Armory / Re: Armory - Discussion Thread

on: April 17, 2014, 02:55:01 AM

Quote from: Deth on April 17, 2014, 01:27:31 AM etotheipi, just for your record, it is getting worse building Armory in non Debian-based distros. Quote: Quote Armory developers don't care about Arch user so i made patchs that fix problems. ...while there are 2 patches already to build Armory in Arch (you can scroll down for comments with fixes). Also, why don`t you upload signed archives (or signed hashes of archives) with git snapshots of releases to your website as well as packages, so it will be more building-friendly without that "git tag -v..." thing, which is e.g. hardly inserted in PKGBUILDs of ArchLinux? The makesfiles for the project have been in flux recently, but I think they finally settled down. One of our guys was able to go in and simplify a bunch of stuff that should make building much easier on all platforms. Admittedly, I'm not familiar with what is needed for each distro, but at least our binaries are universal now (the _CppBlockUtils.so). However, it still requires the target system to have Python2.7. We will be merging the v0.91-beta tag into master soon, but there was a merge conflict and the guy I assigned to do that was on vacation. I should've done it already. Also, I actually put the archives into our build&release scripts, but they are like 100 MB each. I think dpkg-build is bundling the entire git repo into those archives (plus some). Until we figure that out, I decided not to release with it.

388

Bitcoin / Armory / Re: Armory - Discussion Thread

on: April 17, 2014, 01:21:05 AM

Quote from: Rampion on April 16, 2014, 11:28:30 PM Please let me suggest that a clear set-up for Tor users should be tested and recommended, running Bitcoin through Tor should be recommended by default IMO, using Bitcoin without Tor is giving away precious privacy to anyone looking at the traffic. While running only Bitcoin Core through Tor is quite easy and intuitive, running Bitcoin Core+Armory isn't easy nor intuitive at all. I think these discussions are part of that process for us. I have zilch experience with Tor, and we never claimed that Armory even had Tor in mind when it was created (not that it is necessarily hard to adapt it, but I probably did things that are non-tor-friendly). I think it would be a good idea for us iron this out more rigorously, and tweak one of the next couple releases to be better-adapted for Tor usage. Then we can put up some informational material about it.

389

Bitcoin / Armory / Re: Armory - Discussion Thread

on: April 16, 2014, 06:54:46 PM

Quote from: goatpig on April 16, 2014, 06:42:59 PM Armory will show offline if one of these 2 requirements isn't met: 1) Connect to a Bitcoin Node on 127.0.0.1 and the port defined by --satoshi-port (8333) by default 2) Be pointed at a folder with a copy of the raw blockchain data, as produced by BitcoinQt. This folder is set by the --satoshi-datadir switch, and defaults to C:\Users\currentuser\AppData\Roaming\Bitcoin\blocks in Windows Im curious if your issue isn't 2) rather than 1) So I'm hardly familiar with Tor at all. But I should remind you that there's a 3rd condition: passing the online-check. You can get around this by adding --skip-online-check to the command-line argument. Most Tor users have required that in order to get online properly.

390

Bitcoin / Armory / Re: How to change path to both .armory and .bitcoin (36GB needed for both atm)

on: April 15, 2014, 09:10:51 PM

Quote from: User1397367406 on April 15, 2014, 08:49:14 PM I just pasted it like that from the website and didn't check it. Argh! The website is killing us. It keeps compressing double-dashes into a single-long dash, and sometimes rendering html as plaintext which butchers the CLI descriptions, etc. I guess now it's replacing quotation marks with lookalike characters. We'll have to figure out a way to get it to behave itself. I hope this issue is resolved now.

391

Bitcoin / Armory / Re: New wallet format

on: April 15, 2014, 07:14:11 PM

Hah. It wasn't so much "maybe later, leave us alone", but more like: "yes! when this reaches high priority, this is exactly what we're going to do!" The answer to this is: new wallet format is highest priority, especially now that we have all the multi-sig hooks in place. And we fixed the RAM issues... and we have resources to handle other things! To address your points directly: we will have support for both compressed and uncompressed. Along with the ability to migrate old wallets. Compressed will be default, but have the capability to handle uncompressed. Standard usermode, will by default, derive all wallets from the same seed, thus requiring one backup per user, not per wallet. But in Adv and Expert, you will have the option to create different seeds which spawn wallets with different backups, encryption passwords and security profiles. This is exceptionally important when it comes to offline wallets and multi-sig, having this flexibility. The new wallet format will also have a much-more-flexible encryption scheme. It will allow for arbitrary data to be stored from set of different encryption and key-stretching options. It would technically allow the user to do very complex things, though none of those complexities will be default. But it allows us to build cool things into it -- like the ability to encrypt comments&labels with your publickey&chaincode, thus all your watching-only wallets can decrypt the data, and thus that data can be backed up and synchronized between devices (as long as you don't store the WO wallet with it!) Or multiple people in an organization can easily synchonize meta-data just by having the WO wallet. There's a lot of cool things we can do with it. This only scratches the surface Stay tuned! --- P.S. - When I said this was high-priority, it was originally because we were really anxious to get some multi-sig features implemented, and we thought that we would have to wait for the new wallet format to do it. With the availability of lockboxes right now we are actually going to prioritize that first, and then work on the new wallet which will provide much more flexible multi-sig. Because, we want to take our time with the new wallets, and if there's already a usable multi-sig solution out there, then we won't be as rushed.

392

Bitcoin / Armory / Re: Armory cannot import _CppBlockUtils.so on my Raspberry Pi

on: April 14, 2014, 04:24:46 AM

That first launch error is silly. We've seen it like 3 times out of 200 launches: it simply prevents Armory from opening that one time, then goes away the next time. I'd love to isolate it, but we can't reproduce it. Maybe one day. As for the wallet error... it's somehow reading a zero-length key. Perhaps the there was wallet corruption after you made the decrypted backup? I'm not sure -- as you can see it's a little thrown off by the duplicate wallet in the .armory directory... it's not intended to store multiple, duplicate wallets there -- you're supposed to make the decrypted backup to a removable drive or something. Of course it's supposed to work. Somehow the original wallet is corrupted...? Maybe you could backup those wallets (in case we need to debug it later) and simply try out all the other operations? It would be good to know if everything else works as expected, and then we can figure out what happened with those wallets later.

393

Bitcoin / Armory / Re: Lubuntu 13.10 + Armory, Dependency Issues

on: April 13, 2014, 06:57:40 PM

For now, I would recommend you use one of the 0.90-beta offline bundles available on the website. If you use the 12.04 bundle, I recommend downloading 12.04.3, as they seemed to change some stuff around in 12.04.4. http://old-releases.ubuntu.com/releases/12.04.3/ And only use regular Ubuntu ... not Lubuntu, Kubunutu, Xubuntu. The offline bundle is very sensitive in this respect...

394

Bitcoin / Armory / Re: [TEASER] Multi-Key Lockboxes!

on: April 13, 2014, 06:52:06 PM

FYI, this was a big hit at the conference. There's a lot of pent-up demand for this feature! Even though it doesn't have all the privacy properties of a properly-implemented linked-wallet solution, the security achievable with it for low-volume transactions is awesome. Since the conference, we have tweaked it quite a bit, and it's a lot more usable and stable. We will be working on it over the next couple weeks and probably breaking it. If you want to play with it and multihacker branch doesn't work, you can checkout this commit which is a very stable snapshot of the new functionality: https://github.com/etotheipi/BitcoinArmory/commit/d8811a1c8892e373d6ff4de779ab2c75b5a21dc1 Seriously, try it out on testnet according the instructions in the top-post. You really can setup multisig lockboxes with multiple offline computers, review them, sign them, broadcast them, etc.

395

Bitcoin / Armory / Re: How to change path to both .armory and .bitcoin (36GB needed for both atm)

on: April 13, 2014, 06:46:05 PM

Notice you're missing a " at the end of the CLI args. I bet that's the problem. I know the log is confusing... the first set of paths are what are autodetected, before it processes the CLI args. Then it processes the CLI args and overwrites them, including the settings file, etc. Too much logging, I guess. Check that target and try again.

396

Bitcoin / Armory / Re: Armory cannot import _CppBlockUtils.so on my Raspberry Pi

on: April 13, 2014, 06:35:33 PM

Quote from: User1397367406 on April 13, 2014, 06:32:11 PM I can create a new wallet, make a paper backup and verify it, get a new receiving address, create and import a watching only wallet, ..., seems to be working. I gonna try it on a fresh install of Raspbian as for now i tested it on the system where i also compiled the other version, just to make sure of any other missing dependency. That tar.gz doesn't have the dependences with it. It assumes all the dependencies are already there. We've been swamped with some other things, so we weren't able to create a full bundle for it, but knew that the compile step was a real PITA, so this helps get over the biggest hurdle.

397

Bitcoin / Armory / Re: How to change path to both .armory and .bitcoin (36GB needed for both atm)

on: April 13, 2014, 06:30:35 PM

Quote from: User1397367406 on April 13, 2014, 06:21:44 PM What do you mean by "both target directories exist" ? The "--satoshi-datadir=I:\bitcoin" folder exists and bitcoin-qt can run out of it and is synced to the network. The "--datadir=I:\armory" exists but is empty, as it should be filled when running Armory. Do i have to remove the bitcoin and Armory dirs from under roaming? Does these dirs have to be fully working under roaming before i can copy them over to a new location? Also the "--dbdir" args doesn't work as when specified armory doesn't start. I meant, Armory won't create them for you, they should exist already. As you said, I:\armory should exist (and be empty) before using it. I'm not sure why it doesn't work unless you simply copied it wrong. It always defaults to the roaming folder if the specified folder doesn't exist... I had been meaning to change that behavior, but that's how it is at the moment. It does appear that you are correctly using --datadir instead of the single-dash version that Bitcoin core expects. If it's starting in the roaming directory, it is also writing an armorylog.txt file there. It may give you a hint (error) concerning the directories. There's a list of directories it's using, near the top of the log. Make sure the timestamps match what you're expecting (i.e. that you're looking at the correct log file). We recently had some issues with CLI args like this, and I did some pretty rigorous testing before making the new release. If those args are set correctly, it won't even see the roaming folders. In the next version, we're going to find a way to make all these things adjustable from the preferences window.

398

Bitcoin / Armory / Re: How to change path to both .armory and .bitcoin (36GB needed for both atm)

on: April 13, 2014, 02:12:05 PM

Quote from: User1397367406 on April 13, 2014, 06:12:02 AM Quote Bitcoin https://en.bitcoin.it/wiki/Data_directory Armory https://bitcoinarmory.com/download/troubleshooting/ (bottom of page) Quote "C:\Program Files (x86)\Armory-testing\ArmoryQt.exe" --satoshi-datadir=I:\bitcoin --datadir=I:\armory These aforementioned hints doesn't seem to apply anymore for the version 0.91 of Armory. I tried it on Win7 but it always tries to create/update the folders under the roaming folder and download the entire files ... Changing the Bitcoin dir in the settings or starting bitcoin-qt manually (with datadir set and disabling armory bitcoinqt/bitcoind control) doesn't help either. Any chance to move these 2 directories to an other folder? I can't let it run in the roaming folder as i have less than 5GB left on the drive. Make sure both target directories exist before running like that.

399

Bitcoin / Armory / Re: Armory cannot import _CppBlockUtils.so on my Raspberry Pi

on: April 13, 2014, 02:27:45 AM

Sorry to keep poking this thread, but I do want to make sure this is right, and I don't have an RPi setup to test (I do have one, but I've never set it up):

https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91-beta_raspbian.tar.gz

Please try it again, the signed hash is below (using my email key, 0xFB596985, which should be good enough at least for testing purposes)

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

c1485f802b33f82998d65611b17861959dedbdb38524233ccce750b822514893  armory_0.91-beta_raspbian.tar.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJTSfWzAAoJEBHe6b77WWmFHYsP/A4B0wx/fJHc3MGjO9hY4M+u
CUJmNrJg2CEOMReyREid8iqVL9F1PGnSdU1FBmO/LMaOqoYFPBFzvILTzVBg5j4T
ynO8DKqaLuKhDyMRYgD1oH8dRaXl8QCXp5i+e19Vsvjv2wUXZ0UqHta+jw8zzunV
CUbZwEZh2SHARzzYiyihpjOsjLtqPfIn/au87l6u1P+3/HthNO4mq3cAwe49exVU
S2ajtmWSyLU9nKXZcwiXgil++CjUdibhyAh83WdJFDIfcAKKWbtzAQGDKt4oIYbS
q6ecO7CeLHdO3WTtpEgVJPEWKt3bNf2GSEZ1wkTK+NMjEPSj23dxv20zO62h7+7C
71lAjeCE6MFoOcKb8KcPV+nyokNUp5m/4n+uH38DcHvpGmnLpwsBUv8enL36DDJk
jDrH/pwFEyXCHkvTvJ0P7N0MC+BQu/ErdAzH7fOd8oqBb056BTGu7xZ9MZ2iXRNa
RYmD4/brbZmT7rrXZgE+4QrqFTQr1nrGetFPw8n2Vg7+Q8hr99UiHl9YBRkXUfb9
81BslwLwgtlCRnFdrE72j/atTMUMXQ4jpbj+KLI5p0/7r5Ky2Mo2NbWWAlsksoIR
Bh79Iz6/BAeteaC/zD6HPGHBfX1Nm76htnhILEHERPRqiqLkksKZ7GmQSoOK8zfm
6k30DkdDuwhD2NBhOBNA
=iTzb
-----END PGP SIGNATURE-----

400

Bitcoin / Armory / Re: Armory cannot import _CppBlockUtils.so on my Raspberry Pi

on: April 13, 2014, 01:22:25 AM

Quote from: etotheipi on April 13, 2014, 12:01:59 AM I bet I botched the build process and compiled for i386 instead of armhf. We verified the build process worked, and then I made a script to make it easier, but I bet I did the script wrong. I'm about to put out 0.91.1 with some tweaks to the wallet-fixing logic and the new Bitcoin Core download. I'll see if I can fix the RPi cross-compile script. It looks like that's exactly what happened, I accidentally use the i386 g++ instead of the armhf g++. The old one: Code: ~/temp/armory_rpi/usr/lib/armory $ file _CppBlockUtils.so _CppBlockUtils.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=0x1e56789efad37396cf2ae2f426ccbd6f0751e2e0, not stripped Now that I did it manually and verified the correct compiler was being used: Code: ~/projects/bitcoin/compiledrpi/usr/lib/armory $ file _CppBlockUtils.so _CppBlockUtils.so: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, not stripped I'll update the RPi cross-compile script and have a new version along with everything else, soon.

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 ... 186 »