Bitcoin Forum
May 04, 2024, 07:10:41 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2] 3 »  All
  Print  
Author Topic: Offline mode 1.5 years unable to get out of blockchain wallet consistant  (Read 2146 times)
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
December 08, 2016, 02:24:41 PM
 #21

Code:
-INFO  - 1481145183: (..\DatabaseBuilder.cpp:268) parsed block file #378

This is way off. This is your last block file. It should be in the #700 instead. You are missing a lot of block data.

I'll explain the model so you get an idea of what's going on:

You are running 3 pieces of software at once:

- First, your bitcoin node. This connects to the bitcoin network, downloads and maintains blockchain data. Bootstrapping the blockchain is long and resource heavy. This is the longest part of the whole process. Once you have the blockchain data, the subsequent startups will be much faster.

The data is found in saved in block files, named blkXXXXX.dat (the XXXXX represent the block file number). You can find them here:

Code:
-INFO  - 1481144202: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\Zebra\AppData\Roaming/Bitcoin/blocks

In your case, you have < 400 of these files, and that's an issue. You are missing about half the data you need to use Bitcoin properly.

- Second, ArmoryDB. This software parses the blkXXXXX.dat files directly from disk. This phase is called building the db.

The process needs to know where the blockchain data is (so far it has found it), and it needs the data to be consistent and complete. In you case, it is consistent but incomplete. Whenever this process says "Enabling zero-conf tracking", it means it has initialized and is now on standby. ArmoryDB interfaces with your node to maintain itself.

- Third, ArmoryQt. This is the client, holding your wallet data and providing the GUI. It interfaces with the DB for its needs. Your client serves the wallet data to the db. The db has to scan the wallets it is presented for the first time. This phase is called scanning the wallet history. It is the second longest, but nowhere as long as bootstrapping your node. This phase will crash if your block data is inconsistent.


Under normal circumstances, you only run the client, and it automates the other 2 processes for you. Since you are having issues, I'm having you run through the process step by step to try and troubleshoot the issue.

-------------------------

Seeing you are very short on block data, you need to start BitcoinQt and let it catch up. Consider adding server=1 in your bitcoin.conf to be get better feedback. Expect this part to take hours. Once that is done, run ArmoryDB again, then post your dbLog.txt again.

Quote
Bitcoin will never take hold when you have complicated problem with wallets. When person that hasn't designed the program and it crashes through no fault of their own is unsolvable. The keys ( solution) to the problem lay with an individual company or person to get it going.  If you piss them off or they go under you are doomed to never recover....I guess being insolent to the customer doesn't count. I will donate but it doesn't encourage me to give as much.

To run a full node solution like Armory you need good internet bandwidth, a decent computer and you can't be afraid of getting technical. Your reward is a full fledged experience and a much better understanding of Bitcoin.

If you can't/won't go through these steps, you will have to look for a more user friendly wallet, at the cost of some important properties that make Bitcoin what it is.

There will always be people on this sub forum ready to explain and help those in need. In return, you should not abuse their patience and generosity by lacking in patience yourself, making it hard for them to help you, or ignore/cherry pick their instructions. That, and be civil when possible.

1714849841
Hero Member
*
Offline Offline

Posts: 1714849841

View Profile Personal Message (Offline)

Ignore
1714849841
Reply with quote  #2

1714849841
Report to moderator
1714849841
Hero Member
*
Offline Offline

Posts: 1714849841

View Profile Personal Message (Offline)

Ignore
1714849841
Reply with quote  #2

1714849841
Report to moderator
1714849841
Hero Member
*
Offline Offline

Posts: 1714849841

View Profile Personal Message (Offline)

Ignore
1714849841
Reply with quote  #2

1714849841
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714849841
Hero Member
*
Offline Offline

Posts: 1714849841

View Profile Personal Message (Offline)

Ignore
1714849841
Reply with quote  #2

1714849841
Report to moderator
SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 10, 2016, 07:42:34 AM
Last edit: December 10, 2016, 11:01:53 AM by SamSpade2
 #22

I guess D have 1/2 the key when I load Armory without it as main data it still load the B part but not the wallet yet at least I think I can use it to pay and receive for now it shows. I will follow through after I study your instructions when I have more time. Thanks we are getting there < was in a real hurry.

SORRY ALSO I DID NOT NOTICE TIL NOW THAT THERE WAS A SECOND PAGE. THIS IS QUITE DIFFERENT LAYOUT THAN OTHERS I HAVE DONE.

Goatpig if you give me your bitcoin ID I will send you a donation thanks.
SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 10, 2016, 08:28:27 PM
Last edit: December 10, 2016, 08:42:55 PM by SamSpade2
 #23

Bitcoin core says no sorceblock available but path, etc. are correct when loading, I had it give info on startup.

Even though it seems to be doing nothing, small box on bottom right the icon isn't moving or bar, when I hover it says 8 Active connections. On same screen it says catching up...personally VERY bad design a novice needs SOME indication that is actually doing something which I assume it is. And people wonder why people have problems with programs NOT you all.

Al I need to know it is actually doing what needs to be done and working to accomplish as such.

Goaatpig I pretty well understood that two soft ware was running but not the three thanks for telling I like to know haw things work I may not get specficis but the general I do.
achow101
Staff
Legendary
*
Offline Offline

Activity: 3388
Merit: 6581


Just writing some code


View Profile WWW
December 10, 2016, 08:43:28 PM
 #24

Bitcoin Core is not developed by goatpig. It is an important part of Armory as a dependency, but Bitcoin Core having problems has nothing to do with Armory.

Your problem looks like it is currently with Bitcoin Core. Usually you need to reindex when it says "no source block available" and you still have connections. Go to the folder where Bitcoin Core is installed. Hold shift, right click, then choose the option to "Open a command window here". Type
Code:
bitcoin-qt.exe -reindex
This will start Bitcoin Core's reindexing. It will look as if it is redownloading the blockchain, but it actually is not. You will see the green progress bar at the bottom, let it reindex and sync. You have to leave Bitcoin Core open until the green progress bar disappears. Once it is, try starting Armory again.

SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 11, 2016, 12:08:36 AM
Last edit: December 11, 2016, 01:56:55 AM by SamSpade2
 #25

I pretty well understood the delegation of labor on software. Armory is stacked on to are linked if preferable to Bitcoin core, as I imagine all wallets are...am I correct? It reminds me of my old command line days where at one time I could whip out something in text then in all their wisdom Windows came in and I lost my mind.

I always tried to explain windows was NOT an OS at the time just a UI as they would call now or front end as I would prefer to call it. I imagine it is linked to OS internally pretty deeply now.

I did the reindex command went thorough from year six to 4 years behind pretty quickly now we are on 3 years 15 weeks and counting down but no green line. doesn't ntis reindex save to disk last spot done? I went to do something else screensaver went on and powered back up now it said back to 5 years 29 weeks. Closed out of BitcoinQT started reindex and now finally to 2 year 38 weeks...it would seem to me Bitcoin would write better recover save routines in it.

A week of blockchain is taking about 20 seconds figured 1/2 hr or so if continues at that rate.
_______________________________________________________________________________ ______

I'm sitting here watching rebuild and all of a sudden it was on 1 year 2 weeks and went back to 6 years 7 weeks...gee. using 47% of CPU power BITcoin Qt will read 5 or so meg then write on my SSD 500 or so kbytes constantly. Hope it is Not killing my wear levels.
SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 16, 2016, 09:20:30 AM
Last edit: December 16, 2016, 09:36:32 AM by SamSpade2
 #26

Posted and state of computer 3 AM 12/16/2016 CST

LATEST!! in manual mode all OK need to safely close down.

 All is done Wallet!
 in armory unchecked manual both bitcoin QT and Armory open
 are done and showing in transactions.
DOS Box open

IMPORTANT ASAP  HOW DO I CLOSE OUT WHERE i SAVE EVERYTHING? CPU AT 100 % AND NEED IT TO QUIT SAYS IT IS ARMORY DB taking that cpu cycle.

i WAS TEMPTED TO CLOSE bITCOIN db first, then Armory, but didn't want to lose position I'm in.

________________________________________________________________________
Current status locked up still, haven't closed anything BUT want TO badly. Corruption in Keyboard file why characters are off and typing very hard.!!

On Armory 95.1 lower corner is all green connected and online 383790 Blocks. Not checked manual mode.

On bitcoin no GREEN checkmark in lower right corner

Transactions Armory tab wallet looks correct

Please help me close out correctly ASAP tried on own and had to rebuild.
_______________________________________________________________
Last part of bitcoinQT log file:

