Armory is running on Windows. It's connected via http to ArmoryDB running on an Ubuntu machine.
This Windows install does have a functioning install of Python 2.7.14
Topic: Armory 0.96.3 released - page 5. (Read 15542 times)
Quote
DbErrorMsg: >
Is your DB running? Do you have any Python in you and what OS do you use?
Quote
I'd want a confidential way of getting that to you.
You can GPG me the thing at the email of my github repo.
This is the pubkey for emails (don't use the offline signing key registered to the same email. This is for offline release signing only):
Code:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2
mQINBFXrA7sBEACyM7MpPE9+H+7YJ94kAu/JZMajOjJaWnw4pb4oiKBu2yMqQQpv
EnRG0t7Qpx/xw+/5bkvyszs9c/Rf9jnSFn7bMEjOwk+cVRIIkhtOG2p2/ZV0d8mw
v5bGTMBIxAhTDY371PzcW42aT+CNEGxeLThHuDauHWVkWxLnYlVabs3oZIBZR2y0
YtVTPSYgI5/XYEQLDze4uwpQuZsvnsCa5doCmX+iJURyUJtFTY3GW/Dx/XqWtQfu
PzRJSGZgxaO40+zOskmbjMerVSjXjEQZlMwzwjB0TR/8Zhu94f1Q98E8W4F4gRXo
X+gcLe0U+zD8rLb7lP99auEw3z8O7Nmxi9sjRN4PoeHB2isshM02j/iL+7qeKpvG
fqZg1yU3Pi4hPqictQGhEpekk/3FxuGWNX5V/PUTeqjfc0aHaYrfRG9ESW59OYnf
QOswdLzrnxyAlmX3cYWOQp4c6vsdbmCMAE4SMhGhIZL4NhxeSoOARR4eB2PNlvIs
u0dCoA6TJLUVVryp0SqnOV5UfUtxCIfyqquYiE5HUFwz418HAVWg+oPEBWp83pp7
kroDgvGF55Q58ZV9Jcx4vHLNFrlo1bVlCY7IZDdFfVJ6scAgiZGcTY+/M5skcaTo
ean9bER4QZ3F6eE+7P9j1p3dPa4Swwy5GQ89+EE3BUYH3kO3F7vXK/pDDQARAQAB
tCJKb2huIERvZSA8bW9vdGhlY293bG9yZEBnbWFpbC5jb20+iQI5BBMBAgAjBQJV
6wO7AhsjBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQIvAz3luFh6JFHw/9
FjT9r2ifgQKbVCoKUzzWGBJ6J5iUTqBClcUXg0DEXa4kCZf9zfCjVL/Cfc5vxPus
WK4f1PT/0Hr0mJBbxTz1yhiePd8zwOfoDVvc8OCPR1FgJRZSItGKl4x3KDWPan76
hrWQyRQTsJ8YLgyzFvkvXhnhsLyY4eTuE3dqlKzWL5Mez+pkvOuYkn+eK2vpC4nK
RzqnN2Okyuu0k6mbnFqxsMevu/IaK6KN9fO5MqIJSLbzqNogUMetyuuXCv80Hw5g
BwrZKQQYhSXZTDAXYBZQ5QdDkcl3ALR+qMBN4ttoQaihJpLPBfdYo2CxgAD+tBjr
/F2YOlZvCCPZFxomncFGXANOQop2h/pRjR88KhLZEYPgob4OsZbbujsZdPJmTwx1
rBvrdEj72Y8PLqtCXM7pze6NtOUbz9qwJc0CXoODHQE7n9ZIkyAp15kzGNEDuN+9
a2aavzJU8KsbRhJ4OMokN6lgsyxfwIqeAZg95dz5fSDg7mSJjBoArlo5kX5s3KDl
QyFkq7pTuVuGer7v2XxATbXt95HrIQzUP8YO0j8Z78xNbHsvwTafmWD9SEyl/Vdu
aECpvXkJ80DPnHsC7L98Dx7snrhABlFqe1hRYThN/5k0Dp7EUI4ETG336QhbmKDN
72XH0gz78x+0RzgFXN5h1wndeyV6SbRM1jpv5Jvfw3e5Ag0EVesDuwEQAMEuHi4f
OdE5dOD9Nb91ftiVrblySbHGjkWrJRgJiUo+jWLsJR1ykPoprNrsvJmbRXs7+tNl
mvDXc9Rd45qbdzpL9Qwsjvhinnw9BGzawivJ08RfrYv86QW6ABu7TJVEy1qKMuK9
Y/yhMe7+DkYn+xACL2alHefdpGYJbCIq1YbAV2hU8+bS52rr5dQyvsvv4NArqKmE
GJiVN+mXksnVtgXvYfhO5Jn/i72WVWYLKpA1JxcluVXDGC6ptn/lJERG9oZsACdU
+t043Poitcrz9jimQD/RRWk9N6X372ys4aeVuVrTl51chOkuyJec/D7PCyxN35P+
I8FSgdtCL3iDl+UdEm3IDXvr4+KXYnJgzCZu3+bV9xwVj6adHf8tOnbAM4yEwnWz
ihZLQu8RTXAGpx0KKVkyFdhdaGTLXntXmLSJSEnmhGYuNKmM9B5d3cklmQ8y9Rqs
ZI1QDD+K74RWeKYlxRDJj29Aezu+W53m5Ol3CkXkEC6ClzAV2JHcFn1kgBaZyc1+
p/XSoSgInwGB+X/aD64dxEgeEuK6uTv/sQMXnWbJLT8XlyHozUO4E23OPU3b9Ssg
keS4ZiPBNXrZPKyqHMxW1J/4HP4jI5aR18jopMO7VTyH8uIt6WYeR540LCSnFCaP
wQv8V4k+Ga3uj0ITEEjCU4IQqt4ByLj5ajkfABEBAAGJAh8EGAECAAkFAlXrA7sC
GwwACgkQIvAz3luFh6Kt5hAAqi+B8Ae1rZOP5SR/ZyjXbB42DUan/R5gmHdi7AIt
3vTKWXJQwFT6Jxy5rS22vwJVd/azi0OxdHSpasqCV45I9oq1ES3//8yOvzhb3d02
7cuh8LTN2iOQgcqjKI8MYMFzP2z7cu4CGYj1wJ2X4L8QbZXA2irzlVT2C6SJ5/Ow
zHJyBCSG3ZkRYUkuIAadK/gZ7hJaDMlkiuvoR1s2SaYm4hTeC0viTDGJFJ9+ReM3
jzEfP8wn0k/95SqFRgMv+38aem6Y1XdU4LHtBGf+3TGrjwPrw2xPmpUXX7tl+6vw
s+60wem8B/8+WCq+11ZLPRdFvqePAQVQolbEVaH8BGHTsQ/wX+L1W8myimkYF4Iq
OTf9wRnfCn/yYZYWwN1UqFsfsRoPKmcY5frIYVV/TnZn9DVfUPE5OKHvR61HglaH
E9aQONQe3u1ZGMmOnvFhFiKTvKRVQgpp4/QoQdptNscU7jB0F2VMOWsfU59u1vWo
phmWZ68P1h/0VgAtqZHcNLmqbrqIn9V9mbPc91yVWhYyoBBlUm9fgXR0pqSi+gGe
5LZTNGd4VhyfETbSAGrKJB7JblIj+dfjcCU2wE87nQAycP569h9dvTPt7huSUFIy
E0Kp1V93yAEr4+UiiheJuNNEPz0rPIDBDVfdP9JH95G2ADLbEUYQ7fxU5gTBMs4+
QdU=
=fgZn
-----END PGP PUBLIC KEY BLOCK-----
I've anonymized this log output -- let me know if you need the un-anonymized output, or if you need to see the entire logfile rather than the output from the troubled period. I'd want a confidential way of getting that to you.
https://pastebin.com/AEtpcSHM
The transaction had 3 Segwit inputs, and one Segwit output (change) and one legacy address output.
Ignore the errors at the top -- I had an issue with the flashdrive, after I realized this and used a different drive I was able to save/sign/broadcast the transaction normally. I was never able to make RBF work -- no errors or crashes, Armory just didn't do anything when I clicked on "Bump fee" on the context menu.
https://pastebin.com/AEtpcSHM
The transaction had 3 Segwit inputs, and one Segwit output (change) and one legacy address output.
Ignore the errors at the top -- I had an issue with the flashdrive, after I realized this and used a different drive I was able to save/sign/broadcast the transaction normally. I was never able to make RBF work -- no errors or crashes, Armory just didn't do anything when I clicked on "Bump fee" on the context menu.
Is it possible to RBF-bump offline transactions?
I see the "right-click to bump", but when I right-click and select "Bump Fee" nothing happens. I was hoping/expecting for an offline transaction window to create an updated unsigned transaction....
I see the "right-click to bump", but when I right-click and select "Bump Fee" nothing happens. I was hoping/expecting for an offline transaction window to create an updated unsigned transaction....
Show me your armorylog.txt
Is it possible to RBF-bump offline transactions?
I see the "right-click to bump", but when I right-click and select "Bump Fee" nothing happens. I was hoping/expecting for an offline transaction window to create an updated unsigned transaction....
I see the "right-click to bump", but when I right-click and select "Bump Fee" nothing happens. I was hoping/expecting for an offline transaction window to create an updated unsigned transaction....
Thanks gangtraet
I think the latest Bitcoin Core is incompatible with 0.96.3. You need to either downgrade Bitcoin Core or upgrade Armory to the release candidate.
Hi Goatpig,Droak,
So I moved the install to Ubuntu via VirtualBox on my Mac, now on 0.96.3. Following some issues with Armory running the Bitcoin Core I did a separate installation of BTC 0.15.*. The armory Database/s are building however the Scan Transaction history fails with the following fault in the armorycpplog.txt "Error - :(StringSockets.cpp:351) FcgiSocket:writeAndRead FcgiError: unexpected fcgi header version".
I made sure there were no armory or bitcoin processes running beforehand, I have also tried to run armory manually. The transaction history gets to about 15% or less before an issue.
I am pretty disappointed about the lack of progress to get my Wallet open :-/
Two questions please...
1. Is there anything else I can try to progress this Transaction History issue ?
2. I am getting to the stage to ask if there is any other Wallet System that could open up my existing armoury wallet.dat ?
Thank you for any advice or input
So I moved the install to Ubuntu via VirtualBox on my Mac, now on 0.96.3. Following some issues with Armory running the Bitcoin Core I did a separate installation of BTC 0.15.*. The armory Database/s are building however the Scan Transaction history fails with the following fault in the armorycpplog.txt "Error - :(StringSockets.cpp:351) FcgiSocket:writeAndRead FcgiError: unexpected fcgi header version".
I made sure there were no armory or bitcoin processes running beforehand, I have also tried to run armory manually. The transaction history gets to about 15% or less before an issue.
I am pretty disappointed about the lack of progress to get my Wallet open :-/
Two questions please...
1. Is there anything else I can try to progress this Transaction History issue ?
2. I am getting to the stage to ask if there is any other Wallet System that could open up my existing armoury wallet.dat ?
Thank you for any advice or input
Thanks. This code seems to work:
Code:
walletManager = Cpp.WalletManager('~/.armory')
wallet = PyBtcWallet().readWalletFile(w)
cppwallet = walletManager.getCppWallet(wallet.uniqueIDB58)
receive = wallet.getNextUnusedAddress()
parms = urllib.urlencode({'amount':'%1.8f'%btc, 'label':comment})
addr = cppwallet.getP2PKHAddrForIndex(receive.chainIndex)
url = "bitcoin:%s?%s" % (addr, parms)
wallet.setComment(receive.getAddr160(), fullcomment)
0.93 is over 3 years old. Update.
Hi Goatpig,
Some help please if you can !
After guidance I moved from using OSX 0.93 to Ubuntu 0.93 with a separate Bitcoin Core installation however I am getting the error message "No block in DB at height 481824" in my armorycpplog.txt file. I have cleared the Blocks file in the .armory path and have rebuilt but it always seems to fail with the advice to 'reset Databases', which I have tried. Is this a Segwit problem with the Wallet or Armoury Client, is there anyway around this please ?
Some help please if you can !
After guidance I moved from using OSX 0.93 to Ubuntu 0.93 with a separate Bitcoin Core installation however I am getting the error message "No block in DB at height 481824" in my armorycpplog.txt file. I have cleared the Blocks file in the .armory path and have rebuilt but it always seems to fail with the advice to 'reset Databases', which I have tried. Is this a Segwit problem with the Wallet or Armoury Client, is there anyway around this please ?
I am using Armory 0.96.0 with bitcoin core 0.14.2. I have been advised to update to the latest version of Armory which I assume is 0.96.3.
I have 2 questions:
1. Can I just install Armory 0.96.3 straight over 0.96.0 (I'm using windows x64 installer) or do I need to totally remove 0.960 and do a clean install of 0.96.3?
2. Do I need to update bitcoin core or can I stay with my existing version 0.14.2
I have 2 questions:
1. Can I just install Armory 0.96.3 straight over 0.96.0 (I'm using windows x64 installer) or do I need to totally remove 0.960 and do a clean install of 0.96.3?
2. Do I need to update bitcoin core or can I stay with my existing version 0.14.2
I am trying to get the next address from a watchonly (offline) wallet. I have:
How do I associate the correct .lmdb mirror wallet with a specific .wallet file?
Code:
ls -1 .armory/*wal*
.armory/armory_2JkNrCxmd_backup.wallet
.armory/armory_2JkNrCxmd_.wallet
.armory/armory_2MhR27GuV_wallet.lmdb
.armory/armory_2MhR27GuV_wallet.lmdb-lock
.armory/armory_mwFUHedu_.watchonly_backup.wallet
.armory/armory_mwFUHedu_.watchonly.wallet
.armory/armory_wfeRswio_wallet.lmdb
.armory/armory_wfeRswio_wallet.lmdb-lock
How do I associate the correct .lmdb mirror wallet with a specific .wallet file?
You can't do it like this anymore, you need to load the cpp mirror wallet as well.
I have a python script that generates a receiving address for an invoice.
Recently (0.96.x ??) that fails in getAddrStr(). Is there a replacement function? I presume this is a side effect of the multiple address formats, segwit stuff.
Code:
wallet = PyBtcWallet().readWalletFile(w)
receive = wallet.getNextUnusedAddress()
parms = urllib.urlencode({'amount':'%1.8f'%btc, 'label':comment})
url = "bitcoin:%s?%s" % (receive.getAddrStr(), parms)
wallet.setComment(receive.getAddr160(), fullcomment)
Recently (0.96.x ??) that fails in getAddrStr(). Is there a replacement function? I presume this is a side effect of the multiple address formats, segwit stuff.
Will look into it.
Oops, of course you are right, my armorydb service stopped..
Thanks, now I know how that looks like too! :-)
Thanks, now I know how that looks like too! :-)
Did it crash or did you stop it on your own?
I didn't stop it at least. Didn't even log into that remote machine for some time.
I checked with 'service armorydb status', did look all ok. Stopped/started nevertheless, and it worked again.
I'm unsure if it was really crashed or something else was hanging. I can try to dig up the old system logs if you want.
I'm still on "months and months of bitcoind & armorydb running with no issues whatsoever" in my counting :-)
Ente
Well, by chance I found the problem why armorydb wasn't running some weeks ago:
Quote
Out of memory: Kill process 13329 (ArmoryDB) score 864 or sacrifice child
Killed process 13329 (ArmoryDB) total-vm:11996956kB, anon-rss:6895508kB, file-rss:0kB
That means 6.6 gigs used? 8 GB memory installed, no swap configured.Killed process 13329 (ArmoryDB) total-vm:11996956kB, anon-rss:6895508kB, file-rss:0kB
Right now it chucks away at a more modest
Quote
VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5603608 537828 7584 S 1.3 6.7 21:58.85 ArmoryDB
5603608 537828 7584 S 1.3 6.7 21:58.85 ArmoryDB
Cheers,
Ente
Oops, of course you are right, my armorydb service stopped..
Thanks, now I know how that looks like too! :-)
Thanks, now I know how that looks like too! :-)
Did it crash or did you stop it on your own?
I didn't stop it at least. Didn't even log into that remote machine for some time.
I checked with 'service armorydb status', did look all ok. Stopped/started nevertheless, and it worked again.
I'm unsure if it was really crashed or something else was hanging. I can try to dig up the old system logs if you want.
I'm still on "months and months of bitcoind & armorydb running with no issues whatsoever" in my counting :-)
Ente
Jump to: