Node v1.5.2 - ERROR : nodestats:cache Get pricing-model/join date failed

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)

Welcome to the forum @grimlock!

Is this a Linux or Windows node ?

This is a linux node

Can you show your docker run command ? Remove any personal info from it.

I’m using this:

docker run -d --restart unless-stopped --stop-timeout 300
–network web
-p 28967:28967
-p 14002:14002
-e WALLET=“0x2ca"
-e EMAIL="grim
om"
-e ADDRESS="n
*********************”
-e STORAGE=“1TB”
–mount type=bind,source="______________/identity",destination=/app/identity
–mount type=bind,source="______________1/storage",destination=/app/config
–name storj storjlabs/storagenode:latest

What is that ^ ?

Can you confirm you are NOT using curly quotes anywhere in your command ?

Your identity is stored in folder under storagenode so this should be ../identity/storagenode

docker run -d --restart unless-stopped --stop-timeout 300
–network web
-p 28967:28967
-p 14002:14002
-e WALLET="—this-is-my-wallet----"
-e EMAIL=“gri—this-is-my-email----m”
-e ADDRESS="—where-the-node-is-exposed----and-post—28967"
-e STORAGE=“1TB”
–mount type=bind,source="/—parent–folder—/identity",destination=/app/identity
–mount type=bind,source="/—parent–folder—/storage",destination=/app/config
–name storj storjlabs/storagenode:latest

--network web
I’m using traefik as a reverse proxy for the dashboard. Hopefully it doesn’t affect anything

0x2 ca is displaying weird because I’m anonymized information using ***

As far as I can see, I’m using straight quotes. they must show as curly because of the forum editor(?)

Does the identity folder need to be under the same parent folder as storage ?

This :arrow_down: should give you an idea of the error

You need to fix the path so your node can locate identity files. Your path should look like

"/—parent–folder—/identity/storagenode

I’ll give that I try…

[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.

The identity folder I’m mapping from the host has only the identity files, no subfolders.
so I agree, that should be ok.

I’m leaning towards that it’s just a side effect of the node being node and that a specific satellite is not aware of my node yet?

When I searched that error message, I saw a previous post mentioning that one satellite needed to be updated.

So far, I got 856.6MB of ingress and 4.64MB of egress… does that mean things should be ok?

Yes, I think you should be fine if you get traffic. Wouldn’t worry about it too much.

That’s good.

Your node is new so it will take time to be vetted completely on each satellite. Good luck :+1:

Sounds good. Thanks for the help, guys!

1 Like

This errors are harmless, we know about this issue, will be fixed in nearest future, should be ignored for now