Hello everyone,

I am having trouble getting cosmology@home to run. I use boinc 5.10.28 under Linux. Having re-attached to Cosmology after the server restructuring a few days ago, I have the following problems:

• My boinc installation is on a 1 GB USB-stick. Local preferences limit disk usage to around 800 MB. I often get error messages indicating that no WUs were downloaded due to missing space, but after leaving boinc alone for a while, it fetches WUs and finishes them, never using more than 200 or 300 MB.
  
  
• After finishing a work unit, my boinc client exits with a symbol lookup error (see console snippet below). A subsequent restart lists the WU as \"lost result\".
  

Do you have any ideas what I might do about this? Any hints are appreciated.

Here is the output from the end of a WU\'s processing:

 >> Beginning Phase 3 <<

 >> ----------------- <<

 at z =   0.0000000E+00  sigma8 (all matter)=  0.8138058

06-Feb-2008 13:42:13 [Cosmology@Home] Computation for task wu_013108_090634_0_2 finished

./boinc: symbol lookup error: ./boinc: undefined symbol: gzopen64



[1]+  Exit 127                ./boinc

06-Feb-2008 13:42:29 [Cosmology@Home] Restarting task wu_013108_090634_0_2 using camb version 205

06-Feb-2008 13:42:31 [Cosmology@Home] Task wu_013108_090634_0_2 exited with zero status but no \'finished\' file

06-Feb-2008 13:42:31 [Cosmology@Home] If this happens repeatedly you may need to reset the project.

(...) maybe the 1gb stick is not enough.

The second part of the error might be a BOINC issue :

Ticket #537 is titled ./boinc: symbol lookup error: ./boinc: undefined symbol: gzopen64

The ticket is still open, I wonder why it\'s still priorized \"minor\", the reason for going to \"minor\" has been that it seemed to be a unique error but now it should go back to \"major\" I guess.


p.s.: I found this, maybe it can fix your problem too

OK, first of all thanks for your replies. I have tried to take a closer look at the problem. I moved the boinc folder from my USB stick onto a hard drive and raised the disk usage limit to 9 GB using global_prefs_override.xml.

Running from hard disk, I could not reproduce the error. However, I doubt that disk space was really the cause: While processing several workunits, I monitored boinc\'s disk consumption every 2 seconds. Those values never went above 129 MB for the boinc client and cosmology and Einstein as projects in the same directory. So, I suppose that CAMB might falsely report \"out of disk space\" when, in fact, there is enough left...

Monitoring, by the way, was done using

watch -n 2 \"du -sh ~/boinc | tee -a ~/boincsize\"