Armory 0.94.1 is out - page 9. | Bitcointalksearch.org

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: cypherdoc on April 12, 2016, 09:35:45 PM

well, there you go.

doubled my memory and it's working again

what clued you in? that mempool.bin error?

Actually 'std::bad_alloc' did. It's a C++ error when something fails to allocate enough memory (I had to google it though).

cypherdoc

legendary

Activity: 1764

Merit: 1002

cypherdoc

legendary

Activity: 1764

Merit: 1002

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

cypherdoc

legendary

Activity: 1764

Merit: 1002

crap, it's back!:

Code:

-Ubuntu:~/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.94.1
   Armory Build:         811798a928
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   OS Variant            : ('Ubuntu', '14.04', 'trusty')
   User home-directory   : /home/x
   Satoshi BTC directory : /home/x/.bitcoin/
   Armory home dir       : /home/x/.armory/
   ArmoryDB directory     : /home/x/.armory/databases
   Armory settings file  : /home/x/.armory/ArmorySettings.txt
   Armory log file       : /home/x/.armory/armorylog.txt
   Do wallet checking    : True
(ERROR) ArmoryQt.py:1336 - 5 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted.
-INFO  - 1460505492: (BlockUtils.cpp:924) blkfile dir: /home/x/.bitcoin/blocks
-INFO  - 1460505492: (BlockUtils.cpp:925) lmdb dir: /home/x/.armory/databases
-INFO  - 1460505492: (lmdb_wrapper.cpp:387) Opening databases...
-INFO  - 1460505492: (BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad
-INFO  - 1460505493: (DatabaseBuilder.cpp:162) Reading headers from db
-INFO  - 1460505499: (DatabaseBuilder.cpp:195) Found 407055 headers in db
-INFO  - 1460505506: (DatabaseBuilder.cpp:43) updating HEADERS db
-INFO  - 1460505508: (DatabaseBuilder.cpp:223) parsed block file #491
-DEBUG - 1460505508: (Blockchain.cpp:213) Organizing chain 
-INFO  - 1460505508: (DatabaseBuilder.cpp:47) updated HEADERS db in 1.785s
-INFO  - 1460505508: (DatabaseBuilder.cpp:98) scanning new blocks from #225967 to #407009
-INFO  - 1460505528: (BlockchainScanner.cpp:636) scanned from height #225967 to #229667
-INFO  - 1460505551: (BlockchainScanner.cpp:636) scanned from height #229668 to #232781

Code:

-INFO  - 1460506296: (BlockchainScanner.cpp:636) scanned from height #368954 to #370252
-INFO  - 1460506309: (BlockchainScanner.cpp:636) scanned from height #370253 to #371493
-INFO  - 1460506321: (BlockchainScanner.cpp:636) scanned from height #371494 to #372486
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

kyren

newbie

Activity: 51

Merit: 0

Been running 94.1 for days now.

Thanks so much! Works great!

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: Carlton Banks on April 08, 2016, 07:29:39 PM

That's even more curious. I might be wrong about it being an Armory bug then, it's hard to believe that something so deterministic has not yet happened to someone else so far. I'm stumped by this one, if the re-index doesn't work, you will need goatpig, droark or knightDk to help troubleshoot. Limited knowledge of C++ runtime errors over here.

bitcoind -reindex worked.

after a variety of issues, i just now finished it, and 0.94.1 is running.

Cassiel

newbie

Activity: 11

Merit: 0

Ah I understand now, OK thanks.

gangtraet

full member

Activity: 159

Merit: 100

Quote from: Cassiel on April 11, 2016, 04:43:36 AM

Now all this worked perfect, but I just realised that Armory never asked for my passphrase for the imported (encrypted) wallet. It just imported it and was good to go.

The encryption only encrypts the private keys. You cannot spend the coins without the password, but you can see them.

Carlton Banks

legendary

Activity: 3430

Merit: 3074

Quote from: Cassiel on April 11, 2016, 04:43:36 AM

Armory never asked for my passphrase for the imported (encrypted) wallet. It just imported it and was good to go.

Is that right?

Yes, that's expected behaviour.

Cassiel

newbie

Activity: 11

Merit: 0

Also, I just realised...

I uninstalled old v0.93 version, moved AppData\Roaming\Amory, installed latest v0.94.1. When Armory was all synced and db built, I imported my wallet from my old AppData\Roaming\Amory folder.

Now all this worked perfect, but I just realised that Armory never asked for my passphrase for the imported (encrypted) wallet. It just imported it and was good to go.

Is that right?

Cassiel

newbie

Activity: 11

Merit: 0

Small install bug...

Armory is 64bit (right?) but wants to install to C:\Program Files (x86) by default, should be C:\Program Files.

That's all!

Carlton Banks

legendary

Activity: 3430

Merit: 3074

That's even more curious. I might be wrong about it being an Armory bug then, it's hard to believe that something so deterministic has not yet happened to someone else so far. I'm stumped by this one, if the re-index doesn't work, you will need goatpig, droark or knightDk to help troubleshoot. Limited knowledge of C++ runtime errors over here.

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: Carlton Banks on April 08, 2016, 06:05:19 PM

Quote from: cypherdoc on April 08, 2016, 05:50:54 PM

Quote from: Carlton Banks on April 08, 2016, 03:23:18 PM

You can also delete the /.armory/atisignedannounce directory. Hasn't caused me any problems thus far.

ok, more trouble:

Code:

-INFO  - 1460146744: (BlockchainScanner.cpp:636) scanned from height #362309 to #363439
-INFO  - 1460146753: (BlockchainScanner.cpp:636) scanned from height #363440 to #364372
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

would that call for a bitcoind -reindex?

hmmmmm, I think that's the C++ runtime making that complaint, but possibly nothing to do with bitcoind. Try erasing the /.armory/databases folder and rebuild the databases folder from the start. If that's unsuccessful, try bitcoind -reindex, but I'm not confident that's the source of your issue.

That part of the code (tx scan) is a multi-threaded high performance wonder, but it took some lengthy debugging in it's original incarnation. It's possible you've done everyone a favour by finding an unknown bug. Keep the log files if you can, goatpig may want to see them.

happened again after outright deletion of /.armory/databases folder, this time at a different blockheight:

Code:

-INFO  - 1460155030: (BlockchainScanner.cpp:636) scanned from height #194857 to #200839
-INFO  - 1460155039: (BlockchainScanner.cpp:636) scanned from height #200840 to #206610
-INFO  - 1460155047: (BlockchainScanner.cpp:636) scanned from height #206611 to #211790
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

running bitcoind -reindex

Carlton Banks

legendary

Activity: 3430

Merit: 3074

Quote from: cypherdoc on April 08, 2016, 05:50:54 PM

Quote from: Carlton Banks on April 08, 2016, 03:23:18 PM

You can also delete the /.armory/atisignedannounce directory. Hasn't caused me any problems thus far.

ok, more trouble:

Code:

-INFO  - 1460146744: (BlockchainScanner.cpp:636) scanned from height #362309 to #363439
-INFO  - 1460146753: (BlockchainScanner.cpp:636) scanned from height #363440 to #364372
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

would that call for a bitcoind -reindex?

hmmmmm, I think that's the C++ runtime making that complaint, but possibly nothing to do with bitcoind. Try erasing the /.armory/databases folder and rebuild the databases folder from the start. If that's unsuccessful, try bitcoind -reindex, but I'm not confident that's the source of your issue.

That part of the code (tx scan) is a multi-threaded high performance wonder, but it took some lengthy debugging in it's original incarnation. It's possible you've done everyone a favour by finding an unknown bug. Keep the log files if you can, goatpig may want to see them.

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: Carlton Banks on April 08, 2016, 03:23:18 PM

You can also delete the /.armory/atisignedannounce directory. Hasn't caused me any problems thus far.

ok, more trouble:

Code:

-INFO  - 1460146744: (BlockchainScanner.cpp:636) scanned from height #362309 to #363439
-INFO  - 1460146753: (BlockchainScanner.cpp:636) scanned from height #363440 to #364372
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

would that call for a bitcoind -reindex?

edit: actually, bitcoind seems to be running normally.

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: achow101 on April 08, 2016, 03:34:18 PM

Quote from: cypherdoc on April 08, 2016, 03:27:22 PM

that's not good, is it?

It's not necessarily bad though.

Quote from: cypherdoc on April 08, 2016, 03:15:48 PM

what are these Errors at the bottom? when the gui client opens, it still says 0.93.3 and isn't updating:

Ubuntu:~/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version: 0.94.1
   Armory Build: x
   PyBtcWallet Version: 1.35
Detected Operating system: Linux
   OS Variant : ('Ubuntu', '14.04', 'trusty')
   User home-directory : /home/x
   Satoshi BTC directory : /home/x/.bitcoin/
   Armory home dir : /home/x/.armory/
   ArmoryDB directory : /home/x/.armory/databases
   Armory settings file : /home/x/.armory/ArmorySettings.txt
   Armory log file : /home/x/.armory/armorylog.txt
   Do wallet checking : True
(ERROR) ArmoryQt.py:6996 - Socket already in use. Sending CLI args to existing proc.
(ERROR) ArmoryQt.py:7000 - Exiting...

It means the the socket that armory uses is in use. This probably means you already have armory open.

yep, had 0.93.3 still open. sheesh. all good now. thks Carlton and KnightDB.

would be comforting if goatpig would git tag his source though...

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: cypherdoc on April 08, 2016, 03:27:22 PM

that's not good, is it?

It's not necessarily bad though.

Quote from: cypherdoc on April 08, 2016, 03:15:48 PM

what are these Errors at the bottom? when the gui client opens, it still says 0.93.3 and isn't updating:

Ubuntu:~/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version: 0.94.1
   Armory Build: x
   PyBtcWallet Version: 1.35
Detected Operating system: Linux
   OS Variant : ('Ubuntu', '14.04', 'trusty')
   User home-directory : /home/x
   Satoshi BTC directory : /home/x/.bitcoin/
   Armory home dir : /home/x/.armory/
   ArmoryDB directory : /home/x/.armory/databases
   Armory settings file : /home/x/.armory/ArmorySettings.txt
   Armory log file : /home/x/.armory/armorylog.txt
   Do wallet checking : True
(ERROR) ArmoryQt.py:6996 - Socket already in use. Sending CLI args to existing proc.
(ERROR) ArmoryQt.py:7000 - Exiting...

It means the the socket that armory uses is in use. This probably means you already have armory open.

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: achow101 on April 08, 2016, 03:18:35 PM

Quote from: cypherdoc on April 08, 2016, 02:32:42 PM

Quote from: Carlton Banks on April 08, 2016, 02:12:49 PM

See above! I strongly suspect that's your issue (git checkout master can only have performed that exact command; etotheipi's master branch is still on 93.3, whereas the goatpig master branch is at 94.1)

