List of SMP WUs with the "1 core usage" issue

[Hyperlife]

Got a repeat too... Project: 2671 (Run 37, Clone 79, Gen 78)

[58Enfield]

Three repeats:

Project: 2677 R27, C20, G31

Project: 2677 R35, C54, G25

Project: 2671 R37, C79, G78

[uncle fuzzy]

Project: 2669 (Run 15, Clone 175, Gen 185)
Project: 2677 (Run 6, Clone 87, Gen 37)

[susato]

By email from a donor who does not wish to post here. Probably many of these repeat WU already reported, but here they are for the record.

Project p2677 Run 34 Clone 82 Gen 31 Payload Size 1516329
Project p2669 Run 03 Clone 116 Gen 82 Payload Size 1530680
Project p2669 Run 01 Clone138 Gen 21 Payload Size 1142751
Project p2671 Run 52 Clone 43 Gen 82 Payload Size 1506854
Project p2671 Run 12 Clone 40 Gen 88 Payload Size 1507358
Project p2669 Run 13 Clone 29 Gen 179 Payload Size 1508833
Project p2677 Run 30 Clone 64 Gen 26 Payload Size 1497200
Project p2677 Run 03 Clone 75 Gen 38 Payload Size 1505629
Project p2677 Run 19 Clone 97 Gen 30 Payload Size 1503468
Project p2669 Run 03 Clone 185 Gen 118 Payload Size 1532635
Project p2671 Run 37 Clone 79 Gen 78 Payload Size 1513842
Project p2677 Run 06 Clone 98 Gen 41 Payload Size 1505194
Project p2677 Run 23 Clone 74 Gen 28 Payload Size 1503184
Project p2671 Run 51 Clone 50 Gen 88 Payload Size 1498239

The donor reports that upon download, most of these immediately EUE'd and stalled, often for many hours, under various Linux clients.

Until this problem is solved, can a line or two be added to the server code on the machines distributing these units, to check the download size against the project number and mark the unit bad if it has the wrong download size?

Any update on what might be causing this problem and what approaches are being taken to fix it? Thanks.

[Pick2]

Project: 2671 (Run 12, Clone 40, Gen 88)
Oh Noes , Not Again ! The Deja Vu WU

[GTron]

Project: 2677 (Run 15, Clone 49, Gen 39)
Was served August 29 23:10:15 by 171.67.108.25:8080 with compressed_data_size=1492918

Greg

[anandhanju]

Another report for Project: 2669 (Run 17, Clone 94, Gen 118) --> viewtopic.php?f=19&t=11270&p=110097

[bollix47]

Project: 2671 (Run 52, Clone 43, Gen 82) .... repeat

compressed_data_size=1506342

[bollix47]

Project: 2669 (Run 11, Clone 148, Gen 181)

compressed_data_size=1513076

[pvh]

Project: 2677 (Run 22, Clone 42, Gen 33)

data size: 1519553

[58Enfield]

A New One:

Project: 2677 R15 C34 G28

size 1493376

[bollix47]

Project: 2671 (Run 52, Clone 43, Gen 82) .... repeat of above on different computer

compressed_data_size=1506342

[HayesK]

last 4 days one core wu. seem to have gotten plentiful again past day or so.
p2671 (52/43/82)
p2669 (17-94-1180
p2677 (5-43-32)
p2671 (51-50-88)
p2671 (37-79-78)
p2669 (17-18-198)
p2677 (24-13-29)
p2671 (52-43-82)
p2677 (30-64-26)
p2671 (12-40-88)
p2671 (24-70-92)

[HendricksSA]

This one is making the rounds. I see it several times on this page above. Project: 2671 (Run 52, Clone 43, Gen 82) Receiving payload (expected size: 1506854)

[gannett]

Hi
My Ubuntu Jaunty rig just hooked up on Project: 2671 (Run 37, Clone 79, Gen 78) which was a unit listed early in this thread. 100% on one process and just a trickle in the other processes. The busy process skips around the cores so it's not completely hung.

Is it ok just to check these units on the floor ? IE Stop , Delete unit and rm Machinedependant.dat and restart ?

Cheers

Gannett