Armory - Discussion Thread

[koeppelmann]

Thanks for the response. I build the Bitcoin BD again but I still have the problem. I can not use Armory at all - while starting it always crashes.

It seems that you are and the problem is related to QT:

Code:

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff873074de mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff8730664f mach_msg + 55
2   com.apple.CoreFoundation      	0x00007fff8f6b4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      	0x00007fff8f6b437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      	0x00007fff8f6b3bd8 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox           	0x00007fff8df3d56f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox           	0x00007fff8df3d2ea ReceiveNextEventCommon + 431
7   com.apple.HIToolbox           	0x00007fff8df3d12b _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit              	0x00007fff8a7578ab _DPSNextEvent + 978
9   com.apple.AppKit              	0x00007fff8a756e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
10  com.apple.AppKit              	0x00007fff8a74caf3 -[NSApplication run] + 594
11  QtGui                         	0x00000001040d684a QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 538
12  QtCore                        	0x000000010366aaad QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 477
13  QtCore                        	0x000000010366dcc7 QCoreApplication::exec() + 199
14  QtGui.so                      	0x00000001038d5a10 meth_QApplication_exec_(_object*, _object*) + 80
15  org.python.python             	0x00000001000b07f6 PyEval_EvalFrameEx + 20486
16  org.python.python             	0x00000001000ab57d PyEval_EvalCodeEx + 1725
17  org.python.python             	0x00000001000aaeb6 PyEval_EvalCode + 54
18  org.python.python             	0x00000001000d43e4 PyRun_FileExFlags + 164
19  org.python.python             	0x00000001000d3f61 PyRun_SimpleFileExFlags + 769
20  org.python.python             	0x00000001000eafd7 Py_Main + 3063
21  Python                        	0x0000000100000e55 0x100000000 + 3669
22  Python                        	0x0000000100000d71 0x100000000 + 3441

Yes, I do use the sleep function often - basically always, I never shut my mac down. But i also started to restart it, start BitcoinQt, start Amory -> same problem.

[1713572059]

1713572059

[doug_armory]

Hello. Is thread 0 the one that actually crashed? It could be a different one. The crash report will always say which one it is.

[Searinox]

Armory Version 0.93.2
Bitcoind version 0.11.0 Running UNMANAGED by Armory
Builds: both x64
OS: Windows 7 x64 SP1 + all recent updates

Internet was down for a whole day and when it picked up again, bitcoind began quickly catching up with the network again, at first Armory ate the new blocks just fine but then it threw a "missing headers" error. When I restarted it rescanned the entire history, then there were no more issues.

The only thing I have in the log is this:

Code:

2015-08-16 11:16 (INFO) -- ArmoryQt.py:6249 - New Block! : 369959
2015-08-16 11:16 (INFO) -- ArmoryQt.py:6257 - Current block number: 369959
2015-08-16 11:16 (INFO) -- ArmoryQt.py:6249 - New Block! : 369960
2015-08-16 11:16 (INFO) -- ArmoryQt.py:6257 - Current block number: 369960
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1076 - C++ block utilities loaded successfully
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1186 - 
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1187 - 
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1188 - 
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1189 - 

11:16 is when it crashed, 11:30 is when I came back to the PC to notice the crash and restarted it.

[koeppelmann]

Hello. Is thread 0 the one that actually crashed? It could be a different one. The crash report will always say which one it is.

It is thread 5:

Code:

Process:               Python [9657]
Path:                  /Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Python [9657]
User ID:               501

Date/Time:             2015-08-16 13:19:16.916 -0700
OS Version:            Mac OS X 10.10.5 (14F27)
Report Version:        11
Anonymous UUID:        0342B016-FFD5-109B-1719-DF5FD2B7FFA6

Sleep/Wake UUID:       CBCA24F7-E0BC-4954-86F2-65CC9B033F86

Time Awake Since Boot: 86000 seconds
Time Since Wake:       10000 seconds

Crashed Thread:        5

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       0x000000000000000a, 0x0000000ae33c8001

VM Regions Near 0xae33c8001:
    mapped file            000000011f02f000-0000000adcead000 [ 39.0G] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
--> mapped file            0000000adcead000-0000000ae5273000 [131.8M] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
    MALLOC_LARGE           0000000ae5273000-0000000ae52f3000 [  512K] rw-/rwx SM=PRV  

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff90b614de mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff90b6064f mach_msg + 55
2   com.apple.CoreFoundation      	0x00007fff913d4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      	0x00007fff913d437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      	0x00007fff913d3bd8 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox           	0x00007fff8fe2456f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox           	0x00007fff8fe242ea ReceiveNextEventCommon + 431
7   com.apple.HIToolbox           	0x00007fff8fe2412b _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit              	0x00007fff92b018ab _DPSNextEvent + 978
9   com.apple.AppKit              	0x00007fff92b00e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
10  com.apple.AppKit              	0x00007fff92af6af3 -[NSApplication run] + 594
11  QtGui                         	0x00000001040d684a QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 538
12  QtCore                        	0x000000010366aaad QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 477
13  QtCore                        	0x000000010366dcc7 QCoreApplication::exec() + 199
14  QtGui.so                      	0x00000001038d5a10 meth_QApplication_exec_(_object*, _object*) + 80
15  org.python.python             	0x00000001000b07f6 PyEval_EvalFrameEx + 20486
16  org.python.python             	0x00000001000ab57d PyEval_EvalCodeEx + 1725
17  org.python.python             	0x00000001000aaeb6 PyEval_EvalCode + 54
18  org.python.python             	0x00000001000d43e4 PyRun_FileExFlags + 164
19  org.python.python             	0x00000001000d3f61 PyRun_SimpleFileExFlags + 769
20  org.python.python             	0x00000001000eafd7 Py_Main + 3063
21  Python                        	0x0000000100000e55 0x100000000 + 3669
22  Python                        	0x0000000100000d71 0x100000000 + 3441

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        	0x00007fff90b67232 kevent64 + 10
1   libdispatch.dylib             	0x00007fff94516a6a _dispatch_mgr_thread + 52

Thread 2:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        	0x00007fff90b663fa __select + 10
1   libsystem_pthread.dylib       	0x00007fff91c5305a _pthread_body + 131
2   libsystem_pthread.dylib       	0x00007fff91c52fd7 _pthread_start + 176
3   libsystem_pthread.dylib       	0x00007fff91c503ed thread_start + 13

Thread 3:
0   libsystem_kernel.dylib        	0x00007fff90b614de mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff90b6064f mach_msg + 55
2   com.apple.CoreFoundation      	0x00007fff913d4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      	0x00007fff913d437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      	0x00007fff913d3bd8 CFRunLoopRunSpecific + 296
5   com.apple.AppKit              	0x00007fff92bc956b _NSEventThread + 137
6   libsystem_pthread.dylib       	0x00007fff91c5305a _pthread_body + 131
7   libsystem_pthread.dylib       	0x00007fff91c52fd7 _pthread_start + 176
8   libsystem_pthread.dylib       	0x00007fff91c503ed thread_start + 13

Thread 4:
0   libsystem_kernel.dylib        	0x00007fff90b663fa __select + 10
1   org.python.python             	0x00000001000b07f6 PyEval_EvalFrameEx + 20486
2   org.python.python             	0x00000001000ab57d PyEval_EvalCodeEx + 1725
3   org.python.python             	0x00000001000364dc function_call + 364
4   org.python.python             	0x0000000100010ca3 PyObject_Call + 99
5   org.python.python             	0x00000001000aecbd PyEval_EvalFrameEx + 13517
6   org.python.python             	0x00000001000ab57d PyEval_EvalCodeEx + 1725
7   org.python.python             	0x00000001000b3129 fast_function + 297
8   org.python.python             	0x00000001000ae995 PyEval_EvalFrameEx + 12709
9   org.python.python             	0x00000001000b30c2 fast_function + 194
10  org.python.python             	0x00000001000ae995 PyEval_EvalFrameEx + 12709
11  org.python.python             	0x00000001000b30c2 fast_function + 194
12  org.python.python             	0x00000001000ae995 PyEval_EvalFrameEx + 12709
13  org.python.python             	0x00000001000ab57d PyEval_EvalCodeEx + 1725
14  org.python.python             	0x00000001000364dc function_call + 364
15  org.python.python             	0x0000000100010ca3 PyObject_Call + 99
16  org.python.python             	0x000000010001de16 instancemethod_call + 166
17  org.python.python             	0x0000000100010ca3 PyObject_Call + 99
18  org.python.python             	0x00000001000b288d PyEval_CallObjectWithKeywords + 93
19  org.python.python             	0x00000001000ed1a6 t_bootstrap + 70
20  libsystem_pthread.dylib       	0x00007fff91c5305a _pthread_body + 131
21  libsystem_pthread.dylib       	0x00007fff91c52fd7 _pthread_start + 176
22  libsystem_pthread.dylib       	0x00007fff91c503ed thread_start + 13

Thread 5 Crashed:
0   _CppBlockUtils.so             	0x0000000104e3a3c6 StoredHeadHgtList::unserializeDBValue(BinaryRefReader&) + 470
1   _CppBlockUtils.so             	0x0000000104e3a694 StoredHeadHgtList::unserializeDBValue(BinaryDataRef) + 52
2   _CppBlockUtils.so             	0x0000000104e157b3 LMDBBlockDatabase::getStoredHeadHgtList(StoredHeadHgtList&, unsigned int) + 179
3   _CppBlockUtils.so             	0x0000000104e1494e LMDBBlockDatabase::putBareHeader(StoredHeader&, bool) + 302
4   _CppBlockUtils.so             	0x0000000104e94e25 Blockchain::putNewBareHeaders(LMDBBlockDatabase*) + 309
5   _CppBlockUtils.so             	0x0000000104e4e131 BlockDataManager_LevelDB::loadDiskState(std::__1::function<void (BDMPhase, double, unsigned int, unsigned int)> const&, bool) + 2945
6   _CppBlockUtils.so             	0x0000000104ea5af2 BlockDataManagerThread::run() + 578
7   _CppBlockUtils.so             	0x0000000104ea57f9 BlockDataManagerThread::thrun(void*) + 9
8   libsystem_pthread.dylib       	0x00007fff91c5305a _pthread_body + 131
9   libsystem_pthread.dylib       	0x00007fff91c52fd7 _pthread_start + 176
10  libsystem_pthread.dylib       	0x00007fff91c503ed thread_start + 13

Thread 6:

[doug_armory]

It is thread 5:

Code:

Thread 5 Crashed:
0   _CppBlockUtils.so             	0x0000000104e3a3c6 StoredHeadHgtList::unserializeDBValue(BinaryRefReader&) + 470
1   _CppBlockUtils.so             	0x0000000104e3a694 StoredHeadHgtList::unserializeDBValue(BinaryDataRef) + 52
2   _CppBlockUtils.so             	0x0000000104e157b3 LMDBBlockDatabase::getStoredHeadHgtList(StoredHeadHgtList&, unsigned int) + 179
3   _CppBlockUtils.so             	0x0000000104e1494e LMDBBlockDatabase::putBareHeader(StoredHeader&, bool) + 302
4   _CppBlockUtils.so             	0x0000000104e94e25 Blockchain::putNewBareHeaders(LMDBBlockDatabase*) + 309
5   _CppBlockUtils.so             	0x0000000104e4e131 BlockDataManager_LevelDB::loadDiskState(std::__1::function<void (BDMPhase, double, unsigned int, unsigned int)> const&, bool) + 2945
6   _CppBlockUtils.so             	0x0000000104ea5af2 BlockDataManagerThread::run() + 578
7   _CppBlockUtils.so             	0x0000000104ea57f9 BlockDataManagerThread::thrun(void*) + 9
8   libsystem_pthread.dylib       	0x00007fff91c5305a _pthread_body + 131
9   libsystem_pthread.dylib       	0x00007fff91c52fd7 _pthread_start + 176
10  libsystem_pthread.dylib       	0x00007fff91c503ed thread_start + 13

Ah ha. That is definitely Armory code.

[goatpig]

Possibly some bad blocks. Try to sync the testnet chain, see if you get the same symptoms.

[koeppelmann]

It is thread 5:

Code:

