Posts by MarkJ
|
21)
(Message 5535)
Posted 27 Oct 2017 by MarkJ Post: The server is out of tasks at the moment. Which means there probably isn't anything wrong with your use of port 80. Almost all the projects have a Server Status page. When you can't get work check there. The Asteroids one is on the home page -> Server Status. Its a good idea to have at least one other project, maybe more if you want a constant supply of work. You can also increase the cache that BOINC uses so you have plenty of work units on hand. Depending on how often your computer is running you might set it to say 1 or 2 days. In the BOINC manager that's the Options -> Computing preferences -> General tab, "store at least xx days of work" and the "store up to an additional xx days of work". |
|
22)
(Message 5517)
Posted 15 Oct 2017 by MarkJ Post: On the vein of keeping things updated is there a chance we could get a neon-optimised app for the Pi2 and Pi3's? Updating to the latest fftw would also allow use of neon. You'd still need to supply a standard armhf version for the Pi Zero and older Pi's that have the ARMv6 so it might entail a plan class or simply dropping support for anything less than a Pi2. I don't run a@h on my Pi3's because the work units take so long now but if the run-time was reasonable... Happy to help with testing. |
|
23)
(Message 5516)
Posted 15 Oct 2017 by MarkJ Post: The cause of the freeze is Floating Point exception in Kernel mode. Until there is a patch to the Linux kernel, you cannot run asteroids and other projects on it. Since then (March 2016) there has been a patch added to the kernel that should fix it, along with many updates. If you update to the current version of Raspbian it should now work. |
|
24)
(Message 5515)
Posted 15 Oct 2017 by MarkJ Post: Tried running some tasks after upgrading nvidia-kernel-dkms to the 384.90 driver. All the CUDA55 tasks failed. Seti CUDA80 tasks work fine on it. Link to one of the failing tasks: result 173016915 Stderr from task <core_client_version>7.8.3</core_client_version> <![CDATA[ <message> process exited with code 2 (0x2, -254)</message> <stderr_txt> CUDA RC12!!!!!!!!!! CUDA Device number: 0 CUDA Device: GeForce GTX 1060 3GB Compute capability: 6.1 Multiprocessors: 9 Grid dim: 144 = 9*16 Block dim: 128 </stderr_txt> ]]> BOINC startup 15-10-2017 08:18 PM CUDA: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 384.90, CUDA version 9.0, compute capability 6.1, 3014MB, 2918MB available, 3936 GFLOPS peak) 15-10-2017 08:18 PM OpenCL: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 384.90, device version OpenCL 1.2 CUDA, 3014MB, 2918MB available, 3936 GFLOPS peak) |
|
25)
(Message 5446)
Posted 16 Jul 2017 by MarkJ Post: Did the server try the sse2 or sse3 app? My rigs seem to start off with the avx app (which is fastest) then the server sends the sse3 and sse2 apps. Its supposed to stick with the one that has the highest APR (average processing rate) once its tried each one but doesn't seem to. |
|
26)
(Message 4198)
Posted 21 Mar 2015 by MarkJ Post: Just now my work queue had 30 download failures of 30 tasks. Twice, I aborted all failures & then got 30 more download failures. 90 of 90 for 100% failures. Aborted all again have 1 running & 29 download failures. etc. etc. You don't need to abort them, just reporting them is sufficient seeing as they failed to download. Just hit the update button on the project tab or use one of the scripts given earlier in this thread. They need to fail 7 times before they are flagged as being in error and then the system will stop trying to send them out. |
|
27)
(Message 4185)
Posted 21 Mar 2015 by MarkJ Post: That's the same error the rest of us are getting. See the news thread "New WU". Basically most of the WU on the server are missing and when it tries to download they fail or are the wrong size. Dingo, I'd suggest you take your Pi2 over to Einstein. If you update to Jessie you'll be able use a later BOINC client that reports CPU features so you can get the Neon optimised app. The 7.0.27 that Wheezy has is too old. Jessie has 7.4.23 in the repo. |
|
28)
(Message 4184)
Posted 21 Mar 2015 by MarkJ Post: Like everyone else getting lots of download failures. I'm running the following script on my Windows machines. Its basically using BOINCCMD (the command-line tool that comes with BOINC) to hit the update button every 2 minutes. Cut and paste it into Notepad and save as a text file as something like aster.bat and then run it. echo Script to get/report Asteroids tasks :1 "C:\Program Files\BOINC\boinccmd" --project http://asteroidsathome.net/boinc update timeout 120 goto 1 |
|
29)
(Message 3950)
Posted 17 Jan 2015 by MarkJ Post: You might be able to abort a bunch of them and the server should try the other apps. You may need to let them start and maybe kill the asteroids task via task manager, so it thinks it's crashed rather than being aborted. I have avx capable rigs but have never received the avx app on them. |
|
30)
(Message 3929)
Posted 7 Jan 2015 by MarkJ Post: Part of the problem is Asteroids do floating point maths. Most GPU's except the super expensive ones are deliberately crippled by the manufacturers. Typically they cripple them to the order of 1/24th or 1/32nd of their single precision performance. It is much more noticeable on lower end cards because they have less processing units than a high end card. Most projects do single precision maths in the GPU apps. Milkyway do floating point, but insist on a card that can do it. I am sure if single precision or integer maths was good enough Asteroids would have used it in their apps. |
|
31)
Posted 9 Nov 2014 by MarkJ Post: According to the log you quoted the upload failed. Its the same issue we're discussing in the Server out of disk space message thread. |
|
32)
(Message 3761)
Posted 9 Nov 2014 by MarkJ Post: Well it's the weekend so move on to another project or give your machine(s) a rest.. I am sure the project team will look into in when they get in on Monday. In the mean time I'm doing some Einstein and Seti work. I will be back once the uploads have cleared. |
|
33)
(Message 3757)
Posted 8 Nov 2014 by MarkJ Post: Same upload issues here... 39 Asteroids@home 08-11-2014 08:31 PM Started upload of ps_141020_315498_1_0_0 And another machine with a slightly different worded message but still out of disk space 47 Asteroids@home 08-11-2014 09:08 PM [error] Error reported by file upload server: can't write file /home/boincadm/projects/boinc/upload/216/ps_141020_316962_7_1_0: No space left on server |
|
34)
(Message 3744)
Posted 2 Nov 2014 by MarkJ Post: That's great news. When you get a moment can you update the server status page please. It will let us know which BOINC bits are running on which machine and the specs. |
|
35)
(Message 3708)
Posted 21 Oct 2014 by MarkJ Post: Have you picked up a kernel update? From the dump it looks like you've got #709. We went through a bunch of issues when they updated the kernel a while back although this one has been stable for me for a while. ~ $ uname -a I'm running Jessie and its also got the current alpha-test BOINC client in the repo. I gave up running Asteroids on mine as they take too long. I did try the boinc-app-seti from the repo but that crashed the Pi too. |
|
36)
(Message 3579)
Posted 21 Aug 2014 by MarkJ Post: I have been already thinking about adding secondary server mounting folder for data via sshfs. db_purge is set to archive older records than 90 days. Problem is that there are too many results now. Would a Drobo be a better idea? It gives storage, handles the data redundancy and you can just attach to it like a network drive. You just put some drives in and connect it to power and a network port. It does the rest. Not too sure if it could handle the speed though. |
|
37)
(Message 2936)
Posted 30 Apr 2014 by MarkJ Post: I took all my Pi's over to E@H after the last size increase I did post about an updated FFT library for the Pi here that might yield a speed increase, however the project would need to revise their app to make use of it. Of course it all depends on if the app uses FFT's. |
|
38)
(Message 2799)
Posted 17 Mar 2014 by MarkJ Post: 7.2.42 will report every hour. No need to use the flag, unless you can't hold on for one hour :-) Preliminary Change Log 7.2.35 --> 7.2.36: |
|
39)
(Message 2675)
Posted 10 Mar 2014 by MarkJ Post: Its in the current alpha client builds (7.3.10, maybe one before). 10/03/2014 9:13:12 PM | | Starting BOINC client version 7.3.10 for windows_x86_64 .. 10/03/2014 9:13:12 PM | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepping 9] 10/03/2014 9:13:12 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt aes f16c rdrandsyscall nx lm avx vmx smx tm2 pbe fsgsbase smep |
|
40)
(Message 2610)
Posted 1 Mar 2014 by MarkJ Post: Kyong, The download errors have come back. I think you might need to check your work creation again. Examples One Two Three Error messages <message> WU download error: couldn't get input files: <file_xfer_error> <file_name>input_20299_34</file_name> <error_code>-224</error_code> <error_message>permanent HTTP error</error_message> </file_xfer_error> |
Previous 20 · Next 20