Bitcoin Forum
December 05, 2016, 08:40:09 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 [169] 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 ... 232 »
  Print  
Author Topic: Armory - Discussion Thread  (Read 481840 times)
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 18, 2014, 05:47:04 PM
 #3361

My guess is that it's looking for a header pointer on a zero-confirmation tx.  It doesn't find it, and then the error somehow leads to crashing the readBlkFileUpdate() loop.  We may need to examine how the loop is handling zero-confirmation transaction and make sure there's not any crashing there.




Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
1480927209
Hero Member
*
Offline Offline

Posts: 1480927209

View Profile Personal Message (Offline)

Ignore
1480927209
Reply with quote  #2

1480927209
Report to moderator
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480927209
Hero Member
*
Offline Offline

Posts: 1480927209

View Profile Personal Message (Offline)

Ignore
1480927209
Reply with quote  #2

1480927209
Report to moderator
1480927209
Hero Member
*
Offline Offline

Posts: 1480927209

View Profile Personal Message (Offline)

Ignore
1480927209
Reply with quote  #2

1480927209
Report to moderator
1480927209
Hero Member
*
Offline Offline

Posts: 1480927209

View Profile Personal Message (Offline)

Ignore
1480927209
Reply with quote  #2

1480927209
Report to moderator
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 18, 2014, 07:01:35 PM
 #3362

Wallet import still crashes Armory on .91 dev branch.

OK, still having the same problem with the new dev branch. Imported wallet after complete sync, application becomes so slow it's hard to tell if it's crashed. Crash occurs at or near the end of transaction history scan. Message in lower right corner says Connected (False Blocks). After restarting, Armory crashes at 99% transaction history scans and message in lower right corner says Connected (0 Blocks). After about 5 minutes it seems to complete, lower right corner now looks normal Connected (29XXX Blocks). A few minutes later the message returns too Connected (False Blocks).

Basically, no different experience than 0.90 version. Although a blank "Factory Reset" window just popped up. Not sure what that's about!

Quote
2014-03-18 12:30 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 2724, in execDlgWalletDetails
    dialog = DlgWalletDetails(wlt, self.usermode, self, self)
  File "/home/***/BitcoinArmory/qtdialogs.py", line 1308, in __init__
    spendFunds = self.wlt.getBalance('Spendable')
  File "/home/***/BitcoinArmory/armoryengine/PyBtcWallet.py", line 392, in getBalance
    return self.cppWallet.getSpendableBalance(currBlk, IGNOREZC)
  File "/home/***/BitcoinArmory/CppBlockUtils.py", line 1710, in getSpendableBalance
    def getSpendableBalance(self, currBlk=0, ignoreAllZeroConf=False): return _CppBlockUtils.BtcWallet_getSpendableBalance(self, currBlk, ignoreAllZeroConf)
NotImplementedError: Wrong number or type of arguments for overloaded function 'BtcWallet_getSpendableBalance'.
  Possible C/C++ prototypes are:
    BtcWallet::getSpendableBalance(uint32_t,bool)
    BtcWallet::getSpendableBalance(uint32_t)
    BtcWallet::getSpendableBalance()


