Bor always looking for peers fail

Archive Matic Mainnet
1

Jul 01 20:35:44 matic bash[1381039]: INFO [07-01|20:35:44.007] Looking for peers peercount=1 tried=68 static=0
Jul 01 20:35:54 matic bash[1381039]: INFO [07-01|20:35:54.065] Looking for peers peercount=0 tried=56 static=0
Jul 01 20:35:54 matic bash[1381039]: WARN [07-01|20:35:54.834] Update txLookup limit provided=0 updated=2,350,000
Jul 01 20:35:54 matic bash[1381039]: INFO [07-01|20:35:54.834] Block synchronisation started
Jul 01 20:35:54 matic bash[1381039]: WARN [07-01|20:35:54.834] Enabling snapshot sync prototype
Jul 01 20:35:54 matic bash[1381039]: WARN [07-01|20:35:54.834] Synchronisation failed, retrying err=“peer is unknown or unhealthy”
Jul 01 20:36:04 matic bash[1381039]: INFO [07-01|20:36:04.243] Looking for peers peercount=0 tried=39 static=0
Jul 01 20:36:14 matic bash[1381039]: INFO [07-01|20:36:14.243] Looking for peers peercount=0 tried=68 static=0
Jul 01 20:36:24 matic bash[1381039]: INFO [07-01|20:36:24.278] Looking for peers peercount=0 tried=62 static=0

3

Hi, Where do I need to find more peers? now peers:
–bootnodes “enode://0cb82b395094ee4a2915e9714894627de9ed8498fb881cec6db7c65e8b9a5bd7f2f25cc84e71e89d0947e51c76e85d0847de848c7782b13c0255247a6758178c@44.232.55.71:30303,enode://88116f4295f5a31538ae409e4d44ad40d22e44ee9342869e7d68bdec55b0f83c1530355ce8b41fbec0928a7d75a5745d528450d30aec92066ab6ba1ee351d710@159.203.9.164:30303”

5

Have you found solution? I’d like to find an answer as well

1 Like