Bitcoin Forum
June 16, 2024, 10:08:46 AM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 [2] 3 4 5 6 7 8 9 10 11 12 »
21  Bitcoin / Armory / Re: Armory 0.96 is out on: May 07, 2017, 08:36:52 PM
Code:
2017-05-07 22:31 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-07 22:31 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-07 22:31 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\Ben\\AppData\\Roaming\\Bitcoin\\', '-dbcache=2000']
2017-05-07 22:31 (INFO) -- SDM.pyc:443 - PID of bitcoind: 4316
2017-05-07 22:31 (INFO) -- SDM.pyc:444 - PID of armory:   6476
2017-05-07 22:31 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '6476', '4316']
2017-05-07 22:31 (WARNING) -- ArmoryQt.py:1804 - DB is already running
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-07 22:31 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-07 22:31 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-07 22:32 (ERROR) -- qtdialogs.pyc:5840 - Error showing TxOut
Traceback (most recent call last):
  File "qtdialogs.pyc", line 5838, in showTxOutDialog
  File "qtdialogs.pyc", line 6069, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-07 22:33 (ERROR) -- qtdialogs.pyc:5840 - Error showing TxOut
Traceback (most recent call last):
  File "qtdialogs.pyc", line 5838, in showTxOutDialog
  File "qtdialogs.pyc", line 6069, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-07 22:33 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3490, in clickReceiveCoins
  File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'ArmoryMainWindow' object has no attribute 'Warning'


I think this was added when I tried the other method:

Code:
2017-05-07 22:36 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 1541, in getNewAddress
  File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'DlgWalletDetails' object has no attribute 'Warning'
22  Bitcoin / Armory / Re: Armory 0.96 is out on: May 07, 2017, 06:37:02 PM
Post armorylog.txt

Will do as soon as I get it back up. I computed an additional 100 addresses for one wallet and now it is always stuck at 99% of rescan of TX history with ArmoryDB has stopped working error. so I deleted the whole DB and am currently building with:
Code:
thread-count=1
db-type=DB_BARE

Will report back.
23  Bitcoin / Armory / Re: Armory 0.96 is out on: May 06, 2017, 09:45:11 PM
Ma Armory synchronizes fine. However if I choose "receive" and then the respective wallet I get a small loading window which just doesn't resolve into anything and just stays there:



When I double click on the wallet and press receive in the wallet view it just doesn't react to the button. Other UI elements work fine.

Win64 0.96

Needless to say that the watch only wallet is configures as my own with security offline.

I had this already on the testing release. Never wanted to receive at times so I don't know if with both which I have tried.
24  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 25, 2017, 10:20:28 PM
Actually it's this one, just checked:

http://www.computershopper.com/desktops/reviews/hp-compaq-8000f-elite-ultra-slim-desktop-pc
25  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 25, 2017, 07:29:11 AM
I think it is this one, will have to double check.

Prozessor
Typ   Intel Core i5
Modell   i5-2400s
Grundtaktfrequenz   2.5 GHz
Sockel total/frei   1 / 1

Pretty sure it's this PC:

https://support.hp.com/us-en/product/hp-compaq-8200-elite-ultra-slim-pc/5037958/manuals

26  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 24, 2017, 07:34:23 PM
armory_0.95.99.3-testing-gcc4.7_amd64

Code:
armory --offline
(ERROR) ArmoryUtils.py:1232 - Error getting system details:
Traceback (most recent call last):
  File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1230, in <module>
    SystemSpecs = GetSystemDetails()
  File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1225, in GetSystemDetails
    out.HddAvailB = getHddSize(BTC_HOME_DIR)    / (1024**3)
  File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1222, in getHddSize
    s = os.statvfs(adir)
OSError: [Errno 2] No such file or directory: '/home/node/.bitcoin/'
(ERROR) ArmoryUtils.py:1233 - Skipping.
(ERROR) ArmoryUtils.py:3743 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
Illegal instruction (core dumped)
27  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 24, 2017, 06:28:18 AM
Can you try the .3 gcc4.7 deb on a Ubuntu machine?

So you mean test the .deb? Or build from source?

I will have to flatten and set up my old offline PC and install Ubuntu to make it my online machine again. I will try this in the next few days. I will then use this low ram option to build the DB.
28  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 23, 2017, 09:06:42 PM
Wonderful, that worked now. Thank you so much!   Kiss

What worked? The .deb, the txsigcollect, or both?

Installed testing version 3 over the top of testing version 2 on the win 7 x64 online machine. Now it creates unsigned tx which can be recognized by the offline testing version 2 on the Ubuntu x64. Sent a transaction went all good.
29  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 23, 2017, 12:28:04 PM
Wonderful, that worked now. Thank you so much!   Kiss
30  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 23, 2017, 11:23:14 AM
3rd testing build has the fix for the txsigcollet issue. I was assuming you were using that.

You can get the gcc4.7 build in the usual place:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.95.99.3-testing

Just checked again. Testing build 2 on both systems. Can you ELI5 gcc4.7? Where should I install this? On both systems or on my online system only?

What about the terminal output I posted above? It seems to not be able to recognize certain parts of the TX as it states it's no legal ASCI or so.
31  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 23, 2017, 09:33:24 AM
1) What is the signer's version?

2) The .deb packages work, I got no idea what kind of Ubuntu you are using that it can't get them to run. Try the gcc4.7 I made just in case you are using some weird distro.

1. Where do I find it?

2. Armory is running fine in offline mode on Ubuntu. It was the one built from source as you instructed me to do (0.95.99.2 on both systems). Testing branch. gcc4.7???

I assume versions should be compatible as the are the same testing version.

I am seriously considering importing the encrypted wallets to my online system and moving to another wallet. However, I love armory for its M/N backups and of course I would have to re-setup backup schedules for me and some other people that I manage their wallets for.
32  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 23, 2017, 06:59:10 AM
Oh boy, just realized I am still on 0.91 on my offline win 32 PC. Can't sign the transaction as the format changed. I was under the impression I was on 0.93 or something.

I was just thinking about installing Ubuntu on that machine and creating the Offline PC from scratch. However, this will be the same HW as the online Ubuntu PC so I fear that I cant't install from .deb and installing all the dependencies to build from source will be a major pain without plugging it into the network.

I'll probably try to find a Win x64 installation disk somehow and try it that way.

Any other ideas?

Edit: What if I downgrade my bitcoin node to 0.13 and use 0.96 Armory? Kind of don't want to change a running system since I just got it all online.

Edit2: Or I use the last 0.95 deb and hope it will work that way?

Edit3: I now disconnected my Ubuntu PC from the network and have set it up as offline machine. Now the next problem haunts me: It tells me my unsigned transaction I want to sign is unrecognized. Tried to export it as unsigned tx file and as text only. It tells me it is unrecognized. Could there be a problem with the language settings.

Edit4: Just tried it from a different wallet and it also tells me unrecognized. Both versions of Armory are the newest testing build. The log just tells me the file was loaded. why it was unrecognized it doesn't tell me.

Edit5: My online wallet can successfully import the unsigned TX and recognizes everything as expected. It must be some kind of language, date format or ASCI Table problem. Any advice mostly appreciated.

Terminal Output:

Code:
Traceback (most recent call last):
  File "/usr/local/bin/../lib/armory/ArmoryQt.py", line 646, in <lambda>
    execAbout   = lambda: DlgHelpAbout(self).exec_()
  File "/usr/local/lib/armory/qtdialogs.py", line 8228, in __init__
    lblHead = QRichLabel(self.tr('Armory Bitcoin Wallet : Version %1-beta-%2').arg(getVersionString(BTCARMORY_VERSION), BTCARMORY_BUILD), doWrap=False)
TypeError: arguments did not match any overloaded call:
  QString.arg(int, int fieldWidth=0, int base=10, QChar fillChar=QLatin1Char(' ')): argument 1 has unexpected type 'str'
  QString.arg(float, int fieldWidth=0, str format='g', int precision=-1, QChar fillChar=QLatin1Char(' ')): argument 1 has unexpected type 'str'
  QString.arg(int, int fieldWidth=0, int base=10, QChar fillChar=QLatin1Char(' ')): argument 1 has unexpected type 'str'
  QString.arg(int, int fieldWidth=0, int base=10, QChar fillChar=QLatin1Char(' ')): argument 1 has unexpected type 'str'
  QString.arg(QString, int fieldWidth=0, QChar fillChar=QLatin1Char(' ')): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString, QString): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  QString.arg(QString, QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
(ERROR) ArmoryUtils.py:1412 - Attempting to unserialize something not an ASCII block
(ERROR) AsciiSerialize.py:74 - Expected str "TXSIGCOLLECT", got "2017-04-23"
(ERROR) ArmoryUtils.py:1412 - Attempting to unserialize something not an ASCII block
(ERROR) AsciiSerialize.py:74 - Expected str "TXSIGCOLLECT", got "AAAAABl2qRSWT5uRjyWH/G6M6BH1J4QiTJJdcIisoxUAAAAAAAAZdqkUIuz4d8vN"
(ERROR) ArmoryUtils.py:1412 - Attempting to unserialize something not an ASCII block
(ERROR) AsciiSerialize.py:74 - Expected str "TXSIGCOLLECT", got "tXsVR2076guIrC9sAAAAAAAAGXapFB4VBiz4+5qD2eHAstbeg/ma9Tq7iKxfKwMA"
(ERROR) ArmoryUtils.py:1412 - Attempting to unserialize something not an ASCII block
(ERROR) AsciiSerialize.py:74 - Expected str "TXSIGCOLLECT", got "iCTUR4nIb36IrB8oDgAAAAAAGXapFG/NbQCufwJlnZ0TZDtVua1ITRHciKzUOQQA"
(ERROR) ArmoryUtils.py:1412 - Attempting to unserialize something not an ASCII block
(ERROR) AsciiSerialize.py:74 - Expected str "TXSIGCOLLECT", got "jKnHF6pv7B6IrPMKBAAAAAAAGXapFDgxh01N8qYL4w1XhEZZi/195I6iiKwXNgAA"
33  Bitcoin / Armory / Re: Armory 0.96 third testing builds on: April 23, 2017, 06:25:55 AM
It worked, thank you so much! I am online!  Grin

Regarding the ram usage, on this machine I have 16gb, and I switched over from the Ubuntu PC which only has 4gb. In the long run I would prefer the Ubuntu PC as I can leave it online 24/7. Do you think with the settings you recommended to me now, it might also work on the Ubuntu PC where it always got stuck building the DB?
34  Bitcoin / Armory / Re: Armory 0.96 thired testing builds on: April 22, 2017, 11:30:16 AM
I think Armory Wants to drive me crazy.... ;-) At 99% of scanning my wallets I get this:

