Bitcoin Forum
April 30, 2024, 05:18:00 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: ArmoryDB Crashes scanning tx from block # to #  (Read 129 times)
GBitcoinG (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 14, 2024, 09:16:19 PM
 #1

I'm running core v25.0.0 and let it download the full blockchain and is currently synced.
I'm running Armory 96.5-beta-8730390989
I run BitcoinQT before I start Armory and let it sync.

If I do not have a wallet registered in Armory, it works perfectly and will sync and update blocks as they come in.

I loaded a watch-only wallet, and ArmoryDB will crash with the following line:
-INFO  - 21:53:26.938: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #142692 to #170004
<crash>

If I delete the DB folder contents and Rebuild and Rescan Databases it also fails at that line.
-INFO  - 21:53:26.938: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #142692 to #170004
<crash>

If I remove that wallet, it begins working and synching perfectly again.

I created a new wallet with Armory to test if it was my watch-only copy, or scanning in general and it gets a little further, but ArmoryDB will still crash during this phase, on a later block but seemingly random one each time, eg:
-INFO  - 14:54:21.016: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #0 to #142691
-INFO  - 14:54:21.594: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #142692 to #170004
-INFO  - 14:54:22.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #170005 to #183110
-INFO  - 14:54:22.516: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #183111 to #189230
-INFO  - 14:54:23.000: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #189231 to #194895
-INFO  - 14:54:23.469: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #194896 to #200879
-INFO  - 14:54:24.891: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #200880 to #206654
<crash>

Here are my logs and settings from me testing the new wallet, but the intention is to get my watch-only working.
Reading it myself, I notice that the settings file has my setting have my logFile set to: C:\Users\<my user>\AppData\Roaming\Armory\ArmoryQt.exe.log.txt, but the one in my install directory is the one that updates: F:\Armory\ArmoryQt.exe.log, but can't see why this is forced here.

armorycpplog.txt

Quote
Log file opened at 15:07:21.000: C:\Users\<my user>\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 15:09:14.047: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:447) POLLERR error in readAndWrite
-ERROR - 15:09:14.047: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:359) POLLERR error in readAndWrite

armorylog.txt

Quote
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1164 - C++ block utilities loaded successfully
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1281 -
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1282 -
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1283 -
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: F:\Armory\ArmoryQt.exe --satoshi-datadir=F:\Bitcoin\Data --dbdir=F:\Armory\DB
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine:
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1288 -    Armory Version        : 0.96.5
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1289 -    Armory Build:         : 8730390989
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1290 -    PyBtcWallet  Version  : 1.35
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1292 -    OS Variant            : 10-10.0.19041--Multiprocessor Free
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\<my user>\AppData\Roaming
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : F:\Bitcoin\Data
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\<my user>\AppData\Roaming\Armory\
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    :
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1297 -    Total Available RAM   : 31.94 GB
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1298 -    CPU ID string         : Intel64 Family 6 Model 158 Stepping 12, GenuineIntel
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1299 -    Number of CPU cores   : 16 cores
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1300 -    System is 64-bit      : True
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1301 -    Preferred Encoding    : cp1252
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1302 -    Machine Arch          : amd64
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1303 -    Available HDD (ARM)   : 163 GB
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1304 -    Available HDD (BTC)   : 276 GB
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1305 -
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py:
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     force_segwit    : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     nettimeout      : 2
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     rescan          : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     force_fcgi      : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreAllZC     : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     rescanBalance   : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     disableModules  : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     port            : None
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     interport       : 8223
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     coverageOutputDir: None
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     forceWalletCheck: False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     regtest         : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     rebuild         : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     thread_count    : -1
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     datadir         : DEFAULT
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     clearMempool    : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     offline         : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     armoryDBDir     : F:\Armory\DB
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_port   : 9001
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiPort     : DEFAULT
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     disableConfPermis: False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     useTorSettings  : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     netlog          : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     keypool         : 100
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     coverageInclude : None
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     forceOnline     : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     disableWalletCheck: False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     redownload      : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     rpcBindAddr     : 127.0.0.1
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_ip     : 127.0.0.1
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     multisigFile    : DEFAULT
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     ram_usage       : -1
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreZC        : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     logDisable      : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     settingsPath    : C:\Users\<my user>\AppData\Roaming\Armory\ArmorySettings.txt
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     language        : en
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     db_type         : DB_FULL
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     doDebug         : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     enableDetSign   : True
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     mtdebug         : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     testnet         : False
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     rpcport         : DEFAULT
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiHome     : F:\Bitcoin\Data
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiRpcport  : DEFAULT
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     logFile         : C:\Users\<my user>\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1311 -     verbosity       : None
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments:
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\<my user>\AppData\Roaming\Armory\ArmorySettings.txt
2024-04-14 15:07:21 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
2024-04-14 15:07:21 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2024-04-14 15:07:21 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2024-04-14 15:07:21 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background. 
2024-04-14 15:07:21 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2024-04-14 15:07:21 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2024-04-14 15:07:21 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2024-04-14 15:07:23 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\<my user>\AppData\Roaming\Armory\ArmorySettings.txt
2024-04-14 15:07:23 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2024-04-14 15:07:23 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2024-04-14 15:07:23 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 1
2024-04-14 15:07:23 (INFO) -- ArmoryQt.py:2190 -    Wallet (2EpWxLkAb):   "Primary Wallet                  "   (Encrypted)
2024-04-14 15:07:23 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2024-04-14 15:07:23 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user.  Done!
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2024-04-14 15:07:25 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = F:\Bitcoin\Data
2024-04-14 15:07:25 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2024-04-14 15:07:25 (INFO) -- SDM.pyc:173 -    F:\Bitcoin\daemon\bitcoind.exe
2024-04-14 15:07:25 (INFO) -- SDM.pyc:175 - Using: F:\Bitcoin\daemon\bitcoind.exe
2024-04-14 15:07:25 (INFO) -- SDM.pyc:340 - Called startBitcoind
2024-04-14 15:07:31 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: F:\Bitcoin\daemon\bitcoind.exe -datadir=F:\Bitcoin\Data
2024-04-14 15:07:31 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: [u'F:\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=F:\\Bitcoin\\Data']
2024-04-14 15:07:31 (INFO) -- SDM.pyc:451 - PID of bitcoind: 7272
2024-04-14 15:07:31 (INFO) -- SDM.pyc:452 - PID of armory:   13692
2024-04-14 15:07:31 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['F:\\Armory\\guardian.exe', '13692', '7272']
2024-04-14 15:07:37 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2024-04-14 15:07:37 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = F:\Bitcoin\Data
2024-04-14 15:07:37 (WARNING) -- SDM.pyc:402 - Spawning DB with command: F:\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="F:\Bitcoin\Data\blocks" --satoshi-port=8333 --datadir="C:\Users\<my user>\AppData\Roaming\Armory\" --dbdir="F:\Armory\DB"
2024-04-14 15:07:37 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['F:\\Armory\\ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="F:\\Bitcoin\\Data\\blocks"', '--satoshi-port=8333', '--datadir="C:\\Users\\<my user>\\AppData\\Roaming\\Armory\\"', u'--dbdir="F:\\Armory\\DB"']
2024-04-14 15:07:42 (INFO) -- ArmoryQt.py:1824 - Connecting on port 57623
2024-04-14 15:07:42 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2024-04-14 15:07:42 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2024-04-14 15:07:42 (ERROR) -- ArmoryQt.py:1198 - 4 attempts to load blockchain failed.  Remove mempool.bin.
2024-04-14 15:07:42 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
2024-04-14 15:07:42 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2024-04-14 15:07:42 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:07:42 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:01 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:01 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:01 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:01 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:01 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:02 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:02 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:02 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:02 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:03 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:03 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:03 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:03 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:03 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:04 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:04 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:04 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:04 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:07 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:08 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:08 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:08 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:09 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:09 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:10 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:10 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:11 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:11 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2024-04-14 15:09:11 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode

