Thank - I will try it!

Hi goatpig,

I think I let it run about 18 hours.

It appeared to have concluded a process, and I created another log file - ArmoryDB_log2.txt in my updated pastebin.

https://github.com/truebar/pastebin

The last line in the terminal was:

-INFO  - 01:10:12: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking

Is this Ok, along with the early log line:

-INFO  - 00:06:28: (BDM_Server.h:263) Listening on port 9001

Also, I noticed that running ArmoryDB on the terminal did not hang in the usual 2-4 hours as it does with Armory GUI running and bitcoind
running in the background. It just kept running on without stopping.

Lastly, when I killed the terminal running ArmoryDB, it looked done, but there was still some kind of process running in it, though nothing new
came on screen.

Also updated in my pastebin is a new file armory_log3.txt.

On December 17th, I ran first BitcoinCore Qt, and let up update the blockchain. Then I launched Armory. Armory still froze, but it got farther
than usual. The Scanning Transactions progress bar went all the way to 100%, and the timer said only 1 second left. But at that point, Armory froze.

Any ideas from this as to get Armory back up and running fully together with bitcoind? It has been a pretty frustrating process so far.

Thanks much,
cobbler7

Hi goatpig,

Please see terminal output after running ArmoryDB at terminal.  File is ArmoryBD_log.txt

https://github.com/truebar/pastebin

The only thing I see in this I see of possible interest is:

-INFO  - 00:06:28: (BDM_Server.h:263) Listening on port 9001

Any ideas? Thanks much.
cobbler7

I uploaded txt files of the odt ones to the pastebin, did you get/see them?

Thanks, cobbler7

Thanks goatpig and HCP -- this updated directory below should have two netstat files, debug.log, and bitcoind last
run terminal log. Any ideas much appreciated.
Thanks,
cobbler7

https://github.com/truebar/pastebin

Thank s much goatpig and HCP for your continued help.

I have updated my pastebin https://github.com/truebar/pastebin
with the following 4 files:

-netstat run 1: scanning port 9001 with BOTH Armory and bitcoind running

-netstat run 2: scanning port 9001 with NEITHER Armory NOR bitcoind running

- armory debug.log

- screenshot of latest bitcoind terminal run

Re netstat, I still can't tell from these two files if anything is there that shouldn't be, or otherwise
is interfering with either Armory or Bitcoin.

Re armory debug.log, it is much like terminal output of bitcoind. Nothing jumps out to me as a
problem.

Re bitcoind run screenshot, this appears to me to indicate that the local bitcoin blockchain copy
is complete, or near complete, and not 100k blocks short of being complete. Any further ideas as
to what is going wrong in making Armory hang on "Organizing Blockchain" or "Scanning Tx"?

One further background fact, in case it matters. In doing re-installs of Armory and BitcoinCore,
I have been making use of a backup copy of the bitcoin blockchain that I keep on a external USB
hard drive. (This is specifically the contents of the .bitcoin directory.) For example, I get a new
computer, install BitcoinCore on it, but don't yet run it. Instead, I copy the contents of my
back up .bitcoin directory from the USB external drive to the .bitcoin directory on my new PC.
Only then do i run BitcoinCore Qt. Does/might this matter?

Thanks much,
cobblert7

Thanks goatpig. I will try it.

Some further comments/questions below.

goatpig
Insert Quote
1. Run bitcoind manually, you're behind some 100k blocks as far as Armory is concerned

cobbler7: I have run bitcoind and bitcoin-qt manually maybe 20+ times, then launched Armory.
No luck, it always hangs. I am sure at least a half dozen times, blockchain was current state before
I launched Armory. I don't know why Armory should be 100k blocks behind.

2. Make sure there are no zombie ArmoryDB instances
oat
cobbler7: pretty sure no zombies. I always hard boot before trying to re-run and reconstitute
bitcoincore/Armory.

3. Make sure nothing is listening on 9001

cobbler7: I tried netstat :9001, both with bitcoin/Armory, and then on clean boot without them. Both
netstat logs are now in my updated pastebin. I can't make heads or tails of these logs. Is something
there that shouldn't be there? And if so, what should I do about it?

Once bitcoind is caught up, start ArmoryDB from the terminal, let it catch up, post the log file back here if it doesn't get beyond block 700k. If ArmoryDB gets as far as "enabling zero conf parser", you can start ArmoryQt.

cobbler7: so I don't introduce anything new, can you tell me what the "clean" default terminal commands are to launch ArmoryDB, and then after that, ArmoryQt?

Thanks much.
cobbler7

cobbler7:

My Armory logfiles can be viewed at:

https://github.com/truebar/pastebin

Any further advice most appreciated.
Thanks,
cobbler7

Hi,
I have a quite similar issue. I am by this point a fairly experienced BitcoinCore and Armory user (since 2014 or 2015). So I have tried my usual tricks
and tilts on the Armory pinball machine, but nothing seems to work now.

I have been running Ubuntu 20.4, Armory 0.96.5, and BitcoinCore 0.21.1, on a one year old System76 laptop with 64GB ram and an
Intel® Core™ i7-10870H CPU @ 2.20GHz × 16. Plus Verizon Fios for Internet. I don't think my system is underpowered to run a BitcoinCore/
Armory combination.

My specific problem is, BitcoinCore and Armory repeatedly hang/freezes after running for 2-6 hours. It hangs on either "Organizing Blockchain".
Or if that process completes, it hangs on "Scanning Tx".

