These models appear to have multiple issues: missing download files, and missing files within the zip files that are present and do get downloaded.

See this thread in the phpBB forums.

I can second that. I have received 10 of them on the 22nd of Feb, all failed. Most of my wingmen have also errored out or haven't reported yet.

I can't seem to look at the task details on the website for any of them. I am clicking on the TaskId links. The website simply displays the CPDN logo at the top and the circle running around indicating its waiting on the website. Using IE9 under Win7.

Links to some wu:
One
Two
Three

Looks like the whole batch are stuffed. I wonder if they could check 1 or 2 in a batch before they send them out? Maybe they could generate one, see if that works and then generate the rest once its successful.

---

BOINC blog

I'm getting similar problems 3 WU's all have computation error's within 1 - 3 mins of starting.

---

"All man born has a right to life and no man born has the right to take that life"

The links are now opening. Looking at the first link, the tasks have two different errors. The machine running Darwin has a segmentation violation, the other two both have something pretty similar, this is the first one.

Signal 11 received, exiting...
Called boinc_finish
Regional Worker:: CPDN process is not running, exiting, bRetVal = 1, checkPID=1460, selfPID=1460, iMonCtr=2
Controller:: CPDN process is not running, exiting, bRetVal = 1, checkPID=1460, selfPID=2428, iMonCtr=1
Model crash detected, will try to restart...
Leaving CPDN_Main::Monitor...
Regional yearly means requires 12 input files got 0
Called boinc_finish

[/url]

I've had 6 PNWs fail this morning. Running on Windows 7 and Intel.

I've just had two PNW failures on Win7 and geophi's had several, probably on Linux. There's clearly something wrong with this batch. At least they don't spend much time crunching.

---

Cpdn news

I've also had one PNW fail this morning. Running on Windows 7 and Intel within 1 min of starting -- hadam3p_pnw_df38_2046_1_008313166

I've just had another PNW crash. I knew it would probably crash at about 25sec so I started the graphics to try to see what was happening. Just a completely black window - the model didn't appear to have started crunching.

---

Cpdn news

I had 3 that failed in one computer and 1 failed in another.
In all cases after a few hours after having started.

---

Occasionally, some ranges of models get released with the wrong values in some of the supporting files. This leads to the model(s) in question failing when it/they get to the incorrect part.

---

Backups: Here

I had all 25 fail on my machines. Are they going to rework these wu's and send them back out?

ccandido, I can't see your models because your computers are hidden.

Flashawk, your crashed PNW models all seem to be from the problematic batch created on 22 February. This is a nuisance, but they do crash very quickly after starting and don't use much processing time.

I expect this batch of models will indeed be reworked and reissued as this is usually done when a batch doesn't run successfully as expected.

---

Cpdn news

The usual way of 'reworking' a large batch of faulty WUs, is to inform the external suppliers of the data in question, and leave it up to them to sort it out. This can take time.
In this case, they're from the University of Oregon in the USA.

---

Backups: Here

Thanks guys, that's where my youngest son goes to school.

Currently I have 14 WU running
Some have reached more than 20% completion
But several ohters failed during download or in the first hours
Lets see how these 14 will do...