I could send you the wallet where I tried with ( watch-only ). If that helps.
Sure, that would help.
If you feel like it, I can also SSH into the machine to try and figure out what's going on.
Topic: Bulk generation of P2SH-P2PK and later P2SH-P2WPKH addresses (Read 948 times)
Sure, that would help.
If you feel like it, I can also SSH into the machine to try and figure out what's going on.
With empty datadir ( .armory complete deleted ) armory starts up.
Importing a wallet ( not all wallets at once ) gives the same problems again.
-ERROR - 09:34:26: (DataObject.cpp:335) command checksum failure
I could send you the wallet where I tried with ( watch-only ). If that helps.
I tried so much now, the only thing what i could try next is to setup armory on another (clean) machine.
I'll try again when the bulk generation is based on the script setting for addresses.
Importing a wallet ( not all wallets at once ) gives the same problems again.
-ERROR - 09:34:26: (DataObject.cpp:335) command checksum failure
I could send you the wallet where I tried with ( watch-only ). If that helps.
I tried so much now, the only thing what i could try next is to setup armory on another (clean) machine.
I'll try again when the bulk generation is based on the script setting for addresses.
( menu entries removed from launcher ).
That has been wacky since the move to autotools but I thought I had it fixed. I do get menu items when I install on Ubuntu 16.04 and Debian Wheezy, for what it's worth.
What OS you on btw?
Ubuntu 16.04
It seems to work now.
Started up without wallets. Now moved wallets back and its scanning tx history.
The bundle seems to be broken for me also ( menu entries removed from launcher ).
Not a big issue as i use command line most time anyway :-)
What OS you on btw?
Try with the builds, see if that works.
Back to 0.94.1 for now.
Will test another day or setup another machine for testing.
Edit:
I'm testing now one more time.
I moved the complete datadir and try first startup now without wallets.
If that works i'll import the watch-only wallets and if not i can just move the datadir back and start up with 0.94-1 again.
Try with the builds, see if that works.
Its all fresh built...
Don't know how they should missmatch...
Last attempt is running now. If its failing again I'll switch back to 0.94 and try again when the bulk generation bug is fixed.
Don't know how they should missmatch...
Last attempt is running now. If its failing again I'll switch back to 0.94 and try again when the bulk generation bug is fixed.
Quote
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:45: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:45: (DataObject.cpp:335) command checksum failure
That's still the version mismatch between client and db.
Ah, that's what messing up. The parser code isn't meant to handle that many tx. Wipe the DB and bootstrap it with --db-type=DB_BARE and you won't have issues anymore. Make sure the dbdir is empty, you cannot swap db-type on existing databases.
Trying now :-)
No luck:
BDM is ready!
Segmentation fault
-INFO - 15:55:34: (BlockchainScanner.cpp:225) scanned transaction history in 1268.66s
-INFO - 15:55:37: (BlockchainScanner.cpp:665) scanned from height #472844 to #472844
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:45: (DataObject.cpp:335) command checksum failure
Quote
Several wallets loaded with estimated ~50k transactions.
Ah, that's what messing up. The parser code isn't meant to handle that many tx. Wipe the DB and bootstrap it with --db-type=DB_BARE and you won't have issues anymore. Make sure the dbdir is empty, you cannot swap db-type on existing databases.
Its scanning tx history atm. If it fails again I'll run make uninstall && make clean && make distclean and test again...
Build again and now probably stuck at pasring tx hashes.
How long should that usual take?
model name : Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
24 GB RAM
Several wallets loaded with estimated ~50k transactions.
Build again and now probably stuck at pasring tx hashes.
How long should that usual take?
model name : Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
24 GB RAM
Several wallets loaded with estimated ~50k transactions.
Do you just make after pulling? Consider cleaning up and building from scratch:
Code:
sudo make uninstall
make clean
make distclean
sh autogen.sh
./configure
make
make clean
make distclean
sh autogen.sh
./configure
make
Describe your setup.
The online version is running ( or not running ) on Ubuntu 16.04
Full node running local on the same machine.
Describe your setup.
I literally just pushed code fixing stuff with tx hash resolution when I wrote that post. Considering the db/client version mismatch, I'd recommend you go over your setup once again.
The latest pushes was used already.
I just built it again and will see if it works now.
Last attempt for now. If it doesn't work i need to go back to an older version.
Code:
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
This means your DB is up to date but your client isn't. The checksum code was added in between 0.96.0.2 and 0.96.0.3
Quote
That was including latest commits...
* branch testing -> FETCH_HEAD
Already up-to-date.
* branch testing -> FETCH_HEAD
Already up-to-date.
I literally just pushed code fixing stuff with tx hash resolution when I wrote that post. Considering the db/client version mismatch, I'd recommend you go over your setup once again.
Quote
I get lot of those entries:
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
Mistmatch between client and DB version.
Quote
Seems Armory is starting now. ( Parsing TX hashes ).
If it dies at this step, try the stuff I pushed in testing yesterday.
That was including latest commits...
* branch testing -> FETCH_HEAD
Already up-to-date.
Quote
I get lot of those entries:
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
Mistmatch between client and DB version.
Quote
Seems Armory is starting now. ( Parsing TX hashes ).
If it dies at this step, try the stuff I pushed in testing yesterday.
Post your logs. Use pastebin.
Will do when i can't solve it :-)
Edit: Seems Armory is starting now. ( Parsing TX hashes ).
DB was created with 0.96.
I recreated it with fresh build amory from the testing branch. Including your commits from 2-3 hours ago.
Edit2:
I get lot of those entries:
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
Edit3:
BDM is ready!
Segmentation fault
dblog:
-INFO - 15:59:34: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-WARN - 16:00:12: (BDM_supportClasses.cpp:1937) running 10 zc parser threads
-WARN - 16:00:12: (BDM_supportClasses.cpp:1937) running 15 zc parser threads
[...] just more parser threads messages
Post your logs. Use pastebin.
Ah, that's a bug then, will fix it.
thank you, during that i try to figure out why the latest testing keeps crashing on the online computer during start up.
Trying now again with deleted database.
Ah, that's a bug then, will fix it.
Yes that works for single generation but not for bulk generation...
Extend Address Pool generates only P2PKH addresses.
I tested that already.
Extend Address Pool generates only P2PKH addresses.
I tested that already.
You can change the default script type for receive addresses in the settings.
Will there be an easy option to bulk generate those type of addresses?
For now Bulk generation works only for P2PKH addresses.
For now Bulk generation works only for P2PKH addresses.
Jump to: