Not so urgent, I think, but after deattaching and then attaching to the project in the new url "cosmologyathome", I can't get any new WU's. I get a message about not having enough disk space. In fact, i have 978 MB (not too much, but I'm ruuning Ubuntu in a little partition) Is it really a problem?

Thanks a lot.

Maybe your general preferences are allowing more that your 978 MB?
Than you have to adjust the values. ;-)
(Go to your account under 'general preferences' and have a closer look at the numbers for: "Use at most x GB disk space"; "Leave at least x GB disk space free"; "Use at most x% of total disk space".
Or if you're using a newer BOINC manager version you can also adjust it for that machine only under Extras -> Preferences -> Disk and Memory usage.)

---

Lovely greetings, Cori

i have 978 MB (not too much, but I'm ruuning Ubuntu in a little partition) Is it really a problem?

Depending on how many Wu's you want to Download (25 is the Max at 1 time allowed) to be safe about 150 mb should be enough Disk Space. As long as the Partition has that much it should run.

Also do as Cori Suggested too ... :)

Not so urgent, I think, but after deattaching and then attaching to the project in the new url "cosmologyathome", I can't get any new WU's. I get a message about not having enough disk space. In fact, i have 978 MB (not too much, but I'm ruuning Ubuntu in a little partition) Is it really a problem?

Thanks a lot.

The files created by CAMB can be quite large, with the checkpointing files being several hundred Mb. So, yes, this can cause a problem. I think the rsc_disk_bound is currently at 1 Gb or so.

Didn't know we needed that much space, I show only using about 100-115 mb of space unless space is being used somewhere I don't know about ...

Not so urgent, I think, but after deattaching and then attaching to the project in the new url "cosmologyathome", I can't get any new WU's. I get a message about not having enough disk space. In fact, i have 978 MB (not too much, but I'm ruuning Ubuntu in a little partition) Is it really a problem?

Thanks a lot.

The files created by CAMB can be quite large, with the checkpointing files being several hundred Mb. So, yes, this can cause a problem. I think the rsc_disk_bound is currently at 1 Gb or so.

Didn't know we needed that much space, I show only using about 100-115 mb of space unless space is being used somewhere I don't know about ...

You probably don't need that much space, but I have seen checkpointing files which are 300 Mb or so. They are deleted at the end of the computation, though.

---

Scott Kruger
Project Administrator, Cosmology@Home

Not so urgent, I think, but after deattaching and then attaching to the project in the new url "cosmologyathome", I can't get any new WU's. I get a message about not having enough disk space. In fact, i have 978 MB (not too much, but I'm ruuning Ubuntu in a little partition) Is it really a problem?

Thanks a lot.

The files created by CAMB can be quite large, with the checkpointing files being several hundred Mb. So, yes, this can cause a problem. I think the rsc_disk_bound is currently at 1 Gb or so.

If I'm right that also implies that Boinc expects this 1GB to available for it to be willing to download a WU.

---

BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair

Not so urgent, I think, but after deattaching and then attaching to the project in the new url "cosmologyathome", I can't get any new WU's. I get a message about not having enough disk space. In fact, i have 978 MB (not too much, but I'm ruuning Ubuntu in a little partition) Is it really a problem?

Thanks a lot.

The files created by CAMB can be quite large, with the checkpointing files being several hundred Mb. So, yes, this can cause a problem. I think the rsc_disk_bound is currently at 1 Gb or so.

If I'm right that also implies that Boinc expects this 1GB to available for it to be willing to download a WU.

Hmm... maybe I'll go ahead and lower it then =)

---

Scott Kruger
Project Administrator, Cosmology@Home

** ALERT **

All my machines are currently getting no work from project messages.

-jim

NOTE: It doesn't appear to be CPU/OS specific, and the server status page says there are WU's available...

9/8/2007 3:43:58 PM|Cosmology@Home|Sending scheduler request: Requested by user
9/8/2007 3:43:58 PM|Cosmology@Home|Requesting 41203 seconds of new work, and reporting 1 completed tasks
9/8/2007 3:44:03 PM|Cosmology@Home|Scheduler RPC succeeded [server version 601]
9/8/2007 3:44:03 PM|Cosmology@Home|Message from server: No work sent
9/8/2007 3:44:03 PM|Cosmology@Home|Deferring communication for 7 sec
9/8/2007 3:44:03 PM|Cosmology@Home|Reason: requested by project
9/8/2007 3:44:03 PM|Cosmology@Home|Deferring communication for 4 min 19 sec
9/8/2007 3:44:03 PM|Cosmology@Home|Reason: no work from project

^^ from AMD Opteron 175 w/ 32bit XP Pro

-jim

---

** ALERT **

All my machines are currently getting no work from project messages.

-jim

NOTE: It doesn't appear to be CPU/OS specific, and the server status page says there are WU's available...

9/8/2007 3:43:58 PM|Cosmology@Home|Sending scheduler request: Requested by user
9/8/2007 3:43:58 PM|Cosmology@Home|Requesting 41203 seconds of new work, and reporting 1 completed tasks
9/8/2007 3:44:03 PM|Cosmology@Home|Scheduler RPC succeeded [server version 601]
9/8/2007 3:44:03 PM|Cosmology@Home|Message from server: No work sent
9/8/2007 3:44:03 PM|Cosmology@Home|Deferring communication for 7 sec
9/8/2007 3:44:03 PM|Cosmology@Home|Reason: requested by project
9/8/2007 3:44:03 PM|Cosmology@Home|Deferring communication for 4 min 19 sec
9/8/2007 3:44:03 PM|Cosmology@Home|Reason: no work from project

^^ from AMD Opteron 175 w/ 32bit XP Pro

-jim

I moved caferace's post from "Urgent Problems" to here. I left his original post there, since I think this might be another problem than what we have experienced over the last weeks. My machines get no work either. Windows nor Linux.

---

BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair

same here, no work from project.

---

Thanks, tutta...

On a side note, even though I am turning in lots of results per hour it appears that around the same time the 'no work' message started, results weren't being compared for completeness. My pending is rising rapidly, and a quick check through them confirms that results with two participants having completed them are not being validated. I did notice that the scheduler version number (I think?) seems to have incremented.

Something is broken. :)

-jim

---

Transitioner shows 6 hour backlog; validator says it is working, but appears to be dead. Unless Scott is working Sundays, see you all on Monday- it looks like we are dead in the water. (PS- Rosetta: dead, SETI: dead, good luck having a back-up project run- my only backup still alive is Einstein. The way things look, I expect them to crash at any moment).

---

Boinc Button Abuser In Training >My Shrubbers<

** ALERT **

All my machines are currently getting no work from project messages.

-jim

Same here... :(

---

last.fm BOINC users group

I'm not getting any more work, but my systems are still going through their cache, so at least they're not dry.

Have gone dry for cosmology :(

Since I last wrote (at least 8 hours ago) the number of work units the server says are waiting to be sent has remained nearly the same, so I imagine no one is going to be getting any work at the moment.

---

I don't know whether this is significant or not, but I noticed a change in the message log recently. When requesting OR reporting work I would always get the message "Scheduler RPC succeeded (server version 511)". But starting from the time that no work is sent I have been getting the message "Scheduler RPC succeeded (server version 601)". Anybody know about this server version number and whether it is relevant? On one occasion it said version 509.

Sorry guys, the software fort this project is simply not up to public release standard yet. The project is good in principle, and I'll return here when the software does what it's supposed to do.

Sorry guys, the software fort this project is simply not up to public release standard yet. The project is good in principle, and I'll return here when the software does what it's supposed to do.

That is why the project is still in Alpha state, we expect problems like this and are willing to accept them.

I saw something new today. A couple of my WUs were finished by me and my wingman, but they're still pending. How come?

441661
441646
441644
441436
436594

I don't know whether this is significant or not, but I noticed a change in the message log recently. When requesting OR reporting work I would always get the message "Scheduler RPC succeeded (server version 511)". But starting from the time that no work is sent I have been getting the message "Scheduler RPC succeeded (server version 601)". Anybody know about this server version number and whether it is relevant? On one occasion it said version 509.

The numbers aren't really accurate. They kind of relate to the version of the core client that's in development (at least that's how I understand it) and I know they've started the check-ins for version 6. So I'd hazard a guess that Scott updated the backend (notice the addition of "Mark all threads as read" in the forums) and something went wrong with one or more of the daemons.

Anyone running Seti who can tell us what their server version says? Backend changes get rolled out there first (as far as I know).

---

Kathryn :o)
The BOINC FAQ Service
The Unofficial BOINC Wiki
The Trac System
More BOINC information than you can shake a stick of RAM at.

SETI says server version 511... ;)

---

last.fm BOINC users group