| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Beta WU crashed at end of run |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 19
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So far, you are the only member to experience this problem. Well, maybe the only one to report the problem, which is a different thing. knreed has posted that a problem is affecting about 8% of the Linux runtime returned for this project. (I'm trying really hard not to say "I told you so".) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Please, go ahead :-D
We can only attempt diagnosis based on the available information, and when a problem is so widespread we usually have at least a couple of reports to correlate. So, good news for you, bad news for everyone else running HCC on Linux. Like I said, WCG prioritise based on the number affected. This cuts both ways, obviously. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There are a couple of aspects to that. Other than ones we've already covered, another is that I'd guess there are plenty of Linux users for whom WCG is totally unobtrusive, while Windows users tend to like fluffy graphical
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We can only attempt diagnosis based on the available information, and when a problem is so widespread we usually have at least a couple of reports to correlate. So, wouldn't it be a good idea if someone was actually asking for information? (And, no, I don't want to dump every single piece of information about my machines into a public thread, nor do I think 99.9% of people want to read it.) Shouldn't data have been obtained about which libs/kernels/etc were involved ... say, back in November? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've been running with my config disallowing HCC. However, I always allow beta tests and there's no way to limit which betas they are, of course.
So, I recently received another beta for this project (BETA_ X0000045461079200502081412_ 0--). It completed and then SEGV'd on exit just like the others. Oddly, the other WU for this group (_1) exited with error status in just over a minute and no replacement has yet been sent. Anyhow, expecting this result, I backed up the data at the previous checkpoint and prevented blocked the program from reporting to your servers. So, if you want the last checkpoint data, I have it. If you can provide me a working program, I can run the job to completion any time. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
At the top of this page you report BETA on Linux. AFAIK the BETA is Windows and a few Linux copies of the old test were send out in error for which knreed apologized.
----------------------------------------A new thread was opened for the (Windows) BETA test commencing Feb.19.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
A new thread was opened for the (Windows) BETA test commencing Feb.19. Oh, bummer. I ignored that thread because it's about Windows. I guess that explains why it's still broken. |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges: 
|
Kremmen,
We are working on the Linux fix and will be Beta testing that one soon. You can delete the checkpoint data, but one question I have is what version of glibc you are running on the machine that gets the error? Thanks, armstrdj |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We are working on the Linux fix and will be Beta testing that one soon. You can delete the checkpoint data, but one question I have is what version of glibc you are running on the machine that gets the error? libc6: 2.3.2.ds1-22sarge6 (I believe this is the last libc6 packaged with Debian Sarge) [Edit 1 times, last edit by Former Member at Feb 20, 2008 10:26:29 PM] |
||
|
|
|