 Show Posts
|
|
Pages: « 1 2 [3]
|
|
Connections are being added automatically now. 7 is the highest number that I've seen displayed. Thank you for the help!
|
|
|
|
|
I tried a couple of searches, but didn't come up with a list of IP addresses for bitcoin nodes. Is one of those available? What is the maximum number of concurrent peers that can be established?
getnetworkinfo returns a value of connections = 3
Is this a configuration limit on the number of concurrent peer connections? I do have three at the moment, but wouldn't 16 would be better?
|
|
|
|
|
Method not found (code -32601)
Attempted addnode and connect commands in the console
|
|
|
|
|
I currently have 1 active connection to the bitcoin network. That happened after I dropped my personal firewall.
Is there a way to enter IP addresses for bitcoin nodes into the bitcoin.conf file?
|
|
|
|
|
It reached block 524491 previously. I started re-indexing headers about 3 weeks ago. After that, it stopped at a lower percentage, but both values were still displayed in the dialog box.
These two lines were the current status:
The re-indexing process stopped at 53.29%
Sat
May 26 7:39:09 2018
2 years and 32 weeks behind
They were displayed below the block 524491 entry. At the moment, I am updating Windows, having run performance tuning on the system. Windows performance was extremely sluggish.
|
|
|
|
|
Could the issue be caused by an intermittent failure in the Internet connection? No new blocks are available?
|
|
|
|
|
The re-indexing process stopped at 53.29%
Sat
May 26 7:39:09 2018
2 years and 32 weeks behind
It still lists the same values at the top: Syncing Headers (524490, 79.5%)
Which way to go on this? Delete db files and rebuild the database in bitcoin core? It took over 3 weeks to get to the stopping point re-indexing headers.
|
|
|
|
|
I am reindexing bitcoin core from command line on Windows 10.0. Bitcoin Core 0.20.1
The counters are incrementing on lines 2 - 4, but they are static on line 1 of the overview tab.
Number of blocks left: Unknown. Syncing Headers (524490, 79.5%)...
The lines containing date and time, progress, and progress increase per hour are all incrementing or changing.
Is the syncing continuing, or do I need to stop this process and try something else?
|
|
|
|
|
There would be no point in looking at the log file to see whether an issue could be indicated there, the way it sounds.
|
|
|
|
|
I should plan to locate new hardware for the online version and install the latest versions of armory and bitcoin qt. Then I will be able to restore the wallet from paper backup, from what I understand. It might also require an upgrade to the offline version.
|
|
|
|
|
I don't know what you mean when you say recovered drive. The C: drive filled up. I was able to free up enough space to keep it running after that. The D: drive, where I want to run everything, as much as possible, anyway, was new when I set it up with the versions that I listed -- armory and bitcoin.
I need to upgrade the offline PC to Armory 96.5 as well in order to sign transactions -- ?
|
|
|
|
|
listening on port 9001
after launching armorydb on external drive ( D: drive)
Afterward, I use - from this directory - D:\BTC datadir 96-2\Armory>
armoryqt -- datadir=d:\btc datadir 96-2\
This returns an error message referencing log file ArmoryQT.exe.log (on the d: drive)
===
See the logfile 'D:\armory 0.96.3.992\Armory\ArmoryQT.log' for details
===
My initial installation was on the C: drive, but I ran out of disk space. Added external drive, reinstalled and upgraded, and am trying to run the following on Windows 7 Home 64 bit:
online PC
armory 0.96.3.992
bitcoin core
0.14.2
Offline PC
Windows 7 Starter 32 bit
armory 0.92.3-beta
I'm thinking that I had this working 2.5 years ago. Checking file date and time stamps, it looks like log files have been changed on both drives. I have attempted to launch armory using executables and shortcuts on both drives.
|
|
|
|
|