Edit: Just reproduced it. It happens at the exact same spot just after height #461932. Any advice for this?

35  Bitcoin / Armory / Re: Armory 0.96 thired testing builds on: April 22, 2017, 10:58:16 AM
It seems to have worked out. Only on the bottom it still tells me Armory is offline. I import my watch only wallets now and see if the balances show up correctly.

Edit: Wallet balances are shown as 0 for all wallets. It also tells me that the Bitcoin node is offline. I set Armory to manage Bitcoin and gave it the correct directories.

Edit2: I think it looks good now. Had to stop ArmoryDB and let everything run by ArmoryQt and have it rund the ArmoryDB itself. I am now at scanning transaction history but database seems built and all. I report again as soon as I can see my balances. History scan seems to take another 30min or so.

36  Bitcoin / Armory / Re: Armory 0.96 second testing builds on: April 21, 2017, 07:11:20 PM
OK with that option I get this:



Without that option the behavior seems the same, a console with ArmoryDB.exe appears with a ton of -INFO and Armory starts making its things. Currently at 14% of building database and also initializing Bitcoin engine. I changed and let armory handle bitcoin in the background. Who knows, maybe works better that way without starting BitcoinQt first. I'll update.

Edit: Nope stuck at block file 220 this time. Is there an ArmoryDB log somewhere?
37  Bitcoin / Armory / Re: Armory 0.96 second testing builds on: April 21, 2017, 05:58:40 AM
Are you using the same block file data on the Windows machine than on the Ubuntu one?

Quote
So far always happended between maybe 18 an 28 % progress.

Yes I copied it over. Bitcoin QT workes fine and is synched. I do not use the default datadir, neither for Armory nor Bitcoin-QT. However it starts to build the DB in the correct place?

Do you recommend to re-download the whole chain again?

Delete the database and try again from the top with --thread-count=1. Does it always fail at the same spot now?
38  Bitcoin / Armory / Re: Armory 0.96 second testing builds on: April 20, 2017, 10:05:00 PM
I moved to a Windows 7 x64 system with 16 gb ram as the ubuntu pc just din't handle the DB build ever. Now I constantly get this. Sorry for the ugly screenshot but as soon as I press cancle ArmorDB and the CMD vanish.

So far always happended between maybe 18 an 28 % progress.

any idea?

39  Bitcoin / Armory / Re: Armory 0.96 second testing builds on: April 17, 2017, 01:37:53 PM
It's running now. Now I have to set up my node again and get it online. Thy for all the help. Was maybe one of the dependencies missing for running it from the .deb file?

Edit: Even though I kept the blocks, it is taking ages to synch the block headers. Could I have prevented this in any way?
40  Bitcoin / Armory / Re: Armory 0.96 second testing builds on: April 17, 2017, 10:54:47 AM
Carlton's tip didn't work either. It tells me it is successfully installed and then I have the same behavior. Building from source needed some dependancies installed. I did that and it seems up to
Code:
./configure
it worked fine.

However, the make process ends with:

Code:
make[3]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig'
Makefile:1446: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig'
Makefile:430: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory'
Makefile:362: recipe for target 'all' failed
make: *** [all] Error 2

The install process then ends with:

Code:
libtool: install: /usr/bin/install -c DB1kIterTest /usr/local/bin/DB1kIterTest
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig/gtest'
make[3]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig/gtest'
make[2]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig/gtest'
make[2]: Entering directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig'
swig -c++ -python -threads -D__GNUC__  CppBlockUtils.i
/bin/bash: swig: command not found
Makefile:1725: recipe for target 'CppBlockUtils_wrap.cxx' failed
make[2]: *** [CppBlockUtils_wrap.cxx] Error 127
make[2]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig'
Makefile:1446: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/home/ben/ArmoryGit/BitcoinArmory/cppForSwig'
Makefile:430: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1

There seem to be a lot of armory files created (including icons ;-)) but somehow installation failed. Any advice?
Pages: « 1 [2] 3 4 5 6 7 8 9 10 11 12 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!