|
DB is tied to the ondisk blockchain. You can't move a DB around to a different copy of the chain. Also I don't think the meta entries for LMDB are even the same going from 64 to 32 bits. It's typically bound to the pointer size, which naturally differs between 64 and 32 bits.
|
|
|
|
|
Sorting is a PITA to implement in GUI so don't hold your breath for that one.
|
|
|
|
"sudo make install" after compiling on my system for my current version. does that mean i did both a compile and a local install? if that's the case, then i need to run "make uninstall" on the previous version before "make clean", right?
Typically you don't need to, as the same files as the previous install will be copied over, overwriting the previous install. But it's preferable to "make uninstall", as it guarantees the old files are removed, in case some of these files are not covered by the new install. |
|
|
|
|
Can I ask you a few questions about your DB usage and experience in PMs?
|
|
|
|
|
Don't build the db on a Pi
|
|
|
|
|
"Compile" is to build the binaries. Install is to setup the binaries on your system. If you use my builds you are only installing, if you build from source, you are "compiling" then installing. If you build from source you could also only "compile" and run the binaries from the source folder, without installing.
I put compile in quotes cause the actual term is to build the binaries.
|
|
|
|
|
compile or install?
Before you compile you should "make clean". If you install, you should "make uninstall" on the previous version before "make clean".
|
|
|
|
|
What version are you using?
|
|
|
|
|
Lockbox will show their proper balance assuming they had coins pre fork.
|
|
|
|
TY for examining the conditions of the log files.
Bitcoind 0.15.1 is loaded to the default location, as is Armory 0.96.3991
Bitcoind 0.15.1 always self-syncs when opened, again confirmed as I was typing this reply.
Let me know if there is any other information you need.
TY again for your kind and quick response.
1) Delete the databases folder as instructed 2) Turn off auto bitcoind in Armory, under File -> Settings. 3) Start BitcoinQt manually, then Armory. added info re my experiences over the years, is the observation of how the database fragments the files on the hard drive, and for
which I regularly run the Glary Utilities program routine to defrag and re-optimize the file locations (typically with a defrag once or
twice per week; plus the defrag and optimize routine circa every week to 10 days).
Both Core's DB and ArmoryDB point to block data by offset on disk. Defragmentation displaces on disk data. Defragmentation is 100% useless on SSDs and pretty useless on HDDs. The only thing it achieves is giving you a chance to damage your Bitcoin/Armory setup twice a week. Stop doing that. |
|
|
|
This is not a valid cli arg. Check your syntax. |
|
|
|
Armory seems to be working better now, however it won't update to the latest block.
What version of Armory are you using? In the Armory settings it asks for Install Folder, and Home Folder
On Linux, the default datadir is ~/.armory. Create an armoryqt.conf in there, and then set whatever other paths you want in there. Say your blockchain data is at /some/custom/path, you'd add this line to the .conf: satoshi-datadir=/some/custom/path
|
|
|
|
If you understand the need for keeping your private keys offline and how to operate that kind of setup with Armory, you are fine. Otherwise you're just asking for trouble. As long as you keep your coins offline, we can proceed. I assumed the worst since it didn't appear you would be taking security seriously. I stand corrected. Let's get to it then. 1) 2018-01-12 09:24:39 (INFO) -- SDM.pyc:459 - Called stopBitcoind
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:509 - bitcoind exited, bitcoind STDOUT:
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:511 -
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:512 - bitcoind exited, bitcoind STDERR:
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:514 -
2018-01-12 09:24:39 (INFO) -- SDM.pyc:465 - ...but bitcoind is not running, to be able to stop
2018-01-12 09:24:39 (INFO) -- ArmoryQt.py:5490 - Attempting to close the main window!
bitcoind is choking when Armory tries to spawn it for you. Start BitcoinQt manually, is it borked? Does it want to resync? Also, are you trying to use a custom folder for your blockchain data? 2) From the looks of your dbLog, it seems ok. To be on the safe side, once the Bitcoin node issue is fixed, delete your databases folder for the good measure before running Armory again (C:\Users\Owner\AppData\Roaming\Armory\databases) |
|
|
|
At present I don't have admin access to any folders deeper than C:\users\owner\ and the customary windows folders
You don't need admin privileges to access your user account. That's the whole point of user accounts. Otherwise, the software you run would need elevation to write to that path. Cheating (using a paused defrag from Glary Utilities) I can see that the files are stored within
C:\users\owner\AppData\Roaming\Bitcoin\chainstate\ then the unique respective files
I don't know where you read this stuff from but don't use backwards tricks like that, that don't do what you think it does to begin with. You cannot start a defragmentation process without admin privileges. The reason you can't see the AppData folder is because it is hidden. Just go in the folder settings and make hidden files visible. You can see folders belonging to other accounts, you just can't read their content. We have a plan to visit the computer shop Friday morning (show them this thread) ask for the keys to admin access,
and also have them assist us to get both the most recent (complete) armorylog.txt and dbLog.txt files & get them into
pastebin - where we can enter them here.
Don't, the shop will steal your wallets! Stop everything you are doing, do not take your computer to a goddamn shop, and just ask for help on how to export your private keys to another wallet. Armory is for expert Bitcoin users, you don't even know your way around Windows. Also consider stepping out of crypto currencies, you are basically asking to get robbed. |
|
|
|
|
Use both on the same invoice, if they both return the same payment address, that should be consistent enough to try.
|
|
|
|
Post your logs now. They're in your datadir (where you wallets are). I need armorylog.txt and dbLog.txt. Use pastebin to post them. Thank you for your assistance. Is there a different version of Armory which should be installed beyond 0.96.3991 in order to sync Bitcoin core 0.15.1
Use the most up to date stuff, always. |
|
|
|
|
Make your own thread please.
|
|
|
|
|
Armory non geek:
Maybe when you'll stop hijacking threads and show some logs someone will help you. Until then, you're not gonna get much assistance.
|
|
|
|
|
Show Posts
