Bitcoin Forum
November 08, 2024, 07:35:43 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Armory eternally in Offline Mode  (Read 2119 times)
spclover (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
March 17, 2014, 02:16:15 PM
 #1

Hello people.

I know I'm new at this, and yes, I HAVE SEARCHED in the site and Google documentation about this and there isn't so many. And the few there are, assume the new people are God in this and understand everything of everything...


I have tried lot of things to set Armory in Online mode, but there is no way: launch Armory with Bitcoin opened/closed, close Bitcoin from Armory, deactivating Firewalls, downloaded the full blockchain, giving Administrator rights to Armory, etc., etc. In the log File it says there is network conection, and the only problem I can find (or see) is "Failed to setup SDM". Every time I have launched Armory, I check the LogFile, and this one is the only that got connected internally, but in the software it says "Armory is Offline". Can somebody please tell me what I'm doing wrong, or what else I can check?

Thanks a lot.

Code:
2014-03-14 17:24 (INFO) -- armoryengine.pyc:809 - ************************************************************
2014-03-14 17:24 (INFO) -- armoryengine.pyc:810 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-03-14 17:24 (INFO) -- armoryengine.pyc:811 - ************************************************************
2014-03-14 17:24 (INFO) -- armoryengine.pyc:812 - Loading Armory Engine:
2014-03-14 17:24 (INFO) -- armoryengine.pyc:813 -    Armory Version        : 0.90
2014-03-14 17:24 (INFO) -- armoryengine.pyc:814 -    PyBtcWallet  Version  : 1.35
2014-03-14 17:24 (INFO) -- armoryengine.pyc:815 - Detected Operating system: Windows
2014-03-14 17:24 (INFO) -- armoryengine.pyc:816 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2014-03-14 17:24 (INFO) -- armoryengine.pyc:817 -    User home-directory   : C:\Users\user\AppData\Roaming
2014-03-14 17:24 (INFO) -- armoryengine.pyc:818 -    Satoshi BTC directory : C:\Users\user\AppData\Roaming\Bitcoin\
2014-03-14 17:24 (INFO) -- armoryengine.pyc:819 -    Armory home dir       : C:\Users\user\AppData\Roaming\Armory\
2014-03-14 17:24 (INFO) -- armoryengine.pyc:820 - Detected System Specs    :
2014-03-14 17:24 (INFO) -- armoryengine.pyc:821 -    Total Available RAM   : 6.92 GB
2014-03-14 17:24 (INFO) -- armoryengine.pyc:822 -    CPU ID string         : Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
2014-03-14 17:24 (INFO) -- armoryengine.pyc:823 -    Number of CPU cores   : 2 cores
2014-03-14 17:24 (INFO) -- armoryengine.pyc:824 -    System is 64-bit      : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:825 -    Preferred Encoding    : cp1252
2014-03-14 17:24 (INFO) -- armoryengine.pyc:826 -
2014-03-14 17:24 (INFO) -- armoryengine.pyc:827 - Network Name: Main Network
2014-03-14 17:24 (INFO) -- armoryengine.pyc:828 - Satoshi Port: 8333
2014-03-14 17:24 (INFO) -- armoryengine.pyc:829 - Named options/arguments to armoryengine.py:
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     maxOpenFiles    : 0
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     nettimeout      : 2
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     rescan          : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     leveldbDir      : DEFAULT
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     port            : None
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     interport       : 8223
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     coverageOutputDir: None
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     rebuild         : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     datadir         : DEFAULT
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     offline         : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     satoshiPort     : DEFAULT
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     netlog          : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     keypool         : 100
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     coverageInclude : None
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     forceOnline     : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     logDisable      : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     mtdebug         : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     skipVerCheck    : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     settingsPath    : C:\Users\user\AppData\Roaming\Armory\ArmorySettings.txt
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     verbosity       : None
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     doDebug         : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     testnet         : False
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     rpcport         : DEFAULT
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     satoshiHome     : DEFAULT
2014-03-14 17:24 (INFO) -- armoryengine.pyc:831 -     logFile         : C:\Users\user\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-03-14 17:24 (INFO) -- armoryengine.pyc:832 - Other arguments:
2014-03-14 17:24 (INFO) -- armoryengine.pyc:835 - ************************************************************
2014-03-14 17:24 (INFO) -- armoryengine.pyc:1041 - C++ block utilities loaded successfully
2014-03-14 17:24 (INFO) -- armoryengine.pyc:13507 - Using the asynchronous/multi-threaded BlockDataManager.
2014-03-14 17:24 (INFO) -- armoryengine.pyc:13508 - Blockchain operations will happen in the background.  
2014-03-14 17:24 (INFO) -- armoryengine.pyc:13509 - Devs: check TheBDM.getBDMState() before asking for data.
2014-03-14 17:24 (INFO) -- armoryengine.pyc:13510 - Registering addresses during rescans will queue them for
2014-03-14 17:24 (INFO) -- armoryengine.pyc:13511 - inclusion after the current scan is completed.
2014-03-14 17:24 (INFO) -- armoryengine.pyc:11561 - Using settings file: C:\Users\user\AppData\Roaming\Armory\ArmorySettings.txt
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1639 - loadWalletsAndSettings
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1686 - Loading wallets...
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1734 - Number of wallets read in: 1
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1739 -    Wallet (EDITED FOR SECURITY):    "RecWallet                       "   (Encrypted)
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1317 - Setting up networking...
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1370 - Internet connection is Available: True
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1371 - Bitcoin-Qt/bitcoind is Available: 8333
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1372 - The first blk*.dat was Available: True
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1373 - Online mode currently possible:   True
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1380 - startBitcoindIfNecessary
2014-03-14 17:24 (WARNING) -- ArmoryQt.py:1390 - Tried to start bitcoind, but satoshi already running
2014-03-14 17:24 (INFO) -- ArmoryQt.py:882 - setupUriRegistration
2014-03-14 17:24 (WARNING) -- ArmoryQt.py:929 - running from: C:\Program Files (x86)\Armory\ArmoryQt.exe, key: "C:\Program Files (x86)\Armory\ArmoryQt.exe" %1
2014-03-14 17:24 (INFO) -- ArmoryQt.py:990 - URL-register action: DoIt
2014-03-14 17:24 (INFO) -- ArmoryQt.py:993 - Registering Armory  for current user
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1007 - Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1007 - Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\URL Protocol
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1007 - Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\shell\
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1007 - Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\shell\open\
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1007 - Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\shell\open\command\
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1007 - Writing key: [HKEY_CURRENT_USER\] Software\Classes\bitcoin\DefaultIcon\
2014-03-14 17:24 (WARNING) -- ArmoryQt.py:1012 - app dir: C:\Program Files (x86)\Armory
2014-03-14 17:24 (INFO) -- ArmoryQt.py:4269 - Dashboard switched to auto-butSatoshiRunning
2014-03-14 17:24 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:Auto, State:OfflineBitcoindRunning
2014-03-14 17:24 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-03-14 17:24 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Offline"
2014-03-14 17:24 (INFO) -- ArmoryQt.py:533 - Usermode: Advanced
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1150 - Changing usermode:
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1151 -    From: Advanced
2014-03-14 17:24 (INFO) -- ArmoryQt.py:1159 -      To: Advanced
2014-03-14 17:25 (INFO) -- armoryengine.pyc:10882 - Signature on signed data block is GOOD!
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1289 - Latest versions:
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1290 -    Satoshi: 0.8.1
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1291 -     Armory: 0.88
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1300 - You are running the latest version!
2014-03-14 17:25 (WARNING) -- armoryengine.pyc:661 - Killing process pid=2864
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1380 - startBitcoindIfNecessary
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1411 - setSatoshiPaths
2014-03-14 17:25 (INFO) -- armoryengine.pyc:10969 - Found bitcoind in the following places:
2014-03-14 17:25 (INFO) -- armoryengine.pyc:10971 -    C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-14 17:25 (INFO) -- armoryengine.pyc:10973 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11125 - Reading bitcoin.conf file
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11131 - No bitcoin.conf available.  Creating it...
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11144 - Setting permissions on bitcoin.conf
2014-03-14 17:25 (INFO) -- armoryengine.pyc:625 - Executing popen: ['icacls', 'C:\\Users\\user\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'user:F']
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11149 - icacls returned: archivo procesado: C:\Users\user\AppData\Roaming\Bitcoin\bitcoin.conf

Se procesaron correctamente 1 archivos; error al procesar 0 archivos


2014-03-14 17:25 (ERROR) -- ArmoryQt.py:1405 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1400, in startBitcoindIfNecessary
  File "armoryengine.pyc", line 10999, in setupSDM
  File "armoryengine.pyc", line 11155, in readBitcoinConf
IOError: [Errno 13] Permission denied: 'C:\\Users\\user\\AppData\\Roaming\\Bitcoin\\bitcoin.conf'
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1480 - Setting netmode: 0
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1380 - startBitcoindIfNecessary
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1411 - setSatoshiPaths
2014-03-14 17:25 (INFO) -- armoryengine.pyc:10969 - Found bitcoind in the following places:
2014-03-14 17:25 (INFO) -- armoryengine.pyc:10971 -    C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-14 17:25 (INFO) -- armoryengine.pyc:10973 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11125 - Reading bitcoin.conf file
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11144 - Setting permissions on bitcoin.conf
2014-03-14 17:25 (INFO) -- armoryengine.pyc:625 - Executing popen: ['icacls', 'C:\\Users\\user\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'user:F']
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11149 - icacls returned: archivo procesado: C:\Users\user\AppData\Roaming\Bitcoin\bitcoin.conf

Se procesaron correctamente 1 archivos; error al procesar 0 archivos


2014-03-14 17:25 (ERROR) -- ArmoryQt.py:1405 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1400, in startBitcoindIfNecessary
  File "armoryengine.pyc", line 10999, in setupSDM
  File "armoryengine.pyc", line 11155, in readBitcoinConf
IOError: [Errno 13] Permission denied: 'C:\\Users\\user\\AppData\\Roaming\\Bitcoin\\bitcoin.conf'
2014-03-14 17:25 (INFO) -- ArmoryQt.py:1480 - Setting netmode: 0
2014-03-14 17:25 (INFO) -- ArmoryQt.py:4982 - BDM is safe for clean shutdown
2014-03-14 17:25 (INFO) -- armoryengine.pyc:13435 - Shutdown Requested
2014-03-14 17:25 (ERROR) -- armoryengine.pyc:13216 - Resetting BDM and all wallets
2014-03-14 17:25 (INFO) -- armoryengine.pyc:13481 - BDM is shutdown.
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11263 - Called stopBitcoind
2014-03-14 17:25 (INFO) -- armoryengine.pyc:11265 - ...but bitcoind is not running, to be able to stop
2014-03-14 17:25 (INFO) -- ArmoryQt.py:5010 - Attempting to close the main window!
2014-03-14 17:25 (INFO) -- ArmoryQt.py:5121 - Resetting BlockDataMgr, freeing memory

idoB
Jr. Member
*
Offline Offline

Activity: 70
Merit: 2


View Profile
March 17, 2014, 02:38:04 PM
 #2

I think I see at least one problem in the log file you attached:

[
Code:
...
IOError: [Errno 13] Permission denied: 'C:\\Users\\user\\AppData\\Roaming\\Bitcoin\\bitcoin.conf
...

It looks like a permission issue.

Try this:
with armory shut down, run bitcoin-qt. Can you get it to run and fully sync (green checkmark at bottom right corner)?

If not, the above is likely the issue. Try changing permission, run bitcoin-qt as adminstrator. This is a prerequisite to getting Armory up and synced.

If bitcoin-qt isn't the issue - run armory, go to File-Settings and clear 'Let Armory run bitcoin-qt ' checkbox.

Have bitcoin-qt running and synced and restart Armory, and let's see what happens.


spclover (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
March 17, 2014, 02:52:03 PM
 #3

I think I see at least one problem in the log file you attached:

[
Code:
...
IOError: [Errno 13] Permission denied: 'C:\\Users\\user\\AppData\\Roaming\\Bitcoin\\bitcoin.conf
...

It looks like a permission issue.

Try this:
with armory shut down, run bitcoin-qt. Can you get it to run and fully sync (green checkmark at bottom right corner)?

If not, the above is likely the issue. Try changing permission, run bitcoin-qt as adminstrator. This is a prerequisite to getting Armory up and synced.

If bitcoin-qt isn't the issue - run armory, go to File-Settings and clear 'Let Armory run bitcoin-qt ' checkbox.

Have bitcoin-qt running and synced and restart Armory, and let's see what happens.





I really thank your help!

Bitcoin-QT was fully sync. As I see, the problem was that, for any reason, bitcoin-qt wasn't getting Admin rights... NOW Armory is building Databases! I don't understand how bitcoin-qt could sync if supposedly didn't have admin rights, but now Armory is making its way.

I thought Armory options to find Bitcoin-QT must be enabled to find the paths itself... Then every time I use Armory, I'll have to launch Bitcoin-QT previously?

Thanks a lot! =D
idoB
Jr. Member
*
Offline Offline

Activity: 70
Merit: 2


View Profile
March 17, 2014, 03:07:08 PM
 #4

Welcome. Also noted from the log file you posted (unrelated to the problem):

Code:
...
2014-03-14 17:24 (INFO) -- armoryengine.pyc:815 - Detected Operating system: Windows
2014-03-14 17:24 (INFO) -- armoryengine.pyc:816 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2014-03-14 17:24 (INFO) -- armoryengine.pyc:821 -    Total Available RAM   : 6.92 GB
2014-03-14 17:24 (INFO) -- armoryengine.pyc:822 -    CPU ID string         : Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
2014-03-14 17:24 (INFO) -- armoryengine.pyc:823 -    Number of CPU cores   : 2 cores
2014-03-14 17:24 (INFO) -- armoryengine.pyc:824 -    [b]System is 64-bit      : False[/b]
...

Looks like you're running windows 7 on an intel 64bit machine with 8gb ram, but 'System is 64-bit : False'

It's best if everything would be 64bit: Windows and Bitcoin-qt and Armory. There are seperate versions for 64 bit. I'm not sure what in the system is not, but if you have windows 64bit running, it will make better use of your memeory, and Armory and bitcoinqt will run with better memory utilization.

spclover (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
March 17, 2014, 03:16:21 PM
 #5

I really appreciate your help, but my system is 64b! o_O

And Armory install says it's to x86 and x64. I searched for Bitcoin-QT in 64, but there isn't... at least in the official download site.
idoB
Jr. Member
*
Offline Offline

Activity: 70
Merit: 2


View Profile
March 17, 2014, 03:39:48 PM
 #6

It's a release candidate, but it's considered stable enough:

http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.9.0/test/
etotheipi
Legendary
*
Offline Offline

Activity: 1428
Merit: 1093


Core Armory Developer


View Profile WWW
March 17, 2014, 07:19:39 PM
 #7

I really appreciate your help, but my system is 64b! o_O

And Armory install says it's to x86 and x64. I searched for Bitcoin-QT in 64, but there isn't... at least in the official download site.

Turns out there's a bug in the isX64 logic.  It reports the python build, not the CPU architecture.  Since Armory was built with all 32-bit libraries on Windows, I believe it always reports 32-bits there regardless of CPU architecture.  You can safely ignore that.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Kluge
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1015



View Profile
August 14, 2014, 08:22:35 PM
 #8

Okay, I definitely deserve some bug squashing money here. Tongue I've had this problem for over a year and actually quit using Armory because of it, but the issue's actually stupid-simple.

Bitcoin.conf ends up perma-locked for reasons I'm unsure of in Windows systems (at the very least, win7 x64). An administrator is actually not able to do anything with the file, with privileges assigned only to a weird hash named "Account unknown." Core appears to be able to get around this, and maybe it is this "Account unknown" hash, but Armory doesn't appear to have any solution to this and is locked out, thus causing to stay in offline mode after failing to read the conf file.

The solution is to right-click bitcoin.conf (probably in C:\Users\YourUserName\AppData\Roaming\Bitcoin), click Properties, click on the Security tab, then click Continue (to provide admin privileges). Click the Edit box, then Add, then Advanced. Click "Find Now" and find "Everyone" (Administrator will not work) and click OK. Ensuring you have Everyone highlighted, in the "Permissions for Everyone" box, tick the box for Allow next to Full Control. Click OK one last time, then boot up Armory and you should be golden.

(Read permission should be enough -- full control is relatively dangerous, I guess)
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!