WARNING! attempt to gzip file .xxt319.out failed: file does not exist.

<stderr_txt>
ERROR:: Unable to obtain sequence information.
fasta file must be provided.
ERROR:: Exit at: .initialize.cc line:236

</stderr_txt>

<stderr_txt>
# random seed: 2996939
# cpu_run_time_pref: 3600
# cpu_run_time_pref: 3600
# cpu_run_time_pref: 3600
ERROR:: Exit at: .dock_structure.cc line:401

</stderr_txt>

...
<message>
- exit code -1073741819 (0xc0000005)
</message>
...

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0061E868 read attempt to address 0xF8F3E75E

So we're trying a new strategy for our workunit queue -- from now on, there will always be work in the queue to help us debug continuously! ... Does that sound OK to everyone?

This version has some boinc-related fixes in the watchdog and graphics.

Instant failure, no graphics displayed but two preempted WU from Rosetta in mem:
http://ralph.bakerlab.org/result.php?resultid=145667

Have two more of those WU, will watch them closely.

How can I turn debug-information on?

The next two WUs failed as well with the same error code after the same time (6sec):

http://ralph.bakerlab.org/result.php?resultid=145641
http://ralph.bakerlab.org/result.php?resultid=145639

While a progress of an unit reached 100% on my BOINC client, strangely it continues to work, and % of completed on the graphic keeps less than 100%, approximately 57%.
(here you can see a screen shot of it.) And I continue to work on the unit several minutes, but it remains at the same percentage.

I must be missing something. Others are processing work and finding bugs. All I have seen for a few days is "No work from project"

This time I had a work unit that ran for 59 min 35 seconds... then went dormant for 60 min 25 seconds. Total was 2 hrs instead of 1.

d287__CASP7_ABRELAX_521_7

has been running for 6 hours and shows only 1.044% progress. This is running on a Mac.

Let it run. It is a test Work Unit for CASP7. It is probably just a large Work Unit. Do not be surprised if it suddenly jumps to 100% at the end of the first model. Do not stop Boinc Or Rosetta or it will start over at 0%.

If it gets to the place where is has run longer that about 5 times the setting for "Time" in your preferences, it will either be stopped by the "Watchdog" or you might want to consider aborting it manually at that time.

Keep us posted.

...
Anyway, has a cause of errors been identified already?

In part yes, and with the help of the people running RALPH they will eliminate it.

...They worked fine without error at first. However, once BOINC client has been closed and restarted, the taskes which were being done more than half started from the beginning. Is it an error, or due to my preference of RALPH?

If the work units start, and then you stop BOINC before about 25-40 min of processing, or in any case before the percent complete is more than 1.4%, when you restart BOINC they will start from zero.