now both servers are working, last time I did the same, only 2 nodes transferred uptime, can you please take a look?
2024-11-16-16T16:47:28.916Z info: CONFIG: ✅ Starting node with peerID: 16Uiu2HAm55ageBow1rqE2rJ8NKZHVdR6s9nPn8t6wPhkhu5QgRKp
and the ip is still the old one, not the new one.
Last time I shut down the server after 8 hours, like you said, only 2 nodes out of 20 showed up in the new server
Hello! We are already checking with the team to determine the cause. Could you please confirm if the IP address of the node has changed or remained the same?
It remains the same and the port has not changed Should I shut down the old server?
Did you not shut down the previous server? Am I correct in understanding that you have two servers running for one node now?
Now noticed slowly began to transfer, so far on 2 servers is working half the nodes have been moved should we shut down the server then?
Nodes on the new server must operate for at least one round of checks before fully transitioning from the old server. If you notice that the nodes are slowly beginning to transfer, it might be best to wait and monitor the progress before shutting down the old server. This gradual transfer can sometimes happen as the system updates the status of each node.
It's been over 6 hours and half of the wallets haven't moved to the new server old server already shut down, how can we transfer uptime?
To transfer uptime when migrating nodes to a new server, make sure that the necessary ports are open and correctly forwarded. Use P2P_ANNOUNCE_ADDRESSES to inform other nodes of your new external IP/port, and avoid changing the P2P_BOOTSTRAP_NODES variable unless necessary. It may also take some time for the dashboard to sync with the new server, so please be patient. Generated using AwesomeQA AI. Please rate this answer.
Since your old server is already shut down, you might face issues with the nodes not showing up or their uptime resetting. Make sure that the necessary ports are open and correctly forwarded on the new server. If you have a private IP, use P2P_ANNOUNCE_ADDRESSES to let other nodes know your external IP/port. Additionally, ensure that you are not using the P2P_BOOTSTRAP_NODES variable as it has a predefined value in the code and should not normally be changed. If the problem persists, it might be due to the backend performance tracking, which updates every Thursday at 00:00 UTC.
Re-enabled it, but still 10 more nodes with uptime 100% are not migrating P2P_ANNOUNCE_ADDRESSES all configured, but 10 nodes do not want to migrate.
Now again the old server has more nodes than the new server, they go back and forth, how do I fix this?
Just in case, it might help to remove the P2P_BOOTSTRAP_NODES variable if you have set it, as it has a predefined value in the code and changing it can affect the visibility of your node.
same problem here i still see in dashboard nodes closed 1 mount ago.
Kindly send me a message so I can look into this, no admin will message you first.
Обсуждают сегодня