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.
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:
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.
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.
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â,
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
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.
I can confirm, this issue yet resolved.
The disqualification for three versions behind is not enabled as far as I know.
So, if your node doesnât have failed audits in log, then two other possibilities will remain:
