My client says \'No work available (there was work but you don\'t have enough disk space allocated)\' when I try to update. But I have plenty of space free - much more than what it should need.

I found the problem. I didn't know you had to change the general settings as well.

> I found the problem. I didn't know you had to change the general settings as
> well.
>

ive got the same problem, and cant find any settings...
in BOINC (4.13) i see just:

File - Settings - Help
and in Settings there is just:
"Attach to Project"
"Proxy Server"

i had a look on the xml files in the directory where BOINC is installed...
i edited global_prefs.xml this way:

<global_preferences>
<source_project>http://climateprediction.net/</source_project>
<source_scheduler>http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi</source_scheduler>
<mod_time>1100538041</mod_time>
<run_if_user_active/>
<idle_time_to_run>3</idle_time_to_run>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<hangup_if_dialed/>
<work_buf_min_days>0.1</work_buf_min_days>
<max_cpus>2</max_cpus>
<disk_interval>60</disk_interval>
<disk_max_used_gb>1</disk_max_used_gb>
<disk_max_used_pct>90</disk_max_used_pct>
<disk_min_free_gb>0.4</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
</global_preferences>


but i still get the msg:
"climateprediction.net - 2004-11-15 18:15:21 - Message from server: No work available (there was work but you don't have enough disk space allocated)"

greets, chris

Hi Chris,

Your problem is likely to be the amount of disk space you're allowing for BOINC (1Gb). Each CPDN model requires 700Mb of disk space (with a further 330Mb required to store the results from each completed model).

If you're running more than one project the disk space available to each project is dependent on the relative resource shares of the projects, so with your current disk usage limit CPDN would require a relative resource share of at least 70% before it will download a model.
<br><a href="http://www.teampicard.net"><img src="http://www.teampicard.net/templates/fisubice/images/phpbb2_logo.jpg"></a><a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/team_display.php?teamid=3">Join us here</a>

&gt; Your problem is likely to be the amount of disk space you're allowing for
&gt; BOINC (1Gb). Each CPDN model requires 700Mb of disk space (with a further
&gt; 330Mb required to store the results from each completed model).
&gt;
&gt; If you're running more than one project the disk space available to each
&gt; project is dependent on the relative resource shares of the projects, so with
&gt; your current disk usage limit CPDN would require a relative resource share of
&gt; at least 70% before it will download a model.

uhm, if every model need a gig, how do i change the drive letter, where to save the data? i copied the boinc-folder on another partition and started it from there, but it doesnt work either...
or maybe i should change something in the general_prefs.xml file?
please tell me what to do, to get this thing run, my computers are running 24/7 and dont have any work :P

&gt; uhm, if every model need a gig, how do i change the drive letter, where to
&gt; save the data? i copied the boinc-folder on another partition and started it
&gt; from there, but it doesnt work either...

You should be able to do this, but you will need to (re)install BOINC to the new location, just as in a normal upgrade. You should be able to choose the drive location during the installation routine.

By the way, you don't need an extra gig each time - at the end of the run the data files are compressed to occupy a <i>mere</i> 300MB. If that is still a problem, then putting them onto CD/DVD is an insurance against you or the project wanting them again. BOINC will wipe old data files itself if running out of space, but it is best to keep them if you can.

There is a problem with this disk space thing but actually it is a server side venue bug :

- BOINC is allowed 100GB and up to 95%
- BOINC uses 27MB for Einstein and BOINC.
- The BOINC HD has 3.1 GB free space
- The BOINC GUI tells me BOINC has 2.44GB available

The computer had a CPDN WU before with the same BOINC version (4.19)

The computer had venue=home on Einstein and client_state.xml had "home" too.


But on CPDN it still had venue=work with lower settings for the allowed HD space so it gave me the message about missing HD space.

Setting the venue to "home" at CPDN too fixed the problem.


I hope this information helps someone :-)


p.s.: It must be a server side bug as the CPDN sched_request did try to set host_venue=home but the server ignored that.

&gt; The computer had venue=home on Einstein and client_state.xml had "home" too.
&gt;
&gt; But on CPDN it still had venue=work with lower settings for the allowed HD
&gt; space so it gave me the message about missing HD space.
&gt;
&gt; Setting the venue to "home" at CPDN too fixed the problem.
&gt;
&gt; p.s.: It must be a server side bug as the CPDN sched_request did try to set
&gt; host_venue=home but the server ignored that. Sometimes I get the idea, that
&gt; the 30 minutes "time shift" on the CPDN server are the reason for some
&gt; preferences related problems.

It's not a server side problem Ananas. It's a designed operational change :(

Looking at the BOINC checkin notes there was a fundamental change to the way host venues work on 1st October 2004. The venue can now be project specific, held in each of the account_*.xml files. I'm not sure when this change was first included in a public release, but I'd a similar problem the other day after upgrading to BOINC 4.43.

The only host venue notification now is in scheduler responses, which causes the appropriate account_*.xml file to be updated with the new venue if required. If the project global preferences update time is more recent than the value in global_prefs.xml the new value is also stored in client_state.xml and becomes the default for all projects without a venue in their account*.xml file.
<br><a href="http://www.teampicard.net/"><img src="http://www.teampicard.net/images/picardmini.gif"></a><a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/team_display.php?teamid=3">Join us here</a>

&gt; ...
&gt; It's not a server side problem Ananas. It's a designed operational change :(
&gt; ...


Oh, one of those 6-legged features :-/


Thanks for telling me. It's quite an important information as it explains more than this one issue.

Knowing those "features" allows to work arround them :-)