Thread 5 Crashed:
0   _CppBlockUtils.so             	0x0000000104e3a3c6 StoredHeadHgtList::unserializeDBValue(BinaryRefReader&) + 470
1   _CppBlockUtils.so             	0x0000000104e3a694 StoredHeadHgtList::unserializeDBValue(BinaryDataRef) + 52
2   _CppBlockUtils.so             	0x0000000104e157b3 LMDBBlockDatabase::getStoredHeadHgtList(StoredHeadHgtList&, unsigned int) + 179
3   _CppBlockUtils.so             	0x0000000104e1494e LMDBBlockDatabase::putBareHeader(StoredHeader&, bool) + 302
4   _CppBlockUtils.so             	0x0000000104e94e25 Blockchain::putNewBareHeaders(LMDBBlockDatabase*) + 309
5   _CppBlockUtils.so             	0x0000000104e4e131 BlockDataManager_LevelDB::loadDiskState(std::__1::function<void (BDMPhase, double, unsigned int, unsigned int)> const&, bool) + 2945
6   _CppBlockUtils.so             	0x0000000104ea5af2 BlockDataManagerThread::run() + 578
7   _CppBlockUtils.so             	0x0000000104ea57f9 BlockDataManagerThread::thrun(void*) + 9
8   libsystem_pthread.dylib       	0x00007fff91c5305a _pthread_body + 131
9   libsystem_pthread.dylib       	0x00007fff91c52fd7 _pthread_start + 176
10  libsystem_pthread.dylib       	0x00007fff91c503ed thread_start + 13

Ah ha. That is definitely Armory code.

So any tipps what I can do? Currently I simply can't access the funds in my Armory wallet?

[goatpig]

Build ffreeze and try that instead.

[Moria843]

I've been playing around with a "Hive" wallet on my iPhone for small change. They don't allow you to see the private key. Is there a way I can monitor, or add a watch-only wallet to my other Armory wallets using only the public keys from the Hive wallet?

[Ente]

This comes up regularly, to add a public key/adress to your Armory wallet.
Currently it is not possible, because this would be an attack vector, where the user believes he received a payment, but in fact only sees a payment on an adress he doesn't control.
The next suggestion was to clearly highlight those adresses, but as of now, nothing like that is possible.

I, for one, would like that feature as well. I would create a watching-only wallet with interesting external adresses.
Oh, wait, the name "watch-only wallet" is already occupied for something similar, but completely different in Armory.. See the problems?

Ente

[Moria843]

Thanks for the explanation. Using my public addresses, I also use bitWallet on my iPhone to monitor the Armory wallets on my hot and cold computers. I never loaded any private keys to bitWallet so I can't spend the coins from bitWallet (except for those in a small spending wallet).

I like bitWallet for mobile monitoring because you can set it up to alert you for transactions. I always thought this was safe since even if my phone or bitWallet were compromised, only the small spending account would be at risk.

Now I'm wondering if this is safe to do, or am I missing something?

[Ente]

Technically it's safe, as there are no privkeys on your phone.
The attack vectors are, as so often, targeting the user. Tricking him to believe something was paid which wasn't (with somehow having the attackers watch-adresses added), or simply checking out the users watch-adresses-balance, and forcing him to give up the coins.
This will eventually be a problem, I suppose. That attackers find out the balance of someone, and simply use force to overcome any smart technical obstacle.
Oh, by the way, sadly, I own no bitcoins. At all.

Ente

[visdude]

I've been exploring and trying to set up my Windows-based online Armory (watch only) wallets in a Linux machine.

So far, Bitcoin Core was a breeze; setting up a different location for the blockchain database other than the default one is made easy as it is now an option during installation. I just copied the up-to-date Windows Bitcoin data over to the Linux location and didn't have to go through the complicated workaround outlined on the Armory support site (I did it for the my Windows Bitcoin Core and Armory installations). I was hoping that Armory would also have such option and allow me to just manually point it to the location of the Bitcoin data folder, wherever that might be.  Unfortunately, it doesn't. With the ever-increasing size of the Armory database along with the Bitcoin core blockchain data and thereby hogging precious SSD space exclusively reserved for system/app files, I thought this would already be an option in Armory (it already is in Bitcoin Core).

I hope that such an option would be incorporated in the next release. In the meantime, can anybody please advice me on a workaround so that I'll be able to define a different location for the Armory database/wallet files in the Linux machine with the intention of using my current Windows Armory database/wallet files with it (parallel setup)?

I am not very well-versed in Linux let alone its file system/structure...and Bash (not yet anyway). But as is obvious, I'm really trying to learn it as my trust in Windows is slowly but surely eroding day by day. Therefore, it is best to assume (for my sake) that I am completely a Linux virgin.

