Forum > Discussion Forum

reschedule - stopped working and won't start working

<< < (2/2)

perryjay:
This is just a guess but some people have been having problems remoting in to the newer BMs because apparently there was an update to Vista/ windows7 that somehow changed the networks from private to public. Changing it back cured their problems. Maybe that could be affecting the rescheduler too though I don't know how.

loudbob:
Is this due to the 6.09 task being incompatible with reschedule?

Marius:
VoidPilot: Its kind of weird, the rescheduler starts by checking some files, like boinc.exe, boinccmd.exe and %data\client_state.xml and %data\projects\setiathome.berkeley.edu. so in all cases it could find those files/paths but it was not able to read the data. A forced reschedule gives more a few more hints as it was even inpossible to find out if you're running cuda!

It could be that the client_state.xml has become corrupted, i have seen this a couple of times that boinc does not properly write the closing xml tag (or makes other mistakes in the xml layout). Unfortunately i cannot detect those .xml errors reliable and once this happends it quickly gets out of control and in the end this can lead to total corruption of the client_state.xml (forcing you to restart and redownload units). This is also exactly the reason why the rescheduler leaves a copy of the client_state.xml in the data directory so i was able to compare the old and new .xml searching for errors..


@loudbob: Rescheduler was tested with 6.08 units and its not posible to have both 6.08 and 6.09 beta units at the same time (its on the wishlist though). If you are only running 6.09 it should be working AFAICT (but i have not tested that situation).

Navigation

[0] Message Index

[*] Previous page