David What is up with all the BAD W/U I must have close to 500
4/8/2006 3:22:39 PM|rosetta@home|Unrecoverable error for result HBLR_1.0_1hz6_426_5085_0 ( - exit code -1073741819 (0xc0000005))
messages on all of my nodes running Rosetta.
You Asked for my/our help here Well you must realize that if you continue to give out W/U that stall our PC, or that can not complete the DC'ers here WILL lose faith in this project and the quality of the data we produce.

I am new here and using version 4.97. I too have almost all my WU's failing with similar codes. ***unrecoverable error for result HBLR_1.0_2reb_426_1061_0 (-exit code -1073741819 (0xc0000005))***

I'm really sorry about these problems. I checked yesterday on RALPH and everything seemed fine, but there clearly is a problem. Unfortunately, I'm just leaving for a family weekend trip so can't figure things out right away. Please bear with us for a couple of days.

Nothing wrong with your trip. But I wonder if you do realize the consequences if nobody else seems to react to serious problems

<core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# random seed: 1359430
# cpu_run_time_pref: 7200
No heartbeat from core client for 31 sec - exiting
# cpu_run_time_pref: 7200

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x007022EA read attempt to address 0x0EB4FC6C


Dump of the Worker(offending) thread:
1: 04/09/06 15:06:25


Dump of the Timer thread:
2: 04/09/06 15:06:25


Dump of the Graphics thread:
3: 04/09/06 15:06:25


Exiting...

</stderr_txt>

since last night ver .97 is causing TONS of errors on all my computers. this is why people avoid this project. i have had about enough of these bugs myself. about to cross the line and crunch for something else more stable.

Until we got the newer WU types, wasn't able to report on any problems with them obviously, and could only report on the older types... Sorry us testers weren't able to catch this problem before it started rolling out...

Click signature for global team stats

Until we got the newer WU types, wasn't able to report on any problems with them obviously, and could only report on the older types... Sorry us testers weren't able to catch this problem before it started rolling out...

I disagree of the quoted above

I started the thread at ralph@home announcing the new version 4.97 to test
on 7 April at 09:37 UTC

by 12:52 UTC 7 April, I have already reported this error on Windows 4.97

by 00:24 UTC 8 April, Son Goku posted that 4.97 was working fine

After that time ... 8 April, is that 4.97 go to rosetta@home ...


I wonder why 4.95 that was working very well ... fixed several problems.
is not what was placed into rosetta@home instead -:(
http://www.fadbeens.co.uk/phpBB2/viewtopic.php?t=53&start=165

Now, that was rolled back to 4.83, I know why I crunched all the day
w/o completing only one WU of 4.98 into two of my pcs

-> see my signature ... my rac is failing down on rosetta -:(

So, I will STOP crunching to rosetta again, until a new version that
checkpoint enough to allow swapping apps removing from ram, comes in.

4.95 was that version !!! 4.96 too

What is interesting here is that the RALPH testers are usually running BOINC version 5.2.32 and most Rosetta users are running BOINC 5.2.13. This may be part of the issue.

It seems like BOINC v5.3.31 is latest, to see the BETA versions one can use the URL

http://boinc.berkeley.edu/download.php?dev=1

whereas the "official" stable versions are at

http://boinc.berkeley.edu/download.php

Until we got the newer WU types, wasn't able to report on any problems with them obviously, and could only report on the older types... Sorry us testers weren't able to catch this problem before it started rolling out...

I disagree of the quoted above

I started the thread at ralph@home announcing the new version 4.97 to test
on 7 April at 09:37 UTC

by 12:52 UTC 7 April, I have already reported this error on Windows 4.97

by 00:24 UTC 8 April, Son Goku posted that 4.97 was working fine

After that time ... 8 April, is that 4.97 go to rosetta@home ...


I wonder why 4.95 that was working very well ... fixed several problems.
is not what was placed into rosetta@home instead -:(
http://www.fadbeens.co.uk/phpBB2/viewtopic.php?t=53&start=165

Now, that was rolled back to 4.83, I know why I crunched all the day
w/o completing only one WU of 4.98 into two of my pcs

-> see my signature ... my rac is failing down on rosetta -:(

So, I will STOP crunching to rosetta again, until a new version that
checkpoint enough to allow swapping apps removing from ram, comes in.

4.95 was that version !!! 4.96 too

In fact the information that I have is that Rosetta version 4.97 WAS in fact RALPH version 4.95. The version number was all that changed when it was implemented for Rosetta. What was not known at the time was how the newer WUs would react in the production environment. What is interesting here is that the RALPH testers are usually running BOINC version 5.2.32 and most Rosetta users are running BOINC 5.2.13. This may be part of the issue.

In any case you are wrong about what was implemented in Rosetta. While the version number for the Rosetta application is different, it is the same application that was working well in RALPH. RALPH version 4.97 is not what was deployed in Rosetta.

The workunit testing in RALPH did not show any problems with the newer workunits, however RALPH is a VERY limited subset of the types of systems and configurations running in Rosetta. Because of this fact it is not possible to test every possible issue before new work unit types are deployed.

As has been pointed out on may occasions, a number of your systems are below the minimum memory requirements for the project. The ones that are not, are reporting a significant portion of the memory as not available for Rosetta to use. This single fact has been and will continue to be the largest problem facing you in running Rosetta or Ralph. There are almost no problems reported for systems running with more memory unless a batch of bad work units comes along, and that will happen from time to time.

Click signature for global team stats

I guess I need to turn on the lights when I type. I meant to say BOINC 5.2.28. Rom had asked all the RALPH testers top upgrade to this version for improved error reporting. I think almost all of them performed the upgrade.

In any case it would be interesting to see if this had any impact on what has happened over the last day or so.

[b]"I'm trying to maintain a shred of dignity in this world." - Me[/b]

I guess you mean the 5.3.28 version? :-) Maybe some more light is needed? ;-)

That was the one Rom asked us to upgrade to. And it is pretty stable, runs fine on my computer.

I guess I need to turn on the lights when I type. I meant to say BOINC 5.2.28. Rom had asked all the RALPH testers top upgrade to this version for improved error reporting. I think almost all of them performed the upgrade.

In any case it would be interesting to see if this had any impact on what has happened over the last day or so.

I guess you mean the 5.3.28 version? :-) Maybe some more light is needed? ;-)

That was the one Rom asked us to upgrade to. And it is pretty stable, runs fine on my computer.

It seems like BOINC v5.3.31 is latest, to see the BETA versions one can use the URL

http://boinc.berkeley.edu/download.php?dev=1

whereas the "official" stable versions are at

http://boinc.berkeley.edu/download.php

I guess I need to turn on the lights when I type. I meant to say BOINC 5.2.28. Rom had asked all the RALPH testers top upgrade to this version for improved error reporting. I think almost all of them performed the upgrade.

In any case it would be interesting to see if this had any impact on what has happened over the last day or so.