Posts by Woodles

1) Message boards : Number crunching : WUs since 22.jul.19 11.UTC not reported (Message 8157) Posted 1 Aug 2019 by Woodles Post: Same here, plus the tasks crunched while the stats were down.
2) Questions and Answers : Web site : "No such computer" ... although it runs, reports results and gets credit. (Message 8155) Posted 31 Jul 2019 by Woodles Post: Hi Michael, Mine are now showing up now as well along with the work done since the 22nd. Hosts normally show up straight away, I think the issues were all due to the same "nothing working since the 22nd" bug that seems to be fixed now. Mark
3) Questions and Answers : Web site : "No such computer" ... although it runs, reports results and gets credit. (Message 8147) Posted 26 Jul 2019 by Woodles Post: I have two hosts that recently changed from Windows to Linux https://moowrap.net/show_host_detail.php?hostid=1277713 https://moowrap.net/show_host_detail.php?hostid=1277756 They both download tasks, run them, report them and get credit for the work but I'm unable to configure them or check on their progress. They're listed under "Computers on this account" but clicking on them (or entering the URL directly) returns a blank page with "Unable to handle request, No such computer" I assume this is related to the new tasks not showing up and the lack of stats exports recently? Some database broken?
4) Message boards : News : BOINC Scheduler changes for multiple app version case (Message 7991) Posted 10 May 2018 by Woodles Post: Right, you seem to have internal Intel GPU as well and Dnet OpenCL app detects that and tries to use but fails to. There's two problems here, first that the Intel GPU fails to run the app and second that it gets detected by the Dnet app so the GPU numbering is out of sync with BOINC Client. BOINC Schduler should have given up after 10 failures on the OpenCL app but doesn't seem to be doing that. I'll try to figure out if this can be fixed (you should only be getting the cuda31 app until problems with Intel GPUs can be fixed). -w I've never used the Intel GPU for crunching so it's probably got none of the correct drivers. The task does indeed give up after ten goes of trying to use the Intel GPU ... and then moves onto the next task and repeats. I tried to download work again last night and got "191 Distributed.net Client v1.04 (opencl_nvidia_101) windows_intelx86" tasks. Some Cuda ones would be nice as the external GPU has no issues with them.
5) Message boards : News : BOINC Scheduler changes for multiple app version case (Message 7987) Posted 4 May 2018 by Woodles Post: It's happened before but it's not my issue, I don't run any anti virus on my crunching machines. I have several hosts running Moo and the only ones having problems are the ones with GTX 1080 GPUs in and only with Opencl tasks, everything else runs without problems. Probably a driver problem but I'm not going to mess around with things at the moment. No matter, I'll move them to a different project.
6) Message boards : News : BOINC Scheduler changes for multiple app version case (Message 7983) Posted 2 May 2018 by Woodles Post: I've let it run again and tasks now state: 17:45:15 (7524): wrapper v1.4 build 18 for nVidia OpenCL starting (BOINC Wrapper v7.5.26011) 17:45:15 (7524): device: OpenCL: NVIDIA GPU 0 (not used): GeForce GTX 1080 (driver version 378.49, device version OpenCL 1.2 CUDA, 8192MB, 3042MB available, 9395 GFLOPS peak) 17:45:15 (7524): device: OpenCL: NVIDIA GPU 1: GeForce GTX 1080 (driver version 378.49, device version OpenCL 1.2 CUDA, 8192MB, 3042MB available, 9395 GFLOPS peak) 17:45:15 (7524): checkpoint interval: 0h15m00s00 (task 1075200 GFLOPS, 0h01m54s44 per packet) 17:45:15 (7524): wrapper: running dnetc520-win32-x86-opencl.exe (-ini dnetc.ini -runoffline -multiok=1) - attempt 1/10 dnetc v2.9112-521-CTR-16020314 for Win64 (WindowsNT 6.1). Using email address (distributed.net ID) 'xxxxxxxx@xxxxxxxx' [May 02 16:45:22 UTC] Automatic processor detection found 8 processors. [May 02 16:45:22 UTC] Loading crunchers with work... [May 02 16:45:22 UTC] Automatic processor type detection found an Intel Core iX-6xxx (Skylake) processor. [May 02 16:45:22 UTC] OGR-NG: using core #2 (cj-asm-sse2). [May 02 16:45:22 UTC] RC5-72: using core #4 (YK AVX2). So apparently these "Distributed.net Client v1.04 (opencl_nvidia_101) windows_intelx86" tasks are running on the CPU?!
7) Message boards : News : BOINC Scheduler changes for multiple app version case (Message 7982) Posted 2 May 2018 by Woodles Post: I have a host with two GTX1080s in http://moowrap.net/show_host_detail.php?hostid=798990 and up until a few hours ago they were both crunching the same "Distributed.net Client v1.03 (cuda31) windows_intelx86" tasks quite happily. Now I'm only getting "Distributed.net Client v1.04 (opencl_nvidia_101) windows_intelx86" tasks which all fail after about 20 seconds with "computation error" The project attempts to run one task per GPU but GPU-Z shows no load and no power used. It may have something to do with the message "[May 02 03:32:57 UTC] Automatic processor type detection did not recognize the processor (tag: "Intel(R) HD Graphics 530 ")" in the stderr file. No changes at my end, another hosts with the same GPUs is also getting the opencl tasks and running them although they are claiming to need over six hours (and increasing) to finish! I don't use an app_config.