"All tasks I checked showed "Exit status -226 (0xffffffffffffff1e) too many exit(0)s" after
14:03:42 (2112): Can't acquire lockfile (32) - exiting
14:03:42 (2112): Error: The process cannot access the file because it is being used by another process. (0x20)
just like others in this thread."
I'm not familiar with much of the terminology referred to in this thread. Are you saying I am closing Boinc too often? I'm running Intel quad core CPU, 6 GB ram, and using Vista 64 bit OS. Please clarify what you think is my problem. Thanks
No. Gundolf was not saying that. He was simply quoting what he had seen in some error messages that were returned with some of your failed tasks. If you don't know how to look at the messages that your failed tasks have returned to the server, take a look at this thread where the OP seems to be having a very similar problem to you. In the second message I have given that person fairly detailed instructions on how to look at the error output and how to interpret what is there. Hopefully you can adapt those instructions to your own list of tasks.
Your three most recent failures show the messages Gundolf was quoting and these are the same messages that were occurring in the other thread that I linked to. In that other case, (if you read right through the thread) it seems likely that the problem is being caused by Kaspersky anti-virus software. This is why Bikeman asked you if you were using Kaspersky. A similar sort of problem can also be caused if you change your computing preferences so that BOINC is throttled to use an amount of less than 100% of your CPU. So this is also why Bikeman asked you if you were using CPU throttling. Go to your account page on the website and click on your computing preferences and tell us what percentage of CPU time you have selected. If it is less than 100% this could be the cause of your problem.
"In that other case, (if you read right through the thread) it seems likely that the problem is being caused by Kaspersky anti-virus software. This is why Bikeman asked you if you were using Kaspersky."
No. Using Norton 360.
"A similar sort of problem can also be caused if you change your computing preferences so that BOINC is throttled to use an amount of less than 100% of your CPU. So this is also why Bikeman asked you if you were using CPU throttling. Go to your account page on the website and click on your computing preferences and tell us what percentage of CPU time you have selected."
On multiprocessors, use at most 4 processors
On multiprocessors, use at most 75 % of the processors
Use at most 50 percent of CPU time
In any case, you should except the BOINC data directory from AV scanning.
Quote:
On multiprocessors, use at most 4 processors
On multiprocessors, use at most 75 % of the processors
Use at most 50 percent of CPU time
The first option is for pre-version 6 BOINC only.
The second makes BOINC use only 3 of your 4 cores.
The last again cuts the amount by half, resulting in effectively 1.5 cores being used and possibly causing the problems with "too many exits."
You should set your preferences to use 100% of CPU time and perhaps 50% of the processors, if you don't want to use all three previously (half) used cores.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
I have noticed the tasks shown on Einstein for my computer that over the period 2 November to 22 November, there are 18 tasks listed. Seven were successful, one is in progress and 10 have computation errors. Of the last seven, one is in progress and the rest have computation error. I don't know what is wrong. Running a quad core with 6 GB Ram.
All tasks I checked showed "Exit status -226 (0xffffffffffffff1e) too many exit(0)s" after
14:03:42 (2112): Can't acquire lockfile (32) - exiting
14:03:42 (2112): Error: The process cannot access the file because it is being used by another process. (0x20)
just like others in this thread.
Gruß,
Gundolf
I've just had a "Can't acquire lockfile" error on another project (CPDN Beta), and managed to recover from it. The recovery process isn't relevant here, but the cause - I'm pretty certain - wasn't an antivirus program: I use a pretty light AV behind a hardware firewall, and I've excluded BOINC Data from scanning.
I suspect that the problem may have been caused by a disk error: it only affected one out of five running tasks (quad + cuda). In any event, I ran "chkdsk /F", reassembled purged files and client_state references back into the same slot directory, and re-tried the task: it seems to be running fine now.
RE: just like others in
)
So....do you use the throttling option "use only xxx % of CPU" or a Kaspersky virus scanner ?
Cheers
Bikeman
"All tasks I checked showed
)
"All tasks I checked showed "Exit status -226 (0xffffffffffffff1e) too many exit(0)s" after
just like others in this thread."
I'm not familiar with much of the terminology referred to in this thread. Are you saying I am closing Boinc too often? I'm running Intel quad core CPU, 6 GB ram, and using Vista 64 bit OS. Please clarify what you think is my problem. Thanks
RE: Are you saying I am
)
No. Gundolf was not saying that. He was simply quoting what he had seen in some error messages that were returned with some of your failed tasks. If you don't know how to look at the messages that your failed tasks have returned to the server, take a look at this thread where the OP seems to be having a very similar problem to you. In the second message I have given that person fairly detailed instructions on how to look at the error output and how to interpret what is there. Hopefully you can adapt those instructions to your own list of tasks.
Your three most recent failures show the messages Gundolf was quoting and these are the same messages that were occurring in the other thread that I linked to. In that other case, (if you read right through the thread) it seems likely that the problem is being caused by Kaspersky anti-virus software. This is why Bikeman asked you if you were using Kaspersky. A similar sort of problem can also be caused if you change your computing preferences so that BOINC is throttled to use an amount of less than 100% of your CPU. So this is also why Bikeman asked you if you were using CPU throttling. Go to your account page on the website and click on your computing preferences and tell us what percentage of CPU time you have selected. If it is less than 100% this could be the cause of your problem.
Cheers,
Gary.
"In that other case, (if you
)
"In that other case, (if you read right through the thread) it seems likely that the problem is being caused by Kaspersky anti-virus software. This is why Bikeman asked you if you were using Kaspersky."
No. Using Norton 360.
"A similar sort of problem can also be caused if you change your computing preferences so that BOINC is throttled to use an amount of less than 100% of your CPU. So this is also why Bikeman asked you if you were using CPU throttling. Go to your account page on the website and click on your computing preferences and tell us what percentage of CPU time you have selected."
On multiprocessors, use at most 4 processors
On multiprocessors, use at most 75 % of the processors
Use at most 50 percent of CPU time
RE: No. Using Norton
)
In any case, you should except the BOINC data directory from AV scanning.
The first option is for pre-version 6 BOINC only.
The second makes BOINC use only 3 of your 4 cores.
The last again cuts the amount by half, resulting in effectively 1.5 cores being used and possibly causing the problems with "too many exits."
You should set your preferences to use 100% of CPU time and perhaps 50% of the processors, if you don't want to use all three previously (half) used cores.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: RE: I have noticed
)
I've just had a "Can't acquire lockfile" error on another project (CPDN Beta), and managed to recover from it. The recovery process isn't relevant here, but the cause - I'm pretty certain - wasn't an antivirus program: I use a pretty light AV behind a hardware firewall, and I've excluded BOINC Data from scanning.
I suspect that the problem may have been caused by a disk error: it only affected one out of five running tasks (quad + cuda). In any event, I ran "chkdsk /F", reassembled purged files and client_state references back into the same slot directory, and re-tried the task: it seems to be running fine now.