Title: Node unactive? Blocks stuck at 97% Post by: Bitcoiner317 on February 09, 2023, 03:20:56 AM I'm not too sure what I've done wrong. The node used to run fine but I've been experimenting with Ubuntu and new blocks aren't loading anymore. Might be due to updating my node from core v22 to v24. Anyway - can anybody spot a clue? Would be much appreciated! It seems like I'm not getting any connections for some reason.
bitcoin.conf: Code: datadir=/media/anonymous/T7/Bitcoin/ debug.log: Code: 2023-02-09T02:34:22Z Ignoring unknown configuration value addumevalid Title: Re: Node unactive? Blocks stuck at 97% Post by: nc50lc on February 09, 2023, 07:21:56 AM Probably not related to the issue but you have a typo in your config:
Code: # Needed for full validation Code: 2023-02-09T02:34:22Z Ignoring unknown configuration value addumevalid Which resulted in skipped signatures verification of blocks older than height 751565. Title: Re: Node unactive? Blocks stuck at 97% Post by: NotATether on February 09, 2023, 11:25:31 AM Check if your proxy is down. You're using only Tor, so make sure you can still connect to that. If you can, check if you have any peers - maybe there are no Tor v3 peers for your node, although I would be baffled if that is indeed the case.
Probably not related to the issue but you have a typo in your config: Code: # Needed for full validation Code: 2023-02-09T02:34:22Z Ignoring unknown configuration value addumevalid Which resulted in skipped signatures verification of blocks older than height 751565. The assumevalid block is a moving target that is changed during releases, so it is not guaranteed to stay at this block for the next version of Bitcoin. Title: Re: Node unactive? Blocks stuck at 97% Post by: DaveF on February 09, 2023, 12:38:27 PM The debug.log seems to be incomplete since it doesn't log any connection problem (e.g. cannot connect to proxy or to other node). You should check your system log and see message which generated by Tor. If you can, check if you have any peers - maybe there are no Tor v3 peers for your node, although I would be baffled if that is indeed the case. debug.log file state peers.dat has 57414 addresses, so IMO it's very unlikely. Although OP can add node which use .onion link from https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes_main.txt#L781-L792 (https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes_main.txt#L781-L792) Does not mean that it can reach those nodes. OP, can you check https://bitnodes.io to see if it sees your node. Bitnodes is NOT A PERFECT test. But if it sees it and you are not updating it's probably on your side since it can be seen. If bitnodes does not see it, then it could be it just does not see it. Other nodes might. And, since you were experimenting with the OS, when did you notice that it stopped working vs what were some of the last changes you made? -Dave Title: Re: Node unactive? Blocks stuck at 97% Post by: Bitcoiner317 on February 09, 2023, 01:12:32 PM Probably not related to the issue but you have a typo in your config: Thanks! Check if your proxy is down. You're using only Tor, so make sure you can still connect to that. When listing system services, it seems tor.service is active but tor@default.service returned as loaded but FAILED. But I can't seem to figure out what went wrong.. I get the following under journalctl -xeu tor@default.service Quote Feb 09 07:51:35 Anonymous-Laptop systemd[1]: Failed to start Anonymizing overlay network for TCP. And the following under sudo journalctl -u tor@default.service At this point, I assume I just didn't config the TOR service properly. I don't remember setting it up, actually - just installing. Would anyone mind pointing me to a good guide? Thank you! Quote Jan 02 22:32:30 Anonymous-Laptop systemd[1]: Starting Anonymizing overlay network for TCP... Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.572 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc. Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.573 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/ Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.573 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Jan 02 22:32:30.574 [notice] Read configuration file "/etc/tor/torrc". Jan 02 22:32:30 Anonymous-Laptop tor[4845]: Configuration was valid Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc. Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/ Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.778 [notice] Read configuration file "/etc/tor/torrc". Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.785 [notice] Opening Socks listener on 127.0.0.1:9050 Jan 02 22:32:30 Anonymous-Laptop tor[4854]: Jan 02 22:32:30.785 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050 Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: We compiled with OpenSSL 30000020: OpenSSL 3.0.2 15 Mar 2022 and we are running with OpenSSL 30000020: 3.0.2. These two versions should be binary compatible. Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Tor 0.4.6.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc. Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/ Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Read configuration file "/etc/tor/torrc". Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Opening Socks listener on 127.0.0.1:9050 Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Opened Socks listener connection (ready) on 127.0.0.1:9050 Jan 02 22:32:30 Anonymous-Laptop Tor[4854]: Parsing GEOIP IPv4 file /usr/share/tor/geoip. Jan 02 22:32:31 Anonymous-Laptop Tor[4854]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Title: Re: Node unactive? Blocks stuck at 97% Post by: nc50lc on February 09, 2023, 01:34:34 PM -snip- The assumevalid block is a moving target that is changed during releases, so it is not guaranteed to stay at this block for the next version of Bitcoin.Which resulted in skipped signatures verification of blocks older than height 751565. Title: Re: Node unactive? Blocks stuck at 97% Post by: Bitcoiner317 on February 10, 2023, 10:24:14 PM Alright so I managed to get TOR up and running (glad I had the node issue cause I wouldn't have realized it wasn't running). Core still wouldn't connect to any peer for some reason so I decided to hash out onlynet=onion and it's working now.
Title: Re: Node unactive? Blocks stuck at 97% Post by: nc50lc on February 11, 2023, 03:07:39 AM -snip- Core still wouldn't connect to any peer for some reason so I decided to hash out onlynet=onion and it's working now. But that essentially enables your node to connect to clearnet, check your peers if all of them have clearnet addresses.If connecting to clearnet isn't an issue, then you're good. Title: Re: Node unactive? Blocks stuck at 97% Post by: Cricktor on February 19, 2023, 02:28:02 PM As you're running Ubuntu: did you install Bitcoin Core as Snap package? Did you install Tor as Snap package?
I'm using Ubuntu too, but had issues with Bitcoin Core installed from Snap ("official" snap package linked via bitcoincore.org). It simply couldn't properly interact with Tor. (After some digging into possible causes of this issue, it looked to me as a snap packaging problem from Core packaging maintainer(s)). When I discovered this issue, Core v22.0 was the current version. If this snap packaging issue has been resolved or corrected in recent Core version, I can't tell as I didn't look at it anymore. My solution back then was to install Bitcoin Core and Tor *not* from Snap and then it was no problem to configure Tor-only access for Core, no Clearnet necessary if not desired. Title: Re: Node unactive? Blocks stuck at 97% Post by: DireWolfM14 on February 19, 2023, 06:31:48 PM Alright so I managed to get TOR up and running (glad I had the node issue cause I wouldn't have realized it wasn't running). Core still wouldn't connect to any peer for some reason so I decided to hash out onlynet=onion and it's working now. It might take a several minutes for TOR to spin up and for your node to find onion peers, are you sure you waited long enough? You can quickly check the status of your Tor proxy with the following command: Code: sudo systemctl status tor I'm also curious how you installed TOR. It's been a while so my memory on the issue is faded, but I tried anonymizing a package (I don't remember which, but it wasn't bitcoin) and had issues with the standard TOR package from the Ubuntu repository. The standard Ubuntu and Debian apt repositories install an older release of TOR, you can get the latest release by updating your source list. Here's a tutorial on how to set up the Tor Project's official repository: https://support.torproject.org/apt/tor-deb-repo/ Title: Re: Node unactive? Blocks stuck at 97% Post by: moijiashiasei on June 05, 2023, 09:53:40 AM could be the case your node was marked as misbehave
add new nodes and make them priority to connect it usually resolved by itself in 24h |