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

Node Operators troubleshooting
,
1

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).
Any idea, what I could do to get it running again?
I tried removing and pulling the docker file, but that didn’t help

Thanks and kind regards, Hannes

grafik
grafik638×629 15.8 KB

2

The certificate has not yet been activated Cannot get REALTIME clock frequency: Operation not permitted

Check clock on your host.

2 Likes
3

If I check in the linux shell with “date” it is displaying the correct date and time. Do I need to set it seperately for docker?

4

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

1 Like
5

That did work!

Thanks a lot

1 Like
6

BTW I’d suggest considering getting away from docker.

Podman is lightweight, containers can be managed by systemctl, with all the features like auto-update and namespaces, and what not. Especially on a raspberry pi I’d think the resource conservation shall be important.

I have summarized how to run rootless containers in podman here: Running auto-updatable services in rootless containers with podman on Oracle Linux/RHEL/Fedora with SELinux enabled | Trinkets, Odds, and Ends

1 Like
7

Are there any other solutions to this?

Stopping/removing the container and then restarting with --priviledged makes no difference. I still get the same error shown in the start of the logs. This is also on an Pi4.

8

Where in the command line do you add the flag? Show the full command.

9

Ah, I does work, I had two problems:

  1. I can’t spell - I’d added an extra d to --privileged
  2. I’d put it last, putting it before the --mount and --name flags made it work

I’m back up and running, thanks for your help :slight_smile:

2 Likes