search

signum-network / signum-node

Signum Node
https://signum.network
GNU General Public License v3.0
195 stars 77 forks source link

Blacklisting x.x.x.x (v3.8.2) because of: feeding us a too old fork #834

Closed PSLLSP closed 1 month ago

PSLLSP commented 2 months ago

I tried to run signum-node v3.8.2 at very old PC with Intel Atom N280 (i686). Default configuration, I have not touched any configuration file and backend DB is H2. OS is Debian 12 (x86).

$ java -version
openjdk version "17.0.12" 2024-07-16
OpenJDK Runtime Environment (build 17.0.12+7-Debian-2deb12u1)
OpenJDK Server VM (build 17.0.12+7-Debian-2deb12u1, mixed mode, sharing)

I see errors that some hosts are blacklisted because they feed fork that is too old. I do not remember I noticed these errors when I was running signum-node on other PCs. Is this an issue with client (java running on 32-bit machine)? Or is there an issue in server code that some nodes really feed clients with forks those are too old?

Aug 07, 2024 7:50:34 AM signum.Launcher main
INFO: Running in headless mode as specified by argument
Aug 07, 2024 7:50:35 AM brs.Signum loadProperties
INFO: Initializing Signum Node version v3.8.2
Aug 07, 2024 7:50:35 AM brs.Signum loadProperties
INFO: Configurations from folder ./conf
Aug 07, 2024 7:50:35 AM brs.Signum loadProperties
INFO: Custom user properties file node.properties not loaded
Aug 07, 2024 7:50:35 AM brs.util.LoggerConfigurator init
INFO: Custom user logging.properties not loaded
[INFO] 2024-08-07 07:50:51 brs.db.sql.Db - Using SQL Backend with Dialect H2 - Version 2.2.224
[INFO] 2024-08-07 07:50:52 brs.db.sql.Db - Running flyway migration
[INFO] 2024-08-07 07:51:07 brs.BlockchainProcessorImpl - Genesis block not in database, starting from scratch
[INFO] 2024-08-07 07:51:08 brs.peer.Peers - P2P max connections: 20
[WARNING] 2024-08-07 07:51:14 brs.peer.Peers - Tried to establish UPnP, but it was denied by the network.
[INFO] 2024-08-07 07:51:15 brs.peer.GetNextBlocks - P2P max number of blocks: 720
[INFO] 2024-08-07 07:51:16 brs.web.server.ServerConnectorHttpBuilderImpl - HTTP API server enabled for 127.0.0.1:8125
[INFO] 2024-08-07 07:51:16 brs.web.server.ServerConnectorWebsocketBuilderImpl - [Experimental] WebSockets server enabled for 127.0.0.1:8126
[INFO] 2024-08-07 07:51:17 brs.web.server.WebServerImpl - API docs enabled
[INFO] 2024-08-07 07:51:19 brs.peer.Peers - Started peer networking server at 0.0.0.0:8123
[INFO] 2024-08-07 07:51:19 brs.web.server.WebServerImpl - Web Server started successfully
[INFO] 2024-08-07 07:51:19 brs.util.ThreadPool - Using 1 cores
[INFO] 2024-08-07 07:51:19 brs.Signum - Initialization took 41588 ms
[INFO] 2024-08-07 07:51:19 brs.Signum - Signum Multiverse v3.8.2 started successfully.
[INFO] 2024-08-07 07:51:19 brs.Signum - Running network: Signum
[INFO] 2024-08-07 07:51:32 brs.peer.Peers - Finished connecting to 3 well known peers.
[INFO] 2024-08-07 07:52:45 brs.peer.PeerImpl - Blacklisting 213.221.57.86 (v3.8.2) because of: feeding us a too old fork
[INFO] 2024-08-07 07:54:23 brs.statistics.StatisticsManagerImpl - handling 2,96 blocks/s account_balance cache hit ratio now/total:85,89%/85,89% account cache hit ratio now/total:79,04%/79,04%
[INFO] 2024-08-07 07:55:04 brs.peer.PeerImpl - Blacklisting 114.34.80.40 (v3.8.2) because of: feeding us a too old fork
[INFO] 2024-08-07 07:55:24 brs.statistics.StatisticsManagerImpl - handling 8,20 blocks/s account_balance cache hit ratio now/total:92,17%/88,88% account cache hit ratio now/total:89,01%/83,93%
pir8radio commented 2 months ago

this is pretty normal. there will be peers out there that are out of sync but they don't know they are out of sync, and send you their latest info that they think is the latest yet its from a day, week, year ago..