@BloodyRookie, it’s a VPS on AWS.
seems nis is not running
just restarting it now
This one now works.
http://52.209.222.196:7880/nr/metaData
I’m just trying to find a way to get this nis working, will keep working at it.
Weird. After I # out the private key and IP entry in the config.properties folder in the nis folder it seems to run the nisStart.sh script fine and nis service starts up. I think it could be related to the path in the nisStart.sh file, somehow linking to either the config.properties or config-user.properties files.
Oh well, it’s starting, lets see how long it lasts! 
config.properties and config-user.properties should be in the same folder.
thanks, just moved them now into same folder.
Just a query, why does it say in the background after starting the nis service Account not yet allowed to generate a block?
Basicly that message is saying that you are harvesting but your account wasn’t lucky enough to be eligible to harvest a block yet…
on the http://52.209.222.196:7890/node/info web page
I can see the following address and public key, neither of which I recognise.
identity":{“name”:“NAWPX6BFJXNBCFR23B5SM4XH35ACOTXFQJWGGG3W”,“public-key”:“047337c6366785939d3c0e3555e821807a6bb245c3b2cba251a8de1c28defe26”}}
Shouldn’t this be my own delegated key and address? Where is this being read from?
The public key displayed is should be your delegated public key.
If it is not, then your nis is using a wrong delegated key. The delegated private key is the boot key taken from config.properties or, in case you have a config-user.properties, taken from there.
I checked all my config.properties files, and config-user.properties files I could find on the system and they have the correct delegated private key. Not sure where that key on the :7890/node/info is coming from. The delegated public key I used for enrollment and IP change is correct in the message as well.
Then it is likely that it is not using the config at all. Probabaly uses the one inside the jar. The config should be in the same folder as the script with which you start nis.
So where is the script and the config files located?
In terms of nis there is a config file
/root/nis-ncc/package/nis/config.properties
/root/nis-ncc/package/nis/config-user.properties
/root/nis-ncc/config-user.properties
I’ve copied them now into the same folder that contains the startup scripts which is /root/nis-ncc/package. Will give that a try.
Thanks BloodyRookie. It’s now reporting correctly. Much appreciated!
It’s been 24 hours now, just checking http://supernodes.nem.io/details/382 and balance, ping and bandwidth are all reporting green. Just height, chain part and version have red X’s through them. The version is the latest .79 beta. Not sure on how I can get it report height and chain part successfully.
Those tests involve NIS. Since you had problems with the config being in the right place the tests failed. Just wait another 12 hours and then it should work.
Thanks, seems to be working find so far…
If I close the putty session where the services are running in the background, would it kill the services?
If so,
Is there a way of closing the putty session without killing the servant and nis services? For example using a special command from the putty session. I haven’t closed the sessions fearing it may kill the services.
I’ve closed putty, and NIS still seems to be running, the servant didn’t though so ran the following command I extracted from one of Pauls scripts.
nohup ./servantStart.sh & and it seems to have kept the script running after closing the putty session
@BloodyRookie, when and how are supernodes rewards provided? As my supernode has passed tests for 24 hours - http://supernodes.nem.io/details/382 As I can’t see any rewards on my Main 3 million NEM client.account Thanks…
It’s OK now, it may have been delayed, but received it this morning. I’ve sent you a PM.