ArmorySettings.txt

Quote
Default_FeeByte                      | 50
ManageSatoshi                        | True
AdjustFee                            | True
SkipOnlineCheck                      | False
MainWalletCols                       | ff0500006000a70079002e01
NotifyBlkFinish                      | False
MainGeometry                         | 01d9d0cb0001000000000601000002d3000009f80000057100000609000002f2000009f00000056 9000000010000
Default_FeeByte_Strategy             | CONSERVATIVE
SendBtcGeometry                      | 01d9d0cb000100000000065100000245000009b2000004610000065900000264000009aa0000045 9000000010000
LastBlkRecvTime                      | 1713065492.13
LastDirectory                        | C:/Users/<my user>/AppData/Roaming/Armory
Agreed_to_EULA                       | True
NotifyBtcIn                          | True
SyncSuccessCount                     | 10
Wallet_2EpWxLkAb_LedgerShow          | True
FeeOption                            | Auto
MainLedgerCols                       | ff0d14000000ad004800ad0096007000000000000000000000000000
UseTorSettings                       | False
DNAA_UnlockTimeout                   | False
WltPropAddrCols                      | ff04bc0064006400d300
AlwaysArmoryURI                      | 1
NotifyDiscon                         | True
FailedLoadCount                      | 5
NotifyIgnore                         |
DNAA_IntroDialog                     | True
SatoshiDatadir                       | F:\Bitcoin\Data
DateFormat                           | 25592d25622d25642025493a254d2570
DNAA_AllBackupWarn                   | False
Default_FeeByte_BlocksToConfirm      | 3
Default_ReceiveType                  | P2PKH
Wallet_mKaDNWWs_LedgerShow           | False
AdvFeature_UseCt                     | 0
UnlockTimeout                        | 10
Default_Fee                          | 20000
LastFilterState                      | 0
MinimizeOrClose                      | Close
User_Mode                            | Expert
Load_Count                           | 42
First_Load_Date                      | 1711849663
NotifyBtcOut                         | True
DNAA_Version092Warn                  | True
MinimizeOnOpen                       | False
First_Load                           | False
Default_ChangeType                   | P2PKH
IgnoreAlerts                         |
LastBlkRecv                          | 839122
DNAA_ImportWarning                   | False
DNAA_DeleteLevelDB                   | False
NotifyReconn                         | True
SatoshiExe                           | F:\Bitcoin
DNAA_DefaultApp                      | True
WltPropGeometry                      | 01d9d0cb00010000000002a4000003560000060300000546000002ac00000375000005fb0000053 e000000010000
LastVersionLoad                      | v0.96.5

