Good day, i just got a new 8tb NVMe server and I’m trying to start a node
I’ve followed the guide really closely and used the snapshots to download the chain, though I find myself stuck after starting the node
Oct 09 09:55:15 POS-Node systemd[1]: Started bor.
Oct 09 09:55:15 POS-Node bor[48079]: WARN [10-09|09:55:15.557] Config File provided, this will overwrite the cli flags. configFile:=/var/lib/bor/config.toml
Oct 09 09:55:15 POS-Node bor[48079]: INFO [10-09|09:55:15.558] GRPC Server started addr=:3131
Oct 09 09:55:15 POS-Node bor[48079]: INFO [10-09|09:55:15.559] Set global gas cap cap=50,000,000
Oct 09 09:55:15 POS-Node bor[48079]: INFO [10-09|09:55:15.560] Allocated trie memory caches clean=2.40GiB dirty=4.00GiB
Oct 09 09:55:15 POS-Node bor[48079]: INFO [10-09|09:55:15.561] Allocated cache and file handles database=/var/lib/bor/data/bor/chaindata cache=8.00GiB handles=262,144
It’s 30 minutes that I received that last log message and it doesn’t look like it want to move from there
I’ve never experienced this problem with my other nodes so I’m here asking why it could be happening
I’m using Ubuntu 20 with latest version of bor and heimdall (catching_up: false)
after a long wait (probably snapshot related work I got another error, I post the log here
Oct 09 15:03:39 POS-Node bor[64989]: INFO [10-09|15:03:39.615] Using LevelDB as the backing database
Oct 09 15:03:39 POS-Node bor[64989]: INFO [10-09|15:03:39.615] Found legacy ancient chain path location=/var/lib/bor/data/bor/chaindata/ancient
Oct 09 15:03:39 POS-Node bor[64989]: Chain metadata
Oct 09 15:03:56 POS-Node bor[64989]: databaseVersion: 8 (0x8)
Oct 09 15:03:56 POS-Node bor[64989]: headBlockHash: 0xbac09fed2256f172df62caca5c930f782b99f4565c4bd4dd67244f8a2d04a752
Oct 09 15:03:56 POS-Node bor[64989]: headFastBlockHash: 0xbac09fed2256f172df62caca5c930f782b99f4565c4bd4dd67244f8a2d04a752
Oct 09 15:03:56 POS-Node bor[64989]: headHeaderHash: 0xbac09fed2256f172df62caca5c930f782b99f4565c4bd4dd67244f8a2d04a752
Oct 09 15:03:56 POS-Node bor[64989]: lastPivotNumber: <nil>
Oct 09 15:03:56 POS-Node bor[64989]: len(snapshotSyncStatus): 0 bytes
Oct 09 15:03:56 POS-Node bor[64989]: snapshotDisabled: false
Oct 09 15:03:56 POS-Node bor[64989]: snapshotJournal: 0 bytes
Oct 09 15:03:56 POS-Node bor[64989]: snapshotRecoveryNumber: <nil>
Oct 09 15:03:56 POS-Node bor[64989]: snapshotRoot: 0x0000000000000000000000000000000000000000000000000000000000000000
Oct 09 15:03:56 POS-Node bor[64989]: txIndexTail: <nil>
Oct 09 15:03:56 POS-Node bor[64989]: fastTxLookupLimit: <nil>
Oct 09 15:04:05 POS-Node bor[64989]: open /var/lib/bor/data/bor/chaindata/ancient/headers.0000.cdat: no such file or directory
Oct 09 15:04:06 POS-Node systemd[1]: bor.service: Main process exited, code=exited, status=1/FAILURE
Oct 09 15:04:06 POS-Node systemd[1]: bor.service: Failed with result 'exit-code'.
Oct 09 15:04:11 POS-Node systemd[1]: bor.service: Scheduled restart job, restart counter is at 9.
Oct 09 15:04:11 POS-Node systemd[1]: Stopped bor.
Oct 09 15:04:11 POS-Node systemd[1]: bor.service: Start request repeated too quickly.
I downloaded again the full gigantic snapshot, a lot of file errored downloading, checksumming the whole thing take several hours
I remember I left developing on Polygon for this very reason more than 6 months ago
Now I rented the most expensive server in my fleet and still facing the same issue
I will (sadly) leave polygon once again as it is basically impossible to maintain a server in this condition