I'm running SETI Main at 45%, Beta at 35%, and Einstein at 20%. Up until this evening; I had all projects set to "Accept work from other projects" as Yes, when I got the message in Event Log stating "Work Not Needed", I changed this for SETI Main to No, but still no new work has been downloaded.

I'm now completely out of work for SETI Main and Beta. HELP!!! :-(

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

What does the event log say?

6/25/2014 8:31:28 PM | SETI@home Beta Test | update requested by user
6/25/2014 8:31:31 PM | SETI@home Beta Test | Sending scheduler request: Requested by user.
6/25/2014 8:31:31 PM | SETI@home Beta Test | Not requesting tasks: don't need
6/25/2014 8:31:32 PM | SETI@home Beta Test | Scheduler request completed

6/25/2014 8:35:35 PM | Einstein@Home | update requested by user
6/25/2014 8:35:37 PM | Einstein@Home | Sending scheduler request: Requested by user.
6/25/2014 8:35:37 PM | Einstein@Home | Not requesting tasks: don't need
6/25/2014 8:35:39 PM | Einstein@Home | Scheduler request completed

6/25/2014 8:46:04 PM | SETI@home Beta Test | update requested by user
6/25/2014 8:46:05 PM | SETI@home Beta Test | Sending scheduler request: Requested by user.
6/25/2014 8:46:05 PM | SETI@home Beta Test | Not requesting tasks: don't need
6/25/2014 8:46:07 PM | SETI@home Beta Test | Scheduler request completed
6/25/2014 8:46:07 PM | SETI@home Beta Test | General prefs: from SETI@home Beta Test (last modified 25-Jun-2014 20:44:57)
6/25/2014 8:46:07 PM | SETI@home Beta Test | Computer location: home
6/25/2014 8:46:07 PM | SETI@home Beta Test | General prefs: no separate prefs for home; using your defaults
6/25/2014 8:46:07 PM | | Reading preferences override file
6/25/2014 8:46:07 PM | | Preferences:
6/25/2014 8:46:07 PM | | max memory usage when active: 1412.65MB
6/25/2014 8:46:07 PM | | max memory usage when idle: 2018.08MB
6/25/2014 8:46:07 PM | | max disk usage: 0.50GB
6/25/2014 8:46:07 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)

6/25/2014 8:46:10 PM | SETI@home | update requested by user
6/25/2014 8:46:12 PM | SETI@home | Sending scheduler request: Requested by user.
6/25/2014 8:46:12 PM | SETI@home | Not requesting tasks: don't need
6/25/2014 8:46:13 PM | SETI@home | Scheduler request completed
6/25/2014 8:46:15 PM | SETI@home | Started download of background_1403754197
6/25/2014 8:46:15 PM | SETI@home | Started download of user_logo_1403754197
6/25/2014 8:46:17 PM | SETI@home | Finished download of background_1403754197
6/25/2014 8:46:17 PM | SETI@home | Finished download of user_logo_1403754197

6/25/2014 8:46:17 PM | Einstein@Home | update requested by user
6/25/2014 8:46:18 PM | Einstein@Home | Sending scheduler request: Requested by user.
6/25/2014 8:46:18 PM | Einstein@Home | Not requesting tasks: don't need
6/25/2014 8:46:20 PM | Einstein@Home | Scheduler request completed

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

At a guess, what work you have for E@H is sufficient to satisfy whatever time period you have for your work cache settings, so BOINC doesn't ask for any more work from any of the projects.

---

Soli Deo Gloria

6/25/2014 8:46:07 PM | | max memory usage when active: 1412.65MB
6/25/2014 8:46:07 PM | | max memory usage when idle: 2018.08MB
6/25/2014 8:46:07 PM | | max disk usage: 0.50GB

What Wedge said PLUS - half a GB of disk space hardly gets Einstein started.

You probably ought to increase that to at least 50GB.

100GB would be safer.

I had all projects set to "Accept work from other projects" as Yes

I'm wondering, where do you think you set this?

---

Since you are running a recent client, find the new 'diagnostics' option and enable 'work_fetch_debug' then post the result from the event log.

My guess is that you have enough work from Einstein and the current RECs are such that Einstein needs more work before SETI gets some again. Over time it levels out.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

