Pages:
Author

Topic: Please Help Test Armory 0.91-beta! - page 5. (Read 21313 times)

legendary
Activity: 3738
Merit: 1360
Armory Developer
April 02, 2014, 04:10:39 AM
Updated from the perfectly working .4 to .5 and it's now back to unusable. Sad

A ton of these in the log:
Code:
2014-04-02 10:17 (ERROR) -- BDM.pyc:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-02 10:17 (ERROR) -- BDM.pyc:253 -   getattr   name: getTopBlockHeight
2014-04-02 10:17 (ERROR) -- BDM.pyc:254 - BDM currently doing: Passthrough (14133058)
2014-04-02 10:17 (ERROR) -- BDM.pyc:255 - Waiting for completion: ID= 81876446
2014-04-02 10:17 (ERROR) -- BDM.pyc:256 - Direct traceback
2014-04-02 10:17 (ERROR) -- BDM.pyc:259 - Traceback:
Traceback (most recent call last):
  File "armoryengine\BDM.pyc", line 249, in passthruFunc
  File "Queue.pyc", line 176, in get

Does it happen after DB build or Tx Scan?

The 99% fix in .4 introduced a transaction ledger entry bug, and did not pass the unit tests. .5 partially fixed the ledger entry issue but still didn't pass the tests.

.6 fully fixes the ledger entry and passes the tests. Let's see if you can load with .6. It should be out today or tomorrow.

EDIT: Identified the issue. Working on it right now. I have a solution but I need to test it to make sure I'm not breaking stuff on the side.
member
Activity: 74
Merit: 10
April 02, 2014, 02:26:51 AM
Updated from the perfectly working .4 to .5 and it's now back to unusable. Sad

A ton of these in the log:
Code:
2014-04-02 10:17 (ERROR) -- BDM.pyc:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-02 10:17 (ERROR) -- BDM.pyc:253 -   getattr   name: getTopBlockHeight
2014-04-02 10:17 (ERROR) -- BDM.pyc:254 - BDM currently doing: Passthrough (14133058)
2014-04-02 10:17 (ERROR) -- BDM.pyc:255 - Waiting for completion: ID= 81876446
2014-04-02 10:17 (ERROR) -- BDM.pyc:256 - Direct traceback
2014-04-02 10:17 (ERROR) -- BDM.pyc:259 - Traceback:
Traceback (most recent call last):
  File "armoryengine\BDM.pyc", line 249, in passthruFunc
  File "Queue.pyc", line 176, in get
legendary
Activity: 3738
Merit: 1360
Armory Developer
April 01, 2014, 03:14:35 PM
I left armory open while system was in standby, after resume armory was more or less frozen (100% cpu on 2/4 cores), OS asking me to kill this process or wait a little longer.

After a restart armory was working again. I created an online transaction and entered my password. Armory was then causing high cpu load again. I left it alone. After some minutes the transaction had been created and broadcasted successfully, armory was reacting again. I clicked on the transaction to view it on blockchain.info which worked as expected.

Some minutes later, when I looked after my armory instance it was reacting very very slow (export of log file took ages).
The right corner bottom shows "Connected (False blocks)"

As next I shut it down via File->Quit which took ~3minutes to finish. After a restart Wallet Consistency Check took place. Then everything was working again, status Connected with current block number.
Switching between from tabs 'Announcements' to 'Transactions' to Dashboard was fast, but then clicking on tab Transactions again I had my next freeze. After ~1min the txs where shown, but then the right corner bottom showed "Connected (False blocks)".
Now armory doesn't react in a proper time one could think it's frozen, but actually it's very very slowly working with very high cpu load.  The tx-table's font is colored in light-gray.

I switched the wallet to display (still tab transactions), table content remains in light-gray font, but now armory reacts again until I trigger an action like Settings then it freezes again.

Here are some hopefully helpful parts of my log.
In case further info is needed let me know please and I'll provide it.

