Disqualified - audit 59% on eu1, but i think he got all the files

hii,
Got email: date 27.05, node is disqfalificated on europe-west-1 sattelite, right?

So my concern is was it rightful, do i really lost files?
i doubts because i suspect audit signal could not connect with my node, (due to some offline times, i was doing works on computer and had to be offline for several hours for few days lastly, but its online score dropped only from 100% to 95% at most)

Soo only on eu1 satelitte i got audits to 58%.

The node is running more than 1 year no porblem.
I always though audit score is only if sattelite is sure that node lost files, but i read from dashboard this:

'Percentage of successful pings/comunication between the node &
satelite". see screen(theres 4 screens tottal, if You click the image):

Saw nothing interested in storagenode.log, You want some quotes? what to search for? the log got 1GB.
So i would like to return my node on this sattelite, can we restore it?
i think it has all the filles.

Hi @Ruskiem,
If is says ‘Suspended’ then the node can recover. If it says ‘Disqualified’ then there is no recovering, that is the end of the node on that satellite.

If that screen shot is correct - you are far to many versions behind ! V1.25.2 is now too old, we are on v1.30.2 - node is lost on that satellite, I would upgrade to try and save the others…

bruuuh’s, im providing feedback,
in the end my node is just a pretext for finding bugs and things to work better.
Yea, its old, from this date “2021/03/25 14:47:21” it tries to update itself but faild, due to some :“invalid character ‘p’ after top-level value” i guess devs should be informed about that too, from that date, the line just keeps reapeting to this day in the same patern:

2021/03/22 14:47:10 storage node version is up to date
2021/03/22 20:47:09 downloading versions from https://version.storj.io/release/
2021/03/22 20:47:10 storage node version is up to date
2021/03/23 02:47:13 downloading versions from https://version.storj.io/release/
2021/03/23 02:47:13 storage node version is up to date
2021/03/23 08:47:13 downloading versions from https://version.storj.io/release/
2021/03/23 08:47:14 start downloading https://github.com/storj/storj/releases/download/v1.25.2/storagenode_windows_amd64.zip to C:\Windows\TEMP\storagenode408504823
2021/03/23 08:47:14 bad status: 404 Not Found
2021/03/23 14:47:13 downloading versions from https://version.storj.io/release/
2021/03/23 14:47:13 start downloading https://github.com/storj/storj/releases/download/v1.25.2/storagenode_windows_amd64.zip to C:\Windows\TEMP\storagenode375541994
2021/03/23 14:47:27 finished downloading https://github.com/storj/storj/releases/download/v1.25.2/storagenode_windows_amd64.zip to C:\Windows\TEMP\storagenode375541994
2021/03/23 14:47:29 restarting service storagenode
2021/03/23 14:47:36 service storagenode restarted successfully
2021/03/23 20:47:13 downloading versions from https://version.storj.io/release/
2021/03/23 20:47:14 storage node version is up to date
2021/03/24 02:47:13 downloading versions from https://version.storj.io/release/
2021/03/24 02:47:18 storage node version is up to date
2021/03/24 08:47:16 downloading versions from https://version.storj.io/release/
2021/03/24 08:47:17 storage node version is up to date
2021/03/24 14:47:16 downloading versions from https://version.storj.io/release/
2021/03/24 14:47:17 storage node version is up to date
2021/03/24 20:47:16 downloading versions from https://version.storj.io/release/
2021/03/24 20:47:17 storage node version is up to date
2021/03/25 02:47:16 downloading versions from https://version.storj.io/release/
2021/03/25 02:47:17 storage node version is up to date
2021/03/25 08:47:20 downloading versions from https://version.storj.io/release/
2021/03/25 08:47:21 storage node version is up to date
2021/03/25 14:47:20 downloading versions from https://version.storj.io/release/
2021/03/25 14:47:21 invalid character ‘p’ after top-level value
2021/03/25 20:47:20 downloading versions from https://version.storj.io/release/
2021/03/25 20:47:21 invalid character ‘p’ after top-level value
2021/03/26 02:47:20 downloading versions from https://version.storj.io/release/
2021/03/26 02:47:21 invalid character ‘p’ after top-level value
2021/03/26 08:47:24 downloading versions from https://version.storj.io/release/
2021/03/26 08:47:25 invalid character ‘p’ after top-level value
2021/03/26 14:47:24 downloading versions from https://version.storj.io/release/
2021/03/26 14:47:25 invalid character ‘p’ after top-level value
(…)
2021/06/01 12:39:14 downloading versions from https://version.storj.io/release/
2021/06/01 12:39:15 invalid character ‘p’ after top-level value

1 Like

The same invalid character ‘p’ after top-level value log entry was showing at a similar time for a small number of node operators. I think the old version will unlikely be the root cause of the disqualification.

Please try manually updating and the node should continue to run on the other satellites.

sure, but im interested in investigation what happened,
shouldn’t happened to a long time perfect node so fast

I just got two suspended emails followed immediately by two disqualified emails for a node that was powered off due to storms and being remote without any means to turn it on. Oh well.

I linked the above thread because of the same error, and we worked through to a solution.

Again I don’t think the old version or that invalid character ‘p’ error is directly linked to the disqualification, but both point to a possible data integrity issue. Have you run any disk checks?

sure, the hdd seems to work just fine, ran just a regular windows 10 scan disc. I has other node on this harddrive and its fine. i would like to perform some test in cooperation with sattelite to verify statemen: i have lost some files.

because im saying i did not.
(porobably, lest check?)
im making my statement: current audit checking system, faild,
falsly accusing my node of losing of files, but what really happened was just time offline. I dont know how to check it,

im writing here to reach official tech support from storj,
and so it can be seen for everybody as well.

I will link this post from Alexey outlining the reasons a node can currently be disqualified:

I will add that you can also be disqualified if your node is more than 3 versions behind the current version.

1 Like

yea all im saying is i dont belive just words, lets check if that really was the case

First step would be to check your logs for “GET_AUDIT” and “failed” in the same line.

cant find any “failed” in entire 1GB log file, using notepad++,
(the search fuction works checked on “GET_AUDIT”)

so i have 153372 “GET_AUDIT” matches, and yet not 1 “failed” mayby other wording?
edit: (i go lots of “failed” without “” in normal download failed, just not with GET_AUDIT)

Edit2: yeah, “file does” is found only 4 times in entire 1GB storagenode.log, and it refers to:

“Action”: “GET”, “error”: “file does not exist”,

And example of a failed audit from my node (due to missing piece):

You could also process your log file with the community success rate script:

the log does not contain failed audit messages.
it is only on satellite side.

1 Like

The log does in fact contain failed audit messages. You can see an example of one in the post directly above your post.

no way
I mean if a piece is in place, you will not know whether it is faulty or not when audit comes
Here is no log messages for pieces that not lost but broken

Somehow my node still claims that «Running the minimal allowed version: v1.24.0». Storjlings, why is this so?

This was discussed - Keeping your node up to date, changes to storage node software! PLEASE READ this thread!

@Toyoo you even commented further down the thread, but may have missed the original post.

I was mostly complaining that the problem of bad communication is still not solved. I won’t put more effort into complaints until Storj puts more effort into answering complaints.