LHC@home

I had a fortran - error with the following messages:

07.05.2005 14:08:34|LHC@home|Unrecoverable error for result v64D1D2MQonlyinjnoskew2b5off-55s12_14574.4231_1_sixvf_40900_2 (Die Sitzung wurde abgebrochen. (0xf0) - exit code 240 (0xf0))
07.05.2005 14:08:34|LHC@home|Deferring communication with project for 59 seconds
07.05.2005 14:08:34|LHC@home|Computation for result v64D1D2MQonlyinjnoskew2b5off-55s12_14574.4231_1_sixvf_40900 finished
07.05.2005 14:08:34|LHC@home|Starting result v64D1D2MQonlyinjnoskew1b5offcomp-58s10_12522.5_1_sixvf_38306_2 using sixtrack version 4.67
07.05.2005 14:08:35|LHC@home|Started upload of v64D1D2MQonlyinjnoskew2b5off-55s12_14574.4231_1_sixvf_40900_2_0
07.05.2005 14:08:40|LHC@home|Finished upload of v64D1D2MQonlyinjnoskew2b5off-55s12_14574.4231_1_sixvf_40900_2_0
07.05.2005 14:08:40|LHC@home|Throughput 10930 bytes/sec

I hope this was/(is) the only one(from about 800 success)....
The WU has processed the 'normal-time' 63 min., but on the end this fortran error occured and the WU aborted.
As we have prob. with the database, I was not able to link this WU...
I will make the hyperlink later.

[EDIT]Fortran error WU:WU 191699

greetz littleBouncer

---

I get the occasional fortran error when I use Eraser to clean my hard drives while crunching. For a short period, my drives are filled with randomized data, and the crunching client has a write error.

edit.
I find the translation of the error code (according to babelfish.altavista.com to read "The meeting was broken off."
I'm guessing this error code has two different meanings in the two languages.

translation would be more like: session was aborted

---

> I get the occasional fortran error when I use Eraser to clean my hard drives
> while crunching. For a short period, my drives are filled with randomized
> data, and the crunching client has a write error.
>
It hasn't to do with a clean up of the HD.

I think it has something to do with the database-outage and the 'triing' of the CC to contact the project (from yesterday: 05.07.05).

As others reported the same WU with success, it seems that the fault isn't to be found in 'wrong parameter settings', like on PAH, when there were WU's with fortran-errors.

greetz littleBouncer

> It hasn't to do with a clean up of the HD.

I agree.

> I think it has something to do with the database-outage and the 'triing' of
> the CC to contact the project (from yesterday: 05.07.05).

I disagree. In the last two weeks that WUs have been sent out I've experienced two of these errors. Both occurred when my pc was unused and was entirely idle, short what BOINC was doing. Both times was a LHC WU. LHC@Home servers were working properly at the time, the databse was not overloaded, nor was there any news on the front page nor posts in the message board about any server problems. I believe one WU was at 87% complete and the other around 30%- I'd venture to guess it's a mathematical problem with those types of failures, and in any case a "bad" WU such as those are still valuable to the LHC@Home team.

---

I'm getting fortran error, whenever diskspace is on low. Problem is, that BOINC doesn't recognize it, until restarted.

---

Yea, I've gotten 2 or 3 of them in the last couple weeks. Something about an open error... looks like it's trying to open a file for output. Wish I'd captured the error screen now. Well, if it happens again I will.

Skip

---

- da shu @ HeliOS,
"Free software” is a matter of liberty, not price. To understand the concept, you should think of “free” as in “free speech”, not as in “free beer".