Thanks.

Sounds like your wallet carries some gigantic transactions, or a lot of them. How long does it take to open the wallet properties windows? We have a long term solution for this but it is part of some massive refactoring and overhauling on the C++ end, so it will have to wait for 0.91.1-beta

If you're willing to send us a watching only copy of your wallet, I can give it a detailed look and maybe I can catch a quick optimization to shove into this release.
full member
Activity: 147
Merit: 100
software developer
April 01, 2014, 12:28:19 PM
I left armory open while system was in standby, after resume armory was more or less frozen (100% cpu on 2/4 cores), OS asking me to kill this process or wait a little longer.

After a restart armory was working again. I created an online transaction and entered my password. Armory was then causing high cpu load again. I left it alone. After some minutes the transaction had been created and broadcasted successfully, armory was reacting again. I clicked on the transaction to view it on blockchain.info which worked as expected.

Some minutes later, when I looked after my armory instance it was reacting very very slow (export of log file took ages).
The right corner bottom shows "Connected (False blocks)"

As next I shut it down via File->Quit which took ~3minutes to finish. After a restart Wallet Consistency Check took place. Then everything was working again, status Connected with current block number.
Switching between from tabs 'Announcements' to 'Transactions' to Dashboard was fast, but then clicking on tab Transactions again I had my next freeze. After ~1min the txs where shown, but then the right corner bottom showed "Connected (False blocks)".
Now armory doesn't react in a proper time one could think it's frozen, but actually it's very very slowly working with very high cpu load.  The tx-table's font is colored in light-gray.

I switched the wallet to display (still tab transactions), table content remains in light-gray font, but now armory reacts again until I trigger an action like Settings then it freezes again.

Here are some hopefully helpful parts of my log.
In case further info is needed let me know please and I'll provide it.

Thanks.


Code:
2014-04-01 13:15 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 13:15 (ERROR) -- BDM.py:253 -   getattr   name: rescanWalletZeroConf
2014-04-01 13:15 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (91872088)
2014-04-01 13:15 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 66039631
2014-04-01 13:15 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 13:15 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:16 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5905, in Heartbeat
    LOGINFO('New Block! : %d', self.currBlockNum)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 653, in LOGINFO
    logstr = msg if len(a)==0 else (msg%a)
TypeError: %d format: a number is required, not NoneType
2014-04-01 13:16 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 13:16 (ERROR) -- BDM.py:253 -   getattr   name: rescanWalletZeroConf
2014-04-01 13:16 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (28966182)
2014-04-01 13:16 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 63705111
2014-04-01 13:16 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 13:16 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:16 (INFO) -- Networking.py:212 - Received new block.  000000000000000028c22ee6f6a61e0617b0aba7419aac0e961ab0e0a84856f4
2014-04-01 13:16 (INFO) -- Networking.py:212 - Received new block.  000000000000000028c22ee6f6a61e0617b0aba7419aac0e961ab0e0a84856f4
2014-04-01 13:16 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5905, in Heartbeat
    LOGINFO('New Block! : %d', self.currBlockNum)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 653, in LOGINFO
    logstr = msg if len(a)==0 else (msg%a)
TypeError: %d format: a number is required, not NoneType
2014-04-01 13:17 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 13:17 (ERROR) -- BDM.py:253 -   getattr   name: rescanWalletZeroConf
2014-04-01 13:17 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (42871766)
2014-04-01 13:17 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 88786028
2014-04-01 13:17 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 13:17 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:17 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5905, in Heartbeat
    LOGINFO('New Block! : %d', self.currBlockNum)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 653, in LOGINFO
    logstr = msg if len(a)==0 else (msg%a)
