Failed to open checkpoint-file for writing. Exiting.
8 Dec 2005 14:38:12 UTC
Topic 190325
(moderation:
My results have all shown this error, as in:
5.2.7
Access is denied. (0x5) - exit code 5 (0x5)
Resuming computation at 1732/63449/64979
Failed to open checkpoint-file for writing. Exiting.
I'm running Windows 2K, SETI, Rosetta, and E@Home, I just moved over from SETI classic. BOINC v5.2.7, E@H v479.
If there is other info someone would need to help me figure out what is causing this error, let me know.
Failed to open checkpoint-file for writing. Exiting.
)
Do you have full permissions to write to the BOINC directory, all files in there and in the subdirectories? Are you an administrator or in the least a power user? If you are using a user account, did you set all the correct permissions to the BOINC directory and its subdirectories?
I am running as
)
I am running as Administrator. From what I can tell I have full permissions to write to the directories and files. File permissions in Win2K running FAT32 on the disk are pretty simple, so I mean it's just a matter of read-only or not, right? I installed BOINC as the same user I'm running it under.
Anybody know exactly which file the checkpoint-file is? Maybe I'm missing it or it's in the wrong directory?
Quinn
The checkpointing file is in
)
The checkpointing file is in one of your BOINC\\slots\\ directories.
My guess is that it is called Fstats.Ha.ckp ... but don't ask me how I get to that conclusion. ;)
Well, the checkpoint-file is
)
Well, the checkpoint-file is there. And it's writable.
Next?
That does not necessarily
)
That does not necessarily mean that windows does not have a "lock" on the file.
USUALLY, this can only be cleared up with a reboot. I have never found or heard of a way to determine what app has a "lock" on files or direcories.
In some cases you can check this by trying to delete the file, not that I recommend that here.
Try a re-boot. All it costs is an hour or so to get through all the start up ... :)
Thing is, I shut down each
)
Thing is, I shut down each night. I know you dedicated BOINC'ers out there will have a hard time fathoming a CPU sitting there cold all night, but I'm not that concerned with my stats. Plus, I'm running Windows. It can use a nightly rest.
Now, I read over on the climateprediction site that shutting down windows without manually shutting down BOINC first has the potential to cause problems with writing correctly to files on shutdown.
Any chance or instances of this happening with locks BOINC or a project executable has on files?
Quin Most likely the effect
)
Quin
Most likely the effect of shutting down whoud be to cause you to redo some mininal amount of work (atleast that is my uderstanding about E@H). If you suspend before shutdown even that should not happen.
I have three windows system running 24/7 which I reboot every couple of weeks. The results they turn out appear to be uneffected by how often the machines are restarted.
So, anyone have a suggestion
)
So, anyone have a suggestion for what to look at next?
RE: So, anyone have a
)
The error message seems quite clear. Here is my line of reasoning:-
* It won't be a permissions thing because the .ckp file will have been written many times before failure
* It has to be something that is putting a lock on a critical file (by chance) at a most inopportune time
* What things do you have running that scan your folders?
I would be looking for anti-virus, anti-spyware, indexing services, disk cleanup, etc, etc. It just seems, when you look at the long length and variability of the times that something, by chance, just happens to stumble past at just the wrong moment and foul things up.
Also, you mentioned FAT32. When was the last time you ran a disk check?
Please realize that these are just random thoughts as I don't have enough knowledge to know for sure. However, maybe it might help.
Cheers,
Gary.