2014-03-18 12:30 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-03-18 12:30 (ERROR) -- BDM.py:253 -   getattr   name: getTopBlockHeight
2014-03-18 12:30 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (94873642)
2014-03-18 12:30 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 22657427
2014-03-18 12:30 (ERROR) -- BDM.py:256 - Direct traceback
2014-03-18 12:30 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/home/***/BitcoinArmory/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-03-18 12:30 (ERROR) -- BDM.py:1218 - ErrorOut var over-represented number of errors!
2014-03-18 12:30 (INFO) -- ArmoryQt.py:5391 - Dashboard switched to fully-online mode
2014-03-18 12:30 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-18 12:30 (INFO) -- ArmoryQt.py:4654 - Switching Armory functional mode to "Online"
2014-03-18 12:30 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-18 12:30 (INFO) -- ArmoryQt.py:2398 - Syncing wallet: ***
2014-03-18 12:30 (INFO) -- ArmoryQt.py:2408 - Current block number: 0
2014-03-18 12:30 (INFO) -- SDM.py:198 - Torrent:  / Seeds: 0 / Peers: 0
2014-03-18 12:30 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-03-18 12:30 (ERROR) -- BDM.py:253 -   getattr   name: getTopBlockHeader
2014-03-18 12:30 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (55769831)
2014-03-18 12:30 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 36071649
2014-03-18 12:30 (ERROR) -- BDM.py:256 - Direct traceback
2014-03-18 12:30 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/home/***/BitcoinArmory/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-03-18 12:30 (ERROR) -- ArmoryQt.py:5718 - Error in heartbeat function
Traceback (most recent call last):
  File "ArmoryQt.py", line 5621, in Heartbeat
    self.finishLoadBlockchain()
  File "/home/***/BitcoinArmory/armoryengine/Timer.py", line 99, in inner
    ret = func(*args, **kwargs)
  File "ArmoryQt.py", line 2413, in finishLoadBlockchain
    self.blkReceived = TheBDM.getTopBlockHeader().getTimestamp()
AttributeError: 'NoneType' object has no attribute 'getTimestamp'
2014-03-18 12:31 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-03-18 12:31 (ERROR) -- BDM.py:253 -   getattr   name: hasTxWithHash
2014-03-18 12:31 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (55769831)
2014-03-18 12:31 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 86350101
2014-03-18 12:31 (ERROR) -- BDM.py:256 - Direct traceback
2014-03-18 12:31 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/home/***/BitcoinArmory/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-03-18 12:31 (ERROR) -- BDM.py:1218 - ErrorOut var over-represented number of errors!
2014-03-18 12:31 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-03-18 12:31 (ERROR) -- BDM.py:253 -   getattr   name: hasTxWithHash
2014-03-18 12:31 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (48095612)
2014-03-18 12:31 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 10895388
2014-03-18 12:31 (ERROR) -- BDM.py:256 - Direct traceback
2014-03-18 12:31 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/home/***/BitcoinArmory/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-03-18 12:32 (INFO) -- SDM.py:198 - Torrent:  / Seeds: 0 / Peers: 0
2014-03-18 12:32 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-03-18 12:32 (ERROR) -- BDM.py:253 -   getattr   name: hasTxWithHash
2014-03-18 12:32 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (48095612)
2014-03-18 12:32 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 19321835
2014-03-18 12:32 (ERROR) -- BDM.py:256 - Direct traceback
2014-03-18 12:32 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/home/***/BitcoinArmory/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
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 18, 2014, 07:07:57 PM
 #3363

Wallet import still crashes Armory on .91 dev branch.

OK, still having the same problem with the new dev branch. Imported wallet after complete sync, application becomes so slow it's hard to tell if it's crashed. Crash occurs at or near the end of transaction history scan. Message in lower right corner says Connected (False Blocks). After restarting, Armory crashes at 99% transaction history scans and message in lower right corner says Connected (0 Blocks). After about 5 minutes it seems to complete, lower right corner now looks normal Connected (29XXX Blocks). A few minutes later the message returns too Connected (False Blocks).

Basically, no different experience than 0.90 version. Although a blank "Factory Reset" window just popped up. Not sure what that's about!


I believe the getSpendableBalance errors are a symptom of the problem, not the problem itself.    Rather, the problem already happened before it got to that line. 

Actually... looking at the errors makes me think that you're still using the old C++ utilities.  Like you didn't recompile the C++ code after checking out the latest version.  I see

Code:
Possible C/C++ prototypes are:
   BtcWallet::getSpendableBalance(uint32_t,bool)
   BtcWallet::getSpendableBalance(uint32_t)
   BtcWallet::getSpendableBalance()

Those prototypes did change in the latest version and now have a second argument.  Try doing a make clean and make and try agian.


Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 18, 2014, 07:36:45 PM
 #3364

No luck, same issues.

Here is the first error message in the log file (other than using dev warning), the rest of the log is just repeated BDM errors. Also, the wallet consistency check finds no errors. After a while, the lower right corner always returns to the false blocks message.