TypeError: %d format: a number is required, not NoneType
2014-04-01 13:17 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 13:17 (ERROR) -- BDM.py:253 -   getattr   name: rescanWalletZeroConf
2014-04-01 13:17 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (42958097)
2014-04-01 13:17 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 69702749
2014-04-01 13:17 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 13:17 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:18 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5905, in Heartbeat
    LOGINFO('New Block! : %d', self.currBlockNum)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 653, in LOGINFO
    logstr = msg if len(a)==0 else (msg%a)
TypeError: %d format: a number is required, not NoneType
2014-04-01 13:18 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 13:18 (ERROR) -- BDM.py:253 -   getattr   name: rescanWalletZeroConf
2014-04-01 13:18 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (85329011)
2014-04-01 13:18 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 35207449
2014-04-01 13:18 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 13:18 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:18 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5905, in Heartbeat
    LOGINFO('New Block! : %d', self.currBlockNum)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 653, in LOGINFO
    logstr = msg if len(a)==0 else (msg%a)
TypeError: %d format: a number is required, not NoneType
2014-04-01 13:19 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 13:19 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 13:19 (ERROR) -- BDM.py:280 - Called from: BDM.py:468 (26747591)
2014-04-01 13:19 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (78008107)
2014-04-01 13:19 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 13:19 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:19 (INFO) -- ArmoryQt.py:5905 - New Block! : 0
2014-04-01 13:19 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5909, in Heartbeat
    didAffectUs = self.newBlockSyncRescanZC(prevLedgSize)
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/ArmoryQt.py", line 5701, in newBlockSyncRescanZC
    self.walletMap[wltID].syncWithBlockchainLite()
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 308, in syncWithBlockchainLite
    startBlk = self.lastSyncBlockNum + 1
TypeError: cannot concatenate 'str' and 'int' objects
2014-04-01 13:20 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 13:20 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 13:20 (ERROR) -- BDM.py:280 - Called from: BDM.py:468 (96357853)
2014-04-01 13:20 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (62895854)
2014-04-01 13:20 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 13:20 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:20 (INFO) -- ArmoryQt.py:5905 - New Block! : 0
2014-04-01 13:20 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5909, in Heartbeat
    didAffectUs = self.newBlockSyncRescanZC(prevLedgSize)
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/ArmoryQt.py", line 5701, in newBlockSyncRescanZC
    self.walletMap[wltID].syncWithBlockchainLite()
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 308, in syncWithBlockchainLite
    startBlk = self.lastSyncBlockNum + 1
TypeError: cannot concatenate 'str' and 'int' objects
2014-04-01 13:20 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 13:20 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 13:20 (ERROR) -- BDM.py:280 - Called from: BDM.py:468 (88166405)
2014-04-01 13:20 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (13118028)
2014-04-01 13:20 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 13:20 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:20 (INFO) -- ArmoryQt.py:5905 - New Block! : 0
2014-04-01 13:20 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5909, in Heartbeat
    didAffectUs = self.newBlockSyncRescanZC(prevLedgSize)
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/ArmoryQt.py", line 5701, in newBlockSyncRescanZC
    self.walletMap[wltID].syncWithBlockchainLite()
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 308, in syncWithBlockchainLite
    startBlk = self.lastSyncBlockNum + 1
TypeError: cannot concatenate 'str' and 'int' objects
2014-04-01 13:21 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 13:21 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 13:21 (ERROR) -- BDM.py:280 - Called from: BDM.py:468 (58685391)
2014-04-01 13:21 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (2448243)
2014-04-01 13:21 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 13:21 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 13:21 (INFO) -- ArmoryQt.py:5905 - New Block! : 0
2014-04-01 13:21 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5909, in Heartbeat
    didAffectUs = self.newBlockSyncRescanZC(prevLedgSize)
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/ArmoryQt.py", line 5701, in newBlockSyncRescanZC
    self.walletMap[wltID].syncWithBlockchainLite()
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 308, in syncWithBlockchainLite
    startBlk = self.lastSyncBlockNum + 1
