Topic: Armory stuck in offline mode... - page 2. (Read 26438 times)

force your block file location using --satoshi-datadir

recently purchased a new ssd to serve to my armory installation but other time is full the disk and i moved the bitcoin directory to other disk and marked it in armory settings, but dont work it keep in offline mode and dont work and bitcoind dont close properly
bitcoin core work well in the new location
help please!!!
2016-02-17 20:32 (ERROR) -- Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 4340, in executeModeSwitch
    TheBDM.goOnline()
  File "/usr/lib/armory/armoryengine/BDM.py", line 148, in inner
    return func(*newArgs, **kwargs)
  File "/usr/lib/armory/armoryengine/BDM.py", line 251, in goOnline
    self.bdmThread.setConfig(self.bdmConfig())
  File "/usr/lib/armory/armoryengine/BDM.py", line 148, in inner
    return func(*newArgs, **kwargs)
  File "/usr/lib/armory/armoryengine/BDM.py", line 339, in bdmConfig
    bdmConfig.blkFileLocation = blockdir
  File "/usr/lib/armory/CppBlockUtils.py", line 2203, in
    __setattr__ = lambda self, name, value: _swig_setattr(self, BlockDataManagerConfig, name, value)
  File "/usr/lib/armory/CppBlockUtils.py", line 51, in _swig_setattr
    return _swig_setattr_nondynamic(self,class_type,name,value,0)
  File "/usr/lib/armory/CppBlockUtils.py", line 44, in _swig_setattr_nondynamic
    if method: return method(self,value)
TypeError: in method 'BlockDataManagerConfig_blkFileLocation_set', argument 2 of type 'string const &'

2016-02-17 20:32 (INFO) -- Networking.py:215 - Received new block.  000000000000000001987699506eb97a6b5423e5191521a4866722fea9d46867
2016-02-17 20:35 (ERROR) -- Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 4340, in executeModeSwitch
    TheBDM.goOnline()
  File "/usr/lib/armory/armoryengine/BDM.py", line 148, in inner
    return func(*newArgs, **kwargs)
  File "/usr/lib/armory/armoryengine/BDM.py", line 251, in goOnline
    self.bdmThread.setConfig(self.bdmConfig())
  File "/usr/lib/armory/armoryengine/BDM.py", line 148, in inner
    return func(*newArgs, **kwargs)
  File "/usr/lib/armory/armoryengine/BDM.py", line 339, in bdmConfig
    bdmConfig.blkFileLocation = blockdir
  File "/usr/lib/armory/CppBlockUtils.py", line 2203, in
    __setattr__ = lambda self, name, value: _swig_setattr(self, BlockDataManagerConfig, name, value)
  File "/usr/lib/armory/CppBlockUtils.py", line 51, in _swig_setattr
    return _swig_setattr_nondynamic(self,class_type,name,value,0)
  File "/usr/lib/armory/CppBlockUtils.py", line 44, in _swig_setattr_nondynamic
    if method: return method(self,value)
TypeError: in method 'BlockDataManagerConfig_blkFileLocation_set', argument 2 of type 'string const &'

2016-02-17 20:35 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2016-02-17 20:35 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window!
2016-02-17 20:35 (ERROR) -- Networking.py:359 - ***Connection to Satoshi client LOST!  Attempting to reconnect...

I finally got mine unstuck. I ended up gutting all the bitcoind and armory data and starting over. I had a paper wallet so I was able to recover so I did not need the wallet file. With my Intel i3 laptop it took about 3 days. A friend told me that as long as the time (in the log file) was updating and not a lot of unexplainable errors it should be good. I did have to recover my wallet from the paper wallet.

Hi!

I am experiencing the same issue as described in this thread's first entry:

Armory simply stays in offline mode, hitting the "Go Online!" button does not have any effect.

What I tried/have done so far:

- use Linux instead of Mac OSX
- either let armory control bitcoind or start bitcoin-qt manually
- start with "Skip online check on startup" checked in settings (and unchecked)
- making sure I am running the latest software versions
- re-download blockchain and start with a fresh install
- making sure all data is read- and writable

Situation now is: The wallet is there, armory has read the blockchain - but it remains offline and so the bitcoin I transfered to this address has not yet appeared..  :-(

As I'm pretty new to armory & bitcoin in general, any advice shall be gratefully taken...

Thanks a lot!

0.11.2 fixes some of these db issues with core, but 0.12 is when the complete fix for Windows users will arrive (only a few weeks till the release candidate apparently).

Corrupted DB, you need to let Core reindex the chain. BitcoinQt should prompt you with the error and ask to reindex. If it doesn't, delete the /chainstate folder. If that still doesn't make it, in /blocks, delete blk00367.dat, rev00367.dat and all blk+rev that come after 367

I have a similar problem with Amory that I suspect is due to Bitcoin Core not connecting. When I run Bitcoin Core I receive this error log:




2015-11-18 15:41:48 Bitcoin version v0.11.1 (2015-10-12 20:58:31 +0200)
2015-11-18 15:41:48 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2015-11-18 15:41:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2015-11-18 15:41:48 Default data directory C:\Users\Greg\AppData\Roaming\Bitcoin
2015-11-18 15:41:48 Using data directory C:\Users\Greg\AppData\Roaming\Bitcoin
2015-11-18 15:41:48 Using config file C:\Users\Greg\AppData\Roaming\Bitcoin\bitcoin.conf
2015-11-18 15:41:48 Using at most 125 connections (2048 file descriptors available)
2015-11-18 15:41:48 Using 4 threads for script verification
2015-11-18 15:41:48 Using wallet wallet.dat
2015-11-18 15:41:48 scheduler thread start
2015-11-18 15:41:48 init message: Verifying wallet...
2015-11-18 15:41:48 CDBEnv::Open: LogDir=C:\Users\Greg\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Greg\AppData\Roaming\Bitcoin\db.log
2015-11-18 15:41:48 Bound to [::]:8333
2015-11-18 15:41:48 Bound to 0.0.0.0:8333
2015-11-18 15:41:48 Cache configuration:
2015-11-18 15:41:48 * Using 2.0MiB for block index database
2015-11-18 15:41:48 * Using 32.5MiB for chain state database
2015-11-18 15:41:48 * Using 65.5MiB for in-memory UTXO set
2015-11-18 15:41:48 init message: Loading block index...
2015-11-18 15:41:48 Opening LevelDB in C:\Users\Greg\AppData\Roaming\Bitcoin\blocks\index
2015-11-18 15:41:48 Opened LevelDB successfully
2015-11-18 15:41:48 Opening LevelDB in C:\Users\Greg\AppData\Roaming\Bitcoin\chainstate
2015-11-18 15:41:48 Opened LevelDB successfully
2015-11-18 15:41:52 LoadBlockIndexDB: last block file = 368
2015-11-18 15:41:52 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=138, size=91703377, heights=382189...382325, time=2015-11-05...2015-11-06)
2015-11-18 15:41:52 Checking all blk files are present...
2015-11-18 15:41:53 LoadBlockIndexDB: transaction index disabled
2015-11-18 15:41:53 LoadBlockIndexDB: hashBestChain=00000000000000000b48452a4825f7a171b7dcc4a4e63db523a39b9bXXXXXXX
height=382323 date=2015-11-06 15:46:00 progress=0.988535
2015-11-18 15:41:53 init message: Verifying blocks...
2015-11-18 15:41:53 Verifying last 288 blocks at level 3
2015-11-18 15:42:02 No coin database inconsistencies in last 6 blocks (10291 transactions)
2015-11-18 15:42:02  block index           13494ms
2015-11-18 15:42:02 init message: Loading wallet...
2015-11-18 15:42:02 nFileVersion = 110100
2015-11-18 15:42:02 Keys: 0 plaintext, 215 encrypted, 1 w/ metadata, 215 total
2015-11-18 15:42:02  wallet                   16ms
2015-11-18 15:42:02 init message: Activating best chain...
2015-11-18 15:42:02 ERROR: CheckProofOfWork(): nBits below minimum work
2015-11-18 15:42:02 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=368, nPos=90754277)
2015-11-18 15:42:02 *** Failed to read block
2015-11-18 15:42:11 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument

Am I correct in thinking that Bitcoin Core needs to be connected?  If so what do I need to do to get this running? If I am wrong about the need for Bitcoin Core connecting I can post the Armory Log.

Unrelated issue. Submit a log file.

Help - Just changed to .92.3 and my Armory says it is Offline and when I go to the logdump it says:
 "2015-11-03 17:43 (ERROR) -- ArmoryUtils.pyc:3154 - Error in pybkgdthread: Must unlock wallet to change passphrase"

How do I "unlock" my wallet. What menu item do I select?  

Awesome.
Thanks!

 