dbLog.txt

Quote
Log file opened at 15:07:39.000: C:\Users\<my user>\AppData\Roaming\Armory\dbLog.txt
-INFO  - 15:07:39.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 16 threads
-INFO  - 15:07:39.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 15:07:39.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: F:\Bitcoin\Data\blocks
-INFO  - 15:07:39.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: F:\Armory\DB
-INFO  - 15:07:39.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 15:07:39.063: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 57623
-INFO  - 15:07:39.063: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:57) RPC connection established
-INFO  - 15:07:39.063: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO  - 15:07:39.063: (e:\users\goat\code\armory3\cppforswig\blockdatamanagerconfig.cpp:919) waiting on node sync: 99.9999%
-INFO  - 15:07:39.063: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:425) Node is ready
-INFO  - 15:07:39.063: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 15:07:42.156: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: 3f1457ad2f9cf3014a9e
-INFO  - 15:09:01.344: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-INFO  - 15:09:04.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 839244 headers in db
-INFO  - 15:09:07.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:64) Rewinding 100 blocks
-INFO  - 15:09:07.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 15:09:07.828: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:493) Found next block after skipping 1895474bytes
-INFO  - 15:09:08.391: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4230
-INFO  - 15:09:08.406: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 15:09:08.438: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 0s
-INFO  - 15:09:08.438: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 15:09:08.469: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 15:09:08.469: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 15:09:08.875: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 15:09:08.906: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO  - 15:09:08.969: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
-INFO  - 15:09:09.344: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #0 to #142691
-INFO  - 15:09:09.875: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #142692 to #170004
-INFO  - 15:09:10.360: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #170005 to #183110
-INFO  - 15:09:10.766: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #183111 to #189230
-INFO  - 15:09:11.235: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #189231 to #194895
-INFO  - 15:09:11.656: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #194896 to #200879
-INFO  - 15:09:11.078: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #200880 to #206654

Can anyone see why ArmoryDB is crashing while scanning Tx history?
Any insights are very appreciated.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714497480
Hero Member
*
Offline Offline

Posts: 1714497480

View Profile Personal Message (Offline)

Ignore
1714497480
Reply with quote  #2

1714497480
Report to moderator
1714497480
Hero Member
*
Offline Offline

Posts: 1714497480

View Profile Personal Message (Offline)

Ignore
1714497480
Reply with quote  #2

1714497480
Report to moderator
1714497480
Hero Member
*
Offline Offline

Posts: 1714497480

View Profile Personal Message (Offline)

Ignore
1714497480
Reply with quote  #2