TypeError: cannot concatenate 'str' and 'int' objects
2014-04-01 13:22 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 13:22 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 13:22 (ERROR) -- BDM.py:280 - Called from: BDM.py:468 (71559535)
2014-04-01 13:22 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (11959664)
2014-04-01 13:22 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 13:22 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty




Code:
2014-04-01 14:50 (INFO) -- ArmoryQt.py:3193 - Sending Tx, 
2014-04-01 14:50 (INFO) -- Networking.py:278 - sendTx called...
2014-04-01 14:50 (INFO) -- ArmoryQt.py:3195 - Transaction sent to Satoshi client...!
2014-04-01 14:50 (INFO) -- ArmoryQt.py:6045 - Bitcoins Sent!
2014-04-01 14:51 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 14:51 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 14:51 (ERROR) -- BDM.py:280 - Called from: BDM.py:519 (21520582)
2014-04-01 14:51 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (21520582)
2014-04-01 14:51 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 14:51 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 14:51 (INFO) -- ArmoryQt.py:5905 - New Block! : 293574
2014-04-01 14:52 (INFO) -- ArmoryQt.py:5923 - Current block number: 293574
2014-04-01 15:08 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 15:08 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 15:08 (ERROR) -- BDM.py:280 - Called from: BDM.py:519 (9418905)
2014-04-01 15:08 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (9418905)
2014-04-01 15:08 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 15:08 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 15:08 (INFO) -- ArmoryQt.py:5905 - New Block! : 293575
2014-04-01 15:09 (INFO) -- ArmoryQt.py:5923 - Current block number: 293575
2014-04-01 15:09 (INFO) -- Networking.py:212 - Received new block.  0000000000000000b89d0c4861a21f733ea9e1a2598985efe97a861e2cb683f6
2014-04-01 15:09 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 15:09 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 15:09 (ERROR) -- BDM.py:280 - Called from: BDM.py:519 (49382616)
2014-04-01 15:09 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (49382616)
2014-04-01 15:09 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 15:09 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 15:09 (INFO) -- ArmoryQt.py:5905 - New Block! : 293576
2014-04-01 15:09 (INFO) -- ArmoryQt.py:5923 - Current block number: 293576
2014-04-01 15:11 (INFO) -- Networking.py:212 - Received new block.  0000000000000000d06382453ca46e8a83326dafc077e6562690aaf655798dda
2014-04-01 15:12 (ERROR) -- BDM.py:278 - Waiting for BDM output that didn't come after 20s.
2014-04-01 15:12 (ERROR) -- BDM.py:279 - BDM state is currently: BlockchainReady
2014-04-01 15:12 (ERROR) -- BDM.py:280 - Called from: BDM.py:519 (10040558)
2014-04-01 15:12 (ERROR) -- BDM.py:281 - BDM currently doing: UpdateWallets (10040558)
2014-04-01 15:12 (ERROR) -- BDM.py:282 - Direct traceback
2014-04-01 15:12 (ERROR) -- BDM.py:284 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 274, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 15:12 (INFO) -- ArmoryQt.py:5905 - New Block! : 293577
2014-04-01 15:12 (INFO) -- announcefetch.py:249 - Fetching: https://bitcoinarmory.com/announce.txt?ver=0.90.99.5
2014-04-01 15:12 (ERROR) -- announcefetch.py:261 - Specified URL was inaccessible
2014-04-01 15:12 (ERROR) -- announcefetch.py:262 - Tried: https://bitcoinarmory.com/announce.txt?ver=0.90.99.5
2014-04-01 15:12 (INFO) -- announcefetch.py:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.5
2014-04-01 15:12 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 15:12 (ERROR) -- BDM.py:253 -   getattr   name: scanRegisteredTxForWallet
2014-04-01 15:12 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (10040558)
2014-04-01 15:12 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 94439112
2014-04-01 15:12 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 15:12 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 15:12 (ERROR) -- BDM.py:1218 - ErrorOut var over-represented number of errors!
2014-04-01 15:12 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5917, in Heartbeat
    self.createCombinedLedger()
  File "/usr/lib/armory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "/usr/lib/armory/ArmoryQt.py", line 2721, in createCombinedLedger
    self.combinedLedger.sort(key=lambda x: currBlk-x[1].getBlockNum()+1, reverse=not sortDir)
  File "/usr/lib/armory/ArmoryQt.py", line 2721, in
    self.combinedLedger.sort(key=lambda x: currBlk-x[1].getBlockNum()+1, reverse=not sortDir)
TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'
2014-04-01 15:12 (INFO) -- ArmoryQt.py:5905 - New Block! : 0
2014-04-01 15:13 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 15:13 (ERROR) -- BDM.py:253 -   getattr   name: scanRegisteredTxForWallet
2014-04-01 15:13 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (14512736)
2014-04-01 15:13 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 72162982
2014-04-01 15:13 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 15:13 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 15:13 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 15:13 (ERROR) -- BDM.py:253 -   getattr   name: getTopBlockHeight
2014-04-01 15:13 (ERROR) -- BDM.py:254 - BDM currently doing: UpdateWallets (14512736)
2014-04-01 15:13 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 28606705
2014-04-01 15:13 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 15:13 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2014-04-01 15:13 (ERROR) -- BDM.py:1218 - ErrorOut var over-represented number of errors!
2014-04-01 15:13 (ERROR) -- BDM.py:1383 - Error processing BDM input
2014-04-01 15:13 (ERROR) -- BDM.py:1385 - Received inputTuple: Passthrough [15, 72162982, True, 'scanRegisteredTxForWallet', >, None]
2014-04-01 15:13 (ERROR) -- BDM.py:1386 - Error processing ID (72162982)
2014-04-01 15:13 (ERROR) -- BDM.py:1387 - ERROR:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 1343, in run
    output = getattr(self.bdm, funcName)(*funcArgs)
  File "/usr/lib/armory/CppBlockUtils.py", line 1877, in scanRegisteredTxForWallet
    def scanRegisteredTxForWallet(self, *args): return _CppBlockUtils.BlockDataManager_LevelDB_scanRegisteredTxForWallet(self, *args)
NotImplementedError: Wrong number of arguments for overloaded function 'BlockDataManager_LevelDB_scanRegisteredTxForWallet'.
  Possible C/C++ prototypes are:
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &)

2014-04-01 15:13 (ERROR) -- BDM.py:1383 - Error processing BDM input
2014-04-01 15:13 (ERROR) -- BDM.py:1385 - Received inputTuple: Passthrough [15, 98337933, True, 'scanRegisteredTxForWallet', >, None]
2014-04-01 15:13 (ERROR) -- BDM.py:1386 - Error processing ID (98337933)
2014-04-01 15:13 (ERROR) -- BDM.py:1387 - ERROR:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 1343, in run
    output = getattr(self.bdm, funcName)(*funcArgs)
  File "/usr/lib/armory/CppBlockUtils.py", line 1877, in scanRegisteredTxForWallet
    def scanRegisteredTxForWallet(self, *args): return _CppBlockUtils.BlockDataManager_LevelDB_scanRegisteredTxForWallet(self, *args)
NotImplementedError: Wrong number of arguments for overloaded function 'BlockDataManager_LevelDB_scanRegisteredTxForWallet'.
  Possible C/C++ prototypes are:
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &)

2014-04-01 15:13 (ERROR) -- BDM.py:1383 - Error processing BDM input
2014-04-01 15:13 (ERROR) -- BDM.py:1385 - Received inputTuple: Passthrough [15, 61270920, True, 'scanRegisteredTxForWallet', >, None]
2014-04-01 15:13 (ERROR) -- BDM.py:1386 - Error processing ID (61270920)
2014-04-01 15:13 (ERROR) -- BDM.py:1387 - ERROR:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 1343, in run
    output = getattr(self.bdm, funcName)(*funcArgs)
  File "/usr/lib/armory/CppBlockUtils.py", line 1877, in scanRegisteredTxForWallet
    def scanRegisteredTxForWallet(self, *args): return _CppBlockUtils.BlockDataManager_LevelDB_scanRegisteredTxForWallet(self, *args)
