Same here:

Message from server: Server error: can't attach shared memory

Tue 15 Dec 2009 05:24:30 PM EET|rosetta@home|Message from server: Server error: can't attach shared memory

Same here, all computer respond with:
Message from server: Server error: can't attach shared memory

OK --so anyone reporting can confirm the error. Haven't seen anything in the way of an acknowledging response from the project though.

Same here, all computer respond with:
Message from server: Server error: can't attach shared memory

---

OK --so anyone reporting can confirm the error. Haven't seen anything in the way of an acknowledging response from the project though.

Same here, all computer respond with:
Message from server: Server error: can't attach shared memory

It's 9:05am at their location now. Should get some action soon...

---

Hi! 9.07 here now :)

Not sure what the problem is - we're looking into it now. THis version
worked fine on RALPH, so it we suspect something went awry during the actual update.

---

http://beautifulproteins.blogspot.com/
http://www.miketyka.com/

OK --so anyone reporting can confirm the error. Haven't seen anything in the way of an acknowledging response from the project though.

Same here, all computer respond with:
Message from server: Server error: can't attach shared memory

It's 9:05am at their location now. Should get some action soon...

I was just going to say that. It's now been 15 hours w/out comm. They will let us know soon...

Hi! 9.07 here now :)

Not sure what the problem is - we're looking into it now. THis version
worked fine on RALPH, so it we suspect something went awry during the actual update.

I'm under the impression it's a server problem not an application problem. Correct me if I'm wrong...

---

So how do we remedy this situation? Is there something we can do on our end or do we just sit tight in the rowboat waiting to be rescued? If WUs were passengers, I've got a cruise ship full of passengers that need evacuation! Googling brings to light past similar occurrences where tinkering directly with the WUs solved the problem, but what I'm picking up here doesn't seem to indicate a physical server switch as much as a software issue.

I'm under the impression it's a server problem not an application problem. Correct me if I'm wrong...

Sounds correct to me. Every post in this thread has nothing to do with 2.03 yet.

My uploads have all gone through now. Now for the big fight over new WUs!

---

Ok, it appears we had to many old application backlogged. It was indeed a server problem - it should be resolved now :) - sorry for the hick up.

---

http://beautifulproteins.blogspot.com/
http://www.miketyka.com/

THis version fixes a stackoverflow error that we didn't catch in 2.02.

Please post issues here, thanks !

I'm seeing work units rolling in again. Thank you to the Rosetta team for a quick resolution.

Is the stack overflow issue the reason why mix_score13_env_rlbd_1hz6__IGNORE_THE_RESTlr8_DECOY_16523_77_09 made 129 decoys from 129 attempts?

---

Have a crunching good day!!

One machine, having run out of work, started a 2.03 WU ver yquickly and closed just as quickly after just 12 decoys. A validate error, but no error messages within the task details:

mix_score13_hb_rlbd_1shf__IGNORE_THE_RESTlr13_DECOY_16324_352_1

---

Is the stack overflow issue the reason why mix_score13_env_rlbd_1hz6__IGNORE_THE_RESTlr8_DECOY_16523_77_09 made 129 decoys from 129 attempts?

No, but 129 decoys is a good thing - isn't it ?

---

http://beautifulproteins.blogspot.com/
http://www.miketyka.com/

This broker_idealclose_kic_in20_hb_t308__IGNORE_THE_REST_16512_810 WU gave an error for both crunchers.

No, but 129 decoys is a good thing - isn't it ?

Absolutely. Reason I asked was because I thought there was a 100 decoy limit for tasks that had a high model count. I think it was limited because there were upload problems for tasks that had over 100 decoys.

---

Have a crunching good day!!

(Hint) It sure would be great if someone from project administration would comment in this forum about this issue, even if just to say "we're looking at the problem."

---

Best wishes:)

304932456 (lr8_combine_smooth_torsion_it00_rama02_A_rlbd_2hng_IGNORE_THE_REST_DECOY_14887_678_2) failed on Mac OS X 10.6

Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/yfsong_lr8_combine_smooth_torsion_it00_rama02_A.zip
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/lr8_2hng.out.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
std::cerr: Exception was thrown:
failure to read decoy F_00003_0004346_0 from silent-file lr8_2hng.out

</stderr_txt>
]]>

I get an issue on this workunit during CPU benchmarks:

mer. 16 déc. 2009 19:57:17 CET||Running CPU benchmarks
mer. 16 déc. 2009 19:57:17 CET||Suspending computation - running CPU benchmarks
mer. 16 déc. 2009 19:57:28 CET|rosetta@home|Task mix_score13_env_rlbd_2apb__IGNORE_THE_RESTlr10_DECOY_16523_731_0: no shared memory segment
mer. 16 déc. 2009 19:57:28 CET|rosetta@home|Task mix_score13_env_rlbd_2apb__IGNORE_THE_RESTlr10_DECOY_16523_731_0 exited with zero status but no 'finished' file
mer. 16 déc. 2009 19:57:28 CET|rosetta@home|If this happens repeatedly you may need to reset the project.
mer. 16 déc. 2009 19:57:49 CET||Benchmark results:
mer. 16 déc. 2009 19:57:49 CET|| Number of CPUs: 2
mer. 16 déc. 2009 19:57:49 CET|| 2217 floating point MIPS (Whetstone) per CPU
mer. 16 déc. 2009 19:57:49 CET|| 6149 integer MIPS (Dhrystone) per CPU
mer. 16 déc. 2009 19:57:50 CET||Resuming computation

But now the task is still running well on Rosetta mini 2.03, no other message.