Armory 0.95 is out - page 4. | Bitcointalksearch.org

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: OtisG on November 01, 2016, 06:11:22 PM

Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all.
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG

I have W7 x64 as well and also ran into a hitch when I upgraded to 0.13.1/0.95. The following steps somehow worked for me (YMMV):

1. Rename old Armory data folder (serves as backup).

2. Uninstall the previous version and install Armory 0.95 from scratch.

3. Start Armory 0.95 in Offline Mode and "Skip" creating a wallet. Change settings accordingly [File/Settings...] and save it. Close Armory.

4. Copy watchonly wallet files from the old Armory data folder to the new one.

5. Start Bitcoin-Qt and let it sync.

6. Start Armory 0.95 and let it build a new DB.

As long as you don't intend to move your Armory data folder to a new location (refer to an issue I presented earlier on this thread), 0.95 should be peachy for you from here on.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: OtisG on November 01, 2016, 07:27:57 PM

Quote from: achow101 on November 01, 2016, 07:11:25 PM

Quote from: OtisG on November 01, 2016, 07:08:18 PM

Sure - are you referring to uploading Armoryqt.exe.log ?

The file from File > Export Log File.

Got the file. What's the best way to get it to you. I don't see a file upload option among the icons under the reply option.
OtisG

Open the file in a text editor. Copy the contents to http://pastebin.com/. If it is too large, get as much as you can from the bottom. Then post the link to the paste here.

OtisG

newbie

Activity: 31

Merit: 0

Quote from: achow101 on November 01, 2016, 07:11:25 PM

Quote from: OtisG on November 01, 2016, 07:08:18 PM

Sure - are you referring to uploading Armoryqt.exe.log ?

The file from File > Export Log File.

Got the file. What's the best way to get it to you. I don't see a file upload option among the icons under the reply option.
OtisG

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: OtisG on November 01, 2016, 07:08:18 PM

Sure - are you referring to uploading Armoryqt.exe.log ?

The file from File > Export Log File.

OtisG

newbie

Activity: 31

Merit: 0

Sure - are you referring to uploading Armoryqt.exe.log ?

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: OtisG on November 01, 2016, 06:56:44 PM

Thanks for your quick reply!

I unchecked the management options. Launching Armory without Bitcoin Core management launches ArmoryDB which then crashes 5 seconds later.
Instead of that option, I've downgraded Armory back to 0.93.3 where I was before.

You should use 0.94.1 instead.

Can you provide the log file?

Quote from: OtisG on November 01, 2016, 06:56:44 PM

Are the Windows 7 related issues expected to be resolved in 0.95.1? I sure hope so. I have cold storage coin, so this is very important for me.

OtisG

It should be fixed. However, if this is a new issue, we need to know so that it can be fixed ASAP.

OtisG

newbie

Activity: 31

Merit: 0

Quote from: achow101 on November 01, 2016, 06:21:22 PM

Quote from: OtisG on November 01, 2016, 06:11:22 PM

Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all.
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG

Armory 0.95 build for Windows was messed up. You can downgrade to 0.94.1, grab the guardian.exe file from 0.94.1 and put it in the installation folder for Armory, or run Bitcoin Core without Armory management. To run without Armory management, start Armory and go to File > Settings and uncheck "Let armory manage bitcoin core". Then start Bitcoin Core and restart Armory.

Thanks for your quick reply!

I unchecked the management options. Launching Armory without Bitcoin Core management launches ArmoryDB which then crashes 5 seconds later.
Instead of that option, I've downgraded Armory back to 0.93.3 where I was before.

Are the Windows 7 related issues expected to be resolved in 0.95.1? I sure hope so. I have cold storage coin, so this is very important for me.

OtisG

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: OtisG on November 01, 2016, 06:11:22 PM

Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all.
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG

Armory 0.95 build for Windows was messed up. You can downgrade to 0.94.1, grab the guardian.exe file from 0.94.1 and put it in the installation folder for Armory, or run Bitcoin Core without Armory management. To run without Armory management, start Armory and go to File > Settings and uncheck "Let armory manage bitcoin core". Then start Bitcoin Core and restart Armory.

OtisG

newbie

Activity: 31

Merit: 0

Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all.
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: goatpig on October 31, 2016, 04:30:43 PM

The first line the db outputs in the terminal is the db log path. Double check against that and let me know.

Yes, that happens reliably. My description was inadequate: I tested the Db build using Whonix, and dbLog.txt was'n't created that test-run, but was created the next time I ran Armory. Because using the Linux tail command with dbLog.txt is the best way to view the Db build progress, I'm double certain that it wasn't created during that 1st test run, despite that being otherwise successful.

Quote from: goatpig on October 31, 2016, 04:30:43 PM

The progress bars were designed in 0.92 when the DB was much slower. I did not change anything to the underlying ETA code, just plugged it into the existing code. I will have overhaul that stuff at some point. Not a priority right now though.

Yep, I was expecting wacky behaviour, seeing as you warned us about that.

Quote from: goatpig on October 31, 2016, 04:30:43 PM

That and the other minor features that were not replicated in this version will be fixed in 0.95.2.

For now, I have one user reporting a crash. I am waiting on his input in order to fix that one, then I'll release 0.95.1

Looking forward to it all. Hail goatpig, etc.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Great, I just realized my response was never posted, thanks to the DDoS episode.

Quote

A few minor things; dbLog.txt didn't get created while I was testing the Db building with Whonix/Qubes.

The first line the db outputs in the terminal is the db log path. Double check against that and let me know.

Quote

That drew my attention to the progress bars: headers stage is too indecisive/imprecise in it's estimates, and the Tx hash resolution stage has a kind of crazy strobe effect as well as supremely eccentric estimates (started at 10 seconds, stayed there for 10 seconds, stayed at 1 second for a minute etc).

The progress bars were designed in 0.92 when the DB was much slower. I did not change anything to the underlying ETA code, just plugged it into the existing code. I will have overhaul that stuff at some point. Not a priority right now though.

Quote

One last minor: uncommented tx's used to inherit the label of the address they're associated with instead of just being fully blank.

That and the other minor features that were not replicated in this version will be fixed in 0.95.2.

For now, I have one user reporting a crash. I am waiting on his input in order to fix that one, then I'll release 0.95.1

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: goatpig on October 30, 2016, 02:58:39 PM

Quote from: Carlton Banks on October 30, 2016, 11:37:58 AM

First pick from a multi input address respects the users choice (which is fixed compared to previous behaviour). Changing one's mind after hitting accepts reveals the bug, and it seems similar to before: all the inputs from the address of the intended selected input appear to get selected, but quickly scrolling down the list shows that not quite all the inputs in fact are selected. It seems that random inputs (only at the same address as any inputs picked originally by the user) are left unselected, but whether that does really conform to some pattern I can't say.

Both these should be fixed in dev, please test and report.

You've got the coin control fixed, given it a fair amount of testing now. Wallet filter in the main tx window is broken for me.

A few minor things; dbLog.txt didn't get created while I was testing the Db building with Whonix/Qubes. That drew my attention to the progress bars: headers stage is too indecisive/imprecise in it's estimates, and the Tx hash resolution stage has a kind of crazy strobe effect as well as supremely eccentric estimates (started at 10 seconds, stayed there for 10 seconds, stayed at 1 second for a minute etc). One last minor: uncommented tx's used to inherit the label of the address they're associated with instead of just being fully blank.

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: goatpig on October 30, 2016, 03:31:09 PM

https://github.com/goatpig/BitcoinArmory/blob/dev/windowsbuild/Windows_build_notes.md

There are some minimal instructions here if you'd like to spend the day battling it =D