2016-12-16 07:57:05 receive version message: /Satoshi:0.13.1/: version 70014, blocks=443681, us=108.45.111.44:54072, peer=34
2016-12-16 07:57:05 AdvertiseLocal: advertising address 108.45.111.44:8333
2016-12-16 07:57:05 socket send error An operation was attempted on something that is not a socket.  (10038)
2016-12-16 08:13:18 socket send error An established connection was aborted by the software in your host machine.  (10053)
2016-12-16 08:13:38 ProcessMessages: advertising address 108.45.111.44:8333
2016-12-16 08:13:38 receive version message: /Satoshi:0.13.1/: version 70014, blocks=443681, us=108.45.111.44:57984, peer=35
2016-12-16 08:13:38 AdvertiseLocal: advertising address 108.45.111.44:8333
2016-12-16 08:23:36 Pre-allocating up to position 0xa00000 in rev00712.dat
2016-12-16 08:23:36 UpdateTip: new best=00000000000000000273ed2ea08f33a703a7872872eb47098a76ca797df6440b height=443682 version=0x20000002 log2_work=85.683142 tx=179467496 date='2016-12-16 08:41:19' progress=1.000005 cache=260.2MiB(136355tx) warning='3 of last 100 blocks have unexpected version'
2016-12-16 08:32:09 ProcessMessages: advertising address 108.45.111.44:8333
2016-12-16 08:32:09 socket send error An operation was attempted on something that is not a socket.  (10038)
2016-12-16 08:32:09 receive version message: /Satoshi:0.13.1/: version 70014, blocks=443682, us=108.45.111.44:54334, peer=36
2016-12-16 08:32:09 AdvertiseLocal: advertising address 108.45.111.44:8333
2016-12-16 08:33:36 ProcessMessages: advertising address 108.45.111.44:8333
2016-12-16 08:33:36 receive version message: /Satoshi:0.13.1/: version 70014, blocks=443682, us=108.45.111.44:63961, peer=37
2016-12-16 08:33:36 AdvertiseLocal: advertising address 108.45.111.44:8333
2016-12-16 08:33:36 socket send error An operation was attempted on something that is not a socket.  (10038)
2016-12-16 08:34:03 ProcessMessages(version, 122 bytes) FAILED peer=38
2016-12-16 08:50:40 UpdateTip: new best=0000000000000000009b2a8b931d27eaa89b7461283e32f2088555d5a950ce8b height=443683 version=0x20000000 log2_work=85.683173 tx=179470112 date='2016-12-16 09:07:57' progress=1.000005 cache=69.3MiB(20491tx) warning='2 of last 100 blocks have unexpected version'
2016-12-16 08:53:38 UpdateTip: new best=0000000000000000036bc997e52996d7c6bd0c1203ea04aba70e6a7b20cbb085 height=443684 version=0x20000002 log2_work=85.683204 tx=179472324 date='2016-12-16 09:11:47' progress=1.000005 cache=72.4MiB(25014tx) warning='2 of last 100 blocks have unexpected version'
2016-12-16 08:59:53 UpdateTip: new best=000000000000000001fa6109151c68860e1071514ebf219982a32257c7ca99d4 height=443685 version=0x20000000 log2_work=85.683235 tx=179474482 date='2016-12-16 09:17:54' progress=1.000005 cache=84.6MiB(32087tx) warning='2 of last 100 blocks have unexpected version'

Parts below Armory Logfile seems like I have two wallets NOT in order Top down
_______________________________________________________________________________ ________________
2016-12-15 13:19 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2016-12-15 13:19 (INFO) -- SDM.pyc:182 - Found bitcoind in the following places:
2016-12-15 13:19 (INFO) -- SDM.pyc:184 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe

2016-12-15 14:13 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2016-12-15 14:13 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2016-12-15 14:13 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2016-12-15 14:13 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\Zebra\AppData\Roaming\Armory\ArmorySettings.txt
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 2bFXcxRew
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2576 -      Wallet 1 (skipped): C:\Users\Zebra\AppData\Roaming\Armory\armory_2bFXcxRew_.watchonly.wallet
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2577 -      Wallet 2 (loaded):  C:\Users\Zebra\AppData\Roaming\Armory\armory_2bFXcxRew_.wallet
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 2bFXcxRew
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2576 -      Wallet 1 (skipped): C:\Users\Zebra\AppData\Roaming\Armory\armory_2bFXcxRew_encrypt.wallet
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2577 -      Wallet 2 (loaded):  C:\Users\Zebra\AppData\Roaming\Armory\armory_2bFXcxRew_.wallet
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 2bFXcxRew
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2576 -      Wallet 1 (skipped): C:\Users\Zebra\AppData\Roaming\Armory\armory_2bFXcxRew_RECOVERED.wallet
2016-12-15 14:13 (WARNING) -- ArmoryQt.py:2577 -      Wallet 2 (loaded):  C:\Users\Zebra\AppData\Roaming\Armory\armory_2bFXcxRew_.wallet
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 1
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2603 -    Wallet (2bFXcxRew):   "Restored - 2bFXcxRew - Chigger  "   (Encrypted)
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2016-12-15 14:13 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2016-12-15 14:13 (INFO) -- ArmoryQt.py:1480 - Armory already registered for current user.  Done!
2016-12-15 14:13 (INFO) -- ArmoryQt.py:546 - Usermode: Advanced
2016-12-15 14:13 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2016-12-15 14:13 (INFO) -- ArmoryQt.py:1709 -    From: Advanced
2016-12-15 14:13 (INFO) -- ArmoryQt.py:1717 -      To: Advanced
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2016-12-15 14:13 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2016-12-15 14:13 (INFO) -- SDM.pyc:395 - Setting permissions on bitcoin.conf
2016-12-15 14:13 (INFO) -- SDM.pyc:404 - Setting permissions on bitcoin.conf
2016-12-15 14:13 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'icacls', u'C:\\Users\\Zebra\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'Zebra:F']
2016-12-15 14:13 (INFO) -- SDM.pyc:410 - icacls returned:
2016-12-15 14:13 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2016-12-15 14:13 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="FVZyUhCo3xXFAsYgxGM2va9uDDy9dVH2x6LDHaQWobpE"', u'--satoshi-datadir="C:\\Users\\Zebra\\AppData\\Roaming\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\Zebra\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Zebra\\AppData\\Roaming\\Armory\\databases"']
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2016-12-15 14:13 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-12-15 14:13 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2016-12-15 14:13 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2016-12-15 20:11 (INFO) -- ArmoryQt.py:2886 - Current block number: 383790


