I’m try to get the official app storj to run on my truenas-scale.
Long time ago I had already a node running on a other server. The difference was the port.
This is the first think, what’s not clear. Why the official storj doc use 28967 and the Storjnode from truenas use 20988.
The second think is, if the app start, the deploying stuck on Back-off restarting failed container and the web butten doesen’t come on.
In the logs there is something with:
Error: systemclock is out of sync: system clock is out of sync with all trusted satellites. Is it possible, that there is the error?
Hi @daschmidt
That’s definitely an issue. You need to fix the system time for the node to work, but there’s likely to be more errors. You can post fuller logs in between three backticks
2023-03-03 05:54:12.999510+00:002023-03-03T05:54:12.998Z ERROR preflight:localtime system clock is out of sync with satellite {"Process": "storagenode", "Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "error": "system clock is out of sync: clock off by 60.285149 minutes", "errorVerbose": "system clock is out of sync: clock off by 60.285149 minutes\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).checkSatelliteTime:132\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:74\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-03-03 05:54:13.068980+00:002023-03-03T05:54:13.068Z ERROR preflight:localtime system clock is out of sync with satellite {"Process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "error": "system clock is out of sync: clock off by 60.283720 minutes", "errorVerbose": "system clock is out of sync: clock off by 60.283720 minutes\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).checkSatelliteTime:132\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:74\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-03-03 05:54:13.219044+00:002023-03-03T05:54:13.218Z ERROR preflight:localtime system clock is out of sync with satellite {"Process": "storagenode", "Satellite ID": "12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo", "error": "system clock is out of sync: clock off by 60.281999 minutes", "errorVerbose": "system clock is out of sync: clock off by 60.281999 minutes\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).checkSatelliteTime:132\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:74\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-03-03 05:54:13.236944+00:002023-03-03T05:54:13.236Z ERROR preflight:localtime system clock is out of sync with satellite {"Process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "error": "system clock is out of sync: clock off by 60.281707 minutes", "errorVerbose": "system clock is out of sync: clock off by 60.281707 minutes\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).checkSatelliteTime:132\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:74\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-03-03 05:54:13.374116+00:002023-03-03T05:54:13.373Z ERROR preflight:localtime system clock is out of sync with satellite {"Process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "error": "system clock is out of sync: clock off by 60.279876 minutes", "errorVerbose": "system clock is out of sync: clock off by 60.279876 minutes\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).checkSatelliteTime:132\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:74\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-03-03 05:54:13.623907+00:002023-03-03T05:54:13.623Z ERROR preflight:localtime system clock is out of sync with satellite {"Process": "storagenode", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "error": "system clock is out of sync: clock off by 60.276401 minutes", "errorVerbose": "system clock is out of sync: clock off by 60.276401 minutes\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).checkSatelliteTime:132\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:74\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-03-03 05:54:13.624171+00:002023-03-03T05:54:13.623Z ERROR Failed preflight check. {"Process": "storagenode", "error": "system clock is out of sync: system clock is out of sync with all trusted satellites", "errorVerbose": "system clock is out of sync: system clock is out of sync with all trusted satellites\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check:96\n\tstorj.io/storj/storagenode.(*Peer).Run:885\n\tmain.cmdRun:251\n\tstorj.io/private/process.cleanup.func1.4:377\n\tstorj.io/private/process.cleanup.func1:395\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:92\n\tmain.main:478\n\truntime.main:250"}
2023-03-03 05:54:13.940547+00:00Error: system clock is out of sync: system clock is out of sync with all trusted satellites
2023-03-03 05:54:13.942649+00:002023-03-03 05:54:13,942 INFO stopped: storagenode (exit status 1)
2023-03-03 05:54:13.943120+00:002023-03-03 05:54:13,942 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
I had this issue and I think I had to manually change the time in my BIOS cause it was syncing to a local time and not UTC. I dont think any try with NTP on system itself worked, but I don’t remember. Currently have windows on that machine (laptop) and it’s showing 1hr behind (I am also EU), so I bet it’s the BIOS I changed.
What’s this BIOS of yours? Looks like a router xD
I would change the +1 timezone to 0 and see what happens.
