Rosetta@Home WU failures

[biodoc]

Since the upgrade to version 4.97, I've had most of the WU's failing with client errors on my 4 windoze boxes. My linux box is OK. These are the errors (42 total) I'm seeing:

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00599FF4 read attempt to address 0x06C2FFF0
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00599FF4 read attempt to address 0x06C2FC8C
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x007022EA read attempt to address 0x06AAFF34
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00599FF4 read attempt to address 0x06CBFA98
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x007022EA read attempt to address 0x0EB4FF90

FYI, I had absolutely no problems with version 4.83.

Anyone else seeing this????

 

[networkman]

Not seeing this specific problem, but it is discouraging to see that I've already had 2 workunits report Computation Errors on this sole machine that I've added the Rosetta project to.. and we're only talking an hour or so thus far of CPU time. :Q

 

[Freewolf]

I'm starting to get them on some of my machines as well. Three out of 4 has failed.
Doc Baker is aware of the problem.

"
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."

 

[biodoc]

Originally posted by: networkman
Not seeing this specific problem, but it is discouraging to see that I've already had 2 workunits report Computation Errors on this sole machine that I've added the Rosetta project to.. and we're only talking an hour or so thus far of CPU time. :Q

I'm seeing more posts on the Rosetta boards & David Baker acknowledges there are problems w/ 4.97, but he's leaving on a 2 day family vacation! Hopefully this is resolved soon!:|

 

[Freewolf]

Everybody has a personal Life. I've seen projects where they would take 2 weeks just to say there may be a problem and a couple of years to get around to fixing it.

 

[Wolfsraider]

Originally posted by: Freewolf
Everybody has a personal Life. I've seen projects where they would take 2 weeks just to say there may be a problem and a couple of years to get around to fixing it.

I hear that, I know its hard when there are things that go wrong, but these guys are doing a great job keeping everyone informed and doing their best to get things fixed.

 

[biodoc]

Originally posted by: Wolfsraider

Originally posted by: Freewolf
Everybody has a personal Life. I've seen projects where they would take 2 weeks just to say there may be a problem and a couple of years to get around to fixing it.

I hear that, I know its hard when there are things that go wrong, but these guys are doing a great job keeping everyone informed and doing their best to get things fixed.

Yes, I must agree with both of you. I'm sure David Kim, Rom Walton & others in Baker's lab are working hard to sort out the problems. Hopefully Dr. Baker will relax & enjoy his 2 days with his family.

 

[Freewolf]

I hope so because it looks like most of my machines will start hitting those work units later today.

 

[biodoc]

Originally posted by: Freewolf
I hope so because it looks like most of my machines will start hitting those work units later today.

I hope you're ready for an 85% failure rate!

 

[networkman]

Originally posted by: biodoc

Originally posted by: Freewolf
I hope so because it looks like most of my machines will start hitting those work units later today.

I hope you're ready for an 85% failure rate!

Hey, that's about the same as the failure rate for the LS-120 drives isn't it? Hehe.. not quite that bad, but it sure seemed like it when they first came out. :roll:

 

[Freewolf]

Originally posted by: networkman

Originally posted by: biodoc

Originally posted by: Freewolf
I hope so because it looks like most of my machines will start hitting those work units later today.

I hope you're ready for an 85% failure rate!

Hey, that's about the same as the failure rate for the LS-120 drives isn't it? Hehe.. not quite that bad, but it sure seemed like it when they first came out. :roll:

You mean you actually brought one of those things ?

 

[Slatzman]

one of my boxes is 1 for 2 right now on the 4.97. The other two boxes haven't gotten into them yet. They should be on them within a few hours though.

Looks like it will be a bad stats weekend :frown:

Slatz

 

[Freewolf]

If it gets too bad I might move some of mine over to malaria for the weekend.

 

[GimpyOne]

:Q

Originally posted by: Freewolf

Originally posted by: networkman

Originally posted by: biodoc

Originally posted by: Freewolf
I hope so because it looks like most of my machines will start hitting those work units later today.

I hope you're ready for an 85% failure rate!

Hey, that's about the same as the failure rate for the LS-120 drives isn't it? Hehe.. not quite that bad, but it sure seemed like it when they first came out. :roll:

You mean you actually brought one of those things ?

I still have and use 2! :Q

 

[networkman]

Actually, I have 3 machines with LS120 drives. I also have 3 spare drives just in case.

Edit: Just checked my Xeon box again.. of the 9 Rosetta@Home(v4.97) workunits that have started processing, 6 of them have ended in "Computation Errors" - that really sucks. :| And the only reason the other 3 haven't errored out yet, is that the processing time was Preempted in favor of another of the projects running on the box. :roll:

 

[Freewolf]

Only one of my machines has made it to these work units. So far 6 out of 8 have failed on that machine.

 

[biodoc]

Hi TeAmmates!

You can reduce the error rate to about 20% if change to 1hr WUs!

Better than 80%.

 

[Freewolf]

It appears they are going back to the working version.


"I have just recieved this essage from David Kim who is working on the version 4.97 error issue as I write this message.

I just reverted back to the previous app. You should notice a version
4.98 now, which is really version 4.83 for windows and mac, and 4.82
for linux.

You should all see some relief very soon. Your systems should update by them selves when the version change takes place, but if not please do a manual update."

 

[Slatzman]

Man, you beat me by two minutes in posting this...I was just thinking of moving the boxes over to malaria..I guess I will leave them be and flush out the bad WU's

Slatz

 

[biodoc]

Originally posted by: Freewolf
It appears they are going back to the working version.


"I have just recieved this essage from David Kim who is working on the version 4.97 error issue as I write this message.

I just reverted back to the previous app. You should notice a version
4.98 now, which is really version 4.83 for windows and mac, and 4.82
for linux.

You should all see some relief very soon. Your systems should update by them selves when the version change takes place, but if not please do a manual update."

Great News Freewolf!!

 

[Insidious]

I just hit the 'project reset' button on each of my machines and it cleared out all the 4.97 WUs and is now full of only 4.98

Ya gotta hand it to them.... they are doing a pretty good job of trying not to leave us floundering when this stuff happens.



but it sure would be nice if it didn't happen at all

everytime we finally start getting some new blood..... for whatever it's worth, what doesn't kill us makes us stronger

-Sid

 

[BadThad]

NoooOOOOooOOOOoooo

LOL

 

[networkman]

Okay, I'll switch a couple machines over to Rosetta then.

 

[Insidious]

Originally posted by: networkman
Okay, I'll switch a couple machines over to Rosetta then.

More the merrier

(glad to hear it NWM!)

-Sid