Hi all,
I am trying to connect my supernodes to a superlink on a different machine in insecure mode. I got this exact setup running in the past (even yesterday), but all of a sudden these errors started coming up:
Yesterday, I was able to solve the issue by using the command sudo systemctl enable systemd-timesyncd. However, today I have the same issue again.
What could be the reason for this?
Hello @stackpilot , the automatic node authentication feature relies on system clocks to be roughly in sync. There are a few seconds (5 seconds as of Flower 1.18.0) of grace in case there is some drift. Are both of your systems (where the SuperLInk and SuperNode run) are connected to the internet or alternative a server that provides a time synchronization via NTP ?
Could you check if the times are in sync? e.g. by typing date on your terminal.
Could you update your Flower installation in case you aren’t using the latest?
pip install -U flwr
Hello @javier , thank you for the quick reply. It looks like this solved the problem. So far, the “Invalid timestamp” error did not show up anymore. Thank you for the recommendation!
Interestingly, date showed the same timestamps on both machines. Is the problem caused when there is even the slightest difference in the timestamps, maybe not even visible when using date?
Hello @stackpilot, glad to hear that this error is not happening anymore. In the current version of Flower (1.18.0) a 5s drift it’s allowed meaning that the times in different machines don’t have to exactly match. In a previous version of Flower this drift allowance didn’t exist which might explain errors if the system time is slightly off.
By the way, how did you fixed it? did you updated your version of Flower?
I see, so Flower is not as strict with the timestamp anymore.
Yes, I used pip install -U flwr as you suggested. Thank you again.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.