Bitcoin Forum
June 26, 2024, 09:08:18 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Armory / Re: Can't make 0.96.0.3-testing --"No targets specified and no makefile found." on: June 29, 2017, 05:29:22 AM
Hey achow101,

Perhaps it would help if I rephrased the question and included my command history, so you know exactly what I did:

 2004  git clone https://github.com/goatpig/BitcoinArmory.git
 2005  sudo apt-get update
 2006  sudo apt-get upgrade
 2007  cd BitcoinArmory/
 2008  git checkout testing
 2009  git submodule init
 2010  git submodule update
 2011  ./autogen.sh
 2012  ./configure

Scrolling back I now see the problem occurred on the configure step:

configure: error: *** A compiler with support for C++11 language features is required.

I did upgrade gcc to 5.4 for this, see:

$ gcc --version
gcc (Ubuntu 5.4.1-2ubuntu1~14.04) 5.4.1 20160904
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

2  Bitcoin / Armory / Re: Can't make 0.96.0.3-testing --"No targets specified and no makefile found." on: June 29, 2017, 04:09:53 AM
Thanks Casimir1904 and achow101.

For whatever reason, at the make step of these instructions, I still get the same error.

I did try each of the Makefiles by exact name:

$ make -j$(grep -c ^processor /proc/cpuinfo) -f Makefile.am
Makefile.am:13: *** missing separator.  Stop.

and:

$ make -j$(grep -c ^processor /proc/cpuinfo) -f Makefile.in
Makefile.in:15: *** missing separator.  Stop.

I'm just a Linux user, not a C++ programmer, I don't really know what I'm doing, sorry.

Best.
3  Bitcoin / Armory / Can't make 0.96.0.3-testing --"No targets specified and no makefile found." on: June 28, 2017, 10:46:38 PM
Trying to build 0.96.0.3-testing from source, following instructions at:

    https://github.com/goatpig/BitcoinArmory/blob/master/linuxbuild/Linux_build_notes.md

Got dependencies installed, keys imported, cloned from git, tag checked out..  There was a message when tag checked out:

==========
Note: checking out 'v0.96.0.3-testing'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 1a126dd... version bump
==========

The git tag -v reported that it was "Good signature from "goatpig"" (for 4922589A).

Alas, upon trying to do the final "make", it says:

   "No targets specified and no makefile found.  Stop."

Did I do something wrong?

Thanks.
4  Bitcoin / Armory / Where are transaction labels? (was: Will Armory 0.93.3 still work after Segwit?) on: June 27, 2017, 04:20:42 PM
Hi goatpig,

It wasn't an issue of not respecting them, simply of not fully understanding them.

After another go at it, it worked.  Almost..  Can you help me understand why many of my Labels are missing?  These are stored in the .wallet file is that right?  I've even had this issue also when moving from one Armory 0.93.3 to another 0.93.3.

Only one of my the wallets has an extra copy named with "_encrypt", even though I have more than one wallet encrypted, and so why would it keep around the same named wallet WITHOUT the "_encrypt" suffix?

Thanks for any clarifications or tips on this for this transition.

PS -- I PM'd you only for sending you the log file links, to minimize the exposure of my personal information like wallet id's and names, computer hardware, OS, etc.  I'm sure you can respect that.
5  Bitcoin / Armory / Will Armory 0.93.3 still work after Segwit? on: June 25, 2017, 04:54:17 AM
I've been working on getting upgraded to 0.96.1, just waiting for it to complete its initialization.  I couldn't get the latest "testing-3" version to launch even after upgrading gcc to 5.4).  It's been "Scanning Tx Hashes" for a few days on a fast 4GHz machine, one core has been pegged @ 100%, with light/moderate HD access, seeing occasional new .ldb files in "chainstate" directory but, besides that, I have no idea if it is actually making progress or stuck in a loop.

Please forgive me this dumb question -- on the off chance I'm still on 0.93.3 on Aug 1st, Segwit is a soft-fork, which means backward compatibility, right?  Will my legacy 0.93.3 installation (on another machine w/ Bitcoin 0.13.2) still be able to communicate with the Bitcoin network as usual after Segwit activates?

Thanks.
6  Bitcoin / Armory / Re: Armory stays in "Initializing BitCoin Engine" forever on: January 18, 2017, 11:52:49 PM
Quote
It's failing to establish a RPC connection with bitcoind. Make sure your user can read and write bitcoin.conf, add server=1 in there and wipe the current log&pass for the good measure.

If I'm able to do

    ./bitcoin-cli getblockcount