EDIT:
Oh, the getspendable errors are still there, just down the list from the initial BDM errors. (NVM, deleted old log.)

Quote
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- ArmoryQt.py:5391 - Dashboard switched to fully-online mode
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4654 - Switching Armory functional mode to "Online"
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-18 13:29 (INFO) -- ArmoryQt.py:5391 - Dashboard switched to fully-online mode
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4654 - Switching Armory functional mode to "Online"
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-18 13:29 (INFO) -- ArmoryQt.py:2398 - Syncing wallet: *****
2014-03-18 13:29 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-03-18 13:29 (ERROR) -- BDM.py:253 -   getattr   name: scanRegisteredTxForWallet
2014-03-18 13:29 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (22290098)
2014-03-18 13:29 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 22290098
2014-03-18 13:29 (ERROR) -- BDM.py:256 - Direct traceback
2014-03-18 13:29 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/home/***/BitcoinArmory/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
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 18, 2014, 07:39:11 PM
 #3365

No luck, same issues.

Here is the first error message in the log file (other than using dev warning), the rest of the log is just repeated BDM errors. Also, the wallet consistency check finds no errors. After a while, the lower right corner always returns to the false blocks message.

Quote
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- BDM.py:384 - Reading blockchain, pct complete: 99.9
2014-03-18 13:29 (INFO) -- ArmoryQt.py:5391 - Dashboard switched to fully-online mode
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4654 - Switching Armory functional mode to "Online"
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-18 13:29 (INFO) -- ArmoryQt.py:5391 - Dashboard switched to fully-online mode
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4654 - Switching Armory functional mode to "Online"
2014-03-18 13:29 (INFO) -- ArmoryQt.py:4712 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-18 13:29 (INFO) -- ArmoryQt.py:2398 - Syncing wallet: *****
2014-03-18 13:29 (ERROR) -- BDM.py:252 - BDM was not ready for your request!  Waited 20 sec.
2014-03-18 13:29 (ERROR) -- BDM.py:253 -   getattr   name: scanRegisteredTxForWallet
2014-03-18 13:29 (ERROR) -- BDM.py:254 - BDM currently doing: Passthrough (22290098)
2014-03-18 13:29 (ERROR) -- BDM.py:255 - Waiting for completion: ID= 22290098
2014-03-18 13:29 (ERROR) -- BDM.py:256 - Direct traceback
2014-03-18 13:29 (ERROR) -- BDM.py:259 - Traceback:
Traceback (most recent call last):
  File "/home/***/BitcoinArmory/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

