I keep having problem in getting local blockchain up to date to current height, including importing downloaded raw blockchain, each time it would get to a point where db gets corrupted & I have to wipe it out to start over. I get 58KB/s download speed from p2p network so I won't ever get synched starting from scratch, and no
--sync-pruned-blocks doesn't help at all.
So after n-th trials, when I got stuck again, I try to connect to remote node from GUI and it said wallet synchronizing & daemon synchronizing. After they're fully synched, I switched back to local node and back to the same crap I started with
Monero 'Oxygen Orion' (v0.17.1.3-release) Height: 1469833, target: 1469833
I thought the point of remote node is to connect to p2p network while synchronizing local blockchain db??
edit: I'll update with the status after an hour as local node
>>> status [19/11/20 10:03] 2020-11-19 03:03:20.276 I Monero 'Oxygen Orion' (v0.17.1.3-release) Height: 1469853/2233672 (65.8%) on mainnet, not mining, net hash 446.04 MH/s, v6, 142(out)+0(in) connections, uptime 0d 0h 13m 35s
half an hour
>>> status [19/11/20 10:20] 2020-11-19 03:20:21.753 I Monero 'Oxygen Orion' (v0.17.1.3-release) Height: 1469853/2233679 (65.8%) on mainnet, not mining, net hash 446.04 MH/s, v6, 269(out)+0(in) connections, uptime 0d 0h 30m 37s
instead of prioritize synching local db to close the gap to current height when starting up so I as node owner can use it for transaction, I have to keep up with new blocks first. There's literally no incentive for me to run a node if I have to run this 24/7 to be usable.