Log file opened at 1481072857: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481352414: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481353148: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1481355070: (..\SocketObject.cpp:438) POLLERR error in readAndWrite


Log file opened at 1481358481: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481358764: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481417504: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481417569: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481704340: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1481708595: (..\SocketObject.cpp:438) POLLERR error in readAndWrite


Log file opened at 1481713845: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481730428: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481736577: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481744132: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481799065: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481823160: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481829546: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


Log file opened at 1481829658: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1481832323: (..\SocketObject.cpp:438) POLLERR error in readAndWrite


Log file opened at 1481832827: C:\Users\Zebra\AppData\Roaming\Armory\armorycpplog.txt


goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
December 16, 2016, 12:18:59 PM
 #27

Quote
On Armory 95.1 lower corner is all green connected and online 383790 Blocks.

That's way off, current top block is in the 440k. You need to let Core sync first before doing any of this. The DB only taxes your system on initial build. It shouldn't do a thing when it's idling. But since you are short on blocks, chances are it is scanning as Core is grabbing blocks off of the network.

You can control the DB's CPU load with --thread-count.

SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 16, 2016, 02:12:26 PM
 #28

My MOST important question I enumerated in previous how CORRECTLY shut this down. achow101 told me to set Armory to not do bitcoin in background start with bicoin QT then Armory
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
December 16, 2016, 02:43:59 PM
 #29

If you run BitcoinQt manually, you can shut it down whenever you want, it runs independently of the DB and the client. If the client automates your bitcoind instance, close the client and let it handle the rest.

As for the DB, if the client spawned it for you, just close the client. If you are running the DB manually, you can shut it down whenever you want. It's still preferable to shutdown the client first if there is one running against that DB, but that won't damage the data set one way or another.

SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 16, 2016, 03:03:37 PM
Last edit: December 16, 2016, 03:15:56 PM by SamSpade2
 #30

Terms?
BitcoinQT= QT core 13.1
Client= Armory 95.1
DB= Dos Box ? or DataBase

To me DB means data base my guess is that bitcoin core does that but NOT explained ( but I assume) Armory uses that DB and only that one. AM I correct Armory DOES NOT build matching DB of it's own? That I can't find ANYWHERE and no one has ever told they assume a person knows for sure.


1. Thanks I just went on( before I read your reply)  and started over shut down bitcoinQT first then armory.

2. Now running QT till stops and hopefully get green check. CPU MUCH more stable and not insane 1% of CPU no problem. After it's done I will close it alone.

3. Next do I load Armory with or without bitcoin in background--- checked or unchecked?  
            If un-checked load QT first then Armory. > Then how to quit?
            IF checked Armory alone and let it take care of QT...correct?

Thanks. Hopefully after it is done all will be well and work normally. Sorry this has been such an ordeal for all.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
December 16, 2016, 03:15:59 PM
 #31

I suggest you don't automate bitcoind until after your system is stable. If you automate bitcoind, let the client automate the DB as well, ie just start the client and shut it all down by just closing the client.

The client always needs a DB to operate. If it fails to find one, it will spawn on one automatically. As such, if you want to manage the DB yourself, you have to start it first. It does not matter which order you start the DB and the node, but it's always preferable to start the node first and let it catch up with the network.

Quote
If un-checked load QT first then Armory. > Then how to quit?

Quote
If you run BitcoinQt manually, you can shut it down whenever you want, it runs independently of the DB and the client.

SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 17, 2016, 12:46:00 AM
Last edit: December 18, 2016, 12:28:34 AM by SamSpade2
 #32

BitcoinQT was done..went to Armory checked it exited out reloaded and it went through three levels still working on last

1. Sync with networks > done
2. Building database > done
3 Parsing TX hashes >still doing and been doing long time Dos box still open left open

Bitcoin exe taking 16% of CPU
guardian exe taking .01 %
Armory exe taking 47%

I assume this is "normal" and when all is through it will be idle or close to and then I can close Armory. I have router firmware I want to update.
_______________________________________________________________________________ _____________________________
11 AM       12/17/11 AM CST
After hours working program crashon parsing like previous times sick of it... anyone in my position would be guess I'll just lose my money.
SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 17, 2016, 10:27:35 PM
 #33

I give up for now... I get to certain point and I get an app crash that I've sent to all during parsing... tired of it. Have not received answer to a lot of questions they will blame it all on me but think all have time just to scan problem then answer with rote answer.

I sent MS program crash text to all and private never got answer. No wonder people gave up on bitcoin all the problems. Left stringing along...tied up my computer for a week eaten up allotment of ISP data in one day more than month crashes the have to start over.

Done it with bitcoin core but I have no wallet with them..Armory used to work well till old cloud update with surgar sync that crashed my whole system.
SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 18, 2016, 07:06:09 AM
 #34

I suggest you don't automate bitcoind until after your system is stable. If you automate bitcoind, let the client automate the DB as well, ie just start the client and shut it all down by just closing the client.

The client always needs a DB to operate. If it fails to find one, it will spawn on one automatically. As such, if you want to manage the DB yourself, you have to start it first. It does not matter which order you start the DB and the node, but it's always preferable to start the node first and let it catch up with the network.

Quote
If un-checked load QT first then Armory. > Then how to quit?

Quote
If you run BitcoinQt manually, you can shut it down whenever you want, it runs independently of the DB and the client.

Did all this EXACTLY!  Almost through parsing crashed, almost at same place with MN crash posted this third time.
Holliday
Legendary
*
Offline Offline

Activity: 1120
Merit: 1009



View Profile
December 18, 2016, 10:44:59 AM
 #35

Here is what I would do to simplify things and almost guarantee a working result.

1. Make sure you have backups of your wallet files.
2. Remove everything Bitcoin related on your PC. Uninstall Armory and Core and delete all associated folders entirely.
3. Install the latest version of Bitcoin Core and let it sync with the network. Forget about Armory until Bitcoin Core is functioning properly and has the most up to date block.
4. Install the latest version of Armory, start it and disable autobitcoind management. Shut it down, copy your wallet file to the appropriate location and then restart Armory and let it do it's thing.

(Extreme version: Prior to those steps, start with a fresh Windows install on your computer.)

If these simple steps do not work, then there is some underlying issue with your OS or hardware. If you are incapable of accomplishing these relatively simple steps or any of this seems confusing to you, read until it's no longer confusing. Perhaps try to find some youtube videos that explain how to get Core synced and running and then Armory running.

If none of that works, start armory in offline mode (unplug your internet if need be) and extract the private keys. Import those keys into a wallet which requires less technical know-how to use.

Finally, if you still can't figure out how to access your bitcoins, pay someone who understands this stuff to do it for you.

Bitcoin has a relatively high bar when it comes to user responsibility. The user is supposed to know how to use the software provided in order to protect and access his private keys. Many people use this software successfully, so when I see a thread where this level of difficulty is experienced, I have to think that there is some underlying issue that is preventing the user from accomplishing his goals.

If you aren't the sole controller of your private keys, you don't have any bitcoins.
Holliday
Legendary
*
Offline Offline

Activity: 1120
Merit: 1009



View Profile
December 18, 2016, 11:23:33 PM
 #36

No you'd get aggravated also when you've done all 24/7 for weeks letting go other work you need to do... I've done everything MANY time for them EXACTLY! THEY do not complete thoughts many times' easy to blame others. Don't reply to debug files or read them, said I have two files. Don't read MS crash in program when I am parsing files, about through.
Background of peoples judgement calls:

All can't get through their thick heads that I CAN'T FINISH CAUSE ARMORY CRASHES WHILE PARSING.  So again my fault. Can't understand that I may have a completely different problem than the rote fixes they always deal with. SPECIAL PROBLEMS!

I've run bitcoin QT alone at LEAST 4 times! I get on Debug window> all blockchains done> but adding individual transaction one at time for hours,> ask what to do NO reply!! I do need my computer ( which by the way has NO OTHER PROBLEMS) for other things than running block-chains day in day out.

Yes, I know that all are purr-fect on programming side when GOATPIG started the rant thing about how bad HE was treated after he told me He could couldn't read my message> and cares less about my brain trauma and why sometimes I have problems assembling things. I could have been blown up in Afghanistan for all he knows. And states he could care less. That's OK cause he's GOD and it is ME that put everything on wrong footing!

I might just start over from paper it could be very long and time consuming but it hasn't been a cake walk so far.

Now I am told to go get another program probably pay for it and learn it where they probably know it backwards and forwards already. i WILL GET CHEWED OUT FOR NOT KNOWING THAT ALSO. I  thank them but my side is far harder, so far.

