is this a correct return for the
sudo systemctl status IncognitoUpdater.service
Loaded: loaded (/etc/systemd/system/IncognitoUpdater.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2021-06-04 10:11:57 CEST; 16s ago
Process: 23551 ExecStart=/bin/run_node.sh (code=exited, status=0/SUCCESS)
Process: 23795 ExecStop=/usr/bin/pkill run_node.sh (code=exited, status=1/FAILURE)
Main PID: 23551 (code=exited, status=0/SUCCESS)
Yes, it is. Since the update checking process will only need a few seconds to complete its task then it will exist.
When the update interval comes, systemd will restart the process by first stop it with ExecStop=/usr/bin/pkill run_node.sh then start it up again.
But since the process completed and existed already, ExecStop action will return the error as you already saw.
thanks, gotcha
could you refer to the "How to check if node sync and other necessary staff’ please. I don’t mean the monitoring tool - How to use the Node monitor. I mean if we can monitor nodes in terminal.
Sorry to be a pain, but you should throw in curl there as well, or remove curl from the update script and replace it with wget. As it is right now, on a fresh install, you’ll end up with this in your system log and nothing is started.
systemd[1]: Started IncognitoChain Node updater.
IncNodeUpdt[13196]: Getting Incognito docker tags
IncNodeUpdt[13199]: /bin/run_node.sh: line 57: curl: command not found
systemd[1]: IncognitoUpdater.service: Control process exited, code=exited, status=1/FAILURE
My bad, will include curl right now
Can one infura API be used for multiple nodes?
Yes, I use one API key for more than one node.
One Infura with free plan supports 100,000 Requests/Day. So yeah, you can use one Infura for more than one.
After using the new script “sudo ./inc_node_installer.sh”, I see only “inc_mainnet” running after sudo docker ps. I no longer see “eth_mainnet” running in docker after using the new script. Is this correct? Can someone share a correct return value for “sudo docker ps” after running the ./inc_node_installer.sh script?
hello! Eth_mainnet The command incognito does not use) infura)
be5fe1410b024a8f94f62fbc106439xxWe no longer use eth_mainnet docker image. We use Infura instead.
If only inc_mainnet is running and no settings for infura are included in the script, what functionality is lost regarding incognito? My nodes appear to be functioning normally.
Please check the post again, I believe there’s a reference to Infura setup guide already.
Sorry, I see the post now and have setup infura and restarted the node. One last question regarding infura: in what ways can I test or check that the infura connection to eth network is working?
@Socrates, let your node sync data and validate transaction for a while (few days i think) then check setting on infura to see if there is any query
mine, for example
Just for clarification for the community.
The eth-mainnet docker container can be killed and we should be running infura now, correct? I had been running both.
Is there anything other than adding our infura api key that we need to do to insure not having our nodes slashed?
Yes, you just need Infura only.
There are many things that can cause the node to be slashed. We will have to take a look at the log to find the cause. If your node is slashed, feel free to contact us we can help investigate.
Prior to slashing taking affect can we have an indepth post about it. For instance, common reasons for slashing and how to prevent each reason.
Yes, we will do that, thanks for the tip.
Hey guys,
I’ve just update the script and this guide to support running multiple node per host.
Please check it out!