I'm getting that "Output file is absent" error message. Running Ubuntu Linux 8.04, and BOINC client/manager 5.10.45. SETI was running fine, but since attaching to Einstein, it hasn't run any files.
EDIT: Correction, SETI had run a file, but was showing only 22 seconds of computing, and .24% complete.
Both of the results from your P4 crashed before completing, but for different reasons. This and the problems with SETI together seem to suggest that there might be a hardware problem with that particular PC.
I'm getting that "Output file is absent" error message. Running Ubuntu Linux 8.04, and BOINC client/manager 5.10.45. SETI was running fine, but since attaching to Einstein, it hasn't run any files.
EDIT: Correction, SETI had run a file, but was showing only 22 seconds of computing, and .24% complete.
Both of the results from your P4 crashed before completing, but for different reasons. This and the problems with SETI together seem to suggest that there might be a hardware problem with that particular PC.
CU
Bikeman
SETI has actually worked fine since this posting. I think it's completed 4 tasks. I've added my notebook to Einstein, so if the P4 can't complete any tasks for E@H, then I'll probably detach and run the notebook only. If I have further problems I will let you know.
Since late August seeing about 75% failure due to compute error. This is on 3 machines 1 Vista, 1 XP, 1 Win 2000. Upgraded Vista machine to latest BOINC in last 18 hrs. Still had 2 failed results on this machine so far.
Are you using "CPU throttling", that is, have you configured BOINC to use only a certain percentage of idle cylces (see the: web preferences, setting: "Use at most XXX percent of CPU time"). BOINC seems to have difficulties with this setting, I would suggest to set this to "100%" and see if the problem goes away.
Interesting will give that a go. I have machines set to about 75% to cut heat. TNX
Clay
Quote:
Hi!
Are you using "CPU throttling", that is, have you configured BOINC to use only a certain percentage of idle cylces (see the: web preferences, setting: "Use at most XXX percent of CPU time"). BOINC seems to have difficulties with this setting, I would suggest to set this to "100%" and see if the problem goes away.
Hi,
I am running Einstein @ home on my Vista laptop, BOINC client 5.10.30, and have had my last few Einstein results fail because of client error. Checking the messsages, I found that the "Output file" is "absent".
Hi,
I have the same issue but I'm running BOINC 5.10.45 on XP SP3. Since I've installed SP3 I experience this problem of the missing output file on the Einstein project only, all other projects are running fine.
Would you recommend doing the same procedure as you've done so for the above Vista machine?
Hi,
I have the same issue but I'm running BOINC 5.10.45 on XP SP3. Since I've installed SP3 I experience this problem of the missing output file on the Einstein project only, all other projects are running fine.
Would you recommend doing the same procedure as you've done so for the above Vista machine?
Thanks a lot!
Yes, as much as I heard, SP3 gives the security features of vista, which cause the problem.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Looks like that was part of the fix. Ran throttles to 100% and made some other adjustments back toward default values and the computation errors ceased. Note also that Vista has too rapid a shutdown cycle. So I upped the write to disk to 1:45 sec. This permits better recovery should the system trip off line. So far so good. Temperatures on the large systems are tollarable at about 40 - 45C.
Clay
Quote:
For multicores, you could limit the numbers of CPU per host instead if you feel heat or responsiveness is an issue.
...
Note also that Vista has too rapid a shutdown cycle. So I upped the write to disk to 1:45 sec. This permits better recovery should the system trip off line...
You could also lengthen the shutdown cycle, see this FAQ.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: I'm getting that
)
Both of the results from your P4 crashed before completing, but for different reasons. This and the problems with SETI together seem to suggest that there might be a hardware problem with that particular PC.
CU
Bikeman
RE: RE: I'm getting that
)
SETI has actually worked fine since this posting. I think it's completed 4 tasks. I've added my notebook to Einstein, so if the P4 can't complete any tasks for E@H, then I'll probably detach and run the notebook only. If I have further problems I will let you know.
Since late August seeing
)
Since late August seeing about 75% failure due to compute error. This is on 3 machines 1 Vista, 1 XP, 1 Win 2000. Upgraded Vista machine to latest BOINC in last 18 hrs. Still had 2 failed results on this machine so far.
Ideas?
Clay
Team NAVY
Hi! Are you using "CPU
)
Hi!
Are you using "CPU throttling", that is, have you configured BOINC to use only a certain percentage of idle cylces (see the: web preferences, setting: "Use at most XXX percent of CPU time"). BOINC seems to have difficulties with this setting, I would suggest to set this to "100%" and see if the problem goes away.
CU
Bikeman
Interesting will give that a
)
Interesting will give that a go. I have machines set to about 75% to cut heat. TNX
Clay
For multicores, you could
)
For multicores, you could limit the numbers of CPU per host instead if you feel heat or responsiveness is an issue.
CU
Bikeman
RE: Hi, I am running
)
Hi,
I have the same issue but I'm running BOINC 5.10.45 on XP SP3. Since I've installed SP3 I experience this problem of the missing output file on the Einstein project only, all other projects are running fine.
Would you recommend doing the same procedure as you've done so for the above Vista machine?
Thanks a lot!
RE: Hi, I have the same
)
Yes, as much as I heard, SP3 gives the security features of vista, which cause the problem.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Bikeman, Looks like that
)
Bikeman,
Looks like that was part of the fix. Ran throttles to 100% and made some other adjustments back toward default values and the computation errors ceased. Note also that Vista has too rapid a shutdown cycle. So I upped the write to disk to 1:45 sec. This permits better recovery should the system trip off line. So far so good. Temperatures on the large systems are tollarable at about 40 - 45C.
Clay
RE: ... Note also that
)
You could also lengthen the shutdown cycle, see this FAQ.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
