One satelite shows 90% online, ther others 100%

is this normal? node id 1gmDCyzjP6sCz6X6fZwVXrHndFztkS1GWFqE1jiVZTVmp4QRSf

No, it’s not normal. This is mean that this satellite was unable to contact your node.
You may check when it was happened:

Then check logs of your firewall/router on those dates to figure out why is it happened.

You may also find some explanations in your node’s logs as well, search for ping satellite failed except rate.

hmm… no output

root@bo-omv:~# ./check-online-score.sh
root@bo-omv:~#

script:

for item in `curl -sL http://localhost:14002/api/sno | jq '.satellites[].id' -r`; do
    curl -s http://192.168.0.163:14002/api/sno/satellite/$item | \
    jq '{id: .id, auditHistory: [.auditHistory.windows[] | select(.totalCount != .onlineCount)]}'
done

are there a oneline command that can do that? will try and locate the log

i think

docker logs storagenode | grep "ping satellite failed except rate"

EDIT… no that did not work

root@bo-omv:~# docker logs storagenode | grep 'ping satellite failed except rate'
-bash:  grep: kommando ikke fundet
root@bo-omv:~#

but grep is installed…

root@bo-omv:~# grep
Brug: grep [FLAG]... MØNSTRE [FIL]...
Prøv "grep --help" for mere information.
root@bo-omv:~#

should be

`curl -sL http://192.168.0.163:14002/api/sno

it should be

docker logs storagenode 2>&1 | grep "ping satellite failed" | grep -v "rate"

upps…

root@bo-omv:~# ./check-online-score.sh
jq: error (at <stdin>:1): Cannot iterate over null (null)
{
  "id": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6",
  "auditHistory": []
}
{
  "id": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S",
  "auditHistory": [
    {
      "windowStart": "2024-09-10T00:00:00Z",
      "totalCount": 5,
      "onlineCount": 4
    }
  ]
}
{
  "id": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs",
  "auditHistory": []
}
root@bo-omv:~#
root@bo-omv:~# docker logs storagenode 2>&1 | grep "ping satellite failed" | grep -v "rate"
root@bo-omv:~#

looks very strange

Why is so? The docker logs keeps only 5 logs with 20MiB each, also they got deleted with the container recreating.
You can see the date when the node missed the audit check. Since it is fairly new, it is expected to be sensitive to downtime, see

i assume that is if the logs had not been deleted… would be nice if the logs was not deleted at restart but only after 30 days…

but oh well i will just ignore that only one satelite says 90% and then hope it goes up again on its own

Easy

But likely you would need a logrotate configured too.

yes. It needs 30 days online to fully recover. Each downtime requires another 30 days online to recover.

question came up in my head… are there not a way so “ask” us1.storj.io:7777 about this too ?

EDIT just when it failed so i could check against my router logs

Yes, restart the node to force check-in. However, the restart itself would produce a downtime, so, well :wink:

Just keep it online, that’s all what’s needed. The node performs an automatically check-in every hour by default.

so there are no way to directly ask the satelite when a given node missed the check?

could be nice as i could then look in my router first… or maybe it was when i restarted the node myself

Q to the above… can a node restart itself?

yes. but only for FATAL or/and Unrecoverable errors, and if the restart policy for the container is set to always or unless-stopped.

See also

you missed that part…

nope. I usually answer only on questions which can be answered and trying to do not answer on duplicate questions from the same requester.
I would try to expand my previous response.
There is no way to do so except restart the node to force check-in, however, this will only updates reputation on your node and would try to contact it and report the result of the attempt (here you would see a ping satellite failed response, if the satellite was unable to contact your node and the reason), and maybe some other useful stat, like the disk usage confirmed on the satellites, and so on.

There is no way to force the satellite to audit your node again. Just keep it online.

no problemo

but it could be a nice to have feature… ie to ask when a node failed the check so diagnosis of network problems was possible

but yes, i dont want to force a check, that could lead to cheating to get better statistics

I do not think so. It’s a spending developers time for nothing. You may just bring it online and check, that the online score would grow.
I see no point to implement the force check, which will increase load on the satellites without any benefit for the customers.

You always may restart the node and make sure that’s not throwing any errors like ping satellite failed.
Or use your mobile phone and the mobile internet and try to open your public IP with port, you will get a response, if it’s externally available. Also UptimeRobot or similar would do the same for you over the time with a nice graphs.

i did not say force check

Can you not just check your e-mail offline notification date/time stamps to corelate to your router logs?

Cheap DDNS service - like duckdns or something?

if i got them yes

no i use static up so no need for DDNS