Message boards : Number crunching : Already have result ... ?
Message board moderation

To post messages, you must log in.

AuthorMessage
genes
Avatar

Send message
Joined: 29 Sep 04
Posts: 25
Credit: 77,910
RAC: 0
Message 6014 - Posted: 24 Feb 2005, 1:18:55 UTC
Last modified: 24 Feb 2005, 1:25:43 UTC

As an experiment, I left one of my machines to continue attempting to download work without detaching/reattaching, and it is now getting work, or at least has gotten work. It has 5 WU's that errored out like this:

2005-02-23 09:08:51 [LHC@home] Unrecoverable error for result v64lhc95-38s10_12530_1_sixvf_2258_3 (CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20))
2005-02-23 09:08:51 [LHC@home] CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
2005-02-23 09:08:52 [LHC@home] Deferring communication with project for 59 seconds

then, over and over, I get these messages:

2005-02-23 09:15:59 [LHC@home] Already have result v64lhc95-38s10_12530_1_sixvf_2258_3

On the work tab of the CC, the status is listed as "computation error". I only showed one of them, but there are five. They do not upload, but it looks like the CC is trying to download them again.

Using CC 4.19.
-----
Edit
-----
Host ID: 7543
WU's in question:
v64lhc95-38s10_12530_1_sixvf_2258_3
v64lhc94-30s10_12530_1_sixvf_2269_3
v64lhc94-30s10_12545_1_sixvf_2270_3
v64lhc94-30s10_12575_1_sixvf_2271_3
v64lhc95-38s12_14575_1_sixvf_2261_3

I could probably fix this by detaching/reattaching, but I'll give it a little more time. Reset, maybe?
ID: 6014 · Report as offensive     Reply Quote
genes
Avatar

Send message
Joined: 29 Sep 04
Posts: 25
Credit: 77,910
RAC: 0
Message 6081 - Posted: 25 Feb 2005, 3:59:04 UTC

Reset didn't fix it, only detaching/reattaching.
ID: 6081 · Report as offensive     Reply Quote
Profile Markku Degerholm

Send message
Joined: 3 Sep 04
Posts: 212
Credit: 4,545
RAC: 0
Message 6098 - Posted: 25 Feb 2005, 12:40:03 UTC

This seems to be quite common problem. But I'm pretty sure it's a BOINC CC problem, so there is not much we can do about it.

Markku Degerholm
LHC@home admin
ID: 6098 · Report as offensive     Reply Quote

Message boards : Number crunching : Already have result ... ?


©2024 CERN