Lastly, my offline Armory is, of course, Windows-based (hopefully will someday be Linux). I assume that I could still use it to sign transactions generated by a Linux-based Armory, right?

Thanks in advance and apologies for the long tale.

[Carlton Banks]

Right click the Armory executable, find the tab (or whatever it is on Windows these days) where the target command line statement is. It should say something like "Armory.exe".

Append the argument "--satoshi-datadir=<your bitcoin core directory location here>" to the command. Should work.

[opentoe]

Right click the Armory executable, find the tab (or whatever it is on Windows these days) where the target command line statement is. It should say something like "Armory.exe".

Append the argument "--satoshi-datadir=<your bitcoin core directory location here>" to the command. Should work.

The Armory settings confused me a little, but you also need to add start up switches. Read this thread for some help.

https://bitcointalk.org/index.php?topic=1146925.0

[visdude]

Right click the Armory executable, find the tab (or whatever it is on Windows these days) where the target command line statement is. It should say something like "Armory.exe".

Append the argument "--satoshi-datadir=<your bitcoin core directory location here>" to the command. Should work.

Thanks for the quick reply.

That's what I did in the Windows installations as outlined in the workaround on the Armory support page and they have been working flawlessly ever since. The following are my Windows shortcut parameters for both executables:

Code:

"C:\Program Files\Bitcoin\bitcoin-qt.exe" -datadir="D:\Bitcoin"

Code:

"C:\Program Files (x86)\Armory\ArmoryQt.exe" --skip-announce-check --satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"

As I alluded earlier, I have no clue as to where I'd put the Armory shortcut parameter in the Linux system (I already got Bitcoin Core running with an alternative database location/directory as it was an option during the Linux Bitcoin Core installation).

[Carlton Banks]

Ah, with Linux, do this:

• Open bash/command line in your distro.
• sudo vi /usr/share/applications/bitcoin-qt.desktop

(or whatever the bitcoin labelled file is named, check using command: ls -l /usr/share/applications/ )

• Press i to begin editing (INSERT will appear at the bottom of the terminal window)
• Add the "--datadir=" line to the executable command
• Press i again
• Type :wq then press return

You can check that the changes were written to the file properly by repeating step 2

[visdude]

Ah, with Linux, do this:

• Open bash/command line in your distro.
• sudo vi /usr/share/applications/bitcoin-qt.desktop

(or whatever the bitcoin labelled file is named, check using command: ls -l /usr/share/applications/ )

• Press i to begin editing (INSERT will appear at the bottom of the terminal window)
• Add the "--datadir=" line to the executable command
• Press i again
• Type :wq then press return

You can check that the changes were written to the file properly by repeating step 2

But I already got Bitcoin Core running in the Linux machine with its ".bitcoin" data folder in a different drive/directory than the default one (defined through an option during installation which Armory doesn't afford).

I guess the crux of the matter of my inquiry is how do I tell Armory in the Linux machine to put/establish its ".armory" data folder in a different drive/directory than the default one as well. As a Linux noob, I haven't the foggiest. Is there a simple way for something that seems to be simple itself? Sorry for not being very clear about it initially.

[Carlton Banks]

I guess the crux of the matter of my inquiry is how do I tell Armory in the Linux machine to put/establish its ".armory" data folder in a different drive/directory than the default one as well. As a Linux noob, I haven't the foggiest. Is there a simple way for something that seems to be simple itself? Sorry for not being very clear about it initially.

Armory settings in the application. Two text boxes at the top of the layout, the lower one is where you specify Armory's folder.

[visdude]

I guess the crux of the matter of my inquiry is how do I tell Armory in the Linux machine to put/establish its ".armory" data folder in a different drive/directory than the default one as well. As a Linux noob, I haven't the foggiest. Is there a simple way for something that seems to be simple itself? Sorry for not being very clear about it initially.

Armory settings in the application. Two text boxes at the top of the layout, the lower one is where you specify Armory's folder.

Thanks for the tip. However, the text boxes are meant to define "Bitcoin Install Dir" (program) and "Bitcoin Home Dir" (data) which are handy in defining the respective non-default Bitcoin Core directories so that Armory is able to locate them and sync with Bitcore Core properly.

What I really need is to be able to establish or define the Linux Armory database folder (".armory") in a different drive with a lot more space instead of the default, limited-space system SSD. How do I go about doing that?