1714497480
Report to moderator
GBitcoinG (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 14, 2024, 09:47:04 PM
 #2

Like I said, ArmoryQt.exe.log for some reason spawns in F:\Armory where Armoryqt.exe is.

ArmoryQt.exe.log

Quote
(ERROR) ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:445 - Spawning bitcoind with command: F:\Bitcoin\daemon\bitcoind.exe -datadir=F:\Bitcoin\Data
(WARNING) SDM.pyc:402 - Spawning DB with command: F:\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="F:\Bitcoin\Data\blocks" --satoshi-port=8333 --datadir="C:\Users\<my user>\AppData\Roaming\Armory\" --dbdir="F:\Armory\DB"
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
April 15, 2024, 07:42:07 AM
 #3

ArmoryDB keeps track of the addresses you present it, so further scanning with fresh wallet will not evict the address from your WO. That test isn't very informative as a result. Try the following:

1. Start ArmoryQt in offline mode, go to File -> Settings, in the first section, uncheck the auto bitcoind management option. You can turn this back on later, but for the purpose of this test, I need it off. Also make sure it only is loading an empty wallet. Do not load your WO for this test either.
2. Delete the content of your database folder (F:\Armory\DB)
3. Without Core running, start ArmoryDB from the command line (it's in  F:\Armory):

Code:
 ArmoryDB.exe --satoshi-datadir="F:\Bitcoin\Data\blocks" --dbdir="F:\Armory\DB" 

It should start building the db. I'll need you to use a hardware monitor and report on the max values for CPU load & temps, as well as RAM usage and SSD load & temps. Use something like OpenHardwareMonitor. Make sure to reset it max values between build & scan phases, I need values for both.

4. Once it's done building, you can start ArmoryQt (remember, Core cannot run so auto bitcoind should be off). ArmoryQt should detect the current instance of ArmoryDB and feed it the addresses from the fresh wallet.
5. Report on how far it went. Also copy the text coming out of the command line prompt, this will have extra data that doesn't make it into the log, possibly some verbose for the error. I don't need the ArmoryQt logs for this, just the command line output.

GBitcoinG (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 16, 2024, 12:09:56 AM
 #4

Thank you so much.

I'm sure you can see in the log that I let ArmoryDB build and then started ArmoryQt at 12:06:21.891. I also reset OHM at that time.

ArmoryDB.exe --satoshi-datadir="F:\Bitcoin\Data\blocks" --dbdir="F:\Armory\DB" >> f:\goatpiglog.txt

Quote
logging in C:\Users\<my user>\AppData\Roaming/Armory/dbLog.txt
-INFO  - 07:37:56.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 16 threads
-INFO  - 07:37:56.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 07:37:56.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: F:\Bitcoin\Data\blocks
-INFO  - 07:37:56.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: F:\Armory\DB
-INFO  - 07:37:56.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 07:37:56.078: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 9001
-INFO  - 07:38:00.156: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 07:38:33.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 07:38:33.609: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 07:38:33.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 07:38:33.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 07:39:19.484: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4
-INFO  - 07:39:22.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #11
-INFO  - 07:39:27.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #13
-INFO  - 07:39:30.562: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #15
-INFO  - 07:40:00.422: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #21
-INFO  - 07:40:09.328: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #26
...
...
...
-INFO  - 11:26:29.062: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4148
-INFO  - 11:26:33.219: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4163
-INFO  - 11:27:13.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4164
-INFO  - 11:27:27.172: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4179
-INFO  - 11:28:09.016: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4180
-INFO  - 11:28:13.594: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4195
-INFO  - 11:28:44.672: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4196
-INFO  - 11:29:07.391: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4211
-INFO  - 11:29:38.266: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4212
-INFO  - 11:29:55.359: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4227
-INFO  - 11:30:24.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4228
-INFO  - 11:31:05.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4229
-INFO  - 11:31:28.812: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4230
-INFO  - 11:31:39.969: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4231
-INFO  - 11:31:39.984: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 11:31:41.187: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 2s
-INFO  - 11:32:04.203: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 14011s
-INFO  - 11:32:06.937: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 11:32:06.984: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 11:34:08.109: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 11:34:08.156: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO  - 12:06:21.891: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: 8bab7e257d874fe15aae
-INFO  - 12:06:21.953: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
-INFO  - 12:06:37.578: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #0 to #142691
-INFO  - 12:06:52.875: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #142692 to #170004
-INFO  - 12:07:12.875: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #170005 to #183110
-INFO  - 12:07:27.125: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #183111 to #189230
-INFO  - 12:07:42.422: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #189231 to #194895
-INFO  - 12:07:57.406: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #194896 to #200879
-INFO  - 12:08:12.203: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #200880 to #206654
-INFO  - 12:08:27.344: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #206655 to #211835
-INFO  - 12:08:42.453: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #211836 to #216013
-INFO  - 12:08:58.531: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #216014 to #219400
-INFO  - 12:09:13.547: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #219401 to #222889
-INFO  - 12:09:28.687: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #222890 to #226014
-INFO  - 12:09:43.625: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #226015 to #229700
-INFO  - 12:09:58.672: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #229701 to #232827
-INFO  - 12:10:12.500: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #232828 to #235987
-INFO  - 12:10:27.359: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #235988 to #239311
-INFO  - 12:10:42.344: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #239312 to #243501
-INFO  - 12:10:57.219: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #243502 to #248592
-INFO  - 12:11:12.125: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #248593 to #252921
-INFO  - 12:11:53.453: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #252922 to #256835
-INFO  - 12:12:08.250: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #256836 to #261047
-INFO  - 12:12:23.031: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #261048 to #265286
-INFO  - 12:12:38.984: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #265287 to #269039
-INFO  - 12:12:53.109: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #269040 to #271688
-INFO  - 12:13:08.937: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #271689 to #274362
-INFO  - 12:13:23.969: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #274363 to #277493
-INFO  - 12:13:38.937: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #277494 to #280827
-INFO  - 12:13:53.172: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #280828 to #283888
-INFO  - 12:14:08.109: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #283889 to #286454
-INFO  - 12:14:23.344: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #286455 to #288768
-INFO  - 12:14:38.437: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #288769 to #290929
-INFO  - 12:14:56.578: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #290930 to #293434
-INFO  - 12:15:11.578: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #293435 to #295975
<Crash>

OHMR after building:

Quote
Open Hardware Monitor Report

--------------------------------------------------------------------------------

Version: 0.9.6.0

--------------------------------------------------------------------------------

Common Language Runtime: 4.0.30319.42000
Operating System: Microsoft Windows NT 10.0.19045.0
Process Type: 64-Bit

--------------------------------------------------------------------------------

Sensors

|
+- MSI MPG Z390 GAMING PLUS (MS-7B51) (/mainboard)
|  |
|  +- Nuvoton NCT6797D (/lpc/nct6797d)
|  |  +- CPU VCore      :    0.704    0.696    1.208 (/lpc/nct6797d/voltage/0)
|  |  +- Voltage #2     :        1        1    1.008 (/lpc/nct6797d/voltage/1)
|  |  +- AVCC           :    3.344    3.344    3.344 (/lpc/nct6797d/voltage/2)
|  |  +- 3VCC           :     3.36     3.36    3.376 (/lpc/nct6797d/voltage/3)
|  |  +- Voltage #5     :        1        1    1.008 (/lpc/nct6797d/voltage/4)
|  |  +- Voltage #6     :    0.152    0.152    0.152 (/lpc/nct6797d/voltage/5)
|  |  +- Voltage #7     :    0.952    0.952     0.96 (/lpc/nct6797d/voltage/6)
|  |  +- 3VSB           :    3.344    3.344    3.344 (/lpc/nct6797d/voltage/7)
|  |  +- VTT            :    1.064    1.056    1.064 (/lpc/nct6797d/voltage/9)
|  |  +- Voltage #11    :    1.048    1.048    1.056 (/lpc/nct6797d/voltage/10)
|  |  +- Voltage #12    :    0.832      0.8    0.848 (/lpc/nct6797d/voltage/11)
|  |  +- Voltage #13    :    1.056    1.056    1.056 (/lpc/nct6797d/voltage/12)
|  |  +- Voltage #14    :      0.6      0.6      0.6 (/lpc/nct6797d/voltage/13)
|  |  +- Voltage #15    :    1.536    1.536    1.544 (/lpc/nct6797d/voltage/14)
|  |  +- CPU Core       :     36.5       35       59 (/lpc/nct6797d/temperature/0)
|  |  +- Temperature #1 :     36.5     35.5     41.5 (/lpc/nct6797d/temperature/1)
|  |  +- Temperature #2 :       38       36       39 (/lpc/nct6797d/temperature/2)
|  |  +- Temperature #3 :       28       28       28 (/lpc/nct6797d/temperature/3)
|  |  +- Temperature #4 :       23       23       23 (/lpc/nct6797d/temperature/4)
|  |  +- Temperature #5 :       35       34       37 (/lpc/nct6797d/temperature/5)
|  |  +- Temperature #6 :       -3       -3       -3 (/lpc/nct6797d/temperature/6)
|  |  +- Fan #2         :  710.153  525.906  920.873 (/lpc/nct6797d/fan/1)
|  |  +- Fan #3         :  991.918  971.922  994.842 (/lpc/nct6797d/fan/2)
|  |  +- Fan #4         :  858.233  844.806  864.277 (/lpc/nct6797d/fan/3)
|  |  +- Fan #5         :  881.201  865.385  883.508 (/lpc/nct6797d/fan/4)
|  |  +- Fan #6         :  840.075  834.363  852.811 (/lpc/nct6797d/fan/5)
|  |  +- Fan Control #1 :      100      100      100 (/lpc/nct6797d/control/0)
|  |  +- Fan Control #2 :  12.9412  12.9412  44.3137 (/lpc/nct6797d/control/1)
|  |  +- Fan Control #3 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/2)
|  |  +- Fan Control #4 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/3)
|  |  +- Fan Control #5 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/4)
|  |  +- Fan Control #6 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/5)
|  |  +- Fan Control #7 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/6)
|
+- Intel Core i9-9900K (/intelcpu/0)
|  +- Bus Speed      :      100   99.998  100.002 (/intelcpu/0/clock/0)
|  +- CPU Core #1    :     2100  799.996  5000.01 (/intelcpu/0/clock/1)
|  +- CPU Core #2    :     1200  799.996  5000.01 (/intelcpu/0/clock/2)
|  +- CPU Core #3    :      800  799.996  5000.02 (/intelcpu/0/clock/3)
|  +- CPU Core #4    :      800  799.984  5000.02 (/intelcpu/0/clock/4)
|  +- CPU Core #5    :      800  799.984  5000.11 (/intelcpu/0/clock/5)
|  +- CPU Core #6    :      800  799.996  5000.02 (/intelcpu/0/clock/6)
|  +- CPU Core #7    :      800  799.996  5000.01 (/intelcpu/0/clock/7)
|  +- CPU Core #8    :      800  799.996  5000.02 (/intelcpu/0/clock/8)
|  +- CPU Core #1    :       35       33       56 (/intelcpu/0/temperature/0)
|  +- CPU Core #2    :       36       34       57 (/intelcpu/0/temperature/1)
|  +- CPU Core #3    :       35       34       59 (/intelcpu/0/temperature/2)
|  +- CPU Core #4    :       36       34       62 (/intelcpu/0/temperature/3)
|  +- CPU Core #5    :       35       33       53 (/intelcpu/0/temperature/4)
|  +- CPU Core #6    :       35       33       58 (/intelcpu/0/temperature/5)
|  +- CPU Core #7    :       36       34       60 (/intelcpu/0/temperature/6)
|  +- CPU Core #8    :       36       34       54 (/intelcpu/0/temperature/7)
|  +- CPU Package    :       37       35       60 (/intelcpu/0/temperature/8)
|  +- CPU Total      :  1.26503 0.0976563  10.5328 (/intelcpu/0/load/0)
|  +- CPU Core #1    :  3.89423        0  26.5625 (/intelcpu/0/load/1)
|  +- CPU Core #2    :        0        0  16.4063 (/intelcpu/0/load/2)
|  +- CPU Core #3    :        0        0  46.9231 (/intelcpu/0/load/3)
|  +- CPU Core #4    :   1.5625        0       50 (/intelcpu/0/load/4)
|  +- CPU Core #5    : 0.769234        0  11.7436 (/intelcpu/0/load/5)
|  +- CPU Core #6    :  1.55048        0       50 (/intelcpu/0/load/6)
|  +- CPU Core #7    :        0        0  48.4375 (/intelcpu/0/load/7)
|  +- CPU Core #8    :  2.34375        0  14.2857 (/intelcpu/0/load/8)
|  +- CPU Package    :  8.89019  8.11068  40.7437 (/intelcpu/0/power/0)
|  +- CPU Cores      :  2.51444  1.73726  34.3413 (/intelcpu/0/power/1)
|  +- CPU Graphics   :        0        0        0 (/intelcpu/0/power/2)
|  +- CPU DRAM       : 0.482589 0.464498  1.26618 (/intelcpu/0/power/3)
|
+- Generic Memory (/ram)
|  +- Memory         :  25.4745  17.2194  26.9941 (/ram/load/0)
|  +- Used Memory    :  8.13548  5.49915  8.62076 (/ram/data/0)
|  +- Available Memory :  23.8003   23.315  26.4366 (/ram/data/1)
|
+- WDC WDS250G2B0A (/hdd/0)
|  +- Temperature    :       40       38       40 (/hdd/0/temperature/0)
|  +- Used Space     :  29.5803  29.5803  29.5845 (/hdd/0/load/0)
|
+- WDC WDS500G2B0A (/hdd/1)
|  +- Temperature    :       42       40       42 (/hdd/1/temperature/0)
|  +- Used Space     :  93.3071  93.3071  93.3071 (/hdd/1/load/0)
|
+- ST3500418AS (/hdd/2)
|  +- Temperature    :       38       34       38 (/hdd/2/temperature/0)
|  +- Used Space     :  88.2378  88.2378  88.2378 (/hdd/2/load/0)
|
+- Generic Hard Disk (/hdd/3)
|  +- Used Space     :  70.8649  70.4349  70.8649 (/hdd/3/load/0)
|
+- Generic Hard Disk (/hdd/4)
|  +- Used Space     : 0.00037384 0.00037384 0.00037384 (/hdd/4/load/0)

--------------------------------------------------------------------------------

OHMR After Reset and Scanning Tx:

Quote

Open Hardware Monitor Report

--------------------------------------------------------------------------------

Version: 0.9.6.0

--------------------------------------------------------------------------------

Common Language Runtime: 4.0.30319.42000
Operating System: Microsoft Windows NT 10.0.19045.0
Process Type: 64-Bit

--------------------------------------------------------------------------------

Sensors

|
+- MSI MPG Z390 GAMING PLUS (MS-7B51) (/mainboard)
|  |
|  +- Nuvoton NCT6797D (/lpc/nct6797d)
|  |  +- CPU VCore      :    0.696    0.696    1.232 (/lpc/nct6797d/voltage/0)
|  |  +- Voltage #2     :    1.008        1    1.008 (/lpc/nct6797d/voltage/1)
|  |  +- AVCC           :    3.344    3.344    3.344 (/lpc/nct6797d/voltage/2)
|  |  +- 3VCC           :    3.376     3.36    3.376 (/lpc/nct6797d/voltage/3)
|  |  +- Voltage #5     :        1        1    1.008 (/lpc/nct6797d/voltage/4)
|  |  +- Voltage #6     :    0.152    0.152     0.16 (/lpc/nct6797d/voltage/5)
|  |  +- Voltage #7     :    0.952    0.952     0.96 (/lpc/nct6797d/voltage/6)
|  |  +- 3VSB           :    3.344    3.344    3.344 (/lpc/nct6797d/voltage/7)
|  |  +- VTT            :    1.064    1.056    1.064 (/lpc/nct6797d/voltage/9)
|  |  +- Voltage #11    :    1.048    1.048    1.056 (/lpc/nct6797d/voltage/10)
|  |  +- Voltage #12    :    0.832    0.784    0.832 (/lpc/nct6797d/voltage/11)
|  |  +- Voltage #13    :    1.056    1.056    1.056 (/lpc/nct6797d/voltage/12)
|  |  +- Voltage #14    :      0.6      0.6      0.6 (/lpc/nct6797d/voltage/13)
|  |  +- Voltage #15    :    1.544    1.536    1.544 (/lpc/nct6797d/voltage/14)
|  |  +- CPU Core       :       37     36.5     60.5 (/lpc/nct6797d/temperature/0)
|  |  +- Temperature #1 :     36.5       36     40.5 (/lpc/nct6797d/temperature/1)
|  |  +- Temperature #2 :       39       38       42 (/lpc/nct6797d/temperature/2)
|  |  +- Temperature #3 :       28       28       28 (/lpc/nct6797d/temperature/3)
|  |  +- Temperature #4 :       23       23       23 (/lpc/nct6797d/temperature/4)
|  |  +- Temperature #5 :       35       35       38 (/lpc/nct6797d/temperature/5)
|  |  +- Temperature #6 :       -3       -3       -2 (/lpc/nct6797d/temperature/6)
|  |  +- Fan #2         :  725.027  707.918  814.725 (/lpc/nct6797d/fan/1)
|  |  +- Fan #3         :  984.683  981.818  1005.21 (/lpc/nct6797d/fan/2)
|  |  +- Fan #4         :  861.519   847.99  884.666 (/lpc/nct6797d/fan/3)
|  |  +- Fan #5         :  880.052  866.496  886.408 (/lpc/nct6797d/fan/4)
|  |  +- Fan #6         :  840.075  826.699  855.513 (/lpc/nct6797d/fan/5)
|  |  +- Fan Control #1 :      100      100      100 (/lpc/nct6797d/control/0)
|  |  +- Fan Control #2 :  12.9412  12.9412  38.8235 (/lpc/nct6797d/control/1)
|  |  +- Fan Control #3 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/2)
|  |  +- Fan Control #4 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/3)
|  |  +- Fan Control #5 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/4)
|  |  +- Fan Control #6 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/5)
|  |  +- Fan Control #7 :  57.6471  57.6471  57.6471 (/lpc/nct6797d/control/6)
|
+- Intel Core i9-9900K (/intelcpu/0)
|  +- Bus Speed      :  99.9996  99.9982  100.002 (/intelcpu/0/clock/0)
|  +- CPU Core #1    :  4799.98  799.986   5000.1 (/intelcpu/0/clock/1)
|  +- CPU Core #2    :  3899.98  799.986  5000.01 (/intelcpu/0/clock/2)
|  +- CPU Core #3    :  2999.99  799.986  5000.01 (/intelcpu/0/clock/3)
|  +- CPU Core #4    :  2099.99  799.986  5000.01 (/intelcpu/0/clock/4)
|  +- CPU Core #5    :     1200  799.986     5000 (/intelcpu/0/clock/5)
|  +- CPU Core #6    :  799.997  799.985     5000 (/intelcpu/0/clock/6)
|  +- CPU Core #7    :  799.997  799.985     5000 (/intelcpu/0/clock/7)
|  +- CPU Core #8    :  799.997  799.985  5000.01 (/intelcpu/0/clock/8)
|  +- CPU Core #1    :       36       34       59 (/intelcpu/0/temperature/0)
|  +- CPU Core #2    :       37       36       60 (/intelcpu/0/temperature/1)
|  +- CPU Core #3    :       36       34       58 (/intelcpu/0/temperature/2)
|  +- CPU Core #4    :       36       35       55 (/intelcpu/0/temperature/3)
|  +- CPU Core #5    :       35       34       61 (/intelcpu/0/temperature/4)
|  +- CPU Core #6    :       35       35       56 (/intelcpu/0/temperature/5)
|  +- CPU Core #7    :       35       35       57 (/intelcpu/0/temperature/6)
|  +- CPU Core #8    :       36       35       52 (/intelcpu/0/temperature/7)
|  +- CPU Package    :       37       36       61 (/intelcpu/0/temperature/8)
|  +- CPU Total      :  0.78125 0.192356  28.4552 (/intelcpu/0/load/0)
|  +- CPU Core #1    :  0.78125        0  45.3125 (/intelcpu/0/load/1)
|  +- CPU Core #2    :   1.5625        0  42.0635 (/intelcpu/0/load/2)
|  +- CPU Core #3    :        0        0  31.5385 (/intelcpu/0/load/3)
|  +- CPU Core #4    :        0        0   34.375 (/intelcpu/0/load/4)
|  +- CPU Core #5    :        0        0  49.2188 (/intelcpu/0/load/5)
|  +- CPU Core #6    :        0        0  38.8112 (/intelcpu/0/load/6)
|  +- CPU Core #7    :   1.5625        0    31.25 (/intelcpu/0/load/7)
|  +- CPU Core #8    :  2.34375        0  20.1082 (/intelcpu/0/load/8)
|  +- CPU Package    :  9.08931  4.25955  60.9273 (/intelcpu/0/power/0)
|  +- CPU Cores      :  2.71157  1.45312  58.1682 (/intelcpu/0/power/1)
|  +- CPU Graphics   :        0        0        0 (/intelcpu/0/power/2)
|  +- CPU DRAM       : 0.489455 0.472622  1.44869 (/intelcpu/0/power/3)
|
+- Generic Memory (/ram)
|  +- Memory         :  17.2949  16.3831  27.5112 (/ram/load/0)
|  +- Used Memory    :  5.52326  5.23206   8.7859 (/ram/data/0)
|  +- Available Memory :  26.4125  23.1499  26.7037 (/ram/data/1)
|
+- WDC WDS250G2B0A (/hdd/0)
|  +- Temperature    :       40       40       42 (/hdd/0/temperature/0)
|  +- Used Space     :  29.7091  29.5801  29.8713 (/hdd/0/load/0)
|
+- WDC WDS500G2B0A (/hdd/1)
|  +- Temperature    :       38       37       43 (/hdd/1/temperature/0)
|  +- Used Space     :  93.3071  93.3071  93.3071 (/hdd/1/load/0)
|
+- ST3500418AS (/hdd/2)
|  +- Temperature    :       38       38       40 (/hdd/2/temperature/0)
|  +- Used Space     :  88.2378  88.2378  88.2378 (/hdd/2/load/0)
|
+- Generic Hard Disk (/hdd/3)
|  +- Used Space     :  70.8649  70.8649  70.8649 (/hdd/3/load/0)
|
+- Generic Hard Disk (/hdd/4)
|  +- Used Space     : 0.00037384 0.00037384 0.00037384 (/hdd/4/load/0)

--------------------------------------------------------------------------------
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
April 16, 2024, 07:50:21 AM
 #5

System looks stable, temps are in check, memory usage doesn't even have time to spike. This kind of blowup is usually symptomatic of a system issue. This is reinforced by the random nature of the crash: if it was a specific block breaking the scan, it would fail at the same place every time, and empty wallets wouldn't reproduce.

It's hard to tell what's going on tbh. How much disk scape is available on F? How big is the databases folder currently? Also try the scan phase by starting ArmoryDB with --thread-count=1

GBitcoinG (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 17, 2024, 04:30:51 AM
 #6

Quote
How much disk scape is available on F?

279 GB

Quote
How big is the databases folder currently?

3.96 GB

Quote
Also try the scan phase by starting ArmoryDB with --thread-count=1

It crashes on this line or an adjacent one:
scanned from block #283889 to #286454

Letting armoryqt start armorydb with whatever the threadcount default is, it crashes on this line or an adjacent one:
scanned from block #229701 to #232827
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
April 17, 2024, 11:16:10 AM
 #7

It crashes on this line or an adjacent one:
scanned from block #283889 to #286454

And that's with the empty wallet? And Core runs fine? I have no idea what's going on there, only solution I can think of atm is to run ArmoryDB in a debugger to catch the crash in there. If you're willing to install MSVC on your system, I can guide you through it.

GBitcoinG (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 18, 2024, 12:38:40 AM
 #8

That's correct, empty wallet. The Core has been running fine the whole time.

When I restart the test, the dblog is wiped out and there are also 1,743,924 white spaces printed in the top of the dblog.txt before it starts again with:

Quote
Log file opened at 18:28:46.000: C:\Users\<my user>\AppData\Roaming/Armory/dbLog.txt
-INFO  - 18:28:46.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 16 threads

I'd love to get to the bottom of this if you're willing to help with MSVC.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
April 18, 2024, 08:23:11 AM
 #9

To get to debug armory, you will have to build a debug version of armorydb from source. It may sound scary but it's not that bad. There are 3 distinct steps:

Git:

1. Download and install "git for windows", use the defaults (https://gitforwindows.org)
2. Create a folder somewhere, in your Documents folder maybe, or use the default one git gives you. This is where git will download repos for you.
3. Start git bash (search for it from your start menu). Once in git bash:
   3.a. navigate to the folder you created
   3.b. type in the following commands:

Code:
git clone https://github.com/goatpig/BitcoinArmory.git (this will setup a local copy of the BitcoinArmory repo and download the source files)
cd BitcoinArmory (navigates you to that folder)
git checkout 0.96.5 (picks the correct version to work off of)
git submodule update --init --recursive (sets up sub repos)

At this point you have the source and it's ready to build. In the next post ill go through the steps to setup MSVC. It will take me a bit longer, have to redo the steps myself to make sure they're right.

GBitcoinG (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 19, 2024, 04:26:05 AM
 #10

I have it installed and cloned bitcoinarmory.

Wasn't able to checkout though, even after navigating to the folder:

Quote
/c/git/bitcoinarmory (master)

$ git checkout 0.96.5

error: pathspec '0.96.5' did not match any file(s) known to git
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
April 19, 2024, 07:49:31 AM
 #11

Ah sorry, the tag is "v0.96.5"

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
April 19, 2024, 07:53:50 AM
 #12

You can go ahead, download and install MSVC community (https://visualstudio.microsoft.com/vs/features/cplusplus/). You only need the C++ compiler and features for our purposes, but if you want to play around with other languages, feel free. I'll try to build it in debug today and get back to you asap.

GBitcoinG (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 20, 2024, 09:37:23 PM
 #13

That worked.

Thank you so much!
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
April 24, 2024, 07:49:08 AM
 #14

1. Loading up the code
1.a. Start MSVC
1.b. Pick load solution and look for BitcoinArmory.sln in the cppForSwig folder
1.c. It will tell you it failed to load some projects, ignore the error
1.d. It will ask to convert the project, say yes to everything

2. Building ArmoryDB_debug.exe


2.a. Pick Debug and x64 (step 1. in the first screenshot)
2.b. Build the projects: from the Solution Explorer, right click on the relevant project then pick Build (first option in right click menu). Follow the order shown in the picture (LMBD_Win -> cryptopp -> BlockDataManager. Steps 2, 3, 4 in first screenshot). Only build these projects, ignore the others.

3. Setting your command line arguments


3.a. Right click the BlockDataManager project in the solution explorer, pick Properties (at the very bottom of the right click menu)
3.b. Set Configuration to Debug, Platform to x64 (steps 1&2 in second screenshot)
3.c. Pick Debugging in Configuration Properties list (step 3 in second screenshot)
3.d. Set your command line arguments (everything that comes after ArmoryDB.exe) in the Command Arguments field (step 4 in the second screenshot)

4. Running ArmoryDB_debug.exe


4.a. Right click the BlockDataManager project, pick Debug -> Start New Instance
4.b. This will start the ArmoryDB in debug, run through the steps (expect it to take ~20min rather than 1min). Once it fails, the debugger should catch the error and display callstack. Take a screenshot of MSVC when that happens and let me look at it.

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!