successfully, does that mean the RPC server is at least working for bitcoin-cli?  If so, then maybe it means the issue is with Armory being able to access the rpcuser and rpcpassword values from the bitcoin.conf file..?

By "wipe" the current log&pass, did you mean I should delete those lines entirely?  Just FYI, here is the exact file contents.

rpcuser=rpcuser
rpcpassword=48djew8cjJDjhuHU7EKQUjs73hsJUXNEPOQBXBFUjsyu72j63y
server=1

I had tried changing the rpcuser from"user02" to "rpcuser" and also the rpcpassword, but it didn't help.  Hmm, I just noticed I have no blank lines after server=1.  That probably doesn't matter.

The file is in the default location, /home/myUser/.bitcoin.  Owner read and write, and I'm the owner..
7  Bitcoin / Armory / Re: Armory stays in "Initializing BitCoin Engine" forever on: January 18, 2017, 03:57:30 AM
Greetings, (finally figuring out this forum sofware, pardon my newbieness!)

I was having the exact same problem trying to get up and running with 0.95.1, using the same configuration I've been using with 0.93.3 for a couple of years.  I normally like to enable:

   "Let Armory run Bitcoin-Core/bitcoind in the background."

but 0.95.1 will get stuck, producing those same errors in the log file.  I was eventually able to get it going by:

  1) starting Armory in offline mode, unchecking that box.  Exit.
  2) starting bitcoind myself with the -daemon argument.

       /my/location/for/bitcoin-13.2/bin/bitcoind -daemon

   3) starting Armory 0.95.1 again in online mode.

I definitely appreciate the faster and smaller database!

I rather prefer it to start bitcoind for me, but I guess this isn't too onerous.  I could autostart bitcoind upon boot, it was just nice for the wallet UI to also start/stop the bitcoin node for convenient and the novice end-users.

Just in case its helpful, I've pasted my full armorylog file, below, when I tried to leave the box checked.  (dbLog.txt was empty)

Best,
  Chris Muller

2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1137 - C++ block utilities loaded successfully
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:651 - Executing popen: free -m
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:651 - Executing popen: ['cat', '/proc/cpuinfo']
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1247 -
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1248 -
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1249 -
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1250 - ************************************************************
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1251 - Invoked: /usr/bin/../lib/armory/ArmoryQt.py
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1252 - ************************************************************
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1253 - Loading Armory Engine:
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1254 -    Armory Version        : 0.95.1
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1255 -    Armory Build:         : eb4d550091
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1256 -    PyBtcWallet  Version  : 1.35
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1257 - Detected Operating system: Linux
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1258 -    OS Variant            : Ubuntu-14.04-trusty
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1259 -    User home-directory   : /home/cmm
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1260 -    Satoshi BTC directory : /home/cmm/.bitcoin/
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1261 -    Armory home dir       : /home/cmm/.armory/
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1262 - Detected System Specs    :
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1263 -    Total Available RAM   : 15.54 GB
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1264 -    CPU ID string         : Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1265 -    Number of CPU cores   : 8 cores
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1266 -    System is 64-bit      : True
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1267 -    Preferred Encoding    : UTF-8
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1268 -    Machine Arch          : x86_64
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1269 -    Available HDD (ARM)   : 330 GB
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1270 -    Available HDD (BTC)   : 330 GB
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1271 -
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1272 - Network Name: Main Network
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1273 - Satoshi Port: 8333
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1274 - Do wlt check: True
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1275 - Named options/arguments to armoryengine.py:
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     thread_count    : -1
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     rescan          : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     ignoreAllZC     : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     rescanBalance   : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     disableModules  : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     port            : None
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     interport       : 8223
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     skipStatsReport : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     forceWalletCheck: False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     regtest         : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     rebuild         : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     nettimeout      : 2
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     datadir         : DEFAULT
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     clearMempool    : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     offline         : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     coverageOutputDir: None
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     armoryDBDir     : DEFAULT
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     armorydb_port   : 9001
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     satoshiPort     : DEFAULT
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     useTorSettings  : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     netlog          : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     keypool         : 100
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     coverageInclude : None
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     forceOnline     : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     skipAnnounceCheck: False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     redownload      : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     armorydb_ip     : 127.0.0.1
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     multisigFile    : DEFAULT
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     ram_usage       : -1
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     testAnnounceCode: False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     mtdebug         : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     logDisable      : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     settingsPath    : /home/cmm/.armory/ArmorySettings.txt
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     db_type         : DB_FULL
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     doDebug         : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     enableDetSign   : True
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     disableConfPermis: False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     testnet         : False
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     rpcport         : DEFAULT
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     satoshiHome     : DEFAULT
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     satoshiRpcport  : DEFAULT
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     logFile         : /home/cmm/.armory/ArmoryQt.py.log.txt
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1277 -     verbosity       : None
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1278 - Other arguments:
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1281 - ************************************************************
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:1684 - C++ block utilities loaded successfully
2017-01-17 20:28 (INFO) -- BDM.py:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-01-17 20:28 (INFO) -- BDM.py:368 - Blockchain operations will happen in the background. 
2017-01-17 20:28 (INFO) -- BDM.py:369 - Devs: check TheBDM.getState() before asking for data.
2017-01-17 20:28 (INFO) -- BDM.py:370 - Registering addresses during rescans will queue them for
2017-01-17 20:28 (INFO) -- BDM.py:371 - inclusion after the current scan is completed.
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:3597 - Using settings file: /home/cmm/.armory/ArmorySettings.txt
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 1x9gZpM9
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2576 -      Wallet 1 (skipped): /home/cmm/.armory/armory_1x9gZpM9_.wallet
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2577 -      Wallet 2 (loaded):  /home/cmm/.armory/armory_1x9gZpM9_encrypt.wallet
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, rxPq829V
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2576 -      Wallet 1 (skipped): /home/cmm/.armory/armory_rxPq829V_WatchOnly.wallet
2017-01-17 20:28 (WARNING) -- ArmoryQt.py:2577 -      Wallet 2 (loaded):  /home/cmm/.armory/armory_rxPq829V__WatchOnly.wallet
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 4
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2603 -    Wallet (36G26ig9V):   "cmm-small-wallet                "   (Encrypted)
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2603 -    Wallet (1x9gZpM9):    "cmm-micro-wallet                "   (Encrypted)
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2603 -    Wallet (rxPq829V):    "Vault (Watch)                   "   (No Encryption)
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2603 -    Wallet (ULnDNsSZ):    "Vaul2 (Watch)                   "   (No Encryption)
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2608 - Loading Multisig Lockboxes
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-01-17 20:28 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:651 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:651 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2017-01-17 20:28 (INFO) -- ArmoryQt.py:546 - Usermode: Expert
2017-01-17 20:28 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-01-17 20:28 (INFO) -- ArmoryQt.py:1709 -    From: Expert
2017-01-17 20:28 (INFO) -- ArmoryQt.py:1717 -      To: Expert
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-01-17 20:28 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:651 - Executing popen: ['whereis', 'bitcoind']
2017-01-17 20:28 (INFO) -- SDM.py:182 - Found bitcoind in the following places:
2017-01-17 20:28 (INFO) -- SDM.py:184 -    /home/cmm/work/cc/bitcoin/bitcoin-0.13.2/bin/bitcoind
2017-01-17 20:28 (INFO) -- SDM.py:186 - Using: /home/cmm/work/cc/bitcoin/bitcoin-0.13.2/bin/bitcoind
2017-01-17 20:28 (INFO) -- SDM.py:382 - Reading bitcoin.conf file
2017-01-17 20:28 (INFO) -- SDM.py:416 - Setting permissions on bitcoin.conf
2017-01-17 20:28 (INFO) -- SDM.py:460 - Called startBitcoind
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:651 - Executing popen: [u'/home/cmm/work/cc/bitcoin/bitcoin-0.13.2/bin/bitcoind', '-datadir=/home/cmm/.bitcoin/']
2017-01-17 20:28 (INFO) -- SDM.py:574 - PID of bitcoind: 9350
2017-01-17 20:28 (INFO) -- SDM.py:575 - PID of armory:   9320
2017-01-17 20:28 (INFO) -- ArmoryUtils.py:651 - Executing popen: ['python', '/usr/lib/armory/guardian.py', '9320', '9350']
2017-01-17 20:28 (INFO) -- SDM.py:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-01-17 20:28 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2017-01-17 20:28 (WARNING) -- SDM.py:679 - Overriding not-available state. This should happen 0-5 times
2017-01-17 20:28 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
    numblks = self.proxy.getinfo()['blocks']
  File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
    resp = json.loads(resp, parse_float=decimal.Decimal)
  File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2017-01-17 20:28 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
    numblks = self.proxy.getinfo()['blocks']
  File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
    resp = json.loads(resp, parse_float=decimal.Decimal)
  File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2017-01-17 20:28 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
    numblks = self.proxy.getinfo()['blocks']
  File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
    resp.....   (snip)
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!