Start BitcoinQt on its own and let it catch up. Then close it and restart Armory. Should be back to normal.

I'm not having a "stuck in offline mode" problem per-se.

My issue is is we had a power outage which shut down my computer and something got corrupted.

When I start Armory it stays on the "initializing bitcoin engine" mode with the "wheel" spinning.

 Forever......

I have tried each of the 3 "Factory Reset" options. The 3rd one is the only one that works.

I usually shut down Armory before turning off my computer, which is what I do when I leave town for extended periods.

When I restart my computer and then Armory. It starts that same process all over again.

I never had this problem before the outage. I'd always turn everything back on and Armory would only take about 45 minutes

to sync to the current block.

Now I have to do the extreme factory reset each time or just leave the computer always "on".

Any ideas?

-Mark-

Hey DLS, I think we should upgrade out bitcoin core to 0.11 which was just released yesterda, just to see if it might work:
https://bitcointalksearch.org/topic/bitcoin-core-0110-has-been-released-1119832

Another thing that I've been using to avoid the frequent problem of having to reindex:
Make a backup of the chainstate golder found in appdata/roaming/bitcoin. If you are asked to reindex you can always use the backet up copy to avoid it (if the backed up copy is reindexed already of course).

Similar issue here. Windows 7, and armory wont connect, with no reason given. I have a few btc I am trying to transfer out of Armory, and can't get it to connect.

Any help from tech support about this issue?

Meantime I tried finishing downloading the blockchain just with bitcoin core, but it is stuck at 9 hours. Any ideas?

On windows 7, have the same problem OFFLINE, and the dashboard doesn't say anything about why. I already tried with skip online check on and off, same result:



My armorycpplog file:

Log file opened at 1435543965: C:\Users\Lortel24jun15\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1435560228: (..\BlockUtils.cpp:894) blkfile dir: C:\Users\Lortel24jun15\AppData\Roaming\Bitcoin\blocks
-INFO  - 1435560228: (..\BlockUtils.cpp:895) lmdb dir: C:\Users\Lortel24jun15\AppData\Roaming\Armory\databases
-INFO  - 1435560228: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO  - 1435560228: (..\BlockUtils.cpp:1226) Executing: doInitialSyncOnLoad
-INFO  - 1435560228: (..\BlockUtils.cpp:1297) Total number of blk*.dat files: 290
-INFO  - 1435560228: (..\BlockUtils.cpp:1298) Total blockchain bytes: 38,855,992,595
-INFO  - 1435560228: (..\BlockUtils.cpp:1671) Reading headers from db
-WARN  - 1435560228: (..\lmdb_wrapper.cpp:1478) No headers in DB yet!
-INFO  - 1435560228: (..\BlockUtils.cpp:1697) Found 1 headers in db
-DEBUG - 1435560228: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN  - 1435560228: (..\BlockUtils.cpp:1327) --- Fetching SSH summaries for 0 registered addresses
-INFO  - 1435560228: (..\BlockUtils.cpp:1340) Left off at file 0, offset 0
-INFO  - 1435560228: (..\BlockUtils.cpp:1343) Reading headers and building chain...
-INFO  - 1435560228: (..\BlockUtils.cpp:1344) Starting at block file 0 offset 0
-INFO  - 1435560228: (..\BlockUtils.cpp:1346) Block height 0
-DEBUG - 1435561653: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO  - 1435561657: (..\BlockUtils.cpp:1381) Looking for first unrecognized block
-INFO  - 1435561919: (..\BlockUtils.cpp:1532) Loading block data... file 0 offset 0
-INFO  - 1435561952: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 0 offset 134209344
-INFO  - 1435561963: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 1 offset 134191315
-INFO  - 1435561968: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 2 offset 134179232
-INFO  - 1435561982: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 3 offset 134213358
-INFO  - 1435561988: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 4 offset 134209035
-INFO  - 1435561996: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 5 offset 134210063
-INFO  - 1435562005: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 6 offset 134209023
-INFO  - 1435562017: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 7 offset 134213992
-INFO  - 1435562059: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 8 offset 134210425
-INFO  - 1435562068: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 9 offset 134216219
-INFO  - 1435562073: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 10 offset 134144442

...continues up to:

