AWESOME - That will give me another chance to move you down a peg...

Yup, I figured I\'d get a response like that from somebody like you Kevint, I don\'t worry about it though, you have the Power to move past me at any Project by hook or crook so it\'s no big deal.

I was only trying to lighten it up a bit - DC contributing is not life or death, but should be fun. And we are having some fun now aren\'t we !! :)

---

My computers are not hidden so if someone wants to waste their time with a manual count, be my guest.

Due to the slow performance, counts are harder to obtain and may only be accurate for short periods of time due to the ability of the host to report and me not being able to cycle back through quick enough to recheck, but, here\'s a start, and I\'ll edit as time permits:

• HostID 18936 : 56
  
• HostID 18199 : 21 (since this is a C2Q with a higher number of tasks than 18936, either you have reporting problems with this host, so I can\'t see any more than that, or it is working on another project)
  
• HostID 2423 : 39
  
• HostID 18934 : 112
  

18199 - no longer on the project, last report was 3/24
18936 - the machine is at work, is split among projects, and probably has not reported since yesterday.
2423 is split among 8 projects.

Try 9930, I stopped counting at 200, and it\'s been splitting between einstein and cosmo since yesterday since it runs out of cosmo work periodically.


15049 is virtaully identical to 9930, and 16821 is also 100% cosmo.

edit for spelling

I also can not get to my pendings, no idea how many are there -

I can get into mine, but since I only have 11 puny tasks pending, that isn\'t surprising.

What it seems like is there is some sort of threshold value which, once passed, causes that mechanism to break. Instead of complaining for the sake of complaining, it might be nice if someone could try to figure out the breaking point. If that seems \"too much like work\", so be it I suppose, but it doesn\'t mean that finding the breaking point isn\'t a worthwhile endeavor...

---

I also can not get to my pendings, no idea how many are there -

I can get into mine, but since I only have 11 puny tasks pending, that isn\'t surprising.

What it seems like is there is some sort of threshold value which, once passed, causes that mechanism to break. Instead of complaining for the sake of complaining, it might be nice if someone could try to figure out the breaking point. If that seems \"too much like work\", so be it I suppose, but it doesn\'t mean that finding the breaking point isn\'t a worthwhile endeavor...

Yesterday morning when mine had 1300 pending, it took 3 or 4 tries to get in without a timeout, so that\'s gotta be pretty close to the breaking point. My guess is that it\'s also partially dependent on database and server load.

worthwhile endeavor...

Apparently this is your definition ...not shared by all...trivial pursuit

Seems the participant is much more interested in the project than the project is in the participant ;)

---

Try 9930, I stopped counting at 200, and it\'s been splitting between einstein and cosmo since yesterday since it runs out of cosmo work periodically.

I\'m running into more DB problems right now, but it does look like that host has more. If we go by the \"upper half has triple the bottom half\", that still amounted to around 200K...

Anyway, like Kevin said, all the hoopla about who has more pending isn\'t that big a deal in the whole scheme of things.

As I said in my edit to the other post with the list, communication is a two-way street. I view it as our responsibility to provide accurate communication, just as much as the project has responsibility to provide us with accurate and timely information...

What I find interesting in all of this though is that some validation does appear to be happening, as many in your list that have granted credit were reported by you on either the 28th or 29th (yesterday or today)... This may debunk my theory about the validator spinning on a lensing task, unless there\'s some timeout value and it moves on to the next task to validate.

All of this is speculation. It would be swell if someone with the project could provide information...

---

worthwhile endeavor...

Apparently this is your definition ...not shared by all...trivial pursuit

Seems the participant is much more interested in the project than the project is in the participant ;)

That value is probably a BOINC value, so it may break at the same threshold level in other projects as well.

Also, as I said, communication is a two-way street, and I\'ll agree wholeheartedly that the communication level from the project to us is very poor right now...

---

That value is probably a BOINC value, so it may break at the same threshold level in other projects as well.

Then please start another thread about it....isn\'t what you propose to do trolling by definition?

People want to express their concerns here and get an answer on a soloution...not trivial pursuit.

It may be as simple as someone hitting a key or the restart to get the daemons running properly......and Jord don\'t interfere please.

EDIT- Brian I have never hidden a post from you til now but you wish to argue with people to the nth degree.You abuse free speech.Perhaps if you were as critical of yourself as you are others this would stop. No replies by you in this URGENT thread will be tolerted on this subject.

---

All my machines are now disconnected until this problem is resolved....


Just don\'t have the time to babysit these machines.

All my machines are now disconnected until this problem is resolved....


Just don\'t have the time to babysit these machines.

Stevea; I have two rigs shut down due to lack of work from cosmo. 1 is
an AMD x2 and the other is an Intel x2. I have others that are draining
their cache and won\'t last the day. My new AMD x2 rig is \"burning in\"
on one of my backup projects (32 bit app). Not happy for the third
weekend in a row.

It occurs to me that the U of I has some serious deficiencies in
hardware, software, and personnel. Cosmo is fast regressing to sub alpha.

