We are recovering from a database crash

I have had problems with my 'SETI@Home Advanced' Tasks with a Status: Waiting to Run. Can only assume this might have something to do with the outage. Everything was going ok until I had to reboot my system. I also lost a couple of other projects as well.

I also joined Enigma 0.76a/0.76b (USA/UK)today. When I worked at RSRE Malvern, in Worcestershire in the late 80's, I got to play with an original German 4-rotor Enigma machine.

Well anyway I will shut down my computer tonight, I have 18
works from 28 minutes left each one..and I am going to bed
its 3:12 in the night and I will wake up after 8 hours.
Its no use to keep my boinc running if there is no work left.

Night night everyone

Hope tomorrow it will be better.
____________

I had hope to find some work, but my pc is empty
I still let him run tonight but no wu work:(
____________

Thanks

Matt; Some of the previous posts recommended doing other projects while waiting and waiting for Seti. That may have been a strategy to get users to use Seti less and maybe ultimately leave Seti and have more of Seti to themselves. Whatever the reason As of now SETI community, I have taken the dedicated (Intel(R) Xeon(R)CPU X5650@ 2.67GHz[Family6 Model 44 Stepping 2](24 processors)NVIDIA GeForce GTX 465 (1023MB) driver: 301.42) away from the SETI Project because of inadequate Server Bandwidth and several Programing issues that impact overall Reliability and Functionally. All that has significantly diminished my sense of any doing any meaningful scientific contribution with Seti@Home. I started with SETI in June of 1999. I currently rank 9,667 out of 2,488,900 (99.6116 percentile)
I will keep the laptop,(Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz [Family 6 Model 30 Stepping 5](8 processors)NVIDIA GeForce GTX 460M (1535MB) driver: 306.23) with only 4 0f the 8 processors running because of heat issues. Token effort only to SETI.
I would say to the rest of the Seti Community "Good Luck" but think it will take more than that. Maybe with me not trying to get wu's or taking up Bandwidth it will be minimally better for the rest of you.
____________

I too have recently cut back on my SETI activity. I regularly run out of WUs for days on end. Luckily there are lots of other valuable science projects available to contribute to. I am currently contributing to seven projects and find that many of them run short of WUs.

While I would like to have more WUs for SETI, I am glad that we are analyzing the data as fast as they can send it to us. That tells me there are lots of like minded people out there trying to help.

Keep up the good work everyone.
____________

My client hasn't updated for days. I just tried (again) to manually update and it's still not uploading my finished WUs and it hasn't downloaded any new ones. In fact, it's doing nothing but deferring communication over and over.

Anyone know what's up?
____________

I too have a machine that is unable to connect and upload/download work units. What I find more interesting is that it is the machine that has a serious GPU and multi CPU cores to do the processing. I have another machine that has a less capable GPU and a modest 2 core CPU that seems to get units as required and keeps the buffer full or close to it. I have a third machine that has no GPU and a slow CPU that I don't run BOINC on but have in the past just for testing.
I decided to run seti on that last night to see how it would connect and down load units. On its first connection it got units, downloaded with no problems making connections.

Whatever is going on seems to be related to machines that have larger computing capacities. There have been hints on the message baords that the scheduler is aware of the capacity of the machines it is dowloading to. It seems to me machine capacity is related to this ongoing problem.

FWIW.

I have tried everything I know to do including the not geting work units trick, which used to work, to deleteing the project entirely and reloading from the beginning. So far, I get 1 unit and then nothing.

My client hasn't updated for days. I just tried (again) to manually update and it's still not uploading my finished WUs and it hasn't downloaded any new ones. In fact, it's doing nothing but deferring communication over and over.

Anyone know what's up?

F Y I

I am using BOINC Version 7.0.28(64), wxWwidget version 2.8.10, BOINC manager shows that I have no work for my i7 870 PC 5663981 , Windows 7 Ultimate 64. This has been an ongoing problem for the last couple of months. My core2 6320 Windows XP 32, PC 6584825, is still getting work!

Now when I check the SETI site for my account, and then on the PC's for my account, there it shows 224 ghosts units are applied to this PC 5663981. I have Reset Seti@home multiple times, and I am still unable to remove these Ghost Units from my account. These ghost Work Units are set to expire sometimes in January 2013.

Until they are removed from my account, then I will have no choice but to move PC 5663981 to another project, that is until the problem with Ghost Units is corrected.

This is not the first time this project has had problems with WU's. I have long since removed my Nvidia GPU's to other useful BOINC scientific medical projects. There, their bandwidth is appreciated, thus not only giving enormous credits(682,005.13 RAC as a side bonus), to doing useful WU's for Medical Research.

Sometimes I do miss the old days before BOINC, with the original SETI program, and where my Windows 95 AMD K6-2 400, would take about 7 days to crunch just one WU. This was using a dial-up modem! I still have my first 100 Unit Certificate, given to me from Berkeley, somewhere. That 100 unit milestone took about 1 year to complete.

Well there it is. Too many people trying to crunch for SETI. We knew this day would come.

Well there it is. Too many people trying to crunch for SETI. We knew this day would come.

Well, maybe they should start and limit the number of WUs a single host can receive to cut down the the number of WUs that are "in progress" (forever).

Each time I check on one of my WUs that hasn't been validated in weeks, it comes down to a deadbeat cruncher hoarding thousands of WUs on a single host and then just abandoning them...
If there would be a way to weed those out, that would probably already help to level the issue at hand... :(

Ralf

Matt; Some of the previous posts recommended doing other projects while waiting and waiting for Seti. That may have been a strategy to get users to use Seti less and maybe ultimately leave Seti and have more of Seti to themselves.

Whatever the reason As of now SETI community, I have taken the dedicated (Intel(R) Xeon(R)CPU X5650@ 2.67GHz[Family6 Model 44 Stepping 2](24 processors)NVIDIA GeForce GTX 465 (1023MB) driver: 301.42) away from the SETI Project because of inadequate Server Bandwidth and several Programing issues that impact overall Reliability and Functionally. All that has significantly diminished my sense of any doing any meaningful scientific contribution with Seti@Home. I started with SETI in June of 1999. I currently rank 9,667 out of 2,488,900 (99.6116 percentile)
I will keep the laptop,(Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz [Family 6 Model 30 Stepping 5](8 processors)NVIDIA GeForce GTX 460M (1535MB) driver: 306.23) with only 4 0f the 8 processors running because of heat issues. Token effort only to SETI.
I would say to the rest of the Seti Community "Good Luck" but think it will take more than that. Maybe with me not trying to get wu's or taking up Bandwidth it will be minimally better for the rest of you.

Well there it is. Too many people trying to crunch for SETI. We knew this day would come.

Well, maybe they should start and limit the number of WUs a single host can receive to cut down the the number of WUs that are "in progress" (forever).

There is a limit of 100 CPU WUs and 100 GPU WUs per host. It's been in place for a couple of weeks.

Each time I check on one of my WUs that hasn't been validated in weeks, it comes down to a deadbeat cruncher hoarding thousands of WUs on a single host and then just abandoning them...
If there would be a way to weed those out, that would probably already help to level the issue at hand... :(

Don't call them all deadbeats. They may just be having trouble getting through to report the ones they've finished.