Just set up a node this morning, and got this on the logs:
{
“error”: “heldamount service error: node not found: 1xWY4xiXUBFAMkvocoHQTTQPjVwAokud4e******************; heldamount service error: node not found: 1xWY4xiXUBFAMkvocoHQTTQPjVwAokud4e******************; heldamount service error: node not found: 1xWY4xiXUBFAMkvocoHQTTQPjVwAokud4e******************”,
“errorVerbose”: “group:
— heldamount service error: node not found: 1xWY4xiXUBFAMkvocoHQTTQPjVwAokud4e******************
tstorj-io/storj/storagenode/heldamount.(Service).GetAllPaystubs:132
storj-io/storj/storagenode/nodestats.(Cache).Run.func1:78
storj-io/storj/storagenode/nodestats.(Cache).satelliteLoop:233
storj-io/storj/storagenode/nodestats.(Cache).Run:77
storj-io/storj/private/lifecycle.(Group).Run.func1:56
golang-org/x/sync/errgroup.(Group).Go.func1:57
— heldamount service error: node not found: 1xWY4xiXUBFAMkvocoHQTTQPjVwAokud4e************
storj-io/storj/storagenode/heldamount.(Service).GetAllPaystubs:132
storj-io/storj/storagenode/nodestats.(Cache).Run.func1:78
storj-io/storj/storagenode/nodestats.(Cache).satelliteLoop:233
storj-io/storj/storagenode/nodestats.(Cache).Run:77
storj-io/storj/private/lifecycle.(Group).Run.func1:56
golang-org/x/sync/errgroup.(Group).Go.func1:57
— heldamount service error: node not found: 1xWY4xiXUBFAMkvocoHQTTQPjVwAokud4e************
storj-io/storj/storagenode/heldamount.(*Service).GetAllPaystubs:132
storj-io/storj/storagenode/nodestats.(*Cache).Run.func1:78
storj-io/storj/storagenode/nodestats.(*Cache).satelliteLoop:233
storj-io/storj/storagenode/nodestats.(*Cache).Run:77
storj-io/storj/private/lifecycle.(*Group).Run.func1:56
golang-org/x/sync/errgroup.(*Group).Go.func1:57”
}
it seems from a post related to v1.3.3. the error is harmful, but indicates a satellite needs updating… is that the same case here?
just wanted to make sure
(I cleaned up the json, anonymized my node ID, and modified the file path so they don’t look like links for the parser, as I can’t post more than 2 links as a new user)
[grimlock@hostname ~]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
da8695a0ec2b storjlabs/storagenode:latest "/entrypoint" 53 minutes ago Up 53 minutes 0.0.0.0:14002->14002/tcp, 0.0.0.0:28967->28967/tcp storj
4fca3366b69a traefik:1.7.2-alpine "/entrypoint.sh trae…" 3 days ago Up 3 days 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp traefik
[grimlock@hostname ~]$ docker exec -it storj sh
/app # ls -la
total 23968
drwxr-xr-x 1 root root 4096 Jun 23 18:35 .
drwxr-xr-x 1 root root 4096 Jun 23 18:35 ..
drwxr-xr-x 1 1000 1000 0 Jun 21 10:19 config
-rwxr-xr-x 1 root root 91 May 20 10:37 dashboard.sh
drwxr-xr-x 1 1000 1000 0 Jun 21 10:16 identity
-rwxr-xr-x 1 root root 24527864 May 20 10:49 storagenode
/app # ls -l identity/
total 7
-rw-r--r-- 1 1000 1000 514 Jun 23 18:34 ca.1592937254.cert
-rw-r--r-- 1 1000 1000 1044 Jun 23 18:34 ca.cert
-rw-r--r-- 1 1000 1000 241 Jun 23 18:34 ca.key
-rw-r--r-- 1 1000 1000 1056 Jun 23 18:34 identity.1592937254.cert
-rw-r--r-- 1 1000 1000 1586 Jun 23 18:34 identity.cert
-rw-r--r-- 1 1000 1000 241 Jun 23 18:34 identity.key
/app # ls storagenode
storagenode
/app # ls config/
config.yaml storage/ trust-cache.json
/app # ls config/storage/blobs/
6r2fgwqz3manwt4aogq343bfkh2n5vvg4ohqqgggrrunaaaaaaaa qstuylguhrn2ozjv4h2c6xpxykd622gtgurhql2k7k75wqaaaaaa v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa
pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa
/app #
I’m posting the above just to show the locations of the folders inside the container that is running… other then the identity folder, is there anything else I should change?
Pretty sure the identity is not the issue here. At least, it’s not that the node can’t find it. The problem is that when trying to get paystub info from the satellite, the satellite isn’t aware of this node.
I’m guessing this is just a side effect of the node being new. Are you getting traffic on this node?
The identity path simply has to point to the exact path where the identity files are. It doesn’t matter where you keep them as long as those files are in the path you point the docker container to without any sub-folders.