Bitcoin Forum
June 27, 2024, 04:37:30 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: September 15, 2017, 07:27:23 PM
I expanded on my explanation given above.  But in essence no, as you would just be wasting time with the relaunch and just because they are "faster" shares, since they are also of lower difficulty they will hold less value at the pool as explained earlier.

Thank you for taking the time to explain that, incredibly helpful!
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: September 15, 2017, 07:20:51 PM
@Za1n

Why wouldn't someone rig the miner to just launch, run for 1 minute, close, and relaunch if this is the case? Wouldn't that be much more lucrative?
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: September 15, 2017, 07:04:43 PM
When I launch the miner, for the first one or two jobs my share rate is fast as hell. See screenshot below.

But then after I get a new job from the pool (and I've tried two different pools). It slows down like 10x.

Anyone heard of this happening?

Start of mining session:
After 2nd or 3rd work detected:
4  Bitcoin / Armory / Re: 0.96.0.4 Stuck Preparing Databases 0% on: July 21, 2017, 12:22:45 AM
Confirmed, the reinstalls fixed all issues I was having. Thanks.
5  Bitcoin / Armory / Re: 0.96.0.4 Stuck Preparing Databases 0% on: July 20, 2017, 11:25:02 PM
Quote
It's saying there's a DB error but I've pointed it to the correct dir for the block chain and it was just working earlier as I mentioned.




Is it not taking the settings into account in this build perhaps?

UPDATE: It's not taking the path settings into account at all, regardless of where I point it, it's looking in the default path on C.
UPDATE2: Reinstalled 0.96.0, then installed 0.96.0.4 again, I'm now progressing through scanning transaction history. Fun times.
6  Bitcoin / Armory / Re: 0.96.0.4 Stuck Preparing Databases 0% on: July 20, 2017, 11:13:30 PM
I was wrong, those two lines are written just at closing. Here's the entirety of the log between launch to close.

It's saying there's a DB error but I've pointed it to the correct dir for the block chain and it was just working earlier as I mentioned.

Any input is appreciated, thank you!

Code:
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1255 -
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1256 -
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1257 -
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: H:\Program Files (x86)\Armory\ArmoryQt.exe
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1262 -    Armory Version        : 0.96.0.4
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1263 -    Armory Build:         : 98578163de
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1264 -    PyBtcWallet  Version  : 1.35
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1266 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1267 -    User home-directory   : C:\Users\***\AppData\Roaming
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1268 -    Satoshi BTC directory : C:\Users\***\AppData\Roaming\Bitcoin\
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1269 -    Armory home dir       : C:\Users\***\AppData\Roaming\Armory\
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs    :
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1271 -    Total Available RAM   : 31.95 GB
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1272 -    CPU ID string         : Intel64 Family 6 Model 94 Stepping 3, GenuineIntel
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1273 -    Number of CPU cores   : 8 cores
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1274 -    System is 64-bit      : True
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1275 -    Preferred Encoding    : cp1252
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1276 -    Machine Arch          : amd64
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1277 -    Available HDD (ARM)   : 3 GB
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1278 -    Available HDD (BTC)   : 0 GB
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1279 -
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     thread_count    : -1
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     rescan          : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     ignoreAllZC     : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     rescanBalance   : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     disableModules  : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     port            : None
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     interport       : 8223
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     coverageOutputDir: None
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     forceWalletCheck: False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     regtest         : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     rebuild         : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     nettimeout      : 2
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     datadir         : DEFAULT
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     clearMempool    : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     offline         : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     armoryDBDir     : DEFAULT
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_port   : 9001
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiPort     : DEFAULT
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     useTorSettings  : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     netlog          : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     keypool         : 100
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     coverageInclude : None
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     forceOnline     : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     redownload      : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     rpcBindAddr     : 127.0.0.1
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_ip     : 127.0.0.1
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     multisigFile    : DEFAULT
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     ram_usage       : -1
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     mtdebug         : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     logDisable      : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     settingsPath    : C:\Users\***\AppData\Roaming\Armory\ArmorySettings.txt
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     language        : en
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     db_type         : DB_FULL
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     doDebug         : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     enableDetSign   : True
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     disableConfPermis: False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     testnet         : False
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     rpcport         : DEFAULT
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiHome     : DEFAULT
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiRpcport  : DEFAULT
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     logFile         : C:\Users\***\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1285 -     verbosity       : None
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\***\AppData\Roaming\Armory\ArmorySettings.txt
2017-07-20 16:01:23 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
2017-07-20 16:01:23 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-07-20 16:01:23 (INFO) -- BDM.pyc:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-07-20 16:01:23 (INFO) -- BDM.pyc:366 - Blockchain operations will happen in the background. 
2017-07-20 16:01:23 (INFO) -- BDM.pyc:367 - Devs: check TheBDM.getState() before asking for data.
2017-07-20 16:01:23 (INFO) -- BDM.pyc:368 - Registering addresses during rescans will queue them for
2017-07-20 16:01:23 (INFO) -- BDM.pyc:369 - inclusion after the current scan is completed.
2017-07-20 16:01:24 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\***\AppData\Roaming\Armory\ArmorySettings.txt
2017-07-20 16:01:24 (INFO) -- ArmoryQt.py:2050 - loadWalletsAndSettings
2017-07-20 16:01:24 (INFO) -- ArmoryQt.py:2110 - Loading wallets...
2017-07-20 16:01:24 (INFO) -- ArmoryQt.py:2175 - Number of wallets read in: 1
2017-07-20 16:01:24 (INFO) -- ArmoryQt.py:2180 -    Wallet (2RAotSsgB):   "Primary Wallet                  "   (Encrypted)
2017-07-20 16:01:24 (INFO) -- ArmoryQt.py:1752 - acquiring process mutex...
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1391 - setupUriRegistration
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1459 - Armory already registered for current user.  Done!
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:565 - Usermode: Advanced
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1687 - Changing usermode:
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1688 -    From: Advanced
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1696 -      To: Advanced
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1825 - startBitcoindIfNecessary
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1861 - setSatoshiPaths
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1881 - Setting satoshi datadir = H:\BitcoinCore\blocks
2017-07-20 16:01:25 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-07-20 16:01:25 (INFO) -- SDM.pyc:171 -    H:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-07-20 16:01:25 (INFO) -- SDM.pyc:173 - Using: H:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-07-20 16:01:25 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-07-20 16:01:25 (INFO) -- ArmoryUtils.pyc:667 - Executing popen: [u'H:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=H:\\BitcoinCore\\blocks', '-dbcache=2000']
2017-07-20 16:01:25 (INFO) -- SDM.pyc:450 - PID of bitcoind: 9008
2017-07-20 16:01:25 (INFO) -- SDM.pyc:451 - PID of armory:   3732
2017-07-20 16:01:25 (INFO) -- ArmoryUtils.pyc:667 - Executing popen: ['.\\guardian.exe', '3732', '9008']
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 1
2017-07-20 16:01:25 (ERROR) -- BDM.pyc:200 - DB error: C:\Users\***\AppData\Roaming/Bitcoin/blocks is not a valid path
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 0
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:1895 - loadBlockchainIfNecessary
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-20 16:01:25 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
7  Bitcoin / Armory / 0.96.0.4 Stuck Preparing Databases 0% on: July 20, 2017, 11:05:12 PM
Bitcoin Core is connected and fully synced. Just an hour ago I'd made a new wallet with Armory and completed a small volume test transaction to it.

After the transaction had one confirmation I closed armory. Reopening it thereafter has resulted in permanent offline mode and being stuck "preparing databases". I've left it here for a half hour, it's using no processor and I'm seeing no change in ram usage. The only log being updated when I close it is armorylog and the only lines it's writing to it are:

2017-07-20 15:59:13 (INFO) -- ArmoryQt.py:5424 - BDM is safe for clean shutdown
2017-07-20 15:59:13 (INFO) -- SDM.pyc:464 - Called stopBitcoind

Any ideas?
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!