Does not update the bandwidth graph in version v1.104.5

Node Operators troubleshooting
, ,
1

Hello, everyone,

The node finished updating and since then the bandwidth graph did not update, I restarted the node, and it did not update, finally the entire PC and it remains the same.

In the logs, data is received and sent without error. I attach the last lines.

2024-05-17T09:42:04+02:00 INFO piecestore upload started {Piece ID: ZMUDDNA7D32HB2DTAREVGKYQEZHBIFZMSE5EQO26QSG5WN2O7RJQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 79.127.219.41:54890, Available Space: 4007509637244}
2024-05-17T09:42:04+02:00 INFO piecestore uploaded {Piece ID: ZMUDDNA7D32HB2DTAREVGKYQEZHBIFZMSE5EQO26QSG5WN2O7RJQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 79.127.219.41:54890, Size: 768}
2024-05-17T09:42:04+02:00 INFO piecestore upload started {Piece ID: FD2GPACATD36EIKC4USQLGSR546GBTLXYDEDF3PVCFGKELEGAZXA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 5.161.143.41:24462, Available Space: 4007509635964}
2024-05-17T09:42:04+02:00 INFO piecestore upload started {Piece ID: SQHDSECJCDVK3ZWFDEXVXEAD2SUCMAQKZDBDJ4ZFSQBO22FHK45A, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 79.127.219.41:54892, Available Space: 4007509635964}
2024-05-17T09:42:04+02:00 INFO piecestore uploaded {Piece ID: SQHDSECJCDVK3ZWFDEXVXEAD2SUCMAQKZDBDJ4ZFSQBO22FHK45A, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 79.127.219.41:54892, Size: 768}
2024-05-17T09:42:04+02:00 INFO piecestore uploaded {Piece ID: FD2GPACATD36EIKC4USQLGSR546GBTLXYDEDF3PVCFGKELEGAZXA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 5.161.143.41:24462, Size: 276992}
2024-05-17T09:42:04+02:00 INFO piecestore download started {Piece ID: 3ZTKQUPVT3TLVDNV7PKFKZOVHKQIR7SUG7MZKVCE4NOYKJXBLQYA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 512, Remote Address: 79.127.213.34:43670}
2024-05-17T09:42:05+02:00 INFO piecestore downloaded {Piece ID: 3ZTKQUPVT3TLVDNV7PKFKZOVHKQIR7SUG7MZKVCE4NOYKJXBLQYA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 512, Remote Address: 79.127.213.34:43670}
2024-05-17T09:42:05+02:00 INFO piecestore download started {Piece ID: Q2IEHQSGXTFBYIXMXPK6WMPHQKK4CE53TYCLA4DZBS3TCOUPI4FA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 181248, Remote Address: 109.61.92.78:60358}
2024-05-17T09:42:05+02:00 INFO piecestore download started {Piece ID: KGLXZV36QXPV5T7ZUZVMNSTGZ5EIHIUVFHZNK4SKTS3OR45X5OCA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 362496, Remote Address: 79.127.201.213:58678}
2024-05-17T09:42:06+02:00 INFO piecestore upload started {Piece ID: U3S3T25TEJBODCHIDN2J2XD72KDX77FGLQAJ7XTBCKHQ5XBDA2UQ, Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, Action: PUT_REPAIR, Remote Address: 49.13.226.201:34972, Available Space: 4007509357180}
2024-05-17T09:42:06+02:00 INFO piecestore uploaded {Piece ID: U3S3T25TEJBODCHIDN2J2XD72KDX77FGLQAJ7XTBCKHQ5XBDA2UQ, Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, Action: PUT_REPAIR, Remote Address: 49.13.226.201:34972, Size: 181504}
2024-05-17T09:42:06+02:00 INFO piecestore downloaded {Piece ID: Q2IEHQSGXTFBYIXMXPK6WMPHQKK4CE53TYCLA4DZBS3TCOUPI4FA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 181248, Remote Address: 109.61.92.78:60358}
2024-05-17T09:42:06+02:00 INFO piecestore downloaded {Piece ID: KGLXZV36QXPV5T7ZUZVMNSTGZ5EIHIUVFHZNK4SKTS3OR45X5OCA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 362496, Remote Address: 79.127.201.213:58678}
2024-05-17T09:42:07+02:00 INFO piecestore download started {Piece ID: WBSWF65NUJIGFBTGLZGJ267Y5FU436BHWJGIEPH6PIABZCNNX4DA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 33792, Remote Address: 79.127.226.102:56400}
2024-05-17T09:42:07+02:00 INFO piecestore upload started {Piece ID: ANOO6PP7W7IW2R3BNK3EEHKYYW6DWAA37V5V4C23RAY4KIW6GK6Q, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 79.127.201.210:39802, Available Space: 4007509175164}
2024-05-17T09:42:07+02:00 INFO piecestore downloaded {Piece ID: WBSWF65NUJIGFBTGLZGJ267Y5FU436BHWJGIEPH6PIABZCNNX4DA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: GET, Offset: 0, Size: 33792, Remote Address: 79.127.226.102:56400}
2024-05-17T09:42:07+02:00 INFO piecestore uploaded {Piece ID: ANOO6PP7W7IW2R3BNK3EEHKYYW6DWAA37V5V4C23RAY4KIW6GK6Q, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 79.127.201.210:39802, Size: 173568}
2024-05-17T09:42:07+02:00 INFO piecestore uploaded {Piece ID: ZQZSXGRZBKA7IJVF3LJRRT5TFO4ZRRFCY4DTDOERRNFNWOQ2TBDA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Remote Address: 5.161.192.57:20276, Size: 240128}
2024-05-17T09:42:08+02:00 INFO piecestore upload started {Piece ID: Y7JBRJELSOQXL27JP265D7IQRWMLQITF3BF6ZHCKFJCJ5DUP26MA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT_REPAIR, Remote Address: 5.161.65.137:33430, Available Space: 4007508760444}
2024-05-17T09:42:08+02:00 INFO piecestore uploaded {Piece ID: Y7JBRJELSOQXL27JP265D7IQRWMLQITF3BF6ZHCKFJCJ5DUP26MA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT_REPAIR, Remote Address: 5.161.65.137:33430, Size: 2304}

