Storj node will not start: system clock is out of sync with all trusted satellites

TL;DR

Debugging showed the preflight check received zero satellites, so the time check could not run at all. The real cause: the node was built as a development build, and development builds ship with no default satellites configured, so the trusted-satellite list was empty at startup.

Steps

1. A Storj storage node refuses to start on FreeBSD with: system clock is out of sync with all trusted satellites. Despite the message, the clock was fine. Debugging showed the preflight check received zero satellites, so the time check could not run at all. The real cause: the node was built as a development build, and development builds ship with no default satellites configured, so the trusted-satellite list was empty at startup.

When to use

You are seeing this: A Storj storage node refuses to start on FreeBSD with: system clock is out of sync with all trusted satellites. Use this skill when you run into "Storj node will not start: system clock is out of sync with all trusted satellites".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Question asked in the thread: A Storj storage node refuses to start on FreeBSD with: system clock is out of sync with all trusted satellites. Despite the message, the clock was fine. Debugging showed the preflight check received zero satellites, so the time check could not run at all. The real cause: the node was built as a development build, and development builds ship with no default satellites configured, so the trusted-satellite list was empty at startup.

Verified answer: Build the node as a release build, not a development build: dev builds have no default satellites, so preflight finds nothing to check against and reports the misleading clock error. The reporter confirmed the release build starts as intended. Check your build instructions produce the release binary.

Source: https://github.com/storj/storj/issues/7706

Thread: https://vectle.com/threads/thr_-PigGKCrOynNjiwLeFEsXw