Bitcoin Forum
February 11, 2016, 01:02:20 PM *
News: Latest stable version of Bitcoin Core: 0.11.2 [Torrent]
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 ... 90 »
501  Bitcoin / Armory / Re: Users experiencing the BDM error message on: March 05, 2015, 06:07:59 PM
All 3 attempts made in BDM mode. bitcoind seemed to choke on the first attempt, despite 30 minutes running time. Second attempt succeeded. 3rd attempt died, and it did so suggesting it hadn't committed the new block height somehow, as it was indicating the same number of catch up blocks as the 2nd attempt (which was also typical behaviour for 0.93.0)

I fixed the block catch up issue yesterday. You can pull bugfix if you want to try that. Ima push a change in a few hours to cover for this issue too. Maybe you want to wait till then to try out both changes.
502  Bitcoin / Armory / Re: [ANN] Armory 0.93 Official Release on: March 05, 2015, 03:31:30 PM
Does the comment reappear on the next start?
503  Bitcoin / Armory / Re: Users experiencing the BDM error message on: March 05, 2015, 03:30:15 PM
Been testing 0.93.0.70, and I'm managing to trigger the "BDM error!" dialog still. Logs?

Yes please.
504  Bitcoin / Armory / Re: [ANN] Armory 0.93 Official Release on: March 04, 2015, 10:17:55 PM
First, the OS X version does not support Armory management of bitcoind, so I'm stuck with the BitcoinQt approach.

I'm aware of that but non Mac users read these threads too so I use platform agnostic statements whenever possible.

