Returning Node Operator. Started a new Node. Up for about 10 days now. I show no repair nor audit traffic. Grepping the log for GET_REPAIR and GET_AUDIT returns nothing. Plenty of normal ingress and egress. Nearly 100GB stored in the 10 days. Any reason I wouldn’t be getting repair/audit traffic?
1 Like
Is repair and audit maybe limited for nodes that are still in their vetting period? To be honest I don’t know either…
1 Like
I have the same situation. New node for 12 days and no audit. It’s the first node I’ve started since changing the data allocation percentage from 5 to 1%. Maybe this is the reason? But I thought it only affected the data and not the audits. So the node will take months to verify
I started a new node around February 10th, I already have 2 full nodes, and I’m at 94 audits
My node started il 23/02 but audit 0. The log is correct and the flows for upload and download is normal. i have 30 nodes and this “problem” occur only for this node. I wait another days and reply here.
I haven’t get_audit and get_repair in my log but the download and upload is correct and don’t have error o fatal or others error,
This is the log:
| 2024-03-07T10:49:58+01:00 | INFO | piecestore | downloaded | {Piece ID: AA7V76OQ5DUNAUWHEJQI6JV2GLAT2BK6SP23O5EZWJWKXQ33BE6A, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 268032, Remote Address: 79.127.223.130:39838} |
|---|---|---|---|---|
| 2024-03-07T10:50:03+01:00 | INFO | piecestore | upload started | {Piece ID: ZIMXG3OXAJREFU5OS3PQMFZNOAXTBRUE5APB2WZ5K5F5FMNYOF6Q, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 3492768571776, Remote Address: 79.127.205.226:38402} |
| 2024-03-07T10:50:03+01:00 | INFO | piecestore | uploaded | {Piece ID: ZIMXG3OXAJREFU5OS3PQMFZNOAXTBRUE5APB2WZ5K5F5FMNYOF6Q, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Size: 19968, Remote Address: 79.127.205.226:38402} |
| 2024-03-07T10:50:06+01:00 | INFO | piecestore | upload started | {Piece ID: XI7OK43K2NITSNTS3DZBR2MLKWSO6QCH3FT6ELWZDUIVM5XOALFA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 3492768551296, Remote Address: 79.127.201.209:44402} |
| 2024-03-07T10:50:06+01:00 | INFO | piecestore | uploaded | {Piece ID: XI7OK43K2NITSNTS3DZBR2MLKWSO6QCH3FT6ELWZDUIVM5XOALFA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Size: 768, Remote Address: 79.127.201.209:44402} |
| 2024-03-07T10:50:07+01:00 | INFO | piecestore | download started | {Piece ID: O7MMLTFNKFFTQHJDDCSPPPXTMDLQNRB6H4QSDSB63EHXYJMSHL3Q, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 768, Remote Address: 79.127.223.130:45612} |
| 2024-03-07T10:50:07+01:00 | INFO | piecestore | downloaded | {Piece ID: O7MMLTFNKFFTQHJDDCSPPPXTMDLQNRB6H4QSDSB63EHXYJMSHL3Q, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 768, Remote Address: 79.127.223.130:45612} |
| 2024-03-07T10:50:08+01:00 | INFO | piecestore | download started | {Piece ID: XI7OK43K2NITSNTS3DZBR2MLKWSO6QCH3FT6ELWZDUIVM5XOALFA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 512, Remote Address: 79.127.201.210:37800} |
| 2024-03-07T10:50:08+01:00 | INFO | piecestore | downloaded | {Piece ID: XI7OK43K2NITSNTS3DZBR2MLKWSO6QCH3FT6ELWZDUIVM5XOALFA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 512, Remote Address: 79.127.201.210:37800} |
| 2024-03-07T10:50:12+01:00 | INFO | piecestore | download started | {Piece ID: XI7OK43K2NITSNTS3DZBR2MLKWSO6QCH3FT6ELWZDUIVM5XOALFA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 512, Remote Address: 79.127.201.210:37800} |
| 2024-03-07T10:50:12+01:00 | INFO | piecestore | downloaded | {Piece ID: XI7OK43K2NITSNTS3DZBR2MLKWSO6QCH3FT6ELWZDUIVM5XOALFA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 512, Remote Address: 79.127.201.210:37800} |
| 2024-03-07T10:50:13+01:00 | INFO | piecestore | upload canceled | {Piece ID: K4K4GWMHDC72AZEVMGD7T3NOLQU6O6PG7WAY3URXRYLLSMQGGH2A, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Size: 131072, Remote Address: 73.57.45.46:48372} |
| 2024-03-07T10:50:15+01:00 | INFO | piecestore | upload started | {Piece ID: CK66GQZXNKPMREWU53WE6WKNNKBAUGGS4TLNSPE6B4TCB7OR3FQQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 3492768550016, Remote Address: 79.127.205.226:38402} |
| 2024-03-07T10:50:15+01:00 | INFO | piecestore | uploaded | {Piece ID: CK66GQZXNKPMREWU53WE6WKNNKBAUGGS4TLNSPE6B4TCB7OR3FQQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Size: 4352, Remote Address: 79.127.205.226:38402} |
| 2024-03-07T10:50:16+01:00 | INFO | piecestore | upload started | {Piece ID: QULJJMSDTJ3OQG7SKGUNSKUQ6K2GISBVDG7RV6UNHPI7YKBVESAA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 3492768545152, Remote Address: 79.127.213.33:56968} |
| 2024-03-07T10:50:20+01:00 | INFO | piecestore | upload started | {Piece ID: NWNSO44RY6NR2KQYIBB4XMD4R2PMCFBRHDMPD2DBSWSRSZSGPECQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 3492768545152, Remote Address: 79.127.226.98:46710} |
| 2024-03-07T10:50:20+01:00 | INFO | piecestore | uploaded | {Piece ID: NWNSO44RY6NR2KQYIBB4XMD4R2PMCFBRHDMPD2DBSWSRSZSGPECQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Size: 1280, Remote Address: 79.127.226.98:46710} |
| 2024-03-07T10:50:21+01:00 | INFO | piecestore | upload started | {Piece ID: E5AT34OTTIFMRZA66HJKJGZVPHG6HWMDQB37OMP4A37HMZJ76ZHQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 3492768543360, Remote Address: 79.127.205.227:37848} |
| 2024-03-07T10:50:22+01:00 | INFO | piecestore | uploaded | {Piece ID: E5AT34OTTIFMRZA66HJKJGZVPHG6HWMDQB37OMP4A37HMZJ76ZHQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Size: 2319360, Remote Address: 79.127.205.227:37848} |
| 2024-03-07T10:50:26+01:00 | INFO | piecestore | upload started | {Piece ID: TTI74ETC3HHALYWFTFJHTAOND7GJWT4WH2NWN35S5OPOD4BZMYFA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 3492766223488, Remote Address: 5.161.192.57:59296} |
I am also experiencing this issue.
Storj recently reduced the amount of traffic unvetted nodes get from 5% to 1%. This will also reduce initial audits and slow down vetting. See: Unvetted/Vetted node traffic - #9 by heunland
The reason this change was made was we had the peverse situation unvetted nodes were seeing more traffic than vetted nodes. This will have a side effect of making the vetting process a bit longer initially.
4 Likes
Ok, i view this modify, but in 15 days not even one audit is very strange.
1 Like
Not really. For the last few weeks the amount of data coming in on my newest, unvetted node has been very low - consequently the amount of audits is also low
2 Likes
How long will the vetting process take now?
I don’t think we’ve been running with the new unvetted-node-ingress-rate changes long enough for anyone to know for sure. My guess is three months: but we’re finding out now!
New node from 2024-02-12 (Saltlake is excluded on this node):
No other new nodes on this IP.
US1 finished very early because of the great number of small files from this satellite.
┌────────────────────────────────┬─────────────┬
│ SATELLITE │ HELD AMOUNT │
│ Joined Month │ Total │
├────────────────────────────────┼─────────────┼
│ ap1.storj.io:7777 (34% Vetted > 16/100 Audits)
│ 2024-02-12 2 │ $ 0.00 │
├────────────────────────────────┼─────────────┼
│ eu1.storj.io:7777 (OK) │ │
│ 2024-02-12 2 │ $ 0.00 │
├────────────────────────────────┼─────────────┼
│ us1.storj.io:7777 (OK) │ │
│ 2024-02-12 2 │ $ 0.05 │
├────────────────────────────────┼─────────────┼
There seems to be an uptick in data today so maybe check if you get some audits soon.
My unvetted node got 32 GB and my vetted node nearly hit 80GB in a day so it’s quite decent.
I view a lot of ingress but actually 0 audit yet. i wait
grep of the logs for GET_AUDIT returns nothing
grep of the logs for GET_REPAIR returns nothing
2 Likes
I see, then please keep us updated when you start to receive them. It should pass 100 audits eventually, so they should come after the more data is collected.
Stopped my node yesterday, updated it, then started up again, to see if that would fix the issue. Still no GET_AUDIT, still no GET_REPAIR. ~120GB stored. My version # went backwards?? I was on 1.96.6, now I’m on 1.95.1 for some reason?
Hi, how did you update?