Says running, but no time elapses, no progress made.
Welcome to the Einstein@home project.
For paucity of information relevant to the problem - things like hardware details, OS, version of BOINC, summary of preference settings, etc - this problem description would have to be a strong candidate for the Guiness Book of Records :-).
Fortunately, you haven't hidden your computers so we can do a bit of searching by clicking on your name and then clicking on view computers to actually see some of the details. You can then click on 'tasks' for the relevant computer and see that you actually did make some progress on a task which then errored out. If you click on the task ID for that task you will be able to see the output that your computer returned to the project, including the error messages. If you scroll down and read through the output you will find
too many exit(0)s
and
21:42:48 (796): Can't acquire lockfile (32) - waiting 35s
21:43:23 (796): Can't acquire lockfile (32) - exiting
21:43:23 (796): Error: The process cannot access the file because it is being used by another process. (0x20)
which gives a bit of a clue as to the problem. Probably some other program, such as a malware or virus scanner, is locking the files as it scans them which means that BOINC's ability to interact with its own files is being interfered with. BOINC tends not to like this very much. The easiest solution is to exclude the BOINC tree from what is being scanned by the offending program. I have a great deal of confidence that it's safe to do this as I trust the project not to send any malware or viruses in the data that is sent to you. Of course you may choose to accept or reject this advice as you see fit.
There may be things other than virus/malware scanners that are locking BOINC's files so you may have to a bit of investigation to find what is doing the locking. Another thing to be aware of is that you can also see somewhat similar types of failure if you choose the BOINC preference to use less than 100% of the available CPU cycles. If your setting is not at 100% try putting it back to 100% and see if that allows tasks to run properly. From memory, the error messages are a bit different if this is the problem.
After updating my BOINC client from 6.6.29 to 6.6.36 I got a message from Einstein:
22-Aug-2009 17:40:35 [Einstein@Home] Message from server: No work sent
22-Aug-2009 17:40:35 [Einstein@Home] Message from server: (won't finish in time) BOINC runs 94.6% of time, computation enabled 100.0% of that
I am running 5 projects on my Linux box, all equally shared.
My TDCF in Einstein is 1.061932
Tullio
After updating my BOINC client from 6.6.29 to 6.6.36 I got a message from Einstein:
22-Aug-2009 17:40:35 [Einstein@Home] Message from server: No work sent
22-Aug-2009 17:40:35 [Einstein@Home] Message from server: (won't finish in time) BOINC runs 94.6% of time, computation enabled 100.0% of that
I am running 5 projects on my Linux box, all equally shared.
My TDCF in Einstein is 1.061932
Tullio
But that's a known bug in 6.6.36. Because of this, many people downgrade or upgrade to development versions. With 6.6.38 it seems to be better.
Gruß,
Gundolf
[edit]Sometimes, a temporary in cc_config.xml helps too.[/edit]
Computer sind nicht alles im Leben. (Kleiner Scherz)
I suspended all other projects and got immediately two Einstein tasks. Then I resumed all. But when another BOINC client shall be available? Cheers.
Tullio
Gary,
Thank you for your immediate response and for the humor. I have checked my security and all BOINC processes were checked and state allowed. Thinking you were onto the most plausible reason, I unloaded the entire security system (spam, virus, malware) to see what would happen and had no change. I raised the CPU usage to 100% and it did make a minute difference. Thinking about the sum of it, I can't find the reason for why most of the other projects run fine (excluding Cosmology@home, which does the same)Actually they all ran fine up until a short time ago. I really don't want to let the project go, any other suggestions?
Quote:
Quote:
Says running, but no time elapses, no progress made.
Welcome to the Einstein@home project.
For paucity of information relevant to the problem - things like hardware details, OS, version of BOINC, summary of preference settings, etc - this problem description would have to be a strong candidate for the Guiness Book of Records :-).
Fortunately, you haven't hidden your computers so we can do a bit of searching by clicking on your name and then clicking on view computers to actually see some of the details. You can then click on 'tasks' for the relevant computer and see that you actually did make some progress on a task which then errored out. If you click on the task ID for that task you will be able to see the output that your computer returned to the project, including the error messages. If you scroll down and read through the output you will find
too many exit(0)s
and
21:42:48 (796): Can't acquire lockfile (32) - waiting 35s
21:43:23 (796): Can't acquire lockfile (32) - exiting
21:43:23 (796): Error: The process cannot access the file because it is being used by another process. (0x20)
which gives a bit of a clue as to the problem. Probably some other program, such as a malware or virus scanner, is locking the files as it scans them which means that BOINC's ability to interact with its own files is being interfered with. BOINC tends not to like this very much. The easiest solution is to exclude the BOINC tree from what is being scanned by the offending program. I have a great deal of confidence that it's safe to do this as I trust the project not to send any malware or viruses in the data that is sent to you. Of course you may choose to accept or reject this advice as you see fit.
There may be things other than virus/malware scanners that are locking BOINC's files so you may have to a bit of investigation to find what is doing the locking. Another thing to be aware of is that you can also see somewhat similar types of failure if you choose the BOINC preference to use less than 100% of the available CPU cycles. If your setting is not at 100% try putting it back to 100% and see if that allows tasks to run properly. From memory, the error messages are a bit different if this is the problem.
All my projects download a new task after finishing the last one, except Einstein which sends me a message "won't finish in time". This happens after I went from BOINC 6.6.29 to 6.6.36. I then suspend all projects except Einstein and get a new task.
Tullio
All my projects download a new task after finishing the last one, except Einstein which sends me a message "won't finish in time". This happens after I went from BOINC 6.6.29 to 6.6.36. I then suspend all projects except Einstein and get a new task.
Tullio
But that's a known bug in 6.6.36. Because of this, many people downgrade or upgrade to development versions. With 6.6.38 it seems to be better.
Sometimes, a project reset or a temporary in cc_config.xml helps too.
Gruß,
Gundolf
[edit]I dare say so, because Ageless seems to be on vacation ;-)[/edit]
Computer sind nicht alles im Leben. (Kleiner Scherz)
Thanks, Gundolf. But I cannot understand while only Einstein does this while SETI and QMC send me their tasks after I have finished one, And QMC tasks take a longer time to finish, not to mention AQUA and CPDN which have longer deadlines.
Tullio
I have checked my security and all BOINC processes were checked and state allowed.
I think you misunderstand the problem. It's not a matter of whether or not BOINC is allowed to run but rather a matter of another program locking BOINC's files and thus preventing BOINC from updating them.
Quote:
Thinking you were onto the most plausible reason, I unloaded the entire security system (spam, virus, malware) to see what would happen and had no change.
If the problem has occurred after BOINC was restarted after the entire security system was shut off for a period, then it can't be the security system locking files. This makes it very likely to be the less than 100% CPU use preference.
Quote:
I raised the CPU usage to 100% and it did make a minute difference.
I'm intrigued by how something that either fails or doesn't fail can be termed a 'minute difference' :-). After setting the preference to 100%, make sure you 'update' the project (update button in BOINC Manager to ensure the local client is aware of the change. Then allow several tasks to crunch to be sure if there has been a solution or not.
Quote:
Thinking about the sum of it, I can't find the reason for why most of the other projects run fine (excluding Cosmology@home, which does the same)Actually they all ran fine up until a short time ago. I really don't want to let the project go, any other suggestions?
If you type the "Can't acquire lockfile" error message into the forum search box and make sure you set the filters for all forums and for at least the last year, you will find quite a few examples where putting the preference back to 100% has solved this very issue. I really can't offer any better advice than to give the 100% setting a thorough test.
Not Downloading
)
Welcome to the Einstein@home project.
For paucity of information relevant to the problem - things like hardware details, OS, version of BOINC, summary of preference settings, etc - this problem description would have to be a strong candidate for the Guiness Book of Records :-).
Fortunately, you haven't hidden your computers so we can do a bit of searching by clicking on your name and then clicking on view computers to actually see some of the details. You can then click on 'tasks' for the relevant computer and see that you actually did make some progress on a task which then errored out. If you click on the task ID for that task you will be able to see the output that your computer returned to the project, including the error messages. If you scroll down and read through the output you will find
and
which gives a bit of a clue as to the problem. Probably some other program, such as a malware or virus scanner, is locking the files as it scans them which means that BOINC's ability to interact with its own files is being interfered with. BOINC tends not to like this very much. The easiest solution is to exclude the BOINC tree from what is being scanned by the offending program. I have a great deal of confidence that it's safe to do this as I trust the project not to send any malware or viruses in the data that is sent to you. Of course you may choose to accept or reject this advice as you see fit.
There may be things other than virus/malware scanners that are locking BOINC's files so you may have to a bit of investigation to find what is doing the locking. Another thing to be aware of is that you can also see somewhat similar types of failure if you choose the BOINC preference to use less than 100% of the available CPU cycles. If your setting is not at 100% try putting it back to 100% and see if that allows tasks to run properly. From memory, the error messages are a bit different if this is the problem.
Let us know how you get on.
Cheers,
Gary.
After updating my BOINC
)
After updating my BOINC client from 6.6.29 to 6.6.36 I got a message from Einstein:
22-Aug-2009 17:40:35 [Einstein@Home] Message from server: No work sent
22-Aug-2009 17:40:35 [Einstein@Home] Message from server: (won't finish in time) BOINC runs 94.6% of time, computation enabled 100.0% of that
I am running 5 projects on my Linux box, all equally shared.
My TDCF in Einstein is 1.061932
Tullio
RE: After updating my BOINC
)
But that's a known bug in 6.6.36. Because of this, many people downgrade or upgrade to development versions. With 6.6.38 it seems to be better.
Gruß,
Gundolf
[edit]Sometimes, a temporary in cc_config.xml helps too.[/edit]
Computer sind nicht alles im Leben. (Kleiner Scherz)
I suspended all other
)
I suspended all other projects and got immediately two Einstein tasks. Then I resumed all. But when another BOINC client shall be available? Cheers.
Tullio
Gary, Thank you for your
)
Gary,
Thank you for your immediate response and for the humor. I have checked my security and all BOINC processes were checked and state allowed. Thinking you were onto the most plausible reason, I unloaded the entire security system (spam, virus, malware) to see what would happen and had no change. I raised the CPU usage to 100% and it did make a minute difference. Thinking about the sum of it, I can't find the reason for why most of the other projects run fine (excluding Cosmology@home, which does the same)Actually they all ran fine up until a short time ago. I really don't want to let the project go, any other suggestions?
All my projects download a
)
All my projects download a new task after finishing the last one, except Einstein which sends me a message "won't finish in time". This happens after I went from BOINC 6.6.29 to 6.6.36. I then suspend all projects except Einstein and get a new task.
Tullio
RE: All my projects
)
But that's a known bug in 6.6.36. Because of this, many people downgrade or upgrade to development versions. With 6.6.38 it seems to be better.
Sometimes, a project reset or a temporary in cc_config.xml helps too.
Gruß,
Gundolf
[edit]I dare say so, because Ageless seems to be on vacation ;-)[/edit]
Computer sind nicht alles im Leben. (Kleiner Scherz)
Thanks, Gundolf. But I cannot
)
Thanks, Gundolf. But I cannot understand while only Einstein does this while SETI and QMC send me their tasks after I have finished one, And QMC tasks take a longer time to finish, not to mention AQUA and CPDN which have longer deadlines.
Tullio
RE: I have checked my
)
I think you misunderstand the problem. It's not a matter of whether or not BOINC is allowed to run but rather a matter of another program locking BOINC's files and thus preventing BOINC from updating them.
If the problem has occurred after BOINC was restarted after the entire security system was shut off for a period, then it can't be the security system locking files. This makes it very likely to be the less than 100% CPU use preference.
I'm intrigued by how something that either fails or doesn't fail can be termed a 'minute difference' :-). After setting the preference to 100%, make sure you 'update' the project (update button in BOINC Manager to ensure the local client is aware of the change. Then allow several tasks to crunch to be sure if there has been a solution or not.
If you type the "Can't acquire lockfile" error message into the forum search box and make sure you set the filters for all forums and for at least the last year, you will find quite a few examples where putting the preference back to 100% has solved this very issue. I really can't offer any better advice than to give the 100% setting a thorough test.
Cheers,
Gary.