Quote
Second, I guess I can just wait till the blockchain downloads, and then have Armory build its db afterwards. But is there some reason in principle that Armory cannot recognize incomplete blocks? During normal operation (i.e. after most of the blockchain is downloaded), Bitcoin-Qt is periodically getting new blocks, so there is a short window every 10 minutes when the situation is similar. Also during normal operation, I assume Armory periodically scans for new blocks (after Bitcoin-Qt tells it a new one has arrived), to extend its own database and display fresh data to the user. When it does this, there are probably no new partial blocks yet (because the next one wouldn't come for at least 10 minutes). But there is a small chance that two blocks are found almost simultaneously, right? In which case, right after Bitcoin-Qt tells armory it's ok to update its db, it might start downloading other partial blocks from random peers. So why couldn't the same "missing block data" cause crashes even after the initial bootstrap? Or are there certain state guarantees about ~/.bitcoin/blocks that are satisfied *except* during the initial bootstrap?

Core behaves differently when it verifies blocks through milestones hashes as opposed to checking each transaction sig. The usual behavior is checking the sigs, which is slow and doesn't trigger empty block data. Milestone hash checking is a lot more aggressive with disk writes and will resort to the headers first approach as much as possible. Also, you don't want to be heavily reading and writing the same data concurrently.

Quote
Regardless, the documentation (for all versions, but especially OS X since there's no choice) should probably be clarified to inform the user who is manually running bitcoin-qt that they must not run Armory until the blockchain is "fully" downloaded.

Too much has changed in this release so I don't expect most documentation to be up to date yet. Headers first changed some significant things under the hood for us and we might be more and more motivated to resort to blocks over P2P.

As for letting BitcoinQt run its course before starting Armory, it wasn't a requirement up until Core 0.10, but rather a good practice. Better let the first finish before moving on to the second.
505  Bitcoin / Armory / Re: Users experiencing the BDM error message on: March 04, 2015, 09:36:26 PM
When you update the git, do I need to make clean && make or just make will do to incorporate the updates?

Some changes are Python only and can get away with not rebuilding, but it's a general guideline to make clean & make every time to you pull, regardless of the changes.
506  Bitcoin / Armory / Re: [ANN] Armory 0.93 Official Release on: March 04, 2015, 03:42:01 PM
Understandable. And in that, Armory works, and better than ever. Significant improvements in speed can be felt in steps 2 and 3. There is nothing that can be done about bitcoind's slow startup is there? It's a problem with bitcoind not Armory.

Something can and will be done in the next version. It won't make it instant but it should prevent it from redownloading the last few blocks over and over.
507  Bitcoin / Armory / Re: [ANN] Armory 0.93 Official Release on: March 04, 2015, 03:07:35 PM
Done rebuilding. For the first time, this version of Armory 0.93 successfully completes building the DB without progress unresponsiveness or non-specific hangups.

I must however make a note about memory usage. While I do understand from other threads that Armory doesn't actually gobble up all the memory and merely softly asks the OS to pre-commit space for it and release it at any moment if another program needs it, I still find it untennable to constantly run a program in the background that makes my gauging of free RAM unreliable. I don't want to have to use my PC in a manner where task manager is continually showing 99% RAM being used up, preventing me from actually seeing when a program does indeed get out of hand. Since I've seen no other program ever do this, I'd find it reasonable that Armory could scale down the practice too since I really don't see it needing to commit so much RAM in the first place.

EDIT: Upon a 2nd startup it seems to only do this RAM thing when it first builds the Armory DB, or at least, because the DB isn't that far behind it does it to a significantly less extent on future startups. It's still weird and, if Armory does think it's nice to have this type of DB lookup convenience, I don't think it should do it in a manner that's visible to the user(task manager).

Btw Armory's startup scanning and reach of full functionality is significantly faster than before. Cheers!

Next version will take it easier on the RAM front. For now I'm more interested in stability.
508  Bitcoin / Armory / Re: [ANN] Armory 0.93 Official Release on: March 04, 2015, 03:06:08 PM
sflicht:

You either let Armory manage bitcoind for you, or you start BitcoinQt manually and let it sync fully before you start Armory. Instead, you are starting BitcoinQt and letting Armory run on top of a blocks folder that Core is still indexing through milestones hashes, which guarantees you'll run into missing block data. Let BitcoinQt do its thing then start Armory.
509  Bitcoin / Armory / Re: Armory crashing when I import my wallet on: March 04, 2015, 05:01:46 AM
For now try the new build with the fresh fixes, but your logs did not indicate anything that would lead me to believe these fixes will cover your issue. At any rate, try and it report here.
510  Bitcoin / Armory / Re: [ANN] Armory 0.93 Official Release on: March 03, 2015, 10:54:19 PM
It's an online machine, and I used the Armory Installer

No x86 online for 0.93. Go back to 0.92.3 and wait for the next release for x86

Odd, your website lists 0.93 for Ubuntu 12.04+ (32bit), I thought your binaries would be compatible... Smiley

I guess I'll just install it on my 64 bit machine

Yeah we forgot to rename all that stuff, sorry about that =(
511  Bitcoin / Armory / Re: Users experiencing the BDM error message on: March 03, 2015, 10:52:10 PM
If you want to forcefully trigger the issue, you can point Armory to a copy of the blockchain it wasn't sync'ed against. Core 0.10 chains will definitely trigger it.
Instead of doing that, I decided to see what would happen if I just deleted the most recent block file (blk00238.dat) entirely.

Turns out that Armory can't repair that.

That's an interesting approach. First of all Armory is not supposed to recover from that. It expects to always start at the same or higher height than it saw on its last run. If it fails to find its highest known block, that's an acceptable condition to fail and ask for a factory reset. I don't think it should step away from that assumption at the risk of rolling back history or failing to detect newly available blocks, which are issues harder to identify.

The weird thing about your log is that you say you deleted the most recent block file, yet Armory detected 239 available block files, which deserves an investigation on its own.
512  Bitcoin / Armory / Re: Armory crashing when I import my wallet on: March 03, 2015, 08:28:41 PM
Log says it's working currently
513  Bitcoin / Armory / Re: Users experiencing the BDM error message on: March 03, 2015, 06:52:15 PM
Also have not been a been able to trigger a repair log entry.

Everything just works so far.

Also have not been a been able to trigger a repair log entry.

Everything just works so far.

As long as it works I'm happy. If you want to forcefully trigger the issue, you can point Armory to a copy of the blockchain it wasn't sync'ed against. Core 0.10 chains will definitely trigger it.
514  Bitcoin / Armory / Re: Armory crashing when I import my wallet on: March 03, 2015, 06:34:14 PM
Delete your log files and Armory's databases folder. Start Armory with your wallet loaded from the start and let it go all the way, then post your log files.
515  Bitcoin / Armory / Re: Users experiencing the BDM error message on: March 03, 2015, 05:23:42 PM
bump
516  Bitcoin / Armory / Re: Armory crashing when I import my wallet on: March 03, 2015, 02:48:49 PM
I need to see armoryccplog.txt
517  Bitcoin / Armory / Re: HW1 Wallet Support? on: March 02, 2015, 10:00:53 PM
Will support for HW1 be eventually added in the near future?

Yeah that's the plan, but we have to get this new DB under control first.
518  Bitcoin / Armory / Re: Armory - Discussion Thread on: March 02, 2015, 09:59:30 PM
I think I'm all good now after updating to fixes branch. Thanks!

Post that in the other thread so I can keep track =)
519  Bitcoin / Armory / Re: [ANN] Armory 0.93 Official Release on: March 02, 2015, 09:58:32 PM
It's an online machine, and I used the Armory Installer

No x86 online for 0.93. Go back to 0.92.3 and wait for the next release for x86
520  Bitcoin / Armory / Re: Armory crashing when I import my wallet on: March 02, 2015, 09:57:52 PM
Ok, that seemed to do the trick. Armory is connecting and building the databases now. However, Armory is still insisting on building the databases in the default folder "C:\Users\owner\appdata\roaming\Armory". I have changed the folder in the settings menu to no avail. Is there a similar argument that will change the default database folder?

Can't set that in the setting menu. use --dbdir instead
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 ... 90 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!