Please fix computer #57018 - only invalids!
log in

Advanced search

Message boards : Number crunching : Please fix computer #57018 - only invalids!

Author Message
Gunnar Hjern
Send message
Joined: 29 Mar 17
Posts: 13
Credit: 9,467,902
RAC: 11,789
Sweden
Message 1797 - Posted: 21 Apr 2020, 23:02:37 UTC

Whoever owns computer number 57018 http://gene.disi.unitn.it/test/show_host_detail.php?hostid=57018 please fix it or take it off the net!
So far it has only produced invalids (2), validation inconclusive (125), or errors (1), not one single valid result!
//Gunnar

L.Gilson
Volunteer developer
Send message
Joined: 25 Mar 20
Posts: 5
Credit: 143,281
RAC: 539
Germany
Message 1798 - Posted: 22 Apr 2020, 8:23:48 UTC - in response to Message 1797.

There are more of those:

http://gene.disi.unitn.it/test/results.php?hostid=34120

That's why boinc is verifying results by running each WU at least twice. And that's something the project admin should see in the backend. I'm not sure if it possible to act on those.

Profile [B@P] Daniel
Volunteer developer
Send message
Joined: 19 Oct 16
Posts: 90
Credit: 2,205,103
RAC: 0
Poland
Message 1799 - Posted: 22 Apr 2020, 9:19:38 UTC

You can limit number of WUs sent to hosts which returned high number of invalid WUs recently. Limit of 1 WU per host and scheduler request delay set to 12h should reduce this problem a lot.
____________

Profile valterc
Project administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 452
Credit: 22,311,765
RAC: 9,932
Italy
Message 1800 - Posted: 22 Apr 2020, 9:25:29 UTC - in response to Message 1799.

You can limit number of WUs sent to hosts which returned high number of invalid WUs recently. Limit of 1 WU per host and scheduler request delay set to 12h should reduce this problem a lot.

Do you remember the server config option for enabling this? Well, I will try to find out... (Is not that easy for me, working at home)

manalog
Send message
Joined: 5 Oct 15
Posts: 22
Credit: 328,451
RAC: 494
Italy
Message 1801 - Posted: 22 Apr 2020, 13:04:32 UTC

I have found another one of these bad hosts: #34120

Profile [B@P] Daniel
Volunteer developer
Send message
Joined: 19 Oct 16
Posts: 90
Credit: 2,205,103
RAC: 0
Poland
Message 1802 - Posted: 22 Apr 2020, 21:04:06 UTC - in response to Message 1800.

You can limit number of WUs sent to hosts which returned high number of invalid WUs recently. Limit of 1 WU per host and scheduler request delay set to 12h should reduce this problem a lot.

Do you remember the server config option for enabling this? Well, I will try to find out... (Is not that easy for me, working at home)

I never tried to setup my own server, so I do not know exactly how to do this. Out of curiosity I tried to search for this, and found that you can set <reliable_priority_on_over> and <reliable_priority_on_over_except_error> options in project settings, they may do the trick.
Reference: https://boinc.berkeley.edu/trac/wiki/ProjectOptions#Acceleratingretries

I also found that you can blacklist a host by setting its max_results_day field to -1. You can use this to ban hosts which return invalid results only.
Reference: https://boinc.berkeley.edu/trac/wiki/BlackList
____________

Profile valterc
Project administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 452
Credit: 22,311,765
RAC: 9,932
Italy
Message 1803 - Posted: 23 Apr 2020, 9:39:02 UTC - in response to Message 1802.

Thank you Daniel


Post to thread

Message boards : Number crunching : Please fix computer #57018 - only invalids!


Main page · Your account · Message boards


Copyright © 2020 CNR-TN & UniTN