NotImplementedError: Wrong number of arguments for overloaded function 'BlockDataManager_LevelDB_scanRegisteredTxForWallet'.
  Possible C/C++ prototypes are:
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &)

2014-04-01 15:13 (ERROR) -- BDM.py:1383 - Error processing BDM input
2014-04-01 15:13 (ERROR) -- BDM.py:1385 - Received inputTuple: Passthrough [15, 36846310, True, 'scanRegisteredTxForWallet', >, None]
2014-04-01 15:13 (ERROR) -- BDM.py:1386 - Error processing ID (36846310)
2014-04-01 15:13 (ERROR) -- BDM.py:1387 - ERROR:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/BDM.py", line 1343, in run
    output = getattr(self.bdm, funcName)(*funcArgs)
  File "/usr/lib/armory/CppBlockUtils.py", line 1877, in scanRegisteredTxForWallet
    def scanRegisteredTxForWallet(self, *args): return _CppBlockUtils.BlockDataManager_LevelDB_scanRegisteredTxForWallet(self, *args)
NotImplementedError: Wrong number of arguments for overloaded function 'BlockDataManager_LevelDB_scanRegisteredTxForWallet'.
  Possible C/C++ prototypes are:
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &,uint32_t)
    scanRegisteredTxForWallet(BlockDataManager_LevelDB *,BtcWallet &)
legendary
Activity: 1190
Merit: 1001
April 01, 2014, 05:20:34 AM
I had to redownload the full blockchain but now it is working again  Grin

Thanks!

What issue were you experiencing?

96-99% analysing crash.
newbie
Activity: 5
Merit: 0
March 31, 2014, 07:55:47 PM
Yes, testing branch should be at 0.90.99.5, the same as the links in this thread.   Though, I was just thinking of merging some fixes that goatpig pushed which will be part of .6 or .7

Can you help to fix the problem:

Code:
2014-04-01 08:54 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-04-01 08:54 (ERROR) -- BDM.py:253 -   getattr   name: hasTxWithHash
2014-04-01 08:54 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (36920340)
2014-04-01 08:54 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 50642907
2014-04-01 08:54 (ERROR) -- BDM.py:256 - Direct traceback
2014-04-01 08:54 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/BDM.py", line 249, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/Users/joeschmoe/buildenv/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/Queue.py", line 176, in get
Empty
 

Keep getting it and I can't open my wallet  Cry

Thanks!
legendary
Activity: 2912
Merit: 1060
March 31, 2014, 07:40:44 PM
Requesting a simple config file for directories. Updating erases my shortcut and I use different Bitcoin and data directories.

Also Windows server not being detected. Server 2012 should be detected as windows 8.

404 https://bitcoinarmory.com/submitbug.php

Keep getting update notice http://imgur.com/vITN2tg
legendary
Activity: 2912
Merit: 1060
March 31, 2014, 07:20:43 PM
Does the latest bitcoin-qt play nice with the latest stable armory?

Yes use the newest Bitcoin core
sr. member
Activity: 252
Merit: 250
March 31, 2014, 06:06:49 PM
Does the latest bitcoin-qt play nice with the latest stable armory?
legendary
Activity: 3738
Merit: 1360
Armory Developer
March 31, 2014, 06:04:54 PM
I had to redownload the full blockchain but now it is working again  Grin

Thanks!

What issue were you experiencing?
legendary
Activity: 1190
Merit: 1001
March 31, 2014, 05:51:24 PM
I had to redownload the full blockchain but now it is working again  Grin

