I can't get remote harvesting working for a few months now. Every time I boot NIS it stops after a few minutes. If I remove "nis.shouldAutoHarvestOnBoot = false" from the config my NIS will sync, but then when I try and start local harvesting on my remote node it throws an error
"ERROR 306 NIS: UNEXPECTED ERROR"
I was hoping the new version would fix this problem but it hasn't. I did a full uninstall of the old version before installing too. Does the account I use to boot my remote node need to have a positive NEM balance? It always worked until Dec 2015 with a zero balance, but did something change? Help!!
"ERROR 306 NIS: UNEXPECTED ERROR"
I was hoping the new version would fix this problem but it hasn't. I did a full uninstall of the old version before installing too. Does the account I use to boot my remote node need to have a positive NEM balance? It always worked until Dec 2015 with a zero balance, but did something change? Help!!
"local harvesting on my remote node"
it shouldnt allow you to start local harvesting when connected to a remote nis
the account you use to boot can been negative and should be, unless you boot it with a delegated harvesting key. for the health of the network its better to boot with a harvesting key(for account security), of which the originating account should have a positive balance.
you need a balance of at least 10k (vested) xem to harvest.
activate delegated harvesting with the account that has funds, then go to your nis config and set auto-boot on and use the delegated accounts private key as the boot key. the delegated account cannot be used to move funds so the coins cannot be stolen even if your remote nis is compromised and delegated key stolen.
in relation to harvestig with a zero balance, that should be impossible.
Thanks for the reply kod! What I did was use my laptop to delegate my main account for harvesting on my VPS. I did that last year and have rarely used my laptop NEM since. On my VPS i used 'nis.shouldAutoHarvestOnBoot = true' and setup a NEM account with zero balance in the config file to use with 'nis.bootKey =xxxxxxxxxx'. This setup was working great for months and I harvested many blocks and reboots of the VPS caused no problem as NIS would start from a shortcut in startup folder
But then in Dec 2015 the NIS on my VPS just kept stopping. I tried re-installing and deleting the cache files (smaragda's tip) but nothing worksed, NIS always stops after a few minutes. Then I noticed that if I change 'nis.shouldAutoHarvestOnBoot' to false the NIS on my VPS will sync, but when I login with my account on the VPS (i.e. the account I use with 'nis.bootKey =xxxxxxxxxx' in the config) and try and start harvesting on the VPS manually by clicking the harvesting button in the GUI I get the error "ERROR 306 NIS: UNEXPECTED ERROR".
I gave up and decided to wait for a new version, but I tried yesterday and NEM Beta 0.6.74 is doing the exact same behavior.
?