I have seen that at the time of the update in the log the following has been recorded in the bandwidth DB:

2024-05-17T08:36:49+02:00 INFO db.migration.57 Create new bandwidth_usage table, backfilling data from bandwidth_usage_rollups and bandwidth_usage tables, and dropping the old tables.
2024-05-17T08:36:59+02:00 INFO db.migration Database Version {“version”: 57}
2024-05-17T08:37:00+02:00 INFO bandwidth Persisting bandwidth usage cache to db

I also attach a screenshot of the dashboard

image
image928Ă—428 18.1 KB

The node is running on W11 23H2

Should I worry? How can I solve it?

Thanks in advance

2

I don’t think so

z
z704Ă—426 25.6 KB

3

I don’t think it’s that either, if it had given an error it would be reflected in the log. Let’s see if someone can see what happened.

4

Checking the log again a couple of minutes ago, I found this record:

2024-05-17T10:24:12+02:00 INFO bandwidth Persisting bandwidth usage cache to db

And the dashboard has been updated, but the data I see is not current, I would say.

image
image938Ă—458 19.4 KB

Reviewing the update notes, I think it has more to do with this point:

image

5

It does. It’s a performance optimization, preventing having to write to the bandwidth.db on every upload. It safes a lot of IO. Worth the tradeoff if you ask me.

3 Likes
6

So it is working correctly and the graph will be updated every time the node sends the orders to the satellites? (Approximately every hour, right?)

7

You might want to switch to Grafana instead. It shows the traffic flow not only live. It also shows a lot of other useful data.

1 Like