Why does it report my node is down when it is online? about bitnodes

[ayeowch]

After a reboot it reports correctly for about a day then it says it is down

@PegasusNZ Was this for the IPv4 address or .onion?

[PegasusNZ]

ip4 address

[ayeowch]

@PegasusNZ How is the load looking on the device? I tried 'check node' on your node and got an unreachable response once out of several tries earlier. Might be worth checking if the same issue persist with tor disabled.

[PegasusNZ]

@PegasusNZ How is the load looking on the device? I tried 'check node' on your node and got an unreachable response once out of several tries earlier. Might be worth checking if the same issue persist with tor disabled.

@ayeowch I was doing some maintenance and installs! Load is very low now?

[ayeowch]

@PegasusNZ I am getting TCP RST packet from your node immediately after my verack message is sent (at the end of handshake). This could be due to firewall along the path or custom Bitcoin node implementation? Try also disabling tor in your Bitcoin node configuration and we could retest IPv4 in isolation.

[ayeowch]

@PegasusNZ Another potential issue is your system may be hitting its file descriptor limit, similar to the situation found in https://stackoverflow.com/a/5245704. Steps to increase file descriptor limit if you are on Linux system: https://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/

[PegasusNZ]

Thank you I will try those tips

[PegasusNZ]

@ayeowch It was working fine for 10 months, I have not changed any hardware the only change is the Casa 2 node has be reflashed as a RaspiBlitz. I checked the file limits for the user bitcoin it was 256000 system limit is a rather large number over 12 digits! I have disabled tor for bitcoind. I will see in 24 hours if there is any change

[ayeowch]

@PegasusNZ Does the reflash to RaspiBlitz date coincide with the recent down spikes (starting around April 30, 2022) in the monthly latency chart in https://bitnodes.io/nodes/210.55.57.179-8333/? Also, were you running in hybrid IPv4 + tor only after the reflash?

For now, I no longer see the TCP RST packet from your node after handshake completion, so that's a good thing.

[PegasusNZ]

@ayeowch Yes this only started happening since I installed RaspiBlitz, On both systems I had TOR enabled, just RaspiBlitz gives more control

[ayeowch]

@PegasusNZ Might be worth opening issue with RaspiBlitz to see if there are others experiencing similar issue when having both IPv4 and tor enabled. Since disabling tor, it looks like your node is reachable normally again.
https://bitnodes.io/nodes/210.55.57.179-8333/: