Host Project Date Message
Xaak Cosmology@Home 4/3/2008 4:13:32 PM Message from client: This project is dead

According to the Server Status all work has now been validated.
That should mean new work can be downloaded and old work uploaded, at least one would think so. As the news announcement indicated.

My pending has not changed for over a day and neither has my total.
So from this I can assume that I am waiting for my wingmen to upload their results so that my pendings can clear.

As my message log says project is down, then the Server Status on the front page seems to be bogus and the work showing on it might not even be there.

The amount of work units that I have waiting to upload is now causing problems with what work the Boinc Manager will download as it says I am over committed with the amount of work I have on the computer.
I run other projects as well but I am running out of work for them now as well.

Please can we at least upload what we currently have ??

---

...
Please can we at least upload what we currently have ??

I think you\'re under the mistaken assumption that someone who could turn on uploads is actually reading this, or even cares.

Stick a for in it, this project is done.

Scott, Server says its up and running... someone go check it as I have been receiving \" Server down for maint\" and I got a whole bunch of wu\'s to report....

Most recent exaggerated guess to WU\'s needing to report.

I have about 20 machines crunching this project, many/most are quads.
Just checking a Q6600 one of my slower quads - it has 171 units to upload.
I do have a couple of duo cores.. so rounding downwards.. to an average of 3 cores per box instead of 4 -
and rounding down from 171 to say 130 (I checked a duo and it has 130 so we will go with that )

130x20 = 2600 WU\'s that have been crunched, needing to upload and report - on the LOW end. 3200 More realistic.

Now I know I am not the only one out there with work ready to report.. from reviewing cache that has not crunched - I am assuming about 65,000 WU have been crunched and waiting to report back.

I am just thinking that if something is not corrected soon, by the time they turn it back on and allow us to report, we are going to be in the same mess that we were a few days ago.

I am thinking they will turn it back on somewhere around Friday afternoon, just before they leave for the weekend.


NOW - lets talk about WU\'s that have been crunched and waiting to report that are now starting to EXPIRE - deadlines are past - NOW WHAT ?????????


**** EDIT *** Just checking further - I found 4 machines with over 170 WU\'s, 5 with more than 200 WU\'s waiting to report, and most with somewhere between 130-160. My slowest Pent D\'s running have 90-110.

This is going to be a real treat when this damn breaks.. Kind of reminds me of the old SETI days. And I have not crunched SETI for A LONG time!

---

Most recent exaggerated guess to WU\'s needing to report.

I have about 20 machines crunching this project, many/most are quads.
Just checking a Q6600 one of my slower quads - it has 171 units to upload.
I do have a couple of duo cores.. so rounding downwards.. to an average of 3 cores per box instead of 4 -
and rounding down from 171 to say 130 (I checked a duo and it has 130 so we will go with that )

2,600 WU\'s that have been crunched, needing to upload and report - on the LOW end. More realistic is about 3,500.



Now I know I am not the only one out there with work ready to report.. from reviewing cache that has not crunched - I am assuming about 65,000 WU have been crunched and waiting to report back.

I am just thinking that if something is not corrected soon, by the time they turn it back on and allow us to report, we are going to be in the same mess that we were a few days ago.

I am thinking they will turn it back on somewhere around Friday afternoon, just before they leave for the weekend.


NOW - lets talk about WU\'s that have been crunched and waiting to report that are now starting to EXPIRE - deadlines are past - NOW WHAT ?????????

Jord already answered you those will be validated before a replacement is sent out Kevint....the way it has worked in the past ....so not an urgent concern....however the hosts d/l other work can be a huge issue ...that part makes it urgent.

[EDIT] I suggest if the machines are done crunching cosmo to suspend the project until you know its back up.

It is important the project keeps set nnw until results can be reported imho.

---

I now have about 1600 ready to upload, including all the unstarted wus I just aborted.

I really don\'t mind that the project has problems. However, I won\'t tolerate the lack of communications.

I hope the project admins plan to stay in academia. They wouldn\'t last 2 seconds if they had to get a real job.

I now have about 1600 ready to upload, including all the unstarted wus I just aborted.

I really don\'t mind that the project has problems. However, I won\'t tolerate the lack of communications.

I hope the project admins plan to stay in academia. They wouldn\'t last 2 seconds if they had to get a real job.

Xaak-Stay away from Orbit then because they give no response at all,zero,zip,nada,had 1000hrs worth of work and they announce on the homepage they listen (but never respond) when trying to complete a 60 hr wu,if it was going to help them knowing it would result in an error by them and me....now Cosmo is not that bad...It felt as though they thought my computer time was of no consequence.I lashed out from lack of response aborting even those at 95% complete. I am of the humor to believe that projects can learn from their mistakes :)

---

Xaak-Stay away from Orbit then because they give no response at all,zero,zip,nada,had 1000hrs worth of work and they announce on the homepage they listen (but never respond) when trying to complete a 60 hr wu,if it was going to help them knowing it would result in an error by them and me....now Cosmo is not that bad...It felt as though they thought my computer time was of no consequence.I lashed out from lack of response aborting even those at 95% complete. I am of the humor to believe that projects can learn from their mistakes :)

The only way they\'ll learn is if they don\'t get enough resources to get what they expect out of the project. They grand too much credit, so that won\'t happen as people will flock here for the credits. So, they\'ll keep on going the way they\'re going because there aren\'t going to be any consequences that they\'ll see. But they can keep going on without me.

Xaak-Stay away from Orbit then because they give no response at all,zero,zip,nada,had 1000hrs worth of work and they announce on the homepage they listen (but never respond) when trying to complete a 60 hr wu,if it was going to help them knowing it would result in an error by them and me....now Cosmo is not that bad...It felt as though they thought my computer time was of no consequence.I lashed out from lack of response aborting even those at 95% complete. I am of the humor to believe that projects can learn from their mistakes :)

The only way they\'ll learn is if they don\'t get enough resources to get what they expect out of the project. They grand too much credit, so that won\'t happen as people will flock here for the credits. So, they\'ll keep on going the way they\'re going because there aren\'t going to be any consequences that they\'ll see. But they can keep going on without me.

Agreed-As I told Brian in another thread people vote with their feet.

---

Ok,

Now this is starting to affect my other projects... I have crunched through a good share of the existing cache on many machines. BUT BOINC will not pull down any work from other projects... The only way I can get it to pull down work is to suspend Cosmo - or reset/detach. If I suspend, then the crunched work will not be uploaded, and since the deadlines have passed on over 40% of the crunched work - well then the work will be lost. OR - if I detach.. then basically the same thing -

4/4/2008 9:01:40 AM|Cosmology@Home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 399 completed tasks
4/4/2008 9:01:50 AM|Cosmology@Home|Scheduler request succeeded: got 0 new tasks
4/4/2008 9:01:50 AM|Cosmology@Home|Message from server: Project is temporarily shut down for maintenance
4/4/2008 9:08:23 AM|Einstein@Home|Sending scheduler request: To fetch work. Requesting 1326400 seconds of work, reporting 0 completed tasks
4/4/2008 9:08:28 AM|Einstein@Home|Scheduler request succeeded: got 0 new tasks
4/4/2008 9:08:28 AM|Einstein@Home|Message from server: No work sent
4/4/2008 9:08:28 AM|Einstein@Home|Message from server: (won\'t finish in time) Computer on 99.8% of time, BOINC on 100.0% of that

HOWEVER, on the bright side of things.. After over 7 days of it not working, I have FINALLY been able to check my pendings - so something seems to be moving forward -

---

<snip>

HOWEVER, on the bright side of things.. After over 7 days of it not working, I have FINALLY been able to check my pendings - so something seems to be moving forward -

Ok- depress me further! On top of the 1000 or so waiting to upload, I can now see the 700+ pendings. :)
The good news on being able to view the pendings is that it most likely means the MySQL problems are no longer an issue.

---

Boinc Button Abuser In Training >My Shrubbers<

I have a theory...
I believe a micro singularity could have been created by one of our LHC runs which has somehow migrated through the Boinc network and trapped the staff of both projects. *sarcastic grin*

Seriously though..
Someone should phone Ben\'s office, you know just to make sure everyone is ok...maybe ask if they would be so kind as to enable uploads for us before leaving for the weekend. That may give a chance for the validator to catch up again before we start crunching new units.

---

[quote]

Now this is starting to affect my other projects... I have crunched through a good share of the existing cache on many machines. BUT BOINC will not pull down any work from other projects... The only way I can get it to pull down work is to suspend Cosmo - or reset/detach. If I suspend, then the crunched work will not be uploaded, and since the deadlines have passed on over 40% of the crunched work - well then the work will be lost. OR - if I detach.. then basically the same thing -

I expect you have tried setting your cache to 0.1 days, I have found in the past that changes how BOINC treats the \"won\'t finish in time\" problem.

Is Cosmology server down for maintenance? It\'s been down now for at least two days.


04/04/2008 15:07:36|Cosmology@Home|Sending scheduler request: Requested by user. Requesting 2845 seconds of work, reporting 1 completed tasks
04/04/2008 15:07:41|Cosmology@Home|Scheduler request succeeded: got 0 new tasks
04/04/2008 15:07:41|Cosmology@Home|Message from server: Project is temporarily shut down for maintenance

---

"All man born has a right to life and no man born has the right to take that life"

If I suspend, then the crunched work will not be uploaded

Are you sure about this? I Just ran a test and a suspended project was able to report WUs just fine.

Suspend doesn\'t affect network, just CPU scheduler (computing).

---

BOINC Project specifications and hardware requirements

Half my PC\'s have returned their finished Wu\'s in the last couple of hours, 1 even downloaded 20 or so more Wu\'s, so somethings afoot I suspect ... :| ... My Credit even moved up a little too ... :)

I guess you get what you pay for. Someone needs to go track down the frat-boy admin. I hope this isn\'t a glimpse of the future trend of IT staff.

05/04/2008 09:51:52|Cosmology@Home|Sending scheduler request: Requested by user. Requesting 114700 seconds of work, reporting 0 completed tasks
05/04/2008 09:51:58|Cosmology@Home|Scheduler request succeeded: got 0 new tasks
05/04/2008 09:51:58|Cosmology@Home|Message from server: No work sent

Results ready to send 56,985, server status all green.

?

---

BOINC Project specifications and hardware requirements