I’ll see if I can figure out why.
- Posts 15556
- Members 386
weird, my node didn't even attempt, nor end up with an orphan. I just flat out skipped its turn
Clue is that just prior to your missing a block:
That’s a connection problem.
"connections" : 0, all of a sudden
That’ll do it.
All your connections timed out.
It’s your provider, or their network.
You are on clearnet, so it’s not tor timing out, which can happen.
Clearnet timing out is a local problem (VPS provider)
ok, well its probably not the wallet.dat (as suggested that it was corrupt) as this is a brand new build, new wallet, with imported privkeys. I'll contact the VPS to have them investigate connectivity issues
now "connections" : 12,
Yeah, absolutely they are having issues.
well, that doesn't fix our problem, but at least I personally wasn't responsible for this fiasco!
LOL no. Blame your VPS provider.
I'll see if they can migrate this image to a different location for us
then I'll change the qpos IP for that node
Very quiet here... Doesn't look anymore like there is a testnet running... 😁
Runs too well 😋
Stealth MonitorStealth Monitor Webapp
% ./StealthCoind getqposinfo | grep pico
"pico_power" : 1000000000000,
"prev_pico_power" : 1000000000000,
"current_pico_power" : 1000000000000,
Shouldn't there be different names in "Queue"?