6/25/2014 8:46:07 PM | | max memory usage when active: 1412.65MB
6/25/2014 8:46:07 PM | | max memory usage when idle: 2018.08MB
6/25/2014 8:46:07 PM | | max disk usage: 0.50GB

What Wedge said PLUS - half a GB of disk space hardly gets Einstein started.

You probably ought to increase that to at least 50GB.

100GB would be safer.

My Hard Drive is only a 250 GB drive; 238 seen by the system, 209 GB Free at last check. So, I did make changes to that number on all projects to 30 GB; so as NOT to take up the entire drive. Still, no joy... NOT getting anymore work... Perhaps the Einstein work in queue is preventing me from getting SETI and SETI Beta work; as has been suggested.

EDIT

Also, the smaller number was set when I had Constellation running, and it had only a 40 GB HD... :-(

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Since you are running a recent client, find the new 'diagnostics' option and enable 'work_fetch_debug' then post the result from the event log.

My guess is that you have enough work from Einstein and the current RECs are such that Einstein needs more work before SETI gets some again. Over time it levels out.

I'm in "Advanced View"; but, I don't see anywhere "Diagnostics"... :-(

[EDIT]

Nothing about "Diagnostics" in "Simple View" either. :-(

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Since you are running a recent client, find the new 'diagnostics' option and enable 'work_fetch_debug' then post the result from the event log.

My guess is that you have enough work from Einstein and the current RECs are such that Einstein needs more work before SETI gets some again. Over time it levels out.

I'm in "Advanced View"; but, I don't see anywhere "Diagnostics"... :-(

[EDIT]

Nothing about "Diagnostics" in "Simple View" either. :-(

Sorry, William was a little ahead of himself.

In order to set diagnostic logging from the Manager screen, you need to be running an alpha test version of BOINC - either v7.3.19 (available from the download all page) or v7.4.2 (perhaps best avoided - still some remedial work on language selection in progress).

When you get a suitable version, 'Diagnostic flags' is an additional item at the foot of the Advanced menu, in Advanced view - keyboard shortcut Ctrl-Shift-F.

yeah, me bad.

right, the hard way then.
do you already have a cc_config.xml?
else get the client to dump one - open options, go to exclusive apps tab, add something there, apply, remove it again apply - that will give you a complete cc_config.xml in the data directory.
edit (notepad) and change the 0 in work_fetch_debug to 1 - read config from advanced view, post results.

you may want to disable afterwards again, it can bloat the log.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

yeah, me bad.

right, the hard way then.
do you already have a cc_config.xml?
else get the client to dump one - open options, go to exclusive apps tab, add something there, apply, remove it again apply - that will give you a complete cc_config.xml in the data directory.
edit (notepad) and change the 0 in work_fetch_debug to 1 - read config from advanced view, post results.

you may want to disable afterwards again, it can bloat the log.

6/26/2014 9:10:15 AM | | Re-reading cc_config.xml
6/26/2014 9:10:15 AM | | cc_config.xml not found - using defaults
6/26/2014 9:10:15 AM | | log flags: file_xfer, sched_ops, task

No cc_config.xml... :-(

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I changed "Max Additional Work Buffer" to 7 Days from 3 Days. Updated all projects; and SETI downloaded a BUNCH of work!!! :-) Beta downloaded nothing; probably it will now wait for both SETI and Einstein to get lower before downloading... Einstein also did not download anything new, yet...

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I changed "Max Additional Work Buffer" to 7 Days from 3 Days. Updated all projects; and SETI downloaded a BUNCH of work!!! :-) Beta downloaded nothing; probably it will now wait for both SETI and Einstein to get lower before downloading... Einstein also did not download anything new, yet...

Well, just so you know - nothing works the way you think it does with work-fetch.

I can't call it an error, because I don't understand it, but Einstein "tends" to be "greedy." BTW - Einstein isn't greedy. BOINC is responsible, not Einstein. It just "looks" like Einstein is greedy.

The way I've had this explained to me in the past was: "Leave it alone and eventually BOINC will figure-it-out and you will get about the mix of work that you have set over the long term."

That's a satisfying answer, but not an acceptable proposition (for me). The whole scheme was set-up to work with "Set And Forget" screensaver / background / I'm-not-all-that-involved users who don't want to goof-around with their settings once set.

You know...sane people... people with a life...

So, while I'm sure it is true that if I set a 10:1 preference for SETI work and just kept the computer housed and fed, eventually it would all work-out; I'm not likely to keep my fingers off of it long enough to see that happen.

It's people like us that cause unrest in the ivy-covered-hallowed-halls and ivory towered castles in the sky. Those poor folks have to figure-out how to make sure that all the stuff we do that they never intended to be done doesn't bring the whole thing crashing-down on the heads of less "fiddly" users.

But don't be surprised if you had a 50/50 mix SETI/Einstein and you set ten days as your work cache (I don't recommend that) if Einstein initially downloads almost ten days' work and then shifts into "high priority" leaving whatever SETI you may have-had sitting there for a long while.

I've never had the patience to let it average-out over time.

Anyway, as you've discovered you can run out of disk, run out of cache, run out of time-to-completion, etc, etc, and work fetch will stop. (if everything's working as it should) No need to panic. Eventually the TARDIS will find its way home.

I changed "Max Additional Work Buffer" to 7 Days from 3 Days. Updated all projects; and SETI downloaded a BUNCH of work!!! :-) Beta downloaded nothing; probably it will now wait for both SETI and Einstein to get lower before downloading... Einstein also did not download anything new, yet...

Remember that BOINC only "needs" '... enough tasks to keep busy for at least' (the first buffer setting).

Additional work is just that - a bonus. BOINC will chew through those extra four days that you've given it, plus the original three, before it feels hungry enough to ask for more.

Next new issue... I'd like to install Lunatics; but, their site has "forgotten" my login... I attempted to sign in last year, and it wouldn't recognize me... Granted it has been years since I logged in; however, I clearly remember my Login ID and Password, yet it didn't work.

How do I now, obtain, and install Lunatics for my GPU, and then set SETI to crunch two WU's at a time?

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

If you can't get into Lunatics, you can try Mike's World


http://mikesworldnet.de/home

Click on Download and then go to lunatics v0.41 installer, just make sure it's the right version for your computer. For 2 work units at a time on the GPU, you will need to either create an app_config.xml or modify the app_info.xml. I didn't know how to do either until someone walked me thru it. Questions, just ask


Here's what mine looks like, but I only Run 1 ap at a time with 1 cpu for it on my GPU. I run 2 Multibeams at a time on the GPU. You might want to lower the value for the CPU to 0.04 I like to have the 0.5 just for my personal preference. For your GPU you can change the 1 to 0.5 in both the GPU and CPU areas for the Astropulse

<app_config>
<app>
<name>astropulse_v6</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app_config>




Zalster

If you can't get into Lunatics, you can try Mike's World


http://mikesworldnet.de/home

Click on Download and then go to lunatics v0.41 installer, just make sure it's the right version for your computer. For 2 work units at a time on the GPU, you will need to either create an app_config.xml or modify the app_info.xml. I didn't know how to do either until someone walked me thru it. Questions, just ask


Here's what mine looks like, but I only Run 1 ap at a time with 1 cpu for it on my GPU. I run 2 Multibeams at a time on the GPU. You might want to lower the value for the CPU to 0.04 I like to have the 0.5 just for my personal preference. For your GPU you can change the 1 to 0.5 in both the GPU and CPU areas for the Astropulse

<app_config>
<app>
<name>astropulse_v6</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app_config>




Zalster

Zalster,

I've installed Lunatics 0.41 Win64 from Mike's site. I've found the App_info.xml; however, when I try to open it, it opens in Internet Explorer. Shouldn't it open in Notepad???

In looking through the App_info.xml in IE, I can't see where I'm supposed to make the changes. Further assistance would be appreciated.


Thanks.

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I've found the App_info.xml; however, when I try to open it, it opens in Internet Explorer. Shouldn't it open in Notepad???

That's what Microsoft have defined as the default handler for files of type 'XML'. Internet Explorer gives you a read-only view, so you can't make changes: and it also adds some display artefacts, which appear as rogue characters if you copy and paste the contents. Don't go there.

Instead, take control yourself. Right-click on the file, and choose either 'Edit' (if available - that would normally open the file in Notepad), or 'Open with... > Notepad'.

I have successfully opened the App_info file and found all of this for MB:

<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda50.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>mbcuda.cfg</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>


So, where in there do I make the changes to run two WU's at a time???

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos