40K nodes. 👉 nodes.oceanprotocol.com https://x.com/oceanprotocol/status/1846086129906327717?t=MnzeopTsmdJDeFdFY_xcEA&s=19

Seems my Node never qualified for any reward Keeps going ineligible after every 3 days of being active and eligible

To address the issue of your node becoming ineligible, ensure that all environment variables are correctly set and that your node maintains a high uptime (90% or higher) [1] [2]. You can monitor your node's performance and eligibility through the Ocean Node Dashboard to identify specific issues [1] [4]. Generated using AwesomeQA AI. Please rate this answer. 👎

How do you judge the 90%

One epoch lasts one week, which is 7 days. To qualify, your node needs to be active for at least 6.3 days (90% of the week). If it’s active for less than that, it won’t be eligible for this epoch. Full activity is considered 7 days (100%).

It's normal for a node to change status automatically from time to time. This happens because of random round checks for each node. If the node is unreachable during a particular check, the system will display the reason on the dashboard 🙂 Also try restarting your node—this has helped some users in similar situations. please check the following: Is your P2P_ANNOUNCE_ADDRESS configured correctly? Have you opened the necessary ports? Can you access your node from the local dashboard? Let us know if the problem persists after checking these steps.

You should check at least once every 10 minutes, because at that moment some node was not working, lost uninterrupted operation for 1-1.5 hours, this is wrong

and here in fact it is random, will you pass into this range of 90% or not

Стикер

here is an example from my case 2 nodes are on one server one has uptime more than 5 days the other has 4 days this shows that it is accidental or another example, a node may not work before the checks, and during the check it suddenly starts working, and in this case the time will be counted, by the way, I checked this a couple of times and if you also run different wallets on one port with a sequence of 5-10 minutes and turn off the other, the time will be counted on 2 nodes, you need to improve))

this is just a small part of what i found in your node

Hm, thank you for your feedback! The team is aware of these issues and working on fixes. Your observations about nodes starting to work just before checks and the impact of running different wallets on one port are valuable. These insights can help improve the system. If you have more detailed logs or specific instances, sharing them with the development team could be beneficial.

and after that, you still say that it's not random

There is no randomness, but there are checks that we are currently working on.I understand your concerns, and I appreciate you sharing your experiences. Our team is actively working to address these issues and enhance the monitoring process. Your feedback is invaluable, and it contributes to our ongoing efforts for improvement. If you encounter any specific instances or have further observations, please feel free to share them. We want to ensure the system is as reliable as possible for everyone.

Why, if the node was not working for 10 seconds during the check, 1-1.5 hours will be subtracted from my total time

I think this is wrong

Thank you for your feedback I understand your concern regarding the monitoring mechanism. If it is indeed down, we will take that downtime into account and subtract it from the threshold

Please guide on how to open the necessary port

To open the necessary ports for your Ocean Node: 1. For a local PC, configure your router to open the required ports. 2. For a VPS, use the following commands: ```shell sudo ufw status sudo ufw enable sudo ufw allow [port_number] sudo ufw allow 8080 sudo ufw allow [port_number]/tcp sudo ufw allow [port_number]/udp ``` For example, to open port 8080 for TCP only: ```shell sudo ufw allow 8080/tcp ``` To open a range of ports, use: ```shell sudo ufw allow [start_port]:[end_port]/[protocol] ``` Make sure to replace `[port_number]` with the actual port number you need to open [1]. Generated using AwesomeQA AI. Please rate this answer.

Hello! The bot provided the correct answers :) If you have any additional questions, feel free to ask!

I just used those commands to open the ports but I discovered that I started having so much error on the terminal

If you are experiencing errors on the terminal after opening ports, ensure that the ports are correctly configured and check if you are using any proxy or VPN that may interfere with the connection [1][4]. Restart your node and wait for a couple of hours to see if the issue is resolved [2]. If the problem persists, please provide the specific error messages for further assistance. Generated using AwesomeQA AI. Please rate this answer.