1) Message boards : News : Migrating MilkyWay@home to a New Server (Message 76505) Posted 3 Nov 2023 by Cyanr & Cinny Post: Sorry about FAQ or bug report, I still cannot contact (re-attach milkyway until now, the time of this article posted) In my case, I am using another squid proxy (http proxy and https proxy) and I figured out that boinc did not use https proxy but only http proxy. Anyway, the local boinc client reported: 93: 03-Nov-2023 11:37:03 (low) [http://milkyway.cs.rpi.edu/milkyway/] project suspended by user 94: 03-Nov-2023 11:37:10 (low) [http://milkyway.cs.rpi.edu/milkyway/] update requested by user 95: 03-Nov-2023 11:37:18 (low) [] Project communication failed: attempting access to reference site 96: 03-Nov-2023 11:37:20 (low) [] Internet access OK - project servers may be temporarily down. my attachment command is here: boinccmd --project_attach http://milkyway.cs.rpi.edu/milkyway/ <key-is-here> My squid server access log is here: 2023-11-03T11:37:16.688+<TZ> 496 <IP> TCP_MISS/302 351 GET http://milkyway.cs.rpi.edu/milkyway/ <user> HIER_DIRECT/milkyway.cs.rpi.edu text/html 2023-11-03T11:37:17.924+<TZ> 1127 <IP> TCP_TUNNEL/200 6950 CONNECT milkyway.cs.rpi.edu:443 <user> HIER_DIRECT/milkyway.cs.rpi.edu - Are we waiting for some good things happened> Thanks for any advice

2) Message boards : News : Server Issues (Message 74560) Posted 25 Oct 2022 by Cyanr & Cinny Post: Now server feeder is down, which cannot accept any reporting 72: 25-Oct-2022 19:24:56 (low) [Milkyway@Home] Sending scheduler request: To report completed tasks. 73: 25-Oct-2022 19:24:56 (low) [Milkyway@Home] Reporting 1 completed tasks 74: 25-Oct-2022 19:24:56 (low) [Milkyway@Home] Not requesting tasks: "no new tasks" requested via Manager 75: 25-Oct-2022 19:25:00 (low) [Milkyway@Home] Scheduler request completed 76: 25-Oct-2022 19:25:00 (low) [Milkyway@Home] Server error: feeder not running 77: 25-Oct-2022 19:25:00 (low) [Milkyway@Home] Project requested delay of 400 seconds

3) Questions and Answers : Unix/Linux : cannot re-register the computer client (Message 74459) Posted 16 Oct 2022 by Cyanr & Cinny Post: I found it is the fault of milkyway@home now (not bothered by arm-based client of Pi to access/register as a new client) I tried to register another client on x86-64 based Windows 10, and it also failed 10/16/2022 1:54:03 PM | | Starting BOINC client version 7.20.2 for windows_x86_64 10/16/2022 1:54:03 PM | | log flags: file_xfer, sched_ops, task 10/16/2022 1:54:03 PM | | Libraries: libcurl/7.84.0-DEV Schannel zlib/1.2.12 10/16/2022 1:54:03 PM | | Data directory: C:\ProgramData\BOINC 10/16/2022 1:54:03 PM | | Running under account me 10/16/2022 1:54:03 PM | | CUDA: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 522.25, CUDA version 11.8, compute capability 6.1, 11264MB, 11264MB available, 11340 GFLOPS peak) 10/16/2022 1:54:03 PM | | CUDA: NVIDIA GPU 1: NVIDIA GeForce GTX 1080 Ti (driver version 522.25, CUDA version 11.8, compute capability 6.1, 11264MB, 11264MB available, 11340 GFLOPS peak) 10/16/2022 1:54:03 PM | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 522.25, device version OpenCL 3.0 CUDA, 11264MB, 11264MB available, 11340 GFLOPS peak) 10/16/2022 1:54:03 PM | | OpenCL: NVIDIA GPU 1: NVIDIA GeForce GTX 1080 Ti (driver version 522.25, device version OpenCL 3.0 CUDA, 11264MB, 11264MB available, 11340 GFLOPS peak) 10/16/2022 1:54:03 PM | | Windows processor group 0: 12 processors 10/16/2022 1:54:03 PM | | Host name: LeDecontracte 10/16/2022 1:54:03 PM | | Processor: 12 GenuineIntel Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz [Family 6 Model 79 Stepping 1] 10/16/2022 1:54:03 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 tm2 pbe fsgsbase bmi1 hle smep bmi2 10/16/2022 1:54:03 PM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.19044.00) 10/16/2022 1:54:03 PM | | Memory: 127.91 GB physical, 146.91 GB virtual 10/16/2022 1:54:03 PM | | Disk: 1.09 TB total, 688.99 GB free 10/16/2022 1:54:03 PM | | Local time is UTC +8 hours 10/16/2022 1:54:03 PM | | No WSL found. 10/16/2022 1:54:03 PM | | VirtualBox version: 6.1.34 10/16/2022 1:54:03 PM | | Config: report completed tasks immediately 10/16/2022 1:54:03 PM | | Config: use all coprocessors 10/16/2022 1:54:03 PM | | No general preferences found - using defaults 10/16/2022 1:54:03 PM | | Reading preferences override file 10/16/2022 1:54:03 PM | | Preferences: 10/16/2022 1:54:03 PM | | max memory usage when active: 65491.16 MB 10/16/2022 1:54:03 PM | | max memory usage when idle: 117884.10 MB 10/16/2022 1:54:03 PM | | max disk usage: 678.99 GB 10/16/2022 1:54:03 PM | | max CPUs used: 3 10/16/2022 1:54:03 PM | | (to change preferences, visit a project web site or select Preferences in the Manager) 10/16/2022 1:54:03 PM | | Setting up project and slot directories 10/16/2022 1:54:03 PM | | Checking active tasks 10/16/2022 1:54:03 PM | | Setting up GUI RPC socket 10/16/2022 1:54:03 PM | | Checking presence of 0 project files 10/16/2022 1:54:03 PM | | This computer is not attached to any projects 10/16/2022 1:55:39 PM | http://milkyway.cs.rpi.edu/milkyway/ | Fetching scheduler list 10/16/2022 1:55:43 PM | | Project communication failed: attempting access to reference site 10/16/2022 1:55:46 PM | | Internet access OK - project servers may be temporarily down. 10/16/2022 1:56:56 PM | | Project communication failed: attempting access to reference site 10/16/2022 1:56:57 PM | | Internet access OK - project servers may be temporarily down.

4) Questions and Answers : Unix/Linux : cannot re-register the computer client (Message 74452) Posted 15 Oct 2022 by Cyanr & Cinny Post: Hi I have a Raspberry Pi, which is used to collect my BOINC statistics of tasks. Recently I deleted its computer record in computer list of Milkyway@home. (it’s arm32v7 arch which never run any MW@h tasks) Now I use boinccmd —project_attach to re-register this tiny Pi, but it never succeeded. Does anyone know what’s going on here about the re project-attach for an once-existed, but deleted client? thanks for any clues

5) Message boards : Application Code Discussion : opencl_ati cannot identify mesa-opencl-icd on ubuntu for amdgpu (Message 70570) Posted 11 Feb 2021 by Cyanr & Cinny Post: Anyway, the vendor string of mesa-opencl-icd is not AMD, so the miklyway gpu app refused to choose that device and platform. instead, it goes to use nvidia opencl gpu. by the AMD opencl support 2.0 API, milkyway does not recognize it either too legacy code

©2024 Astroinformatics Group