What is “InvalidArgument desc” ? i got those all the time now(solved)

= Clock out of sync for more than 1h

It will be splitted into 60MB segment and you will have 1h for each segment.

1 Like

Each satellite gives your node to their clients. Exactly that satellite do not offer your node to its clients, so your node do not store data for that satellite and that satellite will not audit your node because there is nothing to audit

@Ruskiem Please, sync your clock and report back is it solved the problem?

w8, what? my clock like windows clock? its synced to my location

Yes, your Windows clock could be out of sync. Try to force sync them with internet time server.

1 Like

I had like correct date, but under sync it was “Last successful time synchronization:” in 2015 what the f? Oo so i just “Sync now”, and that made some traffic goin right away, (whaaat?) i see some uplaod being done, (whaaaat?) how did You even catch this?
i guess node is on hes way to normal work!
Like, an Fn’ thank YOU?

That is what the error message is telling me.

Normal process:
Satellite issues and order, uplink sends that order to the storage node. I belive the uplink itself has no validation on the timestamp. So the uplink clock could be out of sync without any problems. Next step is the storage node with the above error message. That only happens if satellite and storage node disagree on the timestamp.

2 Likes