-INFO  - 1435564513: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 278 offset 134159179
-INFO  - 1435564519: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 279 offset 134017433
-INFO  - 1435564526: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 280 offset 134208192
-INFO  - 1435564533: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 281 offset 133873878
-INFO  - 1435564539: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 282 offset 133569496
-INFO  - 1435564544: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 283 offset 134006723
-INFO  - 1435564550: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 284 offset 134060217
-INFO  - 1435564555: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 285 offset 133828750
-INFO  - 1435564560: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 286 offset 133725066
-INFO  - 1435564566: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 287 offset 134188100
-INFO  - 1435564573: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 288 offset 133593832

**************************************

Last lines of my armorylog file:

2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1189 - ************************************************************
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1190 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1191 - ************************************************************
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1192 - Loading Armory Engine:
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1193 -    Armory Version        : 0.93.2
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1194 -    Armory Build:         : 85959b20d8
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1195 -    PyBtcWallet  Version  : 1.35
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1196 - Detected Operating system: Windows
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1197 -    OS Variant            : 7-6.1.7600--Multiprocessor Free
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1198 -    User home-directory   : C:\Users\Lortel24jun15\AppData\Roaming
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1199 -    Satoshi BTC directory : C:\Users\Lortel24jun15\AppData\Roaming\Bitcoin\
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1200 -    Armory home dir       : C:\Users\Lortel24jun15\AppData\Roaming\Armory\
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1201 - Detected System Specs    :
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1202 -    Total Available RAM   : 3.98 GB
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1203 -    CPU ID string         : AMD64 Family 20 Model 2 Stepping 0, AuthenticAMD
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1204 -    Number of CPU cores   : 2 cores
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1205 -    System is 64-bit      : True
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1206 -    Preferred Encoding    : cp1252
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1207 -    Machine Arch          : amd64
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1208 -    Available HDD (ARM)   : 71 GB
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1209 -    Available HDD (BTC)   : 71 GB
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1210 -
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1211 - Network Name: Main Network
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1212 - Satoshi Port: 8333
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1213 - Do wlt check: True
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1214 - Named options/arguments to armoryengine.py:
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     nettimeout      : 2
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     rescan          : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     ignoreAllZC     : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     enableSupernode : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     disableModules  : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     port            : None
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     interport       : 8223
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     skipStatsReport : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     forceWalletCheck: False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     rebuild         : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     datadir         : DEFAULT
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     clearMempool    : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     offline         : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     coverageOutputDir: None
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     armoryDBDir     : DEFAULT
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiPort     : DEFAULT
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     useTorSettings  : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     netlog          : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     keypool         : 100
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     coverageInclude : None
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     forceOnline     : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     skipAnnounceCheck: False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     redownload      : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     multisigFile    : DEFAULT
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     disableTorrent  : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     testAnnounceCode: False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     mtdebug         : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     logDisable      : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     settingsPath    : C:\Users\Lortel24jun15\AppData\Roaming\Armory\ArmorySettings.txt
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     verbosity       : None
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     doDebug         : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     enableDetSign   : True
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     testnet         : False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     rpcport         : DEFAULT
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiHome     : DEFAULT
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiRpcport  : DEFAULT
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     logFile         : C:\Users\Lortel24jun15\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1216 -     disableConfPermis: False
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1217 - Other arguments:
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1220 - ************************************************************
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:1615 - C++ block utilities loaded successfully
2015-07-06 22:39 (INFO) -- BDM.pyc:418 - Using the asynchronous/multi-threaded BlockDataManager.
2015-07-06 22:39 (INFO) -- BDM.pyc:419 - Blockchain operations will happen in the background. 
2015-07-06 22:39 (INFO) -- BDM.pyc:420 - Devs: check TheBDM.getState() before asking for data.
2015-07-06 22:39 (INFO) -- BDM.pyc:421 - Registering addresses during rescans will queue them for
2015-07-06 22:39 (INFO) -- BDM.pyc:422 - inclusion after the current scan is completed.
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:3521 - Using settings file: C:\Users\Lortel24jun15\AppData\Roaming\Armory\ArmorySettings.txt
2015-07-06 22:39 (INFO) -- announcefetch.pyc:95 - Reading files in fetcher directory:
2015-07-06 22:39 (INFO) -- announcefetch.pyc:104 -    announce         : 59e8b1d1ce166d2721b4264d29ce82b6779431f339b70df3739c98cc62499652
2015-07-06 22:39 (INFO) -- announcefetch.pyc:104 -    bootstrap        : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-07-06 22:39 (INFO) -- announcefetch.pyc:104 -    changelog        : 791059d52f04d68a142730b421f46f52c3169440a168db50088fb2b7856e3d9b
2015-07-06 22:39 (INFO) -- announcefetch.pyc:104 -    downloads        : 21707983b98ad85f3ac5fd50ec765c08a346d00eaddbeb117516d0b7c25c5dbf
2015-07-06 22:39 (INFO) -- announcefetch.pyc:104 -    notify           : 78bbf86a93b31c391ad34ee1b26097abd9064c0c037a6d4a16d6d1cdb0c7635d
2015-07-06 22:39 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.93.2&id=087bf462
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2735 - loadWalletsAndSettings
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2789 - Loading wallets...
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2848 - Number of wallets read in: 2
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2853 -    Wallet (************ (Watch)                     "      EDITED out wallet info
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2853 -    Wallet (************ (Watch)                      "     EDITED out wallet info
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2297 - Setting up networking...
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2326 - Internet status: 0
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2441 - startBitcoindIfNecessary
2015-07-06 22:39 (INFO) -- ArmoryQt.py:2490 - setSatoshiPaths
2015-07-06 22:39 (INFO) -- SDM.pyc:415 - Found Bitcoin-Qt link on desktop: C:\Users\Lortel24jun15\AppData\Roaming
2015-07-06 22:39 (INFO) -- SDM.pyc:321 - Found bitcoind in the following places:
2015-07-06 22:39 (INFO) -- SDM.pyc:323 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2015-07-06 22:39 (INFO) -- SDM.pyc:325 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2015-07-06 22:39 (INFO) -- SDM.pyc:496 - Reading bitcoin.conf file
2015-07-06 22:39 (INFO) -- SDM.pyc:515 - Setting permissions on bitcoin.conf
2015-07-06 22:39 (INFO) -- SDM.pyc:524 - Setting permissions on bitcoin.conf
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: [u'icacls', u'C:\\Users\\Lortel24jun15\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'Lortel24jun15:F']
2015-07-06 22:39 (INFO) -- SDM.pyc:530 - icacls returned:
2015-07-06 22:39 (INFO) -- SDM.pyc:597 - Called startBitcoind
2015-07-06 22:39 (INFO) -- SDM.pyc:282 - Total size of files in C:\Users\Lortel24jun15\AppData\Roaming\Bitcoin\blocks is 36.7 GB
2015-07-06 22:39 (ERROR) -- announcefetch.pyc:312 - Could not verify data in signed message block
Traceback (most recent call last):
  File "announcefetch.pyc", line 304, in __runFetchSequence
  File "jasvet.pyc", line 589, in readSigBlock
IndexError: list index out of range
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\Lortel24jun15\\AppData\\Roaming\\Bitcoin\\']
2015-07-06 22:39 (INFO) -- SDM.pyc:669 - PID of bitcoind: 6788
2015-07-06 22:39 (INFO) -- SDM.pyc:670 - PID of armory:   6688
2015-07-06 22:39 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: ['.\\guardian.exe', '6688', '6788']
2015-07-06 22:39 (INFO) -- SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2015-07-06 22:39 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-07-06 22:39 (INFO) -- ArmoryQt.py:1582 - Armory already registered for current user.  Done!
2015-07-06 22:39 (INFO) -- ArmoryQt.py:664 - Usermode: Advanced
2015-07-06 22:39 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-07-06 22:39 (INFO) -- ArmoryQt.py:1810 -    From: Advanced
2015-07-06 22:39 (INFO) -- ArmoryQt.py:1818 -      To: Advanced
2015-07-06 22:39 (INFO) -- ArmoryQt.py:5898 - Dashboard switched to auto-InitSync
2015-07-06 23:09 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-07-06 23:26 (INFO) -- ArmoryQt.py:6774 - BDM is safe for clean shutdown
2015-07-06 23:26 (INFO) -- ArmoryQt.py:6816 - Attempting to close the main window!

Then it cant find your blockchain and/or Core binary folders, you have to give it the proper paths.

I was adding this line to my post when you replied:

I just tried the rescan and rebuild, restarted Armory and got the same results - it just stays offline (and never ran the rescan/rebuild).

From the looks of it you will have to rebuild and rescan.

I didn't have to reload the blockchain; I salvaged it from the PC that died.
I just moved the drive containing the blockchain to my new computer, gave it the same drive letter as before.
Then I installed Armory and it found my wallet files (somehow) but never tried to go online.
Still stuck.

I just tried the rescan and rebuild, restarted Armory and got the same results - it stays offline.