TL;DR: ArmoryDB on commandline gave Illegal Instruction.  Building from source solved issue.  Thanks!

########## Not gonna be that guy that says "fixed it!" with no info.

Uninstalled Armory to build from source, read goatpig's post, reinstalled 96.5 from .deb.  Result:

$ ArmoryDB
/home/happy
/home/happy
/home/happy/.armory is not a valid path
logging in /home/happy/.armory/dbLog.txt
-INFO  - 18:22:04: (main.cpp:32) Running on 4 threads
-INFO  - 18:22:04: (main.cpp:33) Ram usage level: 50
-INFO  - 18:22:04: (BDM_Server.h:263) Listening on port 9001

# Hangs so I close

^C

# Ran Armory from Mint Menu, got "Failed to spawn DB", closed Armory

$ ArmoryDB
/home/happy
/home/happy
logging in /home/happy/.armory/dbLog.txt
-INFO  - 18:22:37: (main.cpp:32) Running on 4 threads
-INFO  - 18:22:37: (main.cpp:33) Ram usage level: 50
-INFO  - 18:22:37: (BlockUtils.cpp:915) blkfile dir:  /media/vault/blockchains/bitcoin/blocks
-INFO  - 18:22:37: (BlockUtils.cpp:916) lmdb dir: /home/happy/.armory/databases
-INFO  - 18:22:37: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 18:22:37: (BDM_Server.h:263) Listening on port 9001
Illegal instruction
$

$ dpkg -r armory

Built v0.96 from source.  Build failed:

lrelease: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/lrelease': No such file or directory

Fix this by: sudo apt-get install qttools5-dev-tools

On a hunch that the illegal instruction was from missing qt library I ran make clean, then reinstalled Armory from .deb.  Configured it, same results, could not spawn DB.  Illegal instruction.  Uninstalled from deb.

Realized that there is a v0.96.5 tag.  Switched to it, verified signature, make clean (again), autogen, configure, make.  Build is successful.

$ python ArmoryQt.py
Traceback (most recent call last):
  File "update_version.py", line 14, in <module>
    f = open(hash_loc, "r")
IOError: [Errno 2] No such file or directory: '.git/6640d6257ab0c37013e5cd4b99681a5cfc3'
/home/happy
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.96.5
   Armory Build:         None
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   OS Variant            : ('LinuxMint', '18.3', 'sylvia')
   User home-directory   : /home/happy
   Satoshi BTC directory : /media/vault/blockchains/bitcoin
   Armory home dir       : /home/happy/.armory/
   ArmoryDB directory     : /home/happy/.armory/databases
   Armory settings file  : /home/happy/.armory/ArmorySettings.txt
   Armory log file       : /home/happy/.armory/armorylog.txt
   Do wallet checking    : True
(ERROR) ArmoryUtils.py:3735 - Unsupported language  specified. Defaulting to English (en)
/home/happy/BitcoinArmory/armoryengine/Transaction.py:3126: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
"sni-qt/8602" WARN  20:54:26.857 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
(WARNING) SDM.py:402 - Spawning DB with command: /home/happy/BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/media/vault/blockchains/bitcoin/blocks" --satoshi-port=8333 --datadir="/home/happy/.armory/" --dbdir="/home/happy/.armory/databases"


# Armory launches and builds databases.

Thanks!

I don't remember which version it was, but ya it was always a bit finicky even back when I was using it more often.  I simplified things a bit, when explaining what I tried to do with the old version.  Tried that, factory resets, deleting the databases folder... various attempts caused it to hang in various points so I decided to start fresh.


Every time it says "fails to spawn the DB!" and goes into offline mode.
No luck.  Fails to spawn DB, goes to offline mode, creating a wallet crashes Armory.  Specifically starting in Offline mode also crashes on create wallet (whether from the intro screen or the drop down menu).
Interesting idea.  I'll give it a shot.

BTW, when launching in online mode (but failover to offline) the Dashboard is empty except for the two loading bars which have no activity.  When launching directly to offline mode the Dashboard is as expected.
I also realized that ps -e | grep Arm reports the ArmoryDB process as defunct, but if I open in offline mode it reports no processes.  So what is the name of the main Armory process?

I'll try to be detailed...
I was using an older version of Armory on Linux Mint 18.1.  I had not booted the machine in months.  After syncing the blockchain and starting Armory everything looked fine with the watching only wallet I had loaded.  After importing other wallets from paper backups the transaction history for the watching only wallet was reduced to two entries.  The newly imported wallets had 0 balance.  I checked their addresses and "Used" listed no addresses.  This is wrong.  Even if somehow coins were stolen there should be Used addresses, or transaction history, or something.  Rebuild and Rescan Databases hangs for hours.

