So, with the newly generated wallet including one imported address, it scans history for an hour, then DB hangs, at -30secs, with (BlockchainScanner.cpp:852) scanned from block #514744 to #515526 as the last line in dbLog.txt. I can't get a Qt connection any more after restarting Qt, no matter what wallets it has loaded. After restarting DB, Qt connects fine and loads wallets and tx instantly. With the watch-only wallet newly added, exactly the same as above. To triplecheck, after removing those wallets again, I created a fresh wallet while not connected to DB. Restarting DB and then Qt, it starts scanning history. Everything again the same, seconds before finishing it hangs DB and Qt. This time I got ever-repeating errors in Qt: (python:7717): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
-ERROR - : (BinaryData.h:563) odd hexit count
-ERROR - }: (BinaryData.h:563) odd hexit count
-ERROR - : (BinaryData.h:563) odd hexit count
-ERROR - }: (BinaryData.h:563) odd hexit count
Well, I have no clue how to go on from here? Ente |
|
|
|
I gather you're getting to load the client before it gets to that stage, right? Have you tried deleting the .lmdb mirror files? Also, consider running the wallet through the recovery tool in full mode.
I removed the two new wallets (one imported watch-only, one freshly created with one imported address), and removed all .lmdb and .lmdb-lock files. And I checked all wallets on "full recovery", no errors found.
Still same behavior.
Like, now, I only have my ages old walletsagain, and still have the "odd hexit count" errors in Qt.edit: restarting ArmoryDB, and everything works with the old wallets only. I'll check a few combinations of wallets, files, scans, and will report back.Is this a wallet problem? And/or a Qt problem? Or a DB problem? DB seems to start scanning from the beginning every time too. Ente |
|
|
|
Ah, neat!
I upgraded both ArmoryDB and ArmoryQt to 0.96.4, still the exact same messages and scanning never finishes..
Ente
I need to see the full Qt log. Is ArmoryQT --debug enough? Nothing more to see, afaik: (INFO) ArmoryQt.py:566 - Usermode: Expert
(INFO) ArmoryQt.py:1698 - Changing usermode:
(INFO) ArmoryQt.py:1699 - From: Expert
(INFO) ArmoryQt.py:1707 - To: Expert
(INFO) ArmoryQt.py:1836 - startBitcoindIfNecessary
(WARNING) ArmoryQt.py:1826 - DB is already running
(INFO) ArmoryQt.py:1924 - Setting netmode: 1
-ERROR - : (BinaryData.h:563) odd hexit count
-ERROR - : (SwigClient.cpp:61) odd hexit count
(INFO) ArmoryQt.py:1924 - Setting netmode: 0
(INFO) ArmoryQt.py:1906 - loadBlockchainIfNecessary
(INFO) ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
(INFO) ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
Cheers, Ente |
|
|
|
i also tried building from the 0.96.4 source but run into this error upon "make": user@user-VirtualBox:~/Downloads/BitcoinArmory-0.96.4$ make
Making all in cppForSwig
make[1]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Making all in lmdb
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
Making all in fcgi
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
make[2]: *** No rule to make target 'all'. Stop.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
Makefile:1538: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Makefile:413: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1 before sh autoconfigure.sh do git submodule init
git submodule update edit: oops, didn't notice the new thread page. Cheers, Ente |
|
|
|
|
Ah, neat!
I upgraded both ArmoryDB and ArmoryQt to 0.96.4, still the exact same messages and scanning never finishes..
Ente
|
|
|
|
I imported a new address in 0.96.3, scanning hangs close to finished:
Have you tried with 0.96.4? Not yet, as it's an RC. If you have no other suggestions, I'll upgrade and recheck. Ente |
|
|
|
I imported a new address in 0.96.3, scanning hangs close to finished: ArmoryDB: (BlockchainScanner.cpp:852) scanned from block #514744 to #515526 ArmoryQt: -ERROR - �Q��o: (BinaryData.h:563) odd hexit count
-ERROR - �Q��o: (SwigClient.cpp:61) odd hexit count I restarted both a few times, always the same. Around half an hour scanning, then it hangs in Qt, and wouldn't show a time estimate any more after restarting Qt. Well, first time I have a computer problem where I literally find noone with the same problem before, yay! :-) Ente |
|
|
|
..irgendwas haben wir eindeutig falsch gemacht..  Ente |
|
|
|
Ganz genau! Morgen abend trifft sich wieder der Bitcoin Themenabend, wie immer am ersten Mittwoch im Monat in der dezentrale [1]. Es gibt diesmal einen Filmabend, den konkreten Film stimmen wir pünktlich um 19:00 Uhr ab. Libre Grüße und bis morgen, Ente [1] dezentrale eV Dreilindenstraße 19 04177 Leipzig https://www.openstreetmap.org/way/41760585 |
|
|
|
|
Morgen ist es wieder so weit, wie immer 19:00 im Café Uptown.
Libre Grüße,
Ente
|
|
|
|
|
Hallo zusammen,
morgen trifft sich um 19:00 der Bitcoin Themenabend, wie jeden ersten Mittwoch im Monat in der dezentrale.
Diesmal gibts als Thema einen allgemeinen Überblick über verschiedene Skalierungsansätze zu de/zentralen digitalen Bezahlsystemen. Das ist quasi der Prequel zum letzten Themenabend zu Lightning.
Danach wird es genug Raum für Fragen und Diskussionen geben. Einiges ging ja auch schon über die Mailingliste.
Last not least müssen wir darüber reden, ob und wie wir den Bitcoin Themenabend fortführen (da sich nur wenig Leute einbringen).
Libre Grüße und bis morgen,
Ente
|
|
|
|
|
Please, people, start your own thread about tether. It's going on and on, over dozens of pages of posts now.
I am very aware of tether, its volume, dubious audits and critical voices by now. And also that there is no proof whatsoever that tether or its USD backing is foul.
Please cut it off, I want to read about stuff concerning bitfinex directly here only.
Thank you.
Ente
|
|
|
|
Wow. Is this a nasty bug, or a backdoor looking like a bug? Who introduced this? Well, I always warn to use bitcoin-branded apps, programs and linux images. It's too tempting to plant malware there, for the preselected bitcoin userbase. I wouldn't have expected that a program of the weight of bitmessage to be infected though.. So, use different hardware or virtualization, or at least hardwarewallets. Ente |
|
|
|
|
In drei Tagen, Donnerstag 15.02., treffen wir uns zum nächsten Bitcoin Stammtisch, wie immer ab 19:00 im Café Uptown.
Bis dahin,
Ente
|
|
|
|
HDD for core blockchain and armory db.
That's your culprit. Sorry, doesn't seem to be the hdd. It's a btrfs filesystem, I scrubbed it, shows zero errors. Nothing in syslog neither. Ente |
|
|
|
Does it use a SSD or a HDD?
SSD for OS and program files, HDD for core blockchain and armory db. Ente |
|
|
|
..happened twice again: -INFO - 20:54:37: (BlockchainScanner.cpp:852) scanned from block #506854 to #506855
-INFO - 20:54:41: (BlockchainScanner.cpp:857) scanned block #506856
-INFO - 20:54:42: (BlockchainScanner.cpp:857) scanned block #506857
-INFO - 20:54:43: (BlockchainScanner.cpp:857) scanned block #506858
-INFO - 20:54:45: (BlockchainScanner.cpp:857) scanned block #506859
-ERROR - 20:54:47: (BlockchainScanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 20:54:47: (BlockchainScanner.cpp:447) Has the following block files:
-ERROR - 20:54:47: (BlockchainScanner.cpp:449) --- #1162
-ERROR - 20:54:47: (BlockchainScanner.cpp:451) Was looking for id #1165
At least in this cae, it seems like my machine was offline (unrelated to armory) and went online (I have to pull the ethernet cable once in a while). That's why it found the blocks so fast. Cheers, Ente |
|
|
|
Can I ask you a few questions about your DB usage and experience in PMs?
Yes please! :-) Ente |
|
|
|
Tonight, apparently ArmoryDB crashed. This happened once before, months ago. Both times on 0.96.3. This is what I got in logs: armorydb.sh[12614]: -INFO - 03:34:40: (BlockchainScanner.cpp:852) scanned from block #504582 to #504583
armorydb.sh[12614]: -INFO - 04:06:12: (BlockchainScanner.cpp:852) scanned from block #504584 to #504586
armorydb.sh[12614]: -INFO - 04:06:31: (BlockchainScanner.cpp:857) scanned block #504587
armorydb.sh[12614]: -INFO - 04:28:58: (BlockchainScanner.cpp:857) scanned block #504588
armorydb.sh[12614]: -ERROR - 04:39:33: (BlockchainScanner.cpp:445) Missing file map for output scan, thi...xpected
armorydb.sh[12614]: -ERROR - 04:39:33: (BlockchainScanner.cpp:447) Has the following block files:
armorydb.sh[12614]: -ERROR - 04:39:33: (BlockchainScanner.cpp:449) --- #1144
armorydb.sh[12614]: -ERROR - 04:39:33: (BlockchainScanner.cpp:451) Was looking for id #1145
armorydb.sh[12614]: terminate called after throwing an instance of 'std::runtime_error'
armorydb.sh[12614]: what(): missing file map
A simple "service armorydb {stop-start}" fixed it (I had to stop it, only a start didn't suffice). It's a FIY only, it's no hassle for me, and eventually I'll update to 0.96.4 anyway. Cheers, Ente |
|
|
|
|
Show Posts
