So all DB are store in my mount point.
It’s an brand new node…
To create file in mount point, or to lunch docker…I must do an sudo
Mayby docker contener is lunch as user and this one cannot write in mount point ?
If it was the case, so I should not have files in, and that’s not what i’m having :
ls /media/StorJ/
config.yaml orders revocations.db storage test test.fds
How disk latency can be benmarked/test ?
Latency could be weird also, everyting is gigabyte connected and working fine.
I’m using same storage to read big 3D flat blueray without issues ^^
on a new node i bet you it’s a permissions issue…
you can do a sudo chown -R nobody:nogroup /media/StorJ
i think that would solve it
you can ofc use whatever users and groups you like… but that blanket one basically just gives everybody access because the files doesn’t belong to anyone, might not be optimal from a security perspective… but it sure won’t cause any permission problems.
and then when you get the node working you can go back and tinker with what folder / file permissions you need for storj.
any particular reason you like to suffer the pains of using semi random capital letters in the folder names?
any regular tool for measuring disk performance will do, but it’s not latency…
ERROR contact:service ping satellite failed {“Satellite ID”: “121RTU84Ticf2L1ntiuUuvgk3vzoA6”, “attempts”: 8, “error”: “ping satellite: failed to dial storage node (ID: 1aWS6BZNdydfeCSWsmeTsr) at address MyPublixFixedIP:28967: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert", “errorVerbose”: "ping satellite: failed to dial storage node (ID: 1aW6BZNdydfekdEY5CSWsmeTsr) at address MyPublicFixedIp:28967: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
Just confirmation that it’s not signed. The signed identity should contain 6 files. But it’s better to check like this:
grep -c BEGIN "/home/freebox/Library/Application Support/StorJ/identity/storagenode/ca.cert"
grep -c BEGIN "/home/freebox/Library/Application Support/StorJ/identity/storagenode/identity.cert"
This was expected right away, when I saw 2 files instead of 6
It’s not a problem, just request a new auth token and sign the identity Identity - Node Operator