Does your wallet have lots of transactions with tons of inputs and outputs?  For instance, we noted huge lagging when we loaded a wallet that had 100 transactions, each of which had 1,000+ outputs (even though only one output was related to the user's wallet).

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 18, 2014, 07:48:29 PM
 #3366


Does your wallet have lots of transactions with tons of inputs and outputs?  For instance, we noted huge lagging when we loaded a wallet that had 100 transactions, each of which had 1,000+ outputs (even though only one output was related to the user's wallet).

I would guess maybe a dozen addresses, maybe 60 incoming transactions, and maybe a dozen outbound transactions.

A very similar wallet loads fine. The only major difference between the two is that the one that does not crash only has one outbound transaction.
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 18, 2014, 08:57:17 PM
 #3367


Does your wallet have lots of transactions with tons of inputs and outputs?  For instance, we noted huge lagging when we loaded a wallet that had 100 transactions, each of which had 1,000+ outputs (even though only one output was related to the user's wallet).

I would guess maybe a dozen addresses, maybe 60 incoming transactions, and maybe a dozen outbound transactions.

A very similar wallet loads fine. The only major difference between the two is that the one that does not crash only has one outbound transaction.

Just in case it has to do with the wallet itself, can you try making a backup of it, then use the menu item "Wallets"->"Recover Damaged Wallet".  Do a full recovery.  Then try it agian (you can do it from offline mode, then restart Armory).

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 18, 2014, 09:53:03 PM
 #3368


Does your wallet have lots of transactions with tons of inputs and outputs?  For instance, we noted huge lagging when we loaded a wallet that had 100 transactions, each of which had 1,000+ outputs (even though only one output was related to the user's wallet).

I would guess maybe a dozen addresses, maybe 60 incoming transactions, and maybe a dozen outbound transactions.

A very similar wallet loads fine. The only major difference between the two is that the one that does not crash only has one outbound transaction.

Just in case it has to do with the wallet itself, can you try making a backup of it, then use the menu item "Wallets"->"Recover Damaged Wallet".  Do a full recovery.  Then try it agian (you can do it from offline mode, then restart Armory).

0 errors where found (sic)
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 18, 2014, 10:12:28 PM
 #3369


Does your wallet have lots of transactions with tons of inputs and outputs?  For instance, we noted huge lagging when we loaded a wallet that had 100 transactions, each of which had 1,000+ outputs (even though only one output was related to the user's wallet).

I would guess maybe a dozen addresses, maybe 60 incoming transactions, and maybe a dozen outbound transactions.

A very similar wallet loads fine. The only major difference between the two is that the one that does not crash only has one outbound transaction.

Just in case it has to do with the wallet itself, can you try making a backup of it, then use the menu item "Wallets"->"Recover Damaged Wallet".  Do a full recovery.  Then try it agian (you can do it from offline mode, then restart Armory).

0 errors where found (sic)

Interesting. I tried making an unencrypted backup and Armory crashed with the following error...
Quote
terminate called after throwing an instance of 'CryptoPP::InvalidKeyLength'
  what():  AES/CFB: 0 is not a valid key length
Aborted

I then tried running a recovery on the decrypted version and it said 999 errors...

Quote
Recovering wallet armory_***_decrypt.wallet (ID: ***) on Tue Mar 18 16:02:45 2014
Using full recovery mode
Wallet contains private keys and uses encryptionThe wallet file is 260107 bytes, of which 260107 bytes were read
1000 chain addresses, 999 imported keys and 0 comments were found
Found 1000 chained address entries
No byte errors were found in the wallet file
The following 999 addresses were not arranged sequentially in the wallet file:

 <snip>

There are no gaps in the address chain
No chained address fork was found
No chaincode corruption was found
All chained public keys are valid EC points
No chained public key is missing
All entries were saved under their matching hashVal
All chained public keys match their respective private keys
Found 999 imported address entries
No errors were found within the imported address entries
999 errors where found
Recovery done

I then backed up the wallet again (encrypted) and performed a recovery and got 998 errors...

Quote
Recovering wallet armory_***_encrypt.wallet (ID: ***) on Tue Mar 18 16:08:11 2014
Using full recovery mode
Wallet contains private keys and uses encryptionThe wallet file is 260107 bytes, of which 260107 bytes were read
1000 chain addresses, 999 imported keys and 0 comments were found
Found 1000 chained address entries
No byte errors were found in the wallet file
The following 998 addresses were not arranged sequentially in the wallet file:

   <snip>

There are no gaps in the address chain
No chained address fork was found
No chaincode corruption was found
All chained public keys are valid EC points
No chained public key is missing
All entries were saved under their matching hashVal
All chained public keys match their respective private keys
Found 999 imported address entries
No errors were found within the imported address entries
998 errors where found
Recovery done

The initial recovery that found zero errors was done in online mode, the next two done offline.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1316

Armory Developer


View Profile
March 18, 2014, 10:45:49 PM
 #3370

Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?

btcarmory.com
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 18, 2014, 10:56:50 PM
 #3371

Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?

After/During the creation of the file. I was watching as the progress bar moved to about 50%, then switched away for another task. When I returned the only thing open was the terminal window. That error was the last thing in the terminal window when Armory crashed and returned me to a prompt.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1316

Armory Developer


View Profile
March 18, 2014, 11:27:49 PM
 #3372

Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?

After/During the creation of the file. I was watching as the progress bar moved to about 50%, then switched away for another task. When I returned the only thing open was the terminal window. That error was the last thing in the terminal window when Armory crashed and returned me to a prompt.

Then it probably happened at the end. Was the process particularly long? Like over a minute?

Quote
Connected (29XXX Blocks)


Did you forget a X or are you showing only 29k blocks?

getSpendable errors are also just a symptom of a locked up BDM. Definitely the wallet. Consider sending us the watching only, it would make this whole process entirely faster, and I could push the fix with the next release.

btcarmory.com
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 18, 2014, 11:43:27 PM
 #3373

Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?

After/During the creation of the file. I was watching as the progress bar moved to about 50%, then switched away for another task. When I returned the only thing open was the terminal window. That error was the last thing in the terminal window when Armory crashed and returned me to a prompt.

Then it probably happened at the end. Was the process particularly long? Like over a minute?

Quote
Connected (29XXX Blocks)


Did you forget a X or are you showing only 29k blocks?

getSpendable errors are also just a symptom of a locked up BDM. Definitely the wallet. Consider sending us the watching only, it would make this whole process entirely faster, and I could push the fix with the next release.

I would guess about 30 seconds, and yes, left off an X. With no wallets, showing 291229 right now.
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 19, 2014, 03:51:26 AM
 #3374

OK, frustrated to the point where I'm ready to create a new wallet. I'm trying to sweep in the BTC from the old wallet, and it is not working. Here's what I'm doing, please tell me if I'm missing something...

1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes

Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).

Thoughts?
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1316

Armory Developer


View Profile
March 19, 2014, 03:54:09 AM
 #3375

OK, frustrated to the point where I'm ready to create a new wallet. I'm trying to sweep in the BTC from the old wallet, and it is not working. Here's what I'm doing, please tell me if I'm missing something...

1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes

Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).

Thoughts?

To sweep, Armory needs to know the available UTXO for the private key. To do that it goes through the same scanning process as if these private keys were loaded with your old wallet. This method will not help you.

btcarmory.com
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 19, 2014, 03:55:40 AM
 #3376

We literally just fixed a bug in the sweep code, like 2 hours ago.  Pull 0.91-dev and try again.

I'm not convinced this won't work.  If anything it will help debug the problem.  This will probably work for some of the keys, and maybe one in particular it will fail. 

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 19, 2014, 04:02:05 AM
 #3377

OK, frustrated to the point where I'm ready to create a new wallet. I'm trying to sweep in the BTC from the old wallet, and it is not working. Here's what I'm doing, please tell me if I'm missing something...

1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes

Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).

Thoughts?

To sweep, Armory needs to know the available UTXO for the private key. To do that it goes through the same scanning process as if these private keys were loaded with your old wallet. This method will not help you.

Wonderful. So what method helps me recover the BTC in a 1.35c paper backup?
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 19, 2014, 04:04:02 AM
 #3378

We literally just fixed a bug in the sweep code, like 2 hours ago.  Pull 0.91-dev and try again.

I'm not convinced this won't work.  If anything it will help debug the problem.  This will probably work for some of the keys, and maybe one in particular it will fail.  

Will give it a shot.

Making. Should I redownload the blockchain as well?
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 19, 2014, 04:11:29 AM
 #3379

We literally just fixed a bug in the sweep code, like 2 hours ago.  Pull 0.91-dev and try again.

I'm not convinced this won't work.  If anything it will help debug the problem.  This will probably work for some of the keys, and maybe one in particular it will fail.  

Will give it a shot.

Making. Should I redownload the blockchain as well?

Nope.  Just pull the latest 0.91 and try sweeping again

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Zoella
Full Member
***
Offline Offline

Activity: 168


View Profile
March 19, 2014, 05:11:00 AM
 #3380

Well it sort of worked on one address. For some reason it left .04 BTC?

I received an invalid transaction error, but it seems to have worked (except for the .04 BTC). Thoughts before I try it on other addresses or retry on this one for the remainder?

https://blockchain.info/address/1JaZiwrMyfYXiNuAdq6cBknJHtQAQFCxUg
Pages: « 1 ... 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 [169] 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 ... 232 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!