I'm told it is so simple (yes to run) when I am SURE it is their ONLY job. It was when it was stable and running NOT so now. I know I'm dumb they are smart I accept that, but I would bet you $500 they wouldn't be worth a damn in my job.

Thank you now that we have learned the truth and accept it lets go on. I'll do my best can everyone else?

Have you deleted the block chain and started from scratch as I suggested? It seems that you most likely have corrupted block chain data, which is a common problem for people trying to get Armory up and running. The reason you have corrupted block chain data is because there is something wrong with your system. I don't care if it sends emails and browses the web correctly, Bitcoin Core will bring semi-functional hardware to it's knees. How do I know this? I've been running it for 6 years on several different machines ranging from top of the line to budget. Bitcoin Core is practically a stress test on your hardware and will find out rather quickly if you have an issue. That said, thousands of people successfully use Bitcoin Core and Armory on a daily basis. Considering that, there are relatively few threads where users have as much difficulty as you've expressed here. Consider also that half of those issues come from the fact that Bitcoin Core must first be working properly for Armory to even have a chance.

I don't really understand why you are flipping out at the people who are attempting to walk you through this issue step by step. You obviously have difficulty communicating, yet you get angry when someone asks you to be more clear and concise. It's not our fault that you have health issues, perhaps you should have let everyone know from the very start that communication might be difficult and ask that everyone please bear with your attempts. Getting pissed and tossing around insults isn't going to do you a lot of favors in getting further assistance. I've read your post several times and I still can't make sense of it. How are people supposed to provide help when they can't even understand what you are saying?

I'm going to reiterate this very important point. Being successful with Bitcoin requires quite a high bar when it comes to user responsibility. These tools work, they simply may take some extra tweaking depending on your particular system. And there are millions of variations of PC hardware in the world along with a multitude of operating systems. The software isn't going to work perfectly for every user every time. Everything you are using to attempt to access your private keys is still beta software that was provided to you free of charge. Perhaps you need to modify your expectations slightly.

Finally, at any point in time you could have simply extracted the private keys from Armory in offline mode and imported them into a wallet which does not require the entire block chain to use. I strongly recommend this path for you.

If you aren't the sole controller of your private keys, you don't have any bitcoins.
SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 19, 2016, 08:35:03 AM
Last edit: December 19, 2016, 09:24:04 AM by SamSpade2
 #37

Remember my questions are legitimate to make sure you have told all and assumed nothing and I am on the correct path.

Here is what I would do to simplify things and almost guarantee a working result.

1. Make sure you have backups of your wallet files.

So what is the exact path of wallet files and names of all I need? I looked for pointer in Armory for them couldn't find and wasn't told?

Is it single file, path with many, DB etc? This is single file with my wallet name I found is this it? >armory_2bFXcxRew__old.wallet

Terms are not consistant, you can
Export: Trasactions
           Log files
           Wallets
           Watching only wallets
Import:
         Private Key address
         Wallet or Restore
         Import sweep private keys

Never explains how to Export private keys or info that you have to have to import.

          
2. Remove everything Bitcoin related on your PC. Uninstall Armory and Core and delete all associated folders entirely.

All bolckchains I have loaded even if duplicates? Used to use 32 bit switched to 64 long ago.

3. Install the latest version of Bitcoin Core and let it sync with the network. Forget about Armory until Bitcoin Core is functioning properly and has the most up to date block.

So what is the indicator it's done (since I've never use bitcoin but only Armory, also an assumption I know). Through debug screen, and what if so, what to look for.

My blockchain on bitcoit QT file seems done, only memory pool acquiring data.

Maybe only check mark at bottom right turning green.  Is memory pool local indication or online and how does it relate? Does it EVER quit and settle down? I assume it is continuing on small transactions all over globe and is informational only. If not what to look for?

What is maximum CPU should I expect to run, and how long with 2 core and 2 Gig sec ISP system so I'll have an idea.


4. Install the latest version of Armory, start it and disable autobitcoind management. Shut it down, copy your wallet file to the appropriate location and then restart Armory and let it do it's thing.

Wallet file location is same as previous

By the way my major was EE and been on 31 years since Telex 120 Baud, built systems with IRQ etc. and know OS is fine. I have experienced support problems that journey throughout. We actually could TALK to people and figure it out without misunderstandings instead of text and Email so their was ACTUAL interaction. Talked to McAfee, knew of Gates when he was in Albuquerque through a buddy on arpanet at Scandia Labs and had many friends down there.

 It has always been operator error and not bad programs NONE  admitted poor support or programming. Not saying this case is that. A person cannot keep up with all the changes nowdays to many and too fast! Would like to go back to Linux box but no time to do so. My SSD driver from Intell won't allow it. Will update system early next year.

You seem most level headed. PS you missed all the personals with numbered replies and questions as above. Thanks
Holliday
Legendary
*
Offline Offline

Activity: 1120
Merit: 1009



View Profile
December 19, 2016, 12:36:20 PM
 #38

Please read my entire reply before continuing.

Remember my questions are legitimate to make sure you have told all and assumed nothing and I am on the correct path.

Here is what I would do to simplify things and almost guarantee a working result.

1. Make sure you have backups of your wallet files.

So what is the exact path of wallet files and names of all I need? I looked for pointer in Armory for them couldn't find and wasn't told?

Is it single file, path with many, DB etc? This is single file with my wallet name I found is this it? >armory_2bFXcxRew__old.wallet

It is a single file. Yes, that is an Armory wallet file. Unless you've changed the default behavior, on a windows OS, Armory wallet files are located at C:/Users/*yourusername*/AppData/Roaming/Armory. Every file in that folder with the file name extension ".wallet" is a wallet file which you should back up. If you lose this file, you will never access your bitcoins (unless you have back ups of course).

2. Remove everything Bitcoin related on your PC. Uninstall Armory and Core and delete all associated folders entirely.

All bolckchains I have loaded even if duplicates? Used to use 32 bit switched to 64 long ago.

Uninstall Armory. Uninstall Bitcoin Core.

Browse to C:/Users/*yourusername*/AppData/Roaming and delete the following two folders: "Bitcoin" and "Armory".

What makes you think that you have duplicate block chains? The block chain is over 90GB in size and there is no reason for you to have a duplicate.

3. Install the latest version of Bitcoin Core and let it sync with the network. Forget about Armory until Bitcoin Core is functioning properly and has the most up to date block.

So what is the indicator it's done (since I've never use bitcoin but only Armory, also an assumption I know). Through debug screen, and what if so, what to look for.

My blockchain on bitcoit QT file seems done, only memory pool acquiring data.

Maybe only check mark at bottom right turning green.  Is memory pool local indication or online and how does it relate? Does it EVER quit and settle down? I assume it is continuing on small transactions all over globe and is informational only. If not what to look for?

What is maximum CPU should I expect to run, and how long with 2 core and 2 Gig sec ISP system so I'll have an idea.

https://bitcoin.org/en/download

Choose your version and install it. Allow it past your firewall if your system asks.

It is finished syncing with the network when there is a check mark in the bottom right corner of the window. If you mouse over that check mark it will bring up a pop up which says "Up to date. Processed 444xxx blocks of transaction history."

Do not worry about the memory pool.

No, this software never stops until you shut it down. This is a full node on the Bitcoin network.

Your two core CPU is going to take ages to sync the block chain. I would imagine that it could take anywhere from 4 days to a full week of 100% uptime. Your computer may be extremely sluggish during that time.

Maintaining the Bitcoin block chain is not the easiest of tasks, especially on older consumer level hardware. This is why I've suggested that you extract your private keys from offline Armory and import them into a light wallet which does not require the entire block chain. It's either that or takes the steps required to achieve a greater understanding of Bitcoin as a whole, and possibly even purchase hardware suited for the task.

Armory is really designed for the online/offline wallet feature. If you aren't taking advantage of that feature and keeping your private keys on an air gapped machine dedicated to securing those keys, there really isn't a great reason for you to be using Armory in the first place. Armory is targeted more toward the advanced Bitcoin user who has a strong understanding of private keys, wallet files, block chains, signing offline transactions, etc.

If you feel like continuing with efforts to get Armory working, get Core synced with a fresh block chain and go from there.

Again, if you aren't storing your private keys on an air gapped machine (one not connected to any network), then I strongly suggest that you forget about Armory entirely and use a light wallet which does not require the entire block chain and two separate programs to use. If you plan to go this route, then you should be asking how to extract your private keys from your Armory wallet and import them into something more user friendly.

If you aren't the sole controller of your private keys, you don't have any bitcoins.
SamSpade2 (OP)
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
December 19, 2016, 08:14:03 PM
Last edit: December 19, 2016, 08:53:36 PM by SamSpade2
 #39

Thanks' very clear! I thought Armory made just the standalone bitcoinQT more secure when I started using it...at least that is the way I remember it being sold.

So in the state it is now even though it says updated I have 444184 Date Mon Dec 19 at 4:10 it doesn't check to say this block-chain is good? That one can be corrupted? At one info page ( or was told ) on CoreQT I read said checkmark turned green.

Duplicate blockchains where did I get that?....Said that in Armory or QT log file I sent one time that apparently no one read. It even said one was more suitable than other. Now I don't know if it split one into two or what but that was error in debug file.

I did ask how to:

Terms are not consistent, you can
Export: Transactions
           Log files
           Wallets
           Watching only wallets
Import:
         Private Key address
         Wallet or Restore
         Import sweep private keys

Never explains how to Export "private keys", not unless terms are changed, or info that you have so "private keys" can be imported.

Client= Armory  Previously said "Not you but others" but I thought computers were precise items. Couldn't bitcoinQT be considered a client as could Armory? If so why not use their individual names? Not trying to be combative just wondering on support  side if it would help?? How does one fix things when terms change, if they did.

I may just wait til I get my screamer laptop with Caby lake and 1060 at least. Then the limiting factor will be internet.
Holliday
Legendary
*
Offline Offline

Activity: 1120
Merit: 1009



View Profile
December 19, 2016, 09:02:38 PM
 #40

Thanks' very clear! I thought Armory made just the standalone bitcoinQT more secure when I started using it...at least that is the way I remember it being sold.

The reason Armory is more secure than Bitcoin Core (formerly BitcoinQt, yes it was renamed), is because Armory allows you to store your private keys (contained in your wallet file) on an air-gapped (not connected to the internet) machine while being able to create transactions with an online installation which you may then sign (via private keys) using the offline machine.

The fact that you apparently have no understanding about how any of that works makes me think that you should do a lot of reading if you want to learn to use Bitcoin securely.

So in the state it is now even though it says I have 44410 Date Mon Dec 19 at 4:10 it doesn't check to say this blackchain is good? That one can be corrupted?

It appears your block chain is synced or very close to synced, but since you've been having such difficulty getting Armory to run properly, there is a chance that parts of your block chain is corrupt. Yes, Bitcoin Core can run and appear to be fully functional while having some issues with block chain corruption.

Another reason that I've suggested a clean install of everything is that there are possibly some settings from a previous installation that are making things more difficult than they need to be. You could try using your current Bitcoin Core install, but start Armory from scratch again.

There is only so much help that can be provided over the internet as we do not have physical access to your machine. I suggested a clean slate because sometimes it has a better chance than trying to salvage something which simply refuses to work.

Said in Armory or QT log file I sent one time that apparently no one read.

Log files can only provide clues to the possible problem. They aren't necessarily a kill shot when it comes to finding the issue which is preventing you from getting everything working.

I did ask how to:

Terms are not consistent, you can
Export: Transactions
           Log files
           Wallets
           Watching only wallets
Import:
         Private Key address
         Wallet or Restore
         Import sweep private keys

Never explains how to Export private keys or info that you have to have to import.

Yes, there is plenty of information about how to do these things available on the internet. Have you looked at the Armory tutorials? Have you read any of the Bitcoin wiki? Expecting people to walk you through every individual step seems a bit much, don't you think? As I've said, Bitcoin requires a lot of user responsibility. While others can provide assistance with specific troubleshooting issues, learning to control your private keys is essential to using Bitcoin securely and something that one should learn on one's own.

http://www.bitcoinarmory.com/tutorials/

Client= Armory  Previously said "Not you but others" but I thought computers were precise items. Couldn't bitcoinQT be considered a client as could Armory? If so why not use their individual names? Not trying to be combative just wondering on support  side if it would help?? How does one fix things when terms change, if they did.

BitcoinQt (now renamed to Bitcoin Core) is indeed a standalone Bitcoin client. It is the reference implementation of Bitcoin and every user running it makes up the Bitcoin network which allows Bitcoin to function.

Armory is wallet software which requires a complete Bitcoin Core installation (it uses Core's block chain and network connectivity) in order to function properly.

Armory's creator (who is no longer associated with the project) wanted to make it easier for people to use Armory so he coded the Armory software to install and run Bitcoin Core (bitcoind) for the user. I personally feel that this was a mistake as Armory is better suited for the advanced user who should be able to run Core on their own. Armory controlling Bitcoin Core, as opposed to the user doing it himself, accounts for a large portion of the issues that come up when users are attempting to use Armory. This is why I suggested you start from scratch getting things running correctly one step at a time. Once Bitcoin Core is working properly, Armory typically functions without issue. Many of the issues that users have with "Armory" actually stem from the Bitcoin Core installation. Trying to troubleshoot both at the same time can be a nightmare and lead to a lot of frustration, as seen in this thread.

I simply can not stress enough that Bitcoin requires large amounts of individual user responsibility. It's up to the user to teach himself how to properly use the associated software to protect his private keys.

I may just wait til I get my screamer laptop with Caby lake and 1060 at least. Then the limiting factor will be internet.

Perhaps that is the best path. I advise you to do some reading and familiarize yourself with the inner workings of Bitcoin in the meantime (if you plan to use Bitcoin into the future). The most important aspect, which I think anyone using Bitcoin should have a firm grasp of, is how to control and secure your private keys.

Also, if you aren't going to use an offline machine for private key storage, there are better (yet far less secure) solutions to use as Bitcoin wallet software.

If you aren't the sole controller of your private keys, you don't have any bitcoins.
Pages: « 1 [2] 3 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!