I'm very interested to learn once I can devote some time to it. Currently, I'm hardly getting by just trying to re-familiarize myself with a Linux install I tinkered around with late last year (a futile attempt to learn) so I can figure out how to generate wallet addresses for that new over-hyped/overpriced crypto that just launched whose initial price dropped about 70% already. I'm hoping to fire up my old boxes and mine some hoping to catch the tail end of the dump. Grin

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

https://github.com/goatpig/BitcoinArmory/blob/dev/windowsbuild/Windows_build_notes.md

There are some minimal instructions here if you'd like to spend the day battling it =D

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: goatpig on October 30, 2016, 03:14:32 PM

Quote from: visdude on October 30, 2016, 03:08:19 PM

Sorry, I'm not familiar with the procedure. Do you mean test for the bug in the next release and report accordingly? Please elaborate.

I mean pull the code from dev, build from source and test for the bug again. If you can't build from source, you're left with crossing your fingers and waiting for the next build.

It would have to be the latter (crossing fingers) as I don't know how to pull code from dev let alone build from source.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: visdude on October 30, 2016, 03:08:19 PM

Sorry, I'm not familiar with the procedure. Do you mean test for the bug in the next release and report accordingly? Please elaborate.

I mean pull the code from dev, build from source and test for the bug again. If you can't build from source, you're left with crossing your fingers and waiting for the next build.

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: goatpig on October 30, 2016, 02:58:39 PM

Both these should be fixed in dev, please test and report.

Sorry, I'm not familiar with the procedure. Do you mean test for the bug in the next release and report accordingly? Please elaborate.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: Carlton Banks on October 30, 2016, 11:37:58 AM

First pick from a multi input address respects the users choice (which is fixed compared to previous behaviour). Changing one's mind after hitting accepts reveals the bug, and it seems similar to before: all the inputs from the address of the intended selected input appear to get selected, but quickly scrolling down the list shows that not quite all the inputs in fact are selected. It seems that random inputs (only at the same address as any inputs picked originally by the user) are left unselected, but whether that does really conform to some pattern I can't say.

Quote from: visdude on October 30, 2016, 02:53:19 PM

Correct. The DB won't put its log file (dblog.txt) in the explicit datadir (which I usually refer to as the alternate location/directory/path) as specified in the arg. Furthermore, if it cannot detect an "Armory" folder still at the default location to put the dblog.txt file into, that's when it hangs. It requires it.

Both these should be fixed in dev, please test and report.

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: goatpig on October 30, 2016, 10:13:57 AM

Quote from: visdude on October 30, 2016, 09:57:17 AM

With the above setup, ArmoryQt runs just fine and properly spawns ArmoryDB but with a caveat: an "Armory" folder must still exist at the default location (i.e. C:\Users\username\AppData\Roaming\Armory) because it insists on having the "dblog.txt" file reside there. Otherwise, it hangs as before.

That's quite a different situation here from what I had understood. Are you saying the DB won't put its log file in the explicit datadir? That's a bug, not a design choice. I'll try to reproduce on my end and fix it for the point release.

Correct. The DB won't put its log file (dblog.txt) in the explicit datadir (which I usually refer to as the alternate location/directory/path) as specified in the arg. Furthermore, if it cannot detect an "Armory" folder still at the default location to put the dblog.txt file into, that's when it hangs. It requires it.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: goatpig on October 29, 2016, 03:52:38 PM

Pushed the fixes for 0.95.1 in dev. People who've had issues, please build and try. Looking to release tomorrow or Monday.

Whonix is fixed for me. Coin control is improved, but not fixed.

First pick from a multi input address respects the users choice (which is fixed compared to previous behaviour). Changing one's mind after hitting accepts reveals the bug, and it seems similar to before: all the inputs from the address of the intended selected input appear to get selected, but quickly scrolling down the list shows that not quite all the inputs in fact are selected. It seems that random inputs (only at the same address as any inputs picked originally by the user) are left unselected, but whether that does really conform to some pattern I can't say.

Topic: Armory 0.95 is out - page 4. (Read 9261 times)