Hi, my storagenode is not working anymore. Probably it happened after auto-updating via watchtower. The logfile says something about a certificate, that is not trusted and the date in the log also appears very strange for me: --1969-12-31 23:59:59– I am using docker on raspberry pi os (buster). …

[image] arrogantrabbit: Cannot get REALTIME clock frequency: Operation not permitted [image] docker: unknown syscalls return invalid `EPERM` (#11774) · Issues · alpine /... This is exposed due to the upgrade to musl-1.2. When trying to execute the syscall clock_gettime64, docker r…

Storagenode stopped working on Pi4 - ERROR: The certificate of 'version.storj.io' is not trusted

Node Operators troubleshooting

arrogantrabbit September 20, 2024, 5:53pm 4

You can workaround it by adding --privileged to the docker run command

1 Like

System clock is out of sync after reboot

Storagenode Docker Update: Changes To Binaries Location For Persistence Between Restarts