does goatpig have 0.94.1 git tagged?:

Code:

Ubuntu:~/BitcoinArmory$ git tag -v v0.94.1
error: 811798a9282d216e0a450fe342d8a4671fee01d3: cannot verify a non-tag object of type commit.
error: could not verify the tag 'v0.94.1'

It isn't signed.

that's not good, is it?

Quote from: cypherdoc on April 08, 2016, 03:15:48 PM

Quote from: Carlton Banks on April 08, 2016, 02:44:18 PM

He does. I suspect there's some minor error in the version string you're supplying, but that's only a guess. I don't make use of that particular git command, so can't help you specifically with it from off the top of my head unfortunately.

ok, got it.

now how do i delete Armory's copy of the blockchain?

Go to the armory data directory and delete everything in the "databases" folder.

what are these Errors at the bottom? when the gui client opens, it still says 0.93.3 and isn't updating:

Ubuntu:~/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version: 0.94.1
   Armory Build: x
   PyBtcWallet Version: 1.35
Detected Operating system: Linux
   OS Variant : ('Ubuntu', '14.04', 'trusty')
   User home-directory : /home/x
   Satoshi BTC directory : /home/x/.bitcoin/
   Armory home dir : /home/x/.armory/
   ArmoryDB directory : /home/x/.armory/databases
   Armory settings file : /home/x/.armory/ArmorySettings.txt
   Armory log file : /home/x/.armory/armorylog.txt
   Do wallet checking : True
(ERROR) ArmoryQt.py:6996 - Socket already in use. Sending CLI args to existing proc.
(ERROR) ArmoryQt.py:7000 - Exiting...

Topic: Armory 0.94.1 is out - page 9. (Read 11877 times)