Message boards :
Number crunching :
Error 194 EXIT_ABORTED_BY_CLIENT
Message board moderation
Author | Message |
---|---|
Bernie Vine Send message Joined: 26 May 99 Posts: 9954 Credit: 103,452,613 RAC: 328 |
In the last few days I have been getting batches of these errors on one machine 6851722 194 (0xc2) EXIT_ABORTED_BY_CLIENT http://setiathome.berkeley.edu/result.php?resultid=2966434528 They are mostly GPU but occasionally CPU http://setiathome.berkeley.edu/result.php?resultid=2959524209 Temperatures are optimal and I have cleaned the fans. This machine is also my daily machine, but if I am using a graphics intensive program or gaming I close Boinc. Any assistance with this would be appreciated. |
Tom* Send message Joined: 12 Aug 11 Posts: 127 Credit: 20,769,223 RAC: 9 |
The only place I can see where it would make any difference is when we kill a process because it hasn't been handling queued shared-memory messages for 180 seconds. 7.0.27 change log - client: enforce <no_gpus> in config file not just at startup, but also when config file is re-read. A first attempt to fix the bug where apps die with exit(1) (whereas they didn't do this w/ older clients). On Windows, the client uses TerminateProcess?(h, 1) to kill processes; the 1 is the exit code the process will appear to have. So instead, add a "will_restart" bool arg to the various kill functions, and if set use 0 (= STATUS_SUCCESS), otherwise use EXIT_ABORTED_BY_CLIENT. Note: in principle this shouldn't make any difference for quitting tasks, since handle_exited_app() checks for task state QUIT_PENDING and ignores the exit code in that case. The only place I can see where it would make any difference is when we kill a process because it hasn't been handling queued shared-memory messages for 180 seconds. |
Bernie Vine Send message Joined: 26 May 99 Posts: 9954 Credit: 103,452,613 RAC: 328 |
Well as I don't really understand the previous post and no one seems to have any answers, I am going to have to stop crunching on this machine as I hate causing errors. I brought the GTX560 especially to crunch!! I have checked the machine for viruses and malware with several different products, nothing found. I have cleaned the fans and air vents, that were to be honest not really very dirty. I have actually seen tasks error and the temps are fine. Oh well that's that then. |
Mike Send message Joined: 17 Feb 01 Posts: 34253 Credit: 79,922,639 RAC: 80 |
Bernie. Why not swap the 560 to another machine and see if the errors continue there ? Or run the cache dry and downgrade to Boinc 6 and see if this helps. Sorry i`m no Boinc expert. With each crime and every kindness we birth our future. |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
Bernie, you want Cuda 4.2 on that Fermi, but that's besides the point here. Checking one of the errored tasks http://setiathome.berkeley.edu/result.php?resultid=2970417390 , it's not on the app level - you can see that the app finished perfectly - and then boinc did something funny. As Tom noted David tried to do something about the problem - Boinc not realising properly that a task has completed - but only shuffeld it to a different kind of error ::) the only thing I can see that might help is to give x41zc slightly elevated priority - try setting mwith Mbcuda.cfg to normal or above_normal. You have excluded boinc folders from AV? A person who won't read has no advantage over one who can't read. (Mark Twain) |
Bernie Vine Send message Joined: 26 May 99 Posts: 9954 Credit: 103,452,613 RAC: 328 |
@ Mike, I don't think it is the 560 as CPU tasks have errored as well. @ William, I have put Cuda 4.2 back! I will try running with elevated priority. I have just realised that this only started after I upgraded to 7.0.64. If it continues to happen I might go back to 7.0.52 which I ran for a while with no problems. Boinc is excluded from AV scans. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.