So is the verdict that tasks, that get the message this thread is about, will continue on to completion just fine?
That depends.
* If they occur once a day or less, ignore them. They are probably "lost heartbeat" message due to (automatic) clock adjusting.
* If you use cpu throttling on multi core machines, use 100% of CPU time, use only one processor/core or do both (if you get heat problems otherwise).
* Check stderr.txt. If it contains "Can't acquire lockfile - exiting", you have a problem. After 100 of those messages the task will be aborted. Try this
I got a bunch of the messages today but the tasks seem to be running still. My DSL connection may have been down because when I looked at BOINC it had the "need a network connection" window up.
I don't know if there is a connetion between network problems and exiting with zero status...
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Late last night I did notice that the clock on the computer that got the messages was not the same as the computer I was using to look at the other. The computer that got the messages is headless and I use Chicken of the VNC to monitor it on my wireless network. I'm not sure how often that happens, but I don't remember ever seeing that before. I reset the clock to the correct time.
I grep'd (searched) my stderrdae.txt and stdoutdae.txt files for "lockfile" and did not find it. All seems good now.
RE: So is the verdict that
)
That depends.
* If you use cpu throttling on multi core machines, use 100% of CPU time, use only one processor/core or do both (if you get heat problems otherwise).
* Check stderr.txt. If it contains "Can't acquire lockfile - exiting", you have a problem. After 100 of those messages the task will be aborted. Try this
FAQ for tipps to resolve the problem.
I don't know if there is a connetion between network problems and exiting with zero status...
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Late last night I did notice
)
Late last night I did notice that the clock on the computer that got the messages was not the same as the computer I was using to look at the other. The computer that got the messages is headless and I use Chicken of the VNC to monitor it on my wireless network. I'm not sure how often that happens, but I don't remember ever seeing that before. I reset the clock to the correct time.
I grep'd (searched) my stderrdae.txt and stdoutdae.txt files for "lockfile" and did not find it. All seems good now.