The \"weekday warriors\" in the IT and astronomy departments are not giving
Urbana a full pull. I will haul all they can send and I am sure all of us
\"lab rats\" would rather crunch than wonder where the cosmo staff is this
weekend.

Flame the project, not each other.

Regards-Voltron

---

If you don't build them, you can't sweat them. Got Stock?

All my machines are now disconnected until this problem is resolved....
Just don\'t have the time to babysit these machines.

Maybe you could just try what I\'m doing, I\'ve basically cut to just 1/3 Resource for this Project on each PC & the other 2/3 on 2 other Projects.

Mainly I did that out of necessity because some of my PC were running out of Wu\'s from this Project. I set my Contact Time to just 0.1 so none of the Projects will send too much work, I do pick up 2 or 3 Wu\'s from this Project every now and then too ... :)

I also can not get to my pendings, no idea how many are there -

I can get into mine, but since I only have 11 puny tasks pending, that isn\'t surprising.

What it seems like is there is some sort of threshold value which, once passed, causes that mechanism to break. Instead of complaining for the sake of complaining, it might be nice if someone could try to figure out the breaking point. If that seems \"too much like work\", so be it I suppose, but it doesn\'t mean that finding the breaking point isn\'t a worthwhile endeavor...

Well I agree, it does seem there is a point where it breaks/times out. But since I can not even check... I only tried to view my pending credit sometime yesterday, and it was not working then.

---

I got to my pendings an hour or so ago.
First time in about 2 days.
984 WU´s was what I found there.

Some credits are coming through,
but in server stats the amount of
Workunits waiting for validation
is stedily rising.
It´s now at 28,462...

G\'Day all,
A few things to say,

@ Brian, We are all getting frustrated with what\'s happening with this project at the moment (It took me 3 attempts to get to this Thread). You can keep trying your Q-TIPS if you want but it may not get you very far (you can have fun trying though).
Overall I have found Scott in particular to be a very good bloke and would like to keep him on the volunteers side.

Alas, it would be nice to know where he is or someone on the project at the moment as this website is a pain to move around.

@ Poorboy,
Please don\'t leave, I would love to see which one of you Power Users is going to be the first to get to 10,000,000 cobblestones/credits in this project.

Of course that will depend on work availability and being able to upload/download work units and of course getting them Validated.

@ The Project,
Still having the \"Unable to open Database\" errors and this means it can take hours to upload any completed work.
Now also getting \"No Work Available\" on a number of work requests.

Still getting the looping resent 09/03/08 work units wrapped in 2.12 clothes, plus a lot of the older work units from early March and February as well which still has the Lensing feature turned on.

---

