Back in April or so I stopped requesting work units from Einstein@home, but have recently wanted to resume my participation. Trouble is, I have not received a single work unit since turning work unit requests back on. Thinking my preferences were faulty, I went on this site and selected the most basic settings profile and then updated the prefs from the BOINC client. Still no sign of any work units.
Anyone have any suggestions on what I can try next? Thanks.
Anyone have any suggestions on what I can try next? Thanks.
Just to double check... have you set "Use CPU" to YES and enabled "Gamma-ray pulsar search #5" and "Gravitational Wave search O2 Multi-Directional" here: https://einsteinathome.org/account/prefs/project
Your computer doesn't show any 'coprosessor' so it won't be able to run any GPU tasks of course.
I would also try a 'Reset project' for Einstein on the Boinc Manager projects tab. Some time has passed since April and wiping the table won't do any harm.
Lastly, are you running any other projects on that host ? Maybe they have much higher priority set and scheduler may think it's not yet time for Einstein to get any activity.
Trouble is, I have not received a single work unit since turning work unit requests back on.
The simple reason is that your BOINC client is not asking for work. Richie has suggested that you check your preferences and that is exactly what you need to do.
You can diagnose this for yourself. Take a look at your computer on the website. The far right hand column contains a link to the most recent contact made with the Einstein scheduler. The date when I looked showed that the contact occurred over a week ago and has not been repeated more recently. If you click the link in the last contact column, you will see that your computer wasn't asking for work - the CPU request was for 0.00 secs of work, ie. none.
You just need to identify the preference setting that prevents your BOINC client from asking for work. Maybe you don't have any of the current CPU searches selected?
You just need to identify the preference setting that prevents your BOINC client from asking for work.
Also, if you updated preferences less than a week ago, the "last contact" indication my mean your machine is not yet aware of the change. I suggest you click on the the Update button in BoincMgr with the Einstein project selected. Reviewing the Event Log available in BoincMgr just after you run an update may be informative.
When I selected the generic settings profile, I just assumed it would check all the right boxes, and that a setting like "Use CPU" is pretty 'generic'. Fact is, when I checked just now after reading the two replies to my post, that option was NOT checked; the "Use GPU" box was. Anyway, I've now selected "Use CPU" and de-selected "Use GPU", saved the changes, and hit Update in my BOINC client. My task queue is currently full of other project's tasks, so for now I guess I just have to wait room to open up and new E&H tasks to arrive.
Thank you. Can't unhide, machine behind firewall sorry. last time contacted report as follows. It can see the NVIDIA GPU which does not support open CL (or the driver does not). other machines with intel GPU are running RPU jobs ok. no more recent driver available for the GPU which is 3 years old.
2021-01-11 22:37:00.0750 [PID=6524] Request: [USER#xxxxx] [HOST#12837642] [IP xxx.xxx.xxx.12] client 7.16.11
2021-01-11 22:37:00.1429 [PID=6524 ] [debug] have_master:1 have_working: 1 have_db: 1
2021-01-11 22:37:00.1429 [PID=6524 ] [debug] using working prefs
2021-01-11 22:37:00.1429 [PID=6524 ] [debug] have db 1; dbmod 1460986048.000000; global mod 1460986048.000000
2021-01-11 22:37:00.1430 [PID=6524 ] [send] effective_ncpus 6 max_jobs_on_host_cpu 999999 max_jobs_on_host 999999
2021-01-11 22:37:00.1430 [PID=6524 ] [send] effective_ngpus 1 max_jobs_on_host_gpu 999999
2021-01-11 22:37:00.1430 [PID=6524 ] [send] Not using matchmaker scheduling; Not using EDF sim
2021-01-11 22:37:00.1430 [PID=6524 ] [send] CPU: req 17338.95 sec, 0.00 instances; est delay 0.00
2021-01-11 22:37:00.1430 [PID=6524 ] [send] CUDA: req 129600.00 sec, 1.00 instances; est delay 0.00
2021-01-11 22:37:00.1430 [PID=6524 ] [send] work_req_seconds: 17338.95 secs
2021-01-11 22:37:00.1430 [PID=6524 ] [send] available disk 91.07 GB, work_buf_min 86400
2021-01-11 22:37:00.1430 [PID=6524 ] [send] active_frac 0.991332 on_frac 0.995222 DCF 1.574075
2021-01-11 22:37:00.1446 [PID=6524 ] [mixed] sending locality work first (0.6019)
2021-01-11 22:37:00.1584 [PID=6524 ] [send] send_old_work() no feasible result older than 336.0 hours
2021-01-11 22:37:01.0594 [PID=6524 ] [version] Checking plan class 'GWnew'
2021-01-11 22:37:01.0625 [PID=6524 ] [version] reading plan classes from file '/BOINC/projects/EinsteinAtHome/plan_class_spec.xml'
2021-01-11 22:37:01.0625 [PID=6524 ] [version] plan class ok
2021-01-11 22:37:01.0626 [PID=6524 ] [version] Best version of app einstein_O2MD1 is 2.08 ID 1255 GWnew (4.25 GFLOPS)
2021-01-11 22:37:01.0626 [PID=6524 ] [send] [HOST#12837642] [WU#514611657 h1_0182.40_O2C02Cl5In0__O2MD1S1a_Spotlight_182.60Hz_1045] using delay bound 1209600 (opt: 1209600 pess: 1209600)
2021-01-11 22:37:01.0633 [PID=6524 ] [debug] Sorted list of URLs follows [host timezone: UTC-21600]
2021-01-11 22:37:01.0633 [PID=6524 ] [debug] zone=-21600 url=http://einstein-dl4.cgca.uwm.edu
2021-01-11 22:37:01.0634 [PID=6524 ] [debug] zone=-18900 url=http://einstein-dl.syr.edu
2021-01-11 22:37:01.0634 [PID=6524 ] [debug] zone=+03600 url=http://einstein2.aei.uni-hannover.de
2021-01-11 22:37:01.0636 [PID=6524 ] [send] [HOST#12837642] Sending app_version 1255 einstein_O2MD1 9 208 GWnew; 4.25 GFLOPS
2021-01-11 22:37:01.0643 [PID=6524 ] [send] est. duration for WU 514611657: unscaled 33918.96 scaled 54116.39
2021-01-11 22:37:01.0643 [PID=6524 ] [HOST#12837642] Sending [RESULT#1057588074 h1_0182.40_O2C02Cl5In0__O2MD1S1a_Spotlight_182.60Hz_1045_1] (est. dur. 54116.39 seconds, delay 1209600, deadline 1611614221)
2021-01-11 22:37:01.9031 [PID=6524 ] [version] have CPU version but no more CPU work needed
2021-01-11 22:37:01.9031 [PID=6524 ] [version] Checking plan class 'GWnew'
2021-01-11 22:37:01.9031 [PID=6524 ] [version] plan class ok
2021-01-11 22:37:01.9032 [PID=6524 ] [version] Don't need CPU jobs, skipping version 208 for einstein_O2MD1 (GWnew)
2021-01-11 22:37:01.9032 [PID=6524 ] [version] no app version available: APP#53 (einstein_O2MD1) PLATFORM#9 (windows_x86_64) min_version 0
2021-01-11 22:37:01.9032 [PID=6524 ] [version] no app version available: APP#53 (einstein_O2MD1) PLATFORM#2 (windows_intelx86) min_version 0
2021-01-11 22:37:01.9035 [PID=6524 ] [mixed] sending non-locality work second
2021-01-11 22:37:01.9320 [PID=6524 ] [version] Checking plan class 'FGRPopencl-ati'
2021-01-11 22:37:01.9320 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_fgrp': 0.000000
2021-01-11 22:37:01.9320 [PID=6524 ] [version] No ATI devices found
2021-01-11 22:37:01.9320 [PID=6524 ] [version] Checking plan class 'FGRPopencl-intel_gpu'
2021-01-11 22:37:01.9320 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_fgrp': 0.000000
2021-01-11 22:37:01.9320 [PID=6524 ] [version] No Intel GPU devices found
2021-01-11 22:37:01.9320 [PID=6524 ] [version] Checking plan class 'FGRPopencl-nvidia'
2021-01-11 22:37:01.9321 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_fgrp': 0.000000
2021-01-11 22:37:01.9321 [PID=6524 ] [version] NVidia device (or driver) doesn't support OpenCL
2021-01-11 22:37:01.9321 [PID=6524 ] [version] Checking plan class 'FGRPopencl1K-ati'
2021-01-11 22:37:01.9321 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_fgrp': 0.000000
2021-01-11 22:37:01.9321 [PID=6524 ] [version] No ATI devices found
2021-01-11 22:37:01.9321 [PID=6524 ] [version] Checking plan class 'FGRPopencl1K-nvidia'
2021-01-11 22:37:01.9321 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_fgrp': 0.000000
2021-01-11 22:37:01.9321 [PID=6524 ] [version] NVidia device (or driver) doesn't support OpenCL
2021-01-11 22:37:01.9321 [PID=6524 ] [version] Checking plan class 'FGRPopenclTV-nvidia'
2021-01-11 22:37:01.9321 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_fgrp': 0.000000
2021-01-11 22:37:01.9321 [PID=6524 ] [version] NVidia device (or driver) doesn't support OpenCL
2021-01-11 22:37:01.9321 [PID=6524 ] [version] no app version available: APP#40 (hsgamma_FGRPB1G) PLATFORM#9 (windows_x86_64) min_version 0
2021-01-11 22:37:01.9321 [PID=6524 ] [version] no app version available: APP#40 (hsgamma_FGRPB1G) PLATFORM#2 (windows_intelx86) min_version 0
2021-01-11 22:37:01.9321 [PID=6524 ] [version] Checking plan class 'BRP4-opencl-intel_gpu-nd'
2021-01-11 22:37:01.9321 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_brp': 0.000000
2021-01-11 22:37:01.9321 [PID=6524 ] [version] No Intel GPU devices found
2021-01-11 22:37:01.9321 [PID=6524 ] [version] Checking plan class 'opencl-intel_gpu'
2021-01-11 22:37:01.9322 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_brp': 0.000000
2021-01-11 22:37:01.9322 [PID=6524 ] [version] No Intel GPU devices found
2021-01-11 22:37:01.9322 [PID=6524 ] [version] Checking plan class 'opencl-intel_gpu-Beta'
2021-01-11 22:37:01.9322 [PID=6524 ] [version] beta test app versions not allowed in project prefs.
2021-01-11 22:37:01.9322 [PID=6524 ] [version] Checking plan class 'opencl-intel_gpu-new'
2021-01-11 22:37:01.9322 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_brp': 0.000000
2021-01-11 22:37:01.9322 [PID=6524 ] [version] No Intel GPU devices found
2021-01-11 22:37:01.9322 [PID=6524 ] [version] Checking plan class 'opencl-intel_gpu'
2021-01-11 22:37:01.9322 [PID=6524 ] [version] parsed project prefs setting 'gpu_util_brp': 0.000000
2021-01-11 22:37:01.9322 [PID=6524 ] [version] No Intel GPU devices found
2021-01-11 22:37:01.9322 [PID=6524 ] [version] no app version available: APP#19 (einsteinbinary_BRP4) PLATFORM#9 (windows_x86_64) min_version 0
2021-01-11 22:37:01.9322 [PID=6524 ] [version] no app version available: APP#19 (einsteinbinary_BRP4) PLATFORM#2 (windows_intelx86) min_version 0
2021-01-11 22:37:01.9323 [PID=6524 ] [version] Checking plan class 'FGRPSSE'
2021-01-11 22:37:01.9324 [PID=6524 ] [version] plan class ok
2021-01-11 22:37:01.9324 [PID=6524 ] [version] Don't need CPU jobs, skipping version 108 for hsgamma_FGRP5 (FGRPSSE)
2021-01-11 22:37:01.9324 [PID=6524 ] [version] no app version available: APP#46 (hsgamma_FGRP5) PLATFORM#9 (windows_x86_64) min_version 0
2021-01-11 22:37:01.9324 [PID=6524 ] [version] no app version available: APP#46 (hsgamma_FGRP5) PLATFORM#2 (windows_intelx86) min_version 0
2021-01-11 22:37:01.9398 [PID=6524 ] Sending reply to [HOST#12837642]: 1 results, delay req 60.00
2021-01-11 22:37:01.9399 [PID=6524 ] Scheduler ran 1.868 seconds
Thank you. Can't unhide, machine behind firewall sorry. last time contacted report as follows. It can see the NVIDIA GPU which does not support open CL (or the driver does not). other machines with intel GPU are running RPU jobs ok. no more recent driver available for the GPU which is 3 years old.
Allowing your computers to be 'seen' is nothing to do with whether or not you are behind a firewall. All 'unhiding' does is give Einstein@Home permission to allow other volunteers to see non-sensitive details about your hosts - the model of the GPU you have and what tasks have been allocated, etc. This is data on the Einstein servers and not behind your firewall. I'm not sure what you mean by "RPU jobs" either.
Because you have published your host ID (in the line above from the snip you posted) I've been able to look (on the Einstein servers) at the GPU you have. It's listed as an "NVIDIA Quadro K620 (2048MB) driver: 397.93". I don't know anything about this particular model but I suspect it's perfectly capable of running the Gamma-ray pulsar OpenCl app if you install the proper OpenCL libraries for it direct from nvidia. Microsoft have a habit of not installing the stuff required to support OpenCL. There have been many examples in the past of people needing to do a clean install of the latest drivers plus libs from nvidia in order to get this working properly.
I don't use MS Windows and don't use nvidia GPUs so I'm not much help unfortunately.
Back in April or so I stopped
)
Back in April or so I stopped requesting work units from Einstein@home, but have recently wanted to resume my participation. Trouble is, I have not received a single work unit since turning work unit requests back on. Thinking my preferences were faulty, I went on this site and selected the most basic settings profile and then updated the prefs from the BOINC client. Still no sign of any work units.
Anyone have any suggestions on what I can try next? Thanks.
Koppany wrote:Anyone have any
)
Just to double check... have you set "Use CPU" to YES and enabled "Gamma-ray pulsar search #5" and "Gravitational Wave search O2 Multi-Directional" here: https://einsteinathome.org/account/prefs/project
Your computer doesn't show any 'coprosessor' so it won't be able to run any GPU tasks of course.
Also make sure the 'Preference set' that you save those settiings for is the same as the 'Location' that you see at https://einsteinathome.org/host/12392193 .
I would also try a 'Reset project' for Einstein on the Boinc Manager projects tab. Some time has passed since April and wiping the table won't do any harm.
Lastly, are you running any other projects on that host ? Maybe they have much higher priority set and scheduler may think it's not yet time for Einstein to get any activity.
Koppany wrote:Trouble is, I
)
The simple reason is that your BOINC client is not asking for work. Richie has suggested that you check your preferences and that is exactly what you need to do.
You can diagnose this for yourself. Take a look at your computer on the website. The far right hand column contains a link to the most recent contact made with the Einstein scheduler. The date when I looked showed that the contact occurred over a week ago and has not been repeated more recently. If you click the link in the last contact column, you will see that your computer wasn't asking for work - the CPU request was for 0.00 secs of work, ie. none.
You just need to identify the preference setting that prevents your BOINC client from asking for work. Maybe you don't have any of the current CPU searches selected?
Cheers,
Gary.
Gary Roberts wrote:You just
)
Also, if you updated preferences less than a week ago, the "last contact" indication my mean your machine is not yet aware of the change. I suggest you click on the the Update button in BoincMgr with the Einstein project selected. Reviewing the Event Log available in BoincMgr just after you run an update may be informative.
Thanks, Richie. When I
)
Thanks, Richie.
When I selected the generic settings profile, I just assumed it would check all the right boxes, and that a setting like "Use CPU" is pretty 'generic'. Fact is, when I checked just now after reading the two replies to my post, that option was NOT checked; the "Use GPU" box was. Anyway, I've now selected "Use CPU" and de-selected "Use GPU", saved the changes, and hit Update in my BOINC client. My task queue is currently full of other project's tasks, so for now I guess I just have to wait room to open up and new E&H tasks to arrive.
Thanks, Gary. It's sorted
)
Thanks, Gary.
It's sorted now. The link you provided to 'my computer' was much appreciated. Good to know it's there now.
Best,
Terry
Thanks, ARCHAE86. Problem
)
Thanks, ARCHAE86.
Problem solved.
Thank you. Can't unhide,
)
Thank you. Can't unhide, machine behind firewall sorry. last time contacted report as follows. It can see the NVIDIA GPU which does not support open CL (or the driver does not). other machines with intel GPU are running RPU jobs ok. no more recent driver available for the GPU which is 3 years old.
Ellis Neufeld wrote:Thank
)
Allowing your computers to be 'seen' is nothing to do with whether or not you are behind a firewall. All 'unhiding' does is give Einstein@Home permission to allow other volunteers to see non-sensitive details about your hosts - the model of the GPU you have and what tasks have been allocated, etc. This is data on the Einstein servers and not behind your firewall. I'm not sure what you mean by "RPU jobs" either.
Because you have published your host ID (in the line above from the snip you posted) I've been able to look (on the Einstein servers) at the GPU you have. It's listed as an "NVIDIA Quadro K620 (2048MB) driver: 397.93". I don't know anything about this particular model but I suspect it's perfectly capable of running the Gamma-ray pulsar OpenCl app if you install the proper OpenCL libraries for it direct from nvidia. Microsoft have a habit of not installing the stuff required to support OpenCL. There have been many examples in the past of people needing to do a clean install of the latest drivers plus libs from nvidia in order to get this working properly.
I don't use MS Windows and don't use nvidia GPUs so I'm not much help unfortunately.
Cheers,
Gary.