No Audit Traffic and No Repair Traffic?

Node Operators troubleshooting
21

Same. 10-days old node in Pacific Northwest, 71GB stored, zero audits.

1 Like
22

Followed the Manual Updates process in here

docker stop -t 300 storagenode 
docker rm storagenode 
docker pull storjlabs/storagenode:latest  
docker run -d --restart unless-stopped --stop-timeout 300 .......
23

Not answering your question: but yeah it feels like most nodes got up to 1.96.6… then once 1.95.1 became the new minimum version many of them went backwards to it. Strange.

24

Yes, the current minimal version is 1.95.1. But we do a rollout, so your nodes should be eventually updated to the latest one.

But it’s still not related to how often audits are performed. I believe it’s a new normal after the change regarding a vetting period

25

Today after 20 days from node’s setup, i have received the first 2 audit.

26

Looks like it would take way more than a month to get vetted.

1 Like
27

Finally started to get audits at 01:28 UTC on March 9th (Node launched on Feb 22). They have been happening regularly, now at 28 audits (~0.6 audits/hour). All from US1 satellite. None from others. Still no repair traffic.

2 Likes
28

So far 44 audits from a single satellite only, started 3 days ago:

# bzgrep GET_AUDIT /var/log/storagenode.* | sed -E 's/.*"Satellite ID": "([^"]*)".*/\1/' | sort | uniq -c
  44 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S

# bzgrep GET_AUDIT /var/log/storagenode.* | sed -E 's/^.*([0-9]{4}-[0-9]{2}-[0-9]{2}).*/\1/' | sort | uniq -c
  18 2024-03-21
  16 2024-03-22
  10 2024-03-23
1 Like
29

There is a more easy way, just check the API endpoint,

it will return a json object, and you can select directly (with jq on Linux, or ConvertFrom-Json in PowerShell).

30

Hi, after 1 month my node is verified on us1 and eu1 with over 100 audit for every satellite, ap1 is on 5 audit. Then a new node for verify, i suppose, that employs about 2 month for all satelites. Thanks

1 Like
31

There does not seem to any audit stats. or was that comment not addressed to me?

"sno" endpoint output 
# curl -L http://localhost:14002/api/sno | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    44  100    44    0     0  43307      0 --:--:-- --:--:-- --:--:-- 44000
100  1184  100  1184    0     0   538k      0 --:--:-- --:--:-- --:--:--  538k
{
  "nodeID": "12xxxx....xxx",
  "wallet": "0xxxxxxxxxxxx",
  "walletFeatures": null,
  "satellites": [
    {
      "id": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE",
      "url": "saltlake.tardigrade.io:7777",
      "disqualified": null,
      "suspended": null,
      "currentStorageUsed": 20896512
    },
    {
      "id": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6",
      "url": "ap1.storj.io:7777",
      "disqualified": null,
      "suspended": null,
      "currentStorageUsed": 1956615680
    },
    {
      "id": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S",
      "url": "us1.storj.io:7777",
      "disqualified": null,
      "suspended": null,
      "currentStorageUsed": 172588335232
    },
    {
      "id": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs",
      "url": "eu1.storj.io:7777",
      "disqualified": null,
      "suspended": null,
      "currentStorageUsed": 20662719232
    }
  ],
  "diskSpace": {
    "used": 195587197824,
    "available": 10000000000000,
    "trash": 0,
    "overused": 0
  },
  "bandwidth": {
    "used": 234171161344,
    "available": 0
  },
  "lastPinged": "2024-03-24T10:23:33.650110413-07:00",
  "version": "1.97.3",
  "allowedVersion": "1.95.1",
  "upToDate": true,
  "startedAt": "2024-03-22T10:22:17.724036663-07:00",
  "configuredPort": "28967",
  "quicStatus": "OK",
  "lastQuicPingedAt": "2024-03-24T10:22:20.090735497-07:00"
}
32

Yes, this is a satellites list, then you need to use the remained part of the linked script

The complete script may look like this:

for item in `curl -sL http://localhost:14002/api/sno | jq '.satellites[].id' -r`; do
    curl -s http://localhost:14002/api/sno/satellite/$item | \
    jq '{id: .id, auditHistory: .auditHistory.windows[]}'
done
2 Likes
33

Been running since 6th of march on two nodes, still no audit or repair traffic at all.

34

Same problem here. One node started 6th of march still waiting for first audit traffic. :thinking:

1 Like
35

Still no audits. Not a single audit after 4 weeks. :roll_eyes:

I wonder what criteria might trigger the audit process? Is there a minimum of data a node needs to accumulate before audit begins?

36

Hi, the node is the only node in your ip/subnet? or you have others nodes on one ip?

37

According to storjnet.info there is no other node in this subnet.

38

I wonder what vetting period to expect now? I understand it was designed to take an everage of 1 month at 5% traffic for new nodes.

Now they changed the traffic number to 1%. Does it mean new expectation is 5 month? :thinking:

Even if this is the case I should have seen some audit traffic for my 3 new nodes.

Could it be that the audit process is completely broken atm?

39

it’s not true. I had first audit after 3 week and it verified in a week about for us1 and eu1. actually after 2 month it verified also for ap1

40

I now noticed a first audit request for the oldest of the 3 nodes. So I can confirm it is not broken.

This was after 4 weeks and shortly after upgrading from 1.96.6 to 1.101.2. The latter might be just coincidence.