If you run out of WUs in BOINC, just pick a project with relatively short WUs (I use Rosetta@Home, and choose \"1hr\" in runtime preference) and set the resources to \"1\" and Cosmology to 1,000. That distribution gives 1hr every 42 days to the other project, but in turn ensures no machine runs idle. (Rosetta is stable and WUs are continuously generated)

Something I noticed when I got a few Cosmology WUs just now:

30/03/2008 15:42:56|Cosmology@Home|Sending scheduler request: To fetch work. Requesting 51498 seconds of work, reporting 0 completed tasks
30/03/2008 15:43:07|Cosmology@Home|Scheduler request succeeded: got 4 new tasks
30/03/2008 15:43:07|Cosmology@Home|You used the wrong URL for this project
30/03/2008 15:43:07|Cosmology@Home|The correct URL is http://www.cosmologyathome.org/
30/03/2008 15:43:07|Cosmology@Home|Using the wrong URL can cause problems in some cases.
30/03/2008 15:43:07|Cosmology@Home|When convenient, detach this project, then reattach to http://www.cosmologyathome.org/
30/03/2008 15:43:09|Cosmology@Home|Started download of params_032608_100139_2.ini
30/03/2008 15:43:09|Cosmology@Home|Started download of params_032608_100139_4.ini
30/03/2008 15:43:11|Cosmology@Home|Finished download of params_032608_100139_2.ini
30/03/2008 15:43:11|Cosmology@Home|Finished download of params_032608_100139_4.ini
30/03/2008 15:43:11|Cosmology@Home|Started download of params_032608_100140_0.ini
30/03/2008 15:43:11|Cosmology@Home|Started download of params_032608_100140_3.ini
30/03/2008 15:43:13|Cosmology@Home|Finished download of params_032608_100140_0.ini
30/03/2008 15:43:13|Cosmology@Home|Finished download of params_032608_100140_3.ini
30/03/2008 15:43:17|Cosmology@Home|Sending scheduler request: To fetch work. Requesting 15801 seconds of work, reporting 0 completed tasks
30/03/2008 15:43:27|Cosmology@Home|Scheduler request succeeded: got 1 new tasks
30/03/2008 15:43:27|Cosmology@Home|You used the wrong URL for this project
30/03/2008 15:43:27|Cosmology@Home|The correct URL is http://www.cosmologyathome.org/
30/03/2008 15:43:27|Cosmology@Home|Using the wrong URL can cause problems in some cases.
30/03/2008 15:43:27|Cosmology@Home|When convenient, detach this project, then reattach to http://www.cosmologyathome.org/
30/03/2008 15:43:29|Cosmology@Home|Started download of params_032608_130824_0.ini
30/03/2008 15:43:31|Cosmology@Home|Finished download of params_032608_130824_0.ini
30/03/2008 15:43:37|Cosmology@Home|Sending scheduler request: To fetch work. Requesting 6888 seconds of work, reporting 0 completed tasks
30/03/2008 15:43:42|Cosmology@Home|Scheduler request succeeded: got 1 new tasks
30/03/2008 15:43:42|Cosmology@Home|You used the wrong URL for this project
30/03/2008 15:43:42|Cosmology@Home|The correct URL is http://www.cosmologyathome.org/
30/03/2008 15:43:42|Cosmology@Home|Using the wrong URL can cause problems in some cases.
30/03/2008 15:43:42|Cosmology@Home|When convenient, detach this project, then reattach to http://www.cosmologyathome.org/
30/03/2008 15:43:44|Cosmology@Home|Started download of params_032608_171029_2.ini
30/03/2008 15:43:45|Cosmology@Home|Finished download of params_032608_171029_2.ini
30/03/2008 15:43:53|Cosmology@Home|Sending scheduler request: To fetch work. Requesting 3440 seconds of work, reporting 0 completed tasks
30/03/2008 15:43:58|Cosmology@Home|Scheduler request succeeded: got 1 new tasks
30/03/2008 15:43:58|Cosmology@Home|You used the wrong URL for this project
30/03/2008 15:43:58|Cosmology@Home|The correct URL is http://www.cosmologyathome.org/
30/03/2008 15:43:58|Cosmology@Home|Using the wrong URL can cause problems in some cases.
30/03/2008 15:43:58|Cosmology@Home|When convenient, detach this project, then reattach to http://www.cosmologyathome.org/
30/03/2008 15:44:00|Cosmology@Home|Started download of params_032608_210243_0.ini
30/03/2008 15:44:02|Cosmology@Home|Finished download of params_032608_210243_0.ini


You\'ll notice it didn\'t get enough work and connected 3 more times in a row - I didn\'t do this manually. I don\'t think this used to happen and it might also be a reason why the servers get hammered.

@ Poorboy,
Please don\'t leave, I would love to see which one of you Power Users is going to be the first to get to 10,000,000 cobblestones/credits in this project.

haha ... I conceded that Milestone to my good Team Mate Chris a long time ago, I hit 5 Million 1\'st (Or at least I think I did) so it was somebody else turn to take the Flame run with it ... :)

I\'ll probably be back once things settle down here but for now I\'m out, don\'t even have any Wu\'s and ain\'t looking for any either until things get better with the project in General & there\'s some semblance of Communication with the Project Dev\'s instead of this abysmal silence from them.

I\'m out of work too. AMD Athlon XP 2600+ running Sabayon Linux (Gentoo based distribution) keeps getting the dreaded

Sun 30 Mar 2008 07:48:14 PM EDT|Cosmology@Home|Message from server: No work sent
Sun 30 Mar 2008 07:48:14 PM EDT|Cosmology@Home|Message from server: (there was work but it was committed to other platforms)

I guess it\'s time to suspend cosmology@home and start running something else until the problems are solved.

I\'m out of work too. AMD Athlon XP 2600+ running Sabayon Linux (Gentoo based distribution) keeps getting the dreaded

Sun 30 Mar 2008 07:48:14 PM EDT|Cosmology@Home|Message from server: No work sent
Sun 30 Mar 2008 07:48:14 PM EDT|Cosmology@Home|Message from server: (there was work but it was committed to other platforms)

I guess it\'s time to suspend cosmology@home and start running something else until the problems are solved.

I was able to pry some WU\'s out of the vault late on 3/30 by using retry over and over and over. Not worth the aggravation. I have added another 64 bit project to my fastest machines, and will be draining Cosmo from all my rigs. This project was the one and only 24/7 on my farm. Too bad the U of I considers it a cute distraction. Over the last month, I considered it to be a growing nuisance. I can\'t afford to air condition idle machines. Unlike Cosmo, my upkeep is dedicated and expensive. I\'ll check back to see how things are going.

It\'s about mid day in my time zone (and U of I) and I haven\'t noticed any communication from the admins regarding the latest performance tweak. It wouldn\'t make a difference anyway. There\'s always next weekend for more fun.

Regards-Voltron

---

If you don't build them, you can't sweat them. Got Stock?

Well, I gave them the benefit of the doubt over the weekend, but no communications at all from the project team well into the workday is enough proof for me that this project isn\'t worth the effort. As my boxes run out of work, I\'ll be moving them permanently to other projects. This one\'s become too much of a pain in the butt...

I even wonder if Ben Wandelt http://cosmos.astro.uiuc.edu/pBen.php?style=explore
knows there is a problem with his project...

---