client_state.xml Broken?


log in

Advanced search

Message boards : Number crunching : client_state.xml Broken?

Author Message
Cherokee150
Send message
Joined: 11 Nov 99
Posts: 103
Credit: 24,534,397
RAC: 26,805
United States
Message 1334205 - Posted: 3 Feb 2013, 8:55:10 UTC

One of my computers, Core2Duo, ID: 3324167, seems to have a problem. For some time now Ghost Detector v1.05 says that the "...Server indicates less Work Units 'In Progress' than client_state.xml thinks you have on board...Aborted". I believe the problem started when I had to reload my Vista OS. Despite my best efforts, BOINC insisted on aborting all the work units still in progress for all my projects.

For the second time I have set my Core2Duo to "No new tasks", let all the SETI units complete and report, then reset the project. After the first time the reset failed to resolve this, I identified several orphaned work units that were still sitting in the setiathome.berkeley.edu project folder. I deleted them manually. The problem persists. Is there something I can do to correct this?

Ghost Detector works find for my other computers, and it used to work fine for Core2Duo, so I do not think it is an error within Ghost Detector.

If it will help, I can provide a copy of my client_state.xml file.

Cherokee150
Send message
Joined: 11 Nov 99
Posts: 103
Credit: 24,534,397
RAC: 26,805
United States
Message 1334312 - Posted: 3 Feb 2013, 17:10:36 UTC

Let me ask a slightly different set of questions.

First, how can I determine for certain that my client_state.xml is showing -more- tasks on board than Berkeley believes are in progress?

Second, if there is truly a problem with my client_state.xml, then how would I be able to repair it?

Third, if all my units are processed, uploaded and reported, what impact, if any, might a repair or deletion of my client_state.xml file have on either my specific computer or my account in general?

Thank you for any insights you might be able to provide! :)

ClaggyProject donor
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 4097
Credit: 33,046,138
RAC: 7,966
United Kingdom
Message 1334316 - Posted: 3 Feb 2013, 17:53:15 UTC - in response to Message 1334312.

Let me ask a slightly different set of questions.

First, how can I determine for certain that my client_state.xml is showing -more- tasks on board than Berkeley believes are in progress?

Count them? How many tasks does Boinc Manager say you have?

Claggy

Cherokee150
Send message
Joined: 11 Nov 99
Posts: 103
Credit: 24,534,397
RAC: 26,805
United States
Message 1334589 - Posted: 4 Feb 2013, 14:33:06 UTC - in response to Message 1334316.

Hi Claggy,
Both BOINC Manager and SETI at Berkeley show no tasks in progress remaining for my Core2Duo computer. Is there a field in client_state.xml that might indicate that there are still tasks in progress remaining on my computer?

ClaggyProject donor
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 4097
Credit: 33,046,138
RAC: 7,966
United Kingdom
Message 1334628 - Posted: 4 Feb 2013, 17:22:04 UTC - in response to Message 1334589.

Hi Claggy,
Both BOINC Manager and SETI at Berkeley show no tasks in progress remaining for my Core2Duo computer. Is there a field in client_state.xml that might indicate that there are still tasks in progress remaining on my computer?


There are four sections in the client_state.xml for for each Wu, a <file_info> (or <file> in Boinc 7) for the downloaded file, a <file_info> (or <file> in Boinc 7) for the uploaded file,
a <work_unit> section giving working parameters, and a <result> section, if any of those are missing, Boinc will delete the others, and the Wu will get resent on the next request,
Once the Wu has started, it also has an <active _tasks> section which points to the slot in use, and i'm sure that gets deleted if the other four sections don't exist.

Check you're got no Orphaned Wu files left in your project directory, and all your slots are empty (I'm sure they will be),

Claggy

Message boards : Number crunching : client_state.xml Broken?

Copyright © 2014 University of California