I remove Armory.  I delete my copy of the blockchain and update bitcoin-core.  I check the version is correct:  https://pastebin.com/9EqTBfsz

I run bitcoin-core via:

nohup bitcoind -datadir= ${btc_local_chain} -daemon >> ${btc_local_chain}/bitcoind.log

where btc_local_chain is defined as:  btc_local_chain="/media/vault/blockchains/bitcoin"

I allow the blockchain to fully sync.  I check the blockheight is correct via:

btc-cli getblockcount
wget -q -O - http://blockchain.info/q/getblockcount

I update gcc and g++ and their symlinks, and confirm version:
https://pastebin.com/L8BDy8ku
https://pastebin.com/Z0DZV7hx

I try installing and uninstalling armory 0.96.5 and 0.96.4 (the GCC 7.2 and 4.9 versions) various times, always getting "Failed to spawn DB!"
I start documenting for this post:

I update mint to 18.3 through Software Manager GUI.  I reboot.

I remove Armory and install armory_0.96.5_amd64_gcc7.2.deb:
https://pastebin.com/qhS8iDRf

I reboot.

I start Armory in offline mode and uncheck "Let Armory run Bitcoin Core..."
I set Bitcoin Home Dir to: /media/vault/blockchains/bitcoin

I check ArmorySettings.txt to confirm the blockchain location is properly set:
https://pastebin.com/BJ0Yt5vz

I create armoryqt.conf and armorydb.conf in ~/.armory/, each contain a single line:
satoshi-datadir="/media/vault/blockchains/bitcoin"

I run: sudo apt-get update
I run: sudo apt-get dist-upgrade
https://pastebin.com/AGmYtbQ4

I reboot.

I run bitcoind as before, and again check the blockheight is correct.  I double check with https://www.blockchain.com/btc/block-height/

I wait for my HDD to stop spinning.

I empty the armorylog.txt file for clarity.

I start Armory from Linux Mint Menu.  Again:  Armory Failed to spawn the DB!
I skip creating a wallet and close Armory.  I check the logs:
armorylog.txt: https://pastebin.com/x4dh1Eqf
dbLog.txt: https://pastebin.com/ajdMszs3

The database invocation looks correct.  It simply fails.
I launch Armory again, again the DB error.  I "create my first wallet" with all defaults and password = password, just to test.
Armory immediately closes without creating the wallet.  I check ps -e | grep armory and it is not running.  There are no .wallet files in the directory.
I launch Armory again.  DB Error.  It wants me to create a wallet.  I click skip.  I do Help->Rebuild and Rescan Databases.
I quit Armory and launch again.  DB Error.  It wants me to create a wallet.
Logfile from the last two launches:  https://pastebin.com/eayz9YNG   [I copied this before closing Armory].

At this point I feel like my only option is to reformat all drives, install the latest mint, download blockchain again, etc. etc. etc.  I'd rather not.  Any other options?

Please help, thank you.

Selling at a loss so I can order 841's:  $1650 a piece, discounts for five or more.  Can match the proper number of AUC3 and Avalon Controller to your order.  Buy enough and I'll go as low as $1300.  Shipping immediately from Saint Louis, MO.  Buyer pays shipping.

Accept PayPal, Wire Transfer, BTC, ETH, or ZEC.

Legally registered and licensed business.
PM me!

James Lea
Infomorphics LLC

I have four left.
Shipping from Saint Louis, MO.

@ myccgear I can't message you since your settings don't accept messages from "newbies"

Unused and unopened Avalon 741's from the November 2017 batch.  Paypal or BTC or ZCash (escrow).  The person who bought these didn't have space for them and asked me to get rid of them  

Five available.

You want the path: (fresh air) -> (machines) -> (outside) to be as wide and have as few turns as possible, while still being fairly direct.
Is dumping the heat into a "receptacle" and then bringing it out going to be a wide open path, or will it just let the heat pool up?
Why not let the entire room be a "duct"?
Is the flex duct running between studs?  If so can you just pan the studs so the channel forms a natural "duct"?
What's above this room?  Attic? Perhaps you could open the entire ceiling, extend wall up and over, and put gable fans on side of house.

Thanks for the input! 

https://canaan.io/product/bulk-pack-resell/
MSRP is 800 for A741, 20 for AUC3.  So they are charging an extra 78.

I have been building PC's for 15 years.

With my mining rigs I have been using ASUS and ASRock mobo's.  Always liked the brands (especially ASRock).  Recently Newegg had a bunch of open box Biostar TB250-BTC for cheap so I picked up 7 of them.

So far two have caught on fire shortly after booting with 6 1080 ti's on powered risers.  These 1080 ti's have previously run for a week straight on an ASRock H81.  The fire started next to/underneath the chipset heatsink near the SATA power in.

In both situations I ran the motherboard for some time without any graphics cards plugged in.  Different power supplies.

I am using 160W Pico-PSU (ITX) plugged into the 24Pin.  I have made adapters by hand crimping mini-fit jr's to take the Pico's 5pin outlet to a chain of 3 4pin MOLEX.   The first MOLEX feeds a MOLEX->SATA power adapter (bought) that plugs into the motherboards SATA power in.  The second MOLEX plugs into the inlet near the CPU, the third to the inlet on the side of the board.  The PICO is fed by a 5mm pigtail from Eyeboot that I spliced into a 6pin PCIE -> 8pinEPS at the EPS terminals.  I've made and used these adapters before without issue.  I use 18AWG stranded hookup wire.

I've read the extra power inlet's aren't technically necessary when using powered risers but where I come from we don't risk underpowering hardware.

In the first case the EPS was fed from a 1200watt HP server supply with an X-Adapter.  The risers were also fed directly from this (they have 6pin inlets).  The top two inlets (6 pin and 8pin) were fed from a separate 1200W HP psu.  I figured I'd have a max of 100W per inlet when hashing (PL @ 205W) and wanted to try split supplies.

I figured the MOLEX->SATA adapter was to blame (a ground pin was loose) so I tossed it.  I was concerned that the GFX cards might have tried to draw too much from one PSU on boot so for the next attempt I used a Delta 2400W PSU with two GekkoScience breakouts, and plugged all 19 connectors into it.  I think I used a different PICO PSU but I'm honestly not sure.  I used the same hand made PCI->EPS and 5pin->MOLEX->MOLEX->MOLEX adapters.  I suppose the adapters could have a short, but I don't see one.

Fire in the same spot on the second mobo.

I could test the adapters with an H81/Pico/adapter combo I know is good.  I suppose I should just toss the PICO and adapters, but want to see if there's something obvious and stupid I'm doing.  And if anyone knows why this would happen at the SATA in of all places.  Are these boards especially prone to problems?  I'm thinking about returning all of them, never liked Biostar much anyway.

Maybe I will stop hooking up on-board MOLEX/SATA in's.

In the USA the IRS defines income as occurring as soon as you have a *right* to collect the income, not when it is received.  Deteemining when that occurs with different payout methods and pools (e.g. nanopool doesn't really show a list of rewards, only a growing number and a list of payouts) is proving problematic.

Anyone have real knowledge, not opinion?

Staying loyal to pool.  Thank you for your hard work kano.
Unfortunately restarted 33 hours ago, but best share since then is:  9,186,558,754
Please say if there's any other information or anything that could help you.

Question:  is maintenance mode completely offline, or testnet, or something else?  Will you need some miners to stay connected?

Notice in phillipma1957's video that the two outer pieces of tape were already sliced.  Also the small piece of tape over the tab on the box flap goes over one of these outer, sliced, pieces of tape.  That's the same as with the units I received.  So clearly someone opened the box and resealed it, which I guess is what they told Steamtyme.

HOWEVER,did anyone else *smell* the machines they got from miner warez?  Mine stink.  The same musty smell of a computer that has been running without cleaning for too long.  Inspecting a package doesn't explain that, unless it is the smell of Beijing smog?  The inside of the cable bags doesn't smell.

The camera work in my video is terrible, I'll still upload it later, right now trying to figure out what to say to canaan/miner warez.

95% sure the units I received from "Miner Warez" are used.  I took an unboxing video which is long, but I will edit/convert and post it soon.

nsx077's photos are concerning but show nothing.  I am going to make an unboxing video and (without revealing personal info attempt to) show invoices, support tickets, tracking numbers, and labels when I'm back home.

In some industries weeks or months of lead time on factory direct purchases is standard.  canaan clearly has/had problems with their logistics, though I don't recall any promises about fulfillment timeframes prior to ordering.

It was in the 9070's, and is still listed as on hold.  Like others I placed an order with distributor but kept my canaan order open.

Ordered five miners with Canaan on Aug 31st.  Exchanged emails with steve and lily about timing.  They were very helpful.  On Aug 15th lily suggested the ditributor would be faster.  I placed an order and emailed miner warez that day.  On the 18th a label was generated.  It shipped on the 19th as five boxes.  FedEx says arrival will be on the 22nd.  My price was same as canaans, shipping reasonable.  I'm in central US and my order number is between 1000 - 1025.

I'm happy with how it has worked out so far.