they are 100% up when I log in on the VM. How is it possible that the node details show me that I have only be up for for example 80%? I don't change anything on the VM, so the config is correct otherwise I could not be eligible at all. Is it worth so reboot my VM's 2 times a day where I loose just 1 or 2 minutes? How many times does oceanprotocol checks if the nodes are still eligible?
To optimize your uptime, it's important to understand that Ocean Protocol performs random round checks for node eligibility. With more than 10,000 nodes in this epoch, if your node misses a check due to connectivity issues, that round's uptime won't be counted, which could explain why you see 80% uptime even though your node appears fully operational when you log in. Ocean Protocol checks eligibility randomly, so any momentary issue could affect your overall uptime.
Rebooting your VM twice a day might not be the best approach, as you're still losing uptime during those reboots. Instead, ensure your node is always reachable, and monitor the dashboard for any specific connectivity issues. Ocean Protocol checks eligibility randomly, so any momentary issue could affect your overall uptime.
Some points I want to ask to investigate this issue: 1) Have you different RPCs on your VMs? 2) Are the components of your VMs the same ?
1. how can I check this? I installed it with your instructions as a docker container in a VM 2. yes, ther are all the same
You can open your docker-compose.yml file to update the RPC URL. Command: nano docker-compose.yml Save the changes and restart your node. This should resolve the issue
you said that I had to update the docker-compose.yml file. I just tried to copy/paste the default to show you what I have now. And my question is what do you want me to change?
Обсуждают сегодня