"Parsing Tx Hashes" all night, hung or wait?

PhoenixZephyrus

full member

Activity: 155

Merit: 102

Quote from: jojo69 on January 07, 2021, 06:15:32 PM

well god dammit, lol

This whole exercise was precipitated by trying to NOT re-download the entire chain, but alas, it appears you are correct and while I do have ample space, it appears that the folder is only 6 gigs in size...

ok then...see you all in a few days after I get that sorted

I did the same exact mistake...pruned it and downloaded ~85% of the blockchain and then read on here that pruned mode wont work, so had to redownload the whole thing again for 12 hours. Even after that it was stuck on a few steps, like "Scanning Transaction history" and "Parsing Tx Hashes". So, if you run into further troubles, here's a list of things you should ensure (just so that you dont have to troubleshoot for hours like I did lol):

1. Check off the auto bitcoind in armory and run Bitcoin Core yourself (and just make sure you're on latest version, I think the latest version is 0.96.5 on Github)
2. Make sure you dont run Chrome in the background with a lot of stuff open, that tends to eat up a huge chunk of RAM and Armory used up ~14GB/16GB for me.
3. Building database seems to take quite a lot of time, even on my Ryzen 7 4800H 8c/16t CPU it took ~8 mins with an all core turbo of 4.17 Ghz for the whole almost (though I was running some other tasks in the background)
4. If nothing seems to work even after making sure of these, rebuild the database. That seemed to fix everything for me.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

well god dammit, lol

This whole exercise was precipitated by trying to NOT re-download the entire chain, but alas, it appears you are correct and while I do have ample space, it appears that the folder is only 6 gigs in size...

ok then...see you all in a few days after I get that sorted

HCP

legendary

Activity: 2086

Merit: 4314

This is your problem right here:

Quote from: https://pastebin.com/0ZCpn4ua

2021-01-07 11:02:07 (WARNING) -- SDM.py:518 - bitcoind exited, bitcoind STDERR:
2021-01-07 11:02:07 (WARNING) -- SDM.py:520 - : You need to rebuild the database using -reindex to go back to unpruned mode. This will redownload the entire blockchain.
2021-01-07 11:02:07 (WARNING) -- SDM.py:520 - Please restart with -reindex or -reindex-chainstate to recover.
2021-01-07 11:02:07 (WARNING) -- SDM.py:520 -

Quote

-ERROR - 10:59:34: (lmdb_wrapper.cpp:1503) Headers DB has no block at height: 0
-ERROR - 10:59:34: (lmdb_wrapper.cpp:1483) No headers at height 0
-ERROR - 10:59:34: (BlockchainScanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 10:59:34: (BlockchainScanner.cpp:447) Has the following block files:
-ERROR - 10:59:34: (BlockchainScanner.cpp:451) Was looking for id #4294967295

It seems that you're running Bitcoin Core in "pruned" mode... Armory needs Bitcoin Core to have a full, unpruned copy of the blockchain... do you have 350+Gigs of free diskspace to be able to sync the full blockchain? Huh

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

netstat -ltnp returns

Code:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      2443/cupsd          
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      2915/smbd           
tcp        0      0 127.0.0.1:8223          0.0.0.0:*               LISTEN      6385/python2        
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      2915/smbd           
tcp        0      0 0.0.0.0:49709           0.0.0.0:*               LISTEN      1876/rpc.statd      
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      1847/rpcbind        
tcp6       0      0 ::1:631                 :::*                    LISTEN      2443/cupsd          
tcp6       0      0 :::445                  :::*                    LISTEN      2915/smbd           
tcp6       0      0 :::36579                :::*                    LISTEN      1876/rpc.statd      
tcp6       0      0 :::6566                 :::*                    LISTEN      2744/saned          
tcp6       0      0 :::139                  :::*                    LISTEN      2915/smbd           
tcp6       0      0 :::111                  :::*                    LISTEN      1847/rpcbind

this while armorycplog.txt is spamming

Code:

-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte

fresh armorylog.txt https://pastebin.com/0ZCpn4ua

fresh dblog.txt

Quote

Log file opened at 10:59:34: /home/stg/.armory/dbLog.txt
-INFO - 10:59:34: (main.cpp:32) Running on 8 threads
-INFO - 10:59:34: (main.cpp:33) Ram usage level: 50
-INFO - 10:59:34: (BlockUtils.cpp:915) blkfile dir: /media/BITCORE/Blockchain/blocks
-INFO - 10:59:34: (BlockUtils.cpp:916) lmdb dir: /home/stg/.armory/databases
-INFO - 10:59:34: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 10:59:34: (BDM_Server.h:263) Listening on port 59328
-INFO - 10:59:34: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO - 10:59:34: (DatabaseBuilder.cpp:199) Reading headers from db
-WARN - 10:59:34: (lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO - 10:59:34: (DatabaseBuilder.cpp:238) Found 1 headers in db
-INFO - 10:59:34: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO - 10:59:34: (Blockchain.cpp:248) Organizing chain
-INFO - 10:59:34: (Blockchain.cpp:370) Organized chain in 0s
-INFO - 10:59:34: (DatabaseBuilder.cpp:76) updated HEADERS db in 0s
-INFO - 10:59:34: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 10:59:34: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO - 10:59:34: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO - 10:59:34: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking
-INFO - 10:59:34: (BDM_Server.cpp:1121) registered bdv: efd166360b74055c3d4d
-INFO - 10:59:34: (BDM_supportClasses.cpp:401) Starting address registration process
-ERROR - 10:59:34: (lmdb_wrapper.cpp:1503) Headers DB has no block at height: 0
-ERROR - 10:59:34: (lmdb_wrapper.cpp:1483) No headers at height 0
-ERROR - 10:59:34: (BlockchainScanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 10:59:34: (BlockchainScanner.cpp:447) Has the following block files:
-ERROR - 10:59:34: (BlockchainScanner.cpp:451) Was looking for id #4294967295

Log file opened at 11:17:09: /home/stg/.armory/dbLog.txt
-INFO - 11:17:09: (main.cpp:32) Running on 8 threads
-INFO - 11:17:09: (main.cpp:33) Ram usage level: 50
-INFO - 11:17:09: (BlockUtils.cpp:915) blkfile dir: /media/BITCORE/Blockchain/blocks
-INFO - 11:17:09: (BlockUtils.cpp:916) lmdb dir: /home/stg/.armory/databases
-INFO - 11:17:09: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 11:17:09: (BDM_Server.h:263) Listening on port 50407
-INFO - 11:17:09: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO - 11:17:09: (DatabaseBuilder.cpp:199) Reading headers from db
-WARN - 11:17:09: (lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO - 11:17:09: (DatabaseBuilder.cpp:238) Found 1 headers in db
-INFO - 11:17:09: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO - 11:17:09: (Blockchain.cpp:248) Organizing chain
-INFO - 11:17:09: (Blockchain.cpp:370) Organized chain in 0s
-INFO - 11:17:09: (DatabaseBuilder.cpp:76) updated HEADERS db in 0s
-INFO - 11:17:09: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 11:17:09: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO - 11:17:09: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO - 11:17:09: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking
-INFO - 11:17:09: (BDM_Server.cpp:1121) registered bdv: bbff82b8b99c0c3a6db6
-INFO - 11:17:09: (BDM_supportClasses.cpp:401) Starting address registration process
-ERROR - 11:17:09: (lmdb_wrapper.cpp:1503) Headers DB has no block at height: 0
-ERROR - 11:17:09: (lmdb_wrapper.cpp:1483) No headers at height 0
-ERROR - 11:17:09: (BlockchainScanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 11:17:09: (BlockchainScanner.cpp:447) Has the following block files:
-ERROR - 11:17:09: (BlockchainScanner.cpp:451) Was looking for id #4294967295

I have gone so far as to uninstall armory and reinstall it and this behavior persists.

HCP

legendary

Activity: 2086

Merit: 4314

You could try using netstat...

Code:

netstat -ltnp

Have a look through the list for the port number you're interested in... You may need to run it using sudo to see all the system processes etc.

Or maybe one of the methods here: https://www.tecmint.com/find-out-which-process-listening-on-a-particular-port/

The thing is that if you let Armory spawn ArmoryDB (ie. you just start with armory command), then it should spawn ArmoryDB with a "random" port number... and it won't use 9001.

Code:

hcp@hcp-VirtualBox:~$ sudo netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:52811         0.0.0.0:*               LISTEN      4965/ArmoryDB       
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      536/systemd-resolve 
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      4720/cupsd          
tcp        0      0 127.0.0.1:8223          0.0.0.0:*               LISTEN      4852/python2        
tcp6       0      0 ::1:631                 :::*                    LISTEN      4720/cupsd          
hcp@hcp-VirtualBox:~$

on next run:

Code:

hcp@hcp-VirtualBox:~$ sudo netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:62284         0.0.0.0:*               LISTEN      5234/ArmoryDB       
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      536/systemd-resolve 
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      4720/cupsd          
tcp        0      0 127.0.0.1:8223          0.0.0.0:*               LISTEN      5121/python2        
tcp6       0      0 ::1:631                 :::*                    LISTEN      4720/cupsd          
hcp@hcp-VirtualBox:~$

You can see the port changed from 52811 to 62284... however, if I spawn ArmoryDB manually using ArmoryDB from the terminal, it always tries for 9001 unless I use the --fcgi-port command:

Code:

hcp@hcp-VirtualBox:~$ sudo netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      536/systemd-resolve 
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      4720/cupsd          
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      5314/ArmoryDB       
tcp6       0      0 ::1:631                 :::*                    LISTEN      4720/cupsd          
hcp@hcp-VirtualBox:~$

and with ArmoryDB --fcgi-port=52828:

Code:

hcp@hcp-VirtualBox:~$ sudo netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      536/systemd-resolve 
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      4720/cupsd          
tcp        0      0 127.0.0.1:52828         0.0.0.0:*               LISTEN      5326/ArmoryDB       
tcp6       0      0 ::1:631                 :::*                    LISTEN      4720/cupsd          
hcp@hcp-VirtualBox:~$

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

I know that this is veering off topic of strictly Armory support into general linux tutoring, but is there a way to discover what this other process is that is squatting my port?

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: jojo69 on January 05, 2021, 12:35:27 PM

would I also have to change the port that QT is sending on, or am I misunderstanding the whole thing?

I don't think so, no.
The problem seems to be between the 2 armory processes: armoryqt and armorydb.

Armoryqt tries to connect to armorydb on a specific port but receives a weird reply -> Some other process is listening on that port.
As far as i am aware, there is no problem between the communication of armory and bitcoin core.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

would I also have to change the port that QT is sending on, or am I misunderstanding the whole thing?

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: jojo69 on January 05, 2021, 11:53:40 AM

ok, is there a guide to modifying the port settings?

You can start armorydb with a custom port by using the --fcgi-port=X argument:

Code:

armorydb.exe --fcgi-port=X

(Replace X with your port, e.g. 55555).

Or you can add this to your config file:

Code:

fcgi-port=X

(Replace X with your port, e.g. 55555).

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

ok, is there a guide to modifying the port settings?

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Quote from: jojo69 on January 04, 2021, 09:03:03 PM

Code:

-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte

is this a clue?

Something else than ArmoryDB is listening on the port that ArmoryQt connection to.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

Code:

-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte

is this a clue?

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

thanks, I did not know that

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: jojo69 on January 03, 2021, 02:14:57 PM

just to be clear, am I good to ctrl C the DB process and close that console? The DB doesn't need any special shutdown does it?

Ctrl + C sends a SIGINT signal to the process. This is not a termination signal like SIGKILL or SIGSTOP.
What the software does after receiving a SIGINT completely depends on the software. It can be ignored, or used as a "shutdown command".

Pressing ctrl + c does not terminate the process. It tells the process to stop / terminate itself. So, yes. you are fine using ctrl + c as its just asking the software to stop.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

thanks HCP,

just to be clear, am I good to ctrl C the DB process and close that console? The DB doesn't need any special shutdown does it?

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: jojo69 on May 23, 2020, 02:31:35 PM

So I created an armorydb.conf in /home/stg/.armory/

Code:

--dbdir="/media/BITCORE/armory"
--satoshi-datadir="/media/BITCORE/Blockchain"

That armorydb.conf looks wrong... I believe it should just be:

Code:

dbdir="/media/BITCORE/armory"
satoshi-datadir="/media/BITCORE/Blockchain"

You don't include the --'s in the .conf files. If you do, the options get ignored. It seems the comment in the pathing docs is slightly incorrect:

Quote from: jojo69 on January 02, 2021, 11:36:28 PM

that seems to return the correct pathing no?

Yep, that seems to be picking up the correct pathing when you run it from the commandline with the "/media/BITCORE/..." paths.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

terribly sorry for the delay

Code:

stg@UD5:~
$ cd /usr/bin
stg@UD5:/usr/bin
$ ./ArmoryDB --dbdir="/media/BITCORE/armory" --satoshi-datadir="/media/BITCORE/Blockchain"
/home/stg
logging in /home/stg/.armory/dbLog.txt
-INFO  - 19:34:04: (main.cpp:32) Running on 8 threads
-INFO  - 19:34:04: (main.cpp:33) Ram usage level: 50
-INFO  - 19:34:04: (BlockUtils.cpp:915) blkfile dir: /media/BITCORE/Blockchain/blocks
-INFO  - 19:34:04: (BlockUtils.cpp:916) lmdb dir: /media/BITCORE/armory
-INFO  - 19:34:04: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 19:34:04: (BDM_Server.h:263) Listening on port 9001
-INFO  - 19:34:04: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 19:34:04: (DatabaseBuilder.cpp:199) Reading headers from db
-WARN  - 19:34:04: (lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 19:34:04: (DatabaseBuilder.cpp:238) Found 1 headers in db
-INFO  - 19:34:04: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO  - 19:34:04: (Blockchain.cpp:248) Organizing chain 
-INFO  - 19:34:04: (Blockchain.cpp:370) Organized chain in 0s
-INFO  - 19:34:04: (DatabaseBuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 19:34:04: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 19:34:04: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO  - 19:34:04: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO  - 19:34:04: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking

that seems to return the correct pathing no?

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Quote from: jojo69 on May 23, 2020, 02:31:35 PM

Is this what you wanted?

Yes. The results are surprising, it is not detecting the pathing at all. Try running the DB directly with the cli args. From /usr/bin run:

Code:

./ArmoryDB --dbdir="/media/BITCORE/armory" --satoshi-datadir="/media/BITCORE/Blockchain"

Quote

then I navigated to /usr/bin and ran ArmoryDB

If you've installed Armory you shouldn't not need to browse to the bin folder to run the binary, it should be in your path, i.e. you can run ArmoryDB, whatever path your terminal is pointing at. Since you bothered browsing to the binary's folder, run with ./ preprended to guarantee you're using the local copy of ArmoryDB. Who knows, maybe you have installation snafu. Also, try the cli args without the quotes (") and lmk.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

OK, I am going to be very methodical here because it is probable that I am making really dumb mistakes. Honestly, goatpig, I do not know what motivates you to continue putting up with people like me but bless you.

So I created an armorydb.conf in /home/stg/.armory/

Code:

--dbdir="/media/BITCORE/armory"

--satoshi-datadir="/media/BITCORE/Blockchain"

then I navigated to /usr/bin and ran ArmoryDB

Code:

stg@UD5:~
$ cd .
stg@UD5:~
$ cd /usr/bin
stg@UD5:/usr/bin
$ ArmoryDB
/home/stg
/home/stg
logging in /home/stg/.armory/dbLog.txt
-INFO  - 11:15:14: (main.cpp:32) Running on 8 threads
-INFO  - 11:15:14: (main.cpp:33) Ram usage level: 50
-INFO  - 11:15:14: (BlockUtils.cpp:915) blkfile dir: /home/stg/.bitcoin/blocks
-INFO  - 11:15:14: (BlockUtils.cpp:916) lmdb dir: /home/stg/.armory/databases
-INFO  - 11:15:14: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 11:15:14: (BDM_Server.h:263) Listening on port 9001
-INFO  - 11:15:14: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 11:15:14: (DatabaseBuilder.cpp:199) Reading headers from db
-WARN  - 11:15:14: (lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 11:15:14: (DatabaseBuilder.cpp:238) Found 1 headers in db
-INFO  - 11:15:14: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO  - 11:15:14: (Blockchain.cpp:248) Organizing chain 
-INFO  - 11:15:14: (Blockchain.cpp:370) Organized chain in 0s
-INFO  - 11:15:14: (DatabaseBuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 11:15:14: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 11:15:14: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO  - 11:15:14: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO  - 11:15:14: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking

Is this what you wanted?

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Create an armorydb.conf, put your --dbdir and --satoshi-datadir args in there, then ArmoryDB from the terminal. What do you get?

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

I don't see any, .armory has .cookie_, several .wallets the three logs and settings in it, well, and a databases folder that I don't think it should be using...

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

What config files do you have?

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

so yeah, had to step away for a bit, frustration and other stuff going on

The situation here is that armorylog shows --dbdir="/home/stg/.armory/databases", but I DO HAVE my alternate path /media/BITCORE/armory specified in the Armory Settings dialog in the GUI.

ArmorySettings.txt agrees with the GUI; ArmoryDbdir l /media/BITCORE/armory

so, I'm stumped

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Quote

I have had Armory Database pointed to /media/BITCORE/armory under file/settings, but is obviously has not written its logs there since the yuletide, while the logs in /home/usr/.armory are more current...why on earth would that be?

Database path is just that.

satoshi-datadir -> Path to Core's datadir, defaults to ~/.bitcoin

datadir -> path to Armory's setting files, logs & wallets. Defaults to ~/.armory

dbdir -> Armory database folder, defaults to [datadir]/databases

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

yeah, clearly my pathing is borked, those logs are from the old Win7 build

I remember having to grapple with editing fstab to get that BITCORE drive with the blockchain on it mounted.

I am running 0.96.5-beta per the about tab in the GUI

I have had Armory Database pointed to /media/BITCORE/armory under file/settings, but is obviously has not written its logs there since the yuletide, while the logs in /home/usr/.armory are more current...why on earth would that be?

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Says 96.3, is there a reason you're on an older release for your online machine?

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

OK, so that is some shit copied over from me trying to not re-download 250GB of blockchain when they stopped supporting win7

that is the only explanation for that

what a mess

Quote

your Armory install is NOT set to use this directory... and is writing to /home/usr/.armory

copy that, investigating

HCP

legendary

Activity: 2086

Merit: 4314

I'm not sure where that logfile has come from... but it is showing an old, outdated version of Armory... running on Windows:

Code:

2020-01-02 09:28:19 (INFO) -- ArmoryUtils.pyc:1271 -    Armory Version        : 0.96.3
2020-01-02 09:28:19 (INFO) -- ArmoryUtils.pyc:1272 -    Armory Build:         : 2b65ac0648
2020-01-02 09:28:19 (INFO) -- ArmoryUtils.pyc:1273 -    PyBtcWallet  Version  : 1.35
2020-01-02 09:28:19 (INFO) -- ArmoryUtils.pyc:1274 - Detected Operating system: Windows
2020-01-02 09:28:19 (INFO) -- ArmoryUtils.pyc:1275 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free

But you say you're now running on Linux? Huh

So, I don't think these logfiles are at all relevant to your current issue.

Quote from: jojo69 on May 13, 2020, 06:30:27 PM

So, pathing, the perennial bugaboo of Armory support; I have both core and Armory pointed to an alternate location, /media/BITCORE/ but both seem to still write some data to /home/usr/.bitcoin and /home/usr/.armory.

It appears that while Bitcoin Core is indeed using /media/BITCORE, your Armory install is NOT set to use this directory... and is writing to /home/usr/.armory

Quote from: jojo69 on May 13, 2020, 06:30:27 PM

nuke DB...right...I remember something about that, of course that was on windows...hmmm

In Armory, Goto "Help -> Rebuild and Rescan Databases"... Click "Yes" and then shut down and restart Armory.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

nuke DB...right...I remember something about that, of course that was on windows...hmmm

wanders off to poke around/

hold up! I found another set of logs, and perhaps this will be instructive, at least about my ignorance if nothing else.

So, pathing, the perennial bugaboo of Armory support; I have both core and Armory pointed to an alternate location, /media/BITCORE/ but both seem to still write some data to /home/usr/.bitcoin and /home/usr/.armory. 200 some odd GB in .bitcoin on my boot nVME was the issue that precipitated this whole exercise.

I am really sorry guys, I swear once you get me trained back up I will help point some noobs to electrum for a while, I try and give back, but the months go by and computers are not my main thing.

The log files in /media/BITCORE are too large for pastebin, and seem to end around newyears, clearly my pathing is borked yet again...I do not recall changing anything but we have already established that this is not unheard of.

here is the tail of armorylog

https://pastebin.com/dFYGZ5jn

"when I click on dblog there it tells me "some file(s) could not be opened! you may not have the permission to read"

ffs...since when, it worked before

linux permissions fml, I am in hell

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Well the DB is reporting that there is no history to scan so it looks like they were never registered. I'd nuke Armory's DB and try again.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

ummmm, 2 I believe, an empty hot wallet and a watching only, they show in the "available wallets" field of the GUI, no balances reported of course

is that a clue?

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Do you not have a wallet loaded?

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

dblog...right, sorry, I forget between problems, thanks!

https://pastebin.com/84Q1LFCP

HCP

legendary

Activity: 2086

Merit: 4314

That's the Armorylog.txt and it looks fine. Nothing untoward showing there. Can you post the contents of the dbLog.txt?

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

log...right...uh...

I hope this is right

https://pastebin.com/NvGXvvkt

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Probably hung, though a look at the logs wouldn't hurt.

jojo69

legendary

Activity: 3066

Merit: 4195

diamond-handed zealot

I am really sorry to bother you guys. It seems like something breaks every couple years and I have to teach myself all the tricks over again. I lose my chops in the intervening months.

I had a drive get full and my node went offline for 13 weeks. I closed and rebooted and fired up bitcoin-qt and let it sync, then closed that normally and rebooted again and started up armory.

Things seemed to go well at first but now it is "Parsing Tx Hashes" for 12 hours which doesn't seem right. There is a python task taking up 12% of my CPU that I think isn't usually there, so maybe that is it working away so I am reluctant to lose patience. I figured I would ask what you folks think.

It is on an MX linux build, which is a debian with xfce.

Topic: "Parsing Tx Hashes" all night, hung or wait? (Read 409 times)