Thanks!
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
March 31, 2014, 03:37:58 PM
If I checkout the testing branch of your github will I get the 0.91-beta?  I don't want to install a .deb for a beta release, I'd rather put it in a separate directory and not overwrite my current version.

Yes, testing branch should be at 0.90.99.5, the same as the links in this thread.   Though, I was just thinking of merging some fixes that goatpig pushed which will be part of .6 or .7
cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
March 31, 2014, 03:34:09 PM
If I checkout the testing branch of your github will I get the 0.91-beta?  I don't want to install a .deb for a beta release, I'd rather put it in a separate directory and not overwrite my current version.
hero member
Activity: 854
Merit: 658
rgbkey.github.io/pgp.txt
March 31, 2014, 03:27:40 PM
Upon running the new version after uninstalling the last version but not deleting the appdata folder.



Next I will be restoring a wallet that I created in .90 which I just deleted once the blockchain is done downloading.
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
March 31, 2014, 01:44:55 PM
New wallets are top priority after 0.91-beta which is in testing right now.  The following version, 0.92-beta, will include the new wallet format, which includes native BIP32 support along with a ton of other things (including compressed public keys and some multisig capability).

hero member
Activity: 496
Merit: 500
March 31, 2014, 01:42:58 PM
Out of curiosity, how soon do you expect to implement BIP 32 wallets? I'd like to switch to Armory (or something else) but have tried holding out for BIP 32 support.

Pretty sure armory has BIP 32, I don't know it follows that protocol, but you only have to backup one thing that will generate all your addresses for you, which is what BIP 32 basically is.

The problem is that it is not interoperable with other BIP 32 implementations. I can't import my Armory seed into my Trezor and vice versa.

So it's not BIP 32.
legendary
Activity: 1498
Merit: 1000
March 31, 2014, 01:35:23 PM
Out of curiosity, how soon do you expect to implement BIP 32 wallets? I'd like to switch to Armory (or something else) but have tried holding out for BIP 32 support.

Pretty sure armory has BIP 32, I don't know it follows that protocol, but you only have to backup one thing that will generate all your addresses for you, which is what BIP 32 basically is.
tlr
member
Activity: 86
Merit: 10
March 31, 2014, 01:14:09 PM
Out of curiosity, how soon do you expect to implement BIP 32 wallets? I'd like to switch to Armory (or something else) but have tried holding out for BIP 32 support.
legendary
Activity: 3738
Merit: 1360
Armory Developer
March 31, 2014, 11:56:23 AM
I don't have an RPi setup that I can use for testing atm

I have an extra Pi lying around if you want it for testing.

Quote
If both wallets are loaded on the online computer, you should see two transactions.  As you said, it is two distinct events, one for each wallet, so it should show up (@goatpig:  didn't you say something about duplicate ledger entries?  did you misread this as a bug and "fix" it?)

Now that you mention it, in addition to no longer seeing an incoming and outgoing entry, I'm also seeing duplicate entires. I created one transaction from an offline to an online wallet, with multiple outputs to the online wallet. In the ledger, I'm seeing multiple entries for the full amount of the transaction, not the individual outputs.

If that doesn't make sense, let me know what I can send you.

That's the send to many issue I just fixed
hero member
Activity: 496
Merit: 500
March 31, 2014, 11:55:26 AM
I don't have an RPi setup that I can use for testing atm

I have an extra Pi lying around if you want it for testing.

Quote
If both wallets are loaded on the online computer, you should see two transactions.  As you said, it is two distinct events, one for each wallet, so it should show up (@goatpig:  didn't you say something about duplicate ledger entries?  did you misread this as a bug and "fix" it?)

Now that you mention it, in addition to no longer seeing an incoming and outgoing entry, I'm also seeing duplicate entires. I created one transaction from an offline to an online wallet, with multiple outputs to the online wallet. In the ledger, I'm seeing multiple entries for the full amount of the transaction, not the individual outputs.

If that doesn't make sense, let me know what I can send you.
Pages:
Jump to: