F@H - WU 3059's - EUE Linux-SMP

[KE1HA]

I dont know about you all, but I've been getting a large number of 3059's that flat fail every time (2,3,4 times in a row). They reach about 95% to 98% and then dump.

I read abit about them on Stanfor'd Forums. Some people are having no trouble at all on with them on Lin-SMP other's can't get them to finish, i'm one of the latter.

I've lost about 2 days on two machines, i'm not very happy about this
.

 

[rich99million]

I've read that the SMP client will let a WU EUE 3 times before getting a new one, that's just stupid if you ask me - would be far better to give it out to a totally separate machine and if it fails in the same place then it's a duff WU

Also sometimes when people report multiple EUEs on the same WU it seems other people have also had the exact same WU fail multiple times on them too - how many times do you have to do a duff WU?


I'm more than slightly perplexed I must say


edit: if you do get the same WU fail twice in a row at the same point it's considered ok to delete the WU and get a new one - just be sure to post a report on the forums so the person running that project can look into it further and remove it if required
Infact what we're possibly seeing here is far too many EUEs going unreported due to people who are beta testing the WUs running it on too many machines and not keeping a close enough eye on them

 

[Cob]

I had them for pretty much 6 weeks solid. Starting to get a bit of a mix again now.

I can't say that they EUE any more often than the others. Are you sure your system is 100% stable?

 

[Snapshot]

edit: if you do get the same WU fail twice in a row at the same point it's considered ok to delete the WU and get a new one - just be sure to post a report on the forums so the person running that project can look into it further and remove it if required

<Hollow laughter>

How do we post a report when the logon bug still isn't fixed?

 

[shadowscotland]

I've just joined that eue at 90%+ club
and guess what its running the same unit again

This is a [email protected] running 24/7 only had a single eue due to a power cut. eue at night with no user input = duff WU with no points given

[00:46:28] Working on Unit 08 [August 22 00:46:28]
[00:46:29] Project: 2652 (Run 0, Clone 197, Gen 15)

Blar blar blar

[05:14:17] Completed 910000 out of 1000000 steps  (91 percent)
[05:18:50] Warning:  long 1-4 interactions
[05:18:52] Gromacs cannot continue further.
[05:18:52] Going to send back what have done.
[05:18:52] logfile size: 545638
[05:18:52] - Writing 546174 bytes of core data to disk...
[05:18:52]   ... Done.
[05:18:52] - Failed to delete work/wudata_08.xtc
[05:18:52] No C.P. to delete.
[05:18:52] - Failed to delete work/wudata_08.sas
[05:18:52] - Failed to delete work/wudata_08.goe
[05:18:52] Warning:  check for stray files
[05:20:52] 
[05:20:52] Folding@home Core Shutdown: EARLY_UNIT_END
[05:20:52] 
[05:20:52] Folding@home Core Shutdown: EARLY_UNIT_END
[05:20:56] CoreStatus = 7B (123)
[05:20:56] Client-core communications error: ERROR 0x7b
[05:20:56] Deleting current work unit & continuing...
[05:23:00] - Warning: Could not delete all work unit files (8): Core returned invalid code
[05:23:00] Trying to send all finished work units
[05:23:00] + No unsent completed units remaining.
[05:23:00] - Preparing to get new work unit...
[05:23:00] + Attempting to get work packet
[05:23:00] - Will indicate memory of 2046 MB
[05:23:00] - Connecting to assignment server
[05:23:00] - Successful: assigned to (171.64.65.64).
[05:23:00] + News From Folding@Home: Welcome to Folding@Home
[05:23:00] Loaded queue successfully.
[05:23:03] - Receiving payload (expected size: 1146087)
[05:23:14] - Downloaded at ~101 kB/s
[05:23:14] - Averaged speed for that direction ~85 kB/s
[05:23:14] + Received work.
[05:23:14] + Closed connections

[05:23:19] Working on Unit 09 [August 23 05:23:19]
[05:23:21] Project: 2652 (Run 0, Clone 197, Gen 15)

Should I sit here and let it run again...... let me think......

 

[rich99million]

<Hollow laughter>

How do we post a report when the logon bug still isn't fixed?

Well I'm happy to post stuff there on your behalf - post it here and I can just quote it there


WW has finally had a chance to look into the login bug so hopefully that will be sorted soon, it seems his real life has gone well and truly bad recently which would explain his absense - though he doesn't seem to want to give up on us at least

 

[KE1HA]

<Hollow laughter>

How do we post a report when the logon bug still isn't fixed?

I drank far to many pints in a vane attempt to figure that one out, an still the answer eludes me. In any case:

" Endevor to Perservere " ... I think a US president once said that, so I dont dare take credit for it, but the sentiment seems fitting wouldn't you agree