I have run it (the boot up) maybe 20x plus over the past 3 weeks, to no avail.  One time, when I wasn't there/didn't see it, it showed me my Armory wallet balances,
but when I got there, the whole computer was frozen, so I couldn't use Armory or anything, and had to reboot. A couple of other times, it completed the "Scanning
Tx" part (at 100%), but then froze my whole computer, and did NOT show me my wallet balances. But that is as far as I have got, after 3 weeks.

I have tried the usual tilts, which have worked before. Like:
- rebuild and rescan databases
- letting, and not letting, Armory run bitcoind in the background
- running bitcoind and bitcoin-qt first, and then manually launching Armory

Also, when I run bitcoind or bitoin-qt manually, BitcoinCore 0.21.1 runs normally and updates the bitcoin blockchain apparently up to
current state.

So the problem appears to be the handshaking of Armory 0.96.5. with BitcoinCore.

I realized tonight that BitcoinCore has been upgraded to 0.22.0. I am currently running an update of blockchain with that. Maybe that will solve the problem,
But I dunno if that will work.

Any thoughts/ideas on what I can do to fix this? Any feedback most appreciated.
Thanks in advance, cobbler7.



Follow-up (by cobbler7): my Armory log files can be viewed at: https://github.com/truebar/pastebin

Thank you

Thank you NC501c,
I will check that out.
Cobbler7

Hi,

I am experiencing a similar problem: Armory hangs apparently endlessly in the "organizing blockchain"
stage, and never completes despite being run all day.

I am running BitcoinCore 0.21.1 and Armory 0.96.5.

This combination worked fine for me previously, but now something somewhere must have changed.
(I am thinking maybe from sudo apt-get update and upgrade etc.)

The only new clue (perhaps) as to what has changed is I get a new error message when I try
to quit the hung instance of Armory. This new error message says:

"ArmoryQt.py is not responding"
 
Any help or pointers would be most appreciated!

Thanks much,
Cobbler7

Carlton,
Thanks much for the quick response. That worked like a charm, and my new offline system
for Armory is now fully installed and operational. Thanks again!
Best regards,
Cobbler7

Hi,

I am having a persistent problem getting my offline copy of Armory to install on a new
Ubuntu 16.04.10 computer. My online copy of Armory installed fine, but I had to use
the "apt-get -f install" to get all the Python dependencies for it.

I have gone through hours of "dependency hell" ferrying python packages via USB
from my Ubuntu 16.04.10 online computer, and am now done to a single unmet dependency
 that is blocking the Armory install on the offline machine. This is the libstdc++6
package.

When I use apt-get to download "libstdc++6", it always pulls version 5.4.0. This version
is installed on both my online system, which works fine, and my offline system, which
won't successfully install Armory and gives the following single error message:

"armory depends on libstdc++ (>= 7); however: Version of libstdc++6:AMD64 on system
is 5.4.0-6ubuntu1~16.04.10."

Can anyone tell me why Armory installs with libstdc,++6 5.4.0 on my online system but
not on my offline system, and how this can be fixed?

Also, I see there are versions of libstdc 7.2 and 8.3 for Ubuntu 17.10 and 18.04, and I could
try reset from scratch by upgrading to one of those. But them I would lose alot of other
setup work on my two existing 16.04 systems. Any suggestions as to best path to take
would be much appreciated! Thanks,
Cobbler7

Hi I had this same problem on two different laptops. In both cases it ultimately appeared armory was scanning just the local
copy of the blockchain in the .bitcoin folder, and then showing my (then correct) wallet balamces. I realized something wasn't right
when I left the computers off for 5 or 6 days and when I rebooted, armory was scanning and updating the blockchain
too fast to be true. Bitcoin Core, however, would continue to update the local copy of the blockchain correctly if run as
a stand-alone.

Choosing "Resync and Rescan" option from the file menu fixed the problem on one machine for me.

In the case of the other machine, I had a custom install directory for Bitcoin Core that was nested a ways down. Turned out
I has a subtle typo in the long directory name, and armory simply couldn't find the executable for Bitcoin Core. Instead it
scanned the local copy of the blockchain, in the .bitcoin folder, as last updated by Core. Then it displayed my wallet balances
based on that info, and then went into "Offline" mode as indicated by the lower right corner message.

In a future version, it would be nice if Armory expressly told you in a splash box error message if it could not find the Core executable
"because no such directory exists". That would put you onto the problem quick, instead of having you troubleshoot a bunch of
different things.
 

Thank you for the quick response. Unfortunately, I am a newbie and
have no idea how to broadcast a raw armory transaction over bitcoin
core.

That is, I should be able to find the raw Armory transaction file, but
could you give me a sentence or two about how to make core broadcast
that file directly?

Thanks much for your help!

Hi, I am repeatedly getting the same error message, but am
running Ubuntu 16.04 LTS and Armory 0.95.1.

("Broadcast failed unexpectedly. Report this error to the developer
team if this issue occurs repeatedly").

I also repeatedly get the same error message when I run Armory 0.95.1 on a
Ubuntu 14 laptop.

I can connect to the bitcoin network okay through Armory on both machines,
and it updates both the balances in my online and offline wallets.

But when I try to transfer the small amount of bitcoin from my encrypted
online armory wallet to my cold storage armory wallet, I get the error
message repeatedly. It doesn't seem like armory/bitcoin tries to connect
for awhile and gives up. It just hits me bam! with an error message as soon as
I hit the send button.

Anyone have any idea about what is going one or how to possibly fix this?!

Thanks for your consideration.