This update fixes the memory and invalidation issues from 2 weeks ago.
please report bugs here.

A lot of wu and no one error.
It seems to be a good wu version....

I have some run times over 40 hrs with one work unit at 38% 2 at 7% and 2 at less than 1%. Should I let them continue to run? No matter what the response I receive they will continue to run until I get home tomorrow evening.

this task Task ID 1976261 Name T0591_AF_rs_stg0_lrlxMultiCst_t000__casp9__aln1_SAVE_ALL_OUT_14996_3920_0 has an elapsed time of 24hrs 7 mins and still 8 hrs run time to go.

32hrs for a task? Preferences are set for 4hr run time not 32hrs.
Will let it run, but there is something wrong with the task if it is fouling up Boinc Manager.

Remember that the elapsed time is wall clock time whereas the preference setting is for cpu time. Open the properties window for that particular task to see how much cpu time it has accumulated.

greg_be, that task completed 4 models in 18418.4 cpu seconds so it appears to have honored your preference of 21600 cpu seconds. If the discrepancy between cpu and elapsed time is dramatically different from from what you are used to seeing then it might be wise to open up task manager (or whatever it's called in Windows) and make sure some new or errant process isn't eating up a bunch of cpu cycles.

Best,
Snags

Task: 1978682
Workunit: t591__boinc_rosetta_cm_loopbuild_threading_cst_relax_wangyr_IGNORE_THE_REST_15010_10

stderr out:

ERROR: Option matching -relax:fastrelax_repeats not found in command line top-level context

AdeB

Same here on Windows 7:
1979016
1979017
1979018
1979019
1979020

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Funzione non corretta. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
[2010-11- 4 20:26:26:] :: BOINC:: Initializing ... ok.
[2010-11- 4 20:26:26:] :: BOINC :: boinc_init()
BOINC:: Setting up shared resources ... ok.
BOINC:: Setting up semaphores ... ok.
BOINC:: Updating status ... ok.
BOINC:: Registering timer callback... ok.
BOINC:: Worker initialized successfully.
Registering options..
Registered extra options.
Initializing broker options ...
Registered extra options.
Initializing core...
Initializing options.... ok
Options::initialize()
Options::adding_options()
Options::initialize() Check specs.
Options::initialize() End reached
ERROR: Option matching -relax:fastrelax_repeats not found in command line top-level context

New error
1980977

ERROR: Unable to open atomset file: workyfsongSVNminirosetta_databasechemical/atom_type_sets/fa_standard//atom_properties.txt
ERROR:: Exit from: ....srccorechemicalAtomTypeSet.cc line: 73
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

ERROR: Unable to open atomset file: workyfsongSVNminirosetta_databasechemical/atom_type_sets/fa_standard//atom_properties.txt
ERROR:: Exit from: ....srccorechemicalAtomTypeSet.cc line: 73
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

Also with windows 7 64-bit, after few seconds:
1982643
1982730

ERROR: Unable to open atomset file: workyfsongSVNminirosetta_databasechemical/atom_type_sets/fa_standard//atom_properties.txt
ERROR:: Exit from: ....srccorechemicalAtomTypeSet.cc line: 73
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

Also with windows 7 64-bit, after few seconds:
1982643
1982730

I also get the same error on over 2 pages (40) of work units, all on 2 Windows machines (XP 32 bit).
Linux not having the same problem.

---

I also get the same error on over 2 pages (40) of work units, all on 2 Windows machines (XP 32 bit). Linux not having the same problem.

So, it's a OS problem....

PCS_PGR122A_v1.frag_18-51_SAVE_ALL_OUT_15041_1_0
This one failed within a few seconds

ERROR: First parameter of SVD_Solver constructor MUST be larger than the second parameter
ERROR:: Exit from: ....srcnumericSVDSVD_Solver.cc line: 202

https://ralph.bakerlab.org/result.php?resultid=1979778
ERROR: Unable to open atomset file: workyfsongSVNminirosetta_databasechemical/atom_type_sets/fa_standard//atom_properties.txt
ERROR:: Exit from: ....srccorechemicalAtomTypeSet.cc line: 73
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

@Snags

Changed a preference setting in BOINC.
Was switching tasks every 60 mins changed that to every 4hrs to try and get tasks under control. Had 6-8 open in various stages at any one time under old setting.
This could account for the bizarre clock time.

@Snags

Changed a preference setting in BOINC.
Was switching tasks every 60 mins changed that to every 4hrs to try and get tasks under control. Had 6-8 open in various stages at any one time under old setting.
This could account for the bizarre clock time.

Hey, greg be - I would imagine that having fewer wus in a "waiting to run" status would lessen the reliance on a swap file and thus increase overall efficiency (assuming you've got "leave apps in memory" set to yes). Is that what you were going for? Have the times improved?

Best,
Snags

https://ralph.bakerlab.org/result.php?resultid=1989563

ERROR: no convergence in svdcmp

Only ran 44 seconds.

---

ERROR: Unable to open atomset file: workyfsongSVNminirosetta_databasechemical/atom_type_sets/fa_standard//atom_properties.txt
ERROR:: Exit from: ....srccorechemicalAtomTypeSet.cc line: 73
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

Same here:
1989656
1989657
1989661

ERROR: Option matching -relax:fastrelax_repeats not found in command line top-level context

Same here:
1989660

Really long run time. It is currently at 75 hours and 0.266%. The machine is a Windows 7 machine based on a Core i7. What information do you need to help debug this problem.

---

BOINC WIKI

What information do you need to help debug this problem.

I would think they would at least like to know the task name. Was the 75hrs CPU time? Or "elapsed" time? Is the task manager showing it getting CPU?

---