None of the problems mentioned here.. just getting NOTHING at all in the way of WUs from main project. Had none for a couple of weeks from the Beta project. However, now down to ONE main project WU and two for the Beta.

Not fussed or panicked, as I can always rev up Einstein to occupy my PC, but I feel this is a network prob and I should report it.

Good luck lads! :)

---

Hammering on the "Reset Project" button about a hundred times in the space of a half hour finally got a WU to download for me, and crunching underway.

Hell of a way to run a project.

Hitting retry or reset project only hammers the servers even harder causing others to get communication errors and makes the situation worse.

The best thing to do is simply let BOINC do its thing on its own. If it can't get work, try a backup project to crunch while your main is having problems.

---

Hammering on the "Reset Project" button about a hundred times in the space of a half hour finally got a WU to download for me, and crunching underway.

Hell of a way to run a project.

Hitting retry or reset project only hammers the servers even harder causing others to get communication errors and makes the situation worse.

The best thing to do is simply let BOINC do its thing on its own. If it can't get work, try a backup project to crunch while your main is having problems.

Precisely... I wonder if all the hammering that's going on is why I haven't been getting ANY downloads for the last 2 or 3 days? Not even a "stuck" transfer. If there are enough crunchers continually sending packets by thumping the "update" or "retry communications" button, maybe it's no wonder it takes a while for the system to recover?

---

Precisely... I wonder if all the hammering that's going on is why I haven't been getting ANY downloads for the last 2 or 3 days? Not even a "stuck" transfer. If there are enough crunchers continually sending packets by thumping the "update" or "retry communications" button, maybe it's no wonder it takes a while for the system to recover?

If you're not even getting any stuck transfers, then the particular problem on your machine is different from the major 'system connect' problem that affects us all equally.

Why not go over to Number Crunching and post (a carefully selected extract from) your message log in one of the threads about download problems - you'll find plenty to choose from.

Better to do the troubleshooting there, rather than in this area which is for Technical News from the project.

Your not the only one, I have 2 system on 24/7 just to crunch but over the last week they have not been able to get work ether! So elect, hard drives and everything that wears out when you leave it on is just setting there doing nothing... I wrote about this problem the other day, it seems like any time theirs a long week end we get no work from Site to crunch.. When they should have everything running at peak and giving everyone something to do we get ZIP, notha, nutin.. At first I thought it was me or my system so I formated the drives and reinstalled everything!! 3 days later and still no work from site!!

9/2/2007 9:02:52 AM||Resuming computation
9/2/2007 9:36:41 AM||Suspending computation - user is active
9/2/2007 9:36:57 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:36:57 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:02 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:02 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:02 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:22 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:22 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:27 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:27 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:27 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:42 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:42 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:47 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:47 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:47 AM|SETI@home|Reason: requested by project


is what it says....

Tim Olivera

---

Look at host 3751792 (created 31 Aug 2007 22:44:51 UTC) and host 3755243 (created 1 Sep 2007 16:56:58 UTC). Those are both genuinely brand new machines, delivered as kits of parts on Friday morning: no fiddling with host IDs, merging old accounts or anything like that. Every result you see under the host IDs has been downloaded, crunched and returned by those hosts since Friday night/Saturday afternoon respectively. I've got about 170 of them logged so far - no tricks, no funny business, no special priviledged access to Berkeley. I've just spent enough time watching the screen, and reading the thousands of helpful advice posts on the boards, to learn what works and what doesn't.

Rev, if you're not getting any work at all, then you're not doing it right. I suggest you stop, take a deep breath, and think. And if you're still stuck, ask for help at Number Crunching, not here.

Your not the only one, I have 2 system on 24/7 just to crunch but over the last week they have not been able to get work ether! So elect, hard drives and everything that wears out when you leave it on is just setting there doing nothing... I wrote about this problem the other day, it seems like any time theirs a long week end we get no work from Site to crunch.. When they should have everything running at peak and giving everyone something to do we get ZIP, notha, nutin.. At first I thought it was me or my system so I formated the drives and reinstalled everything!! 3 days later and still no work from site!!

9/2/2007 9:02:52 AM||Resuming computation
9/2/2007 9:36:41 AM||Suspending computation - user is active
9/2/2007 9:36:57 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:36:57 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:02 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:02 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:02 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:22 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:22 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:27 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:27 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:27 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:42 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:42 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:47 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:47 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:47 AM|SETI@home|Reason: requested by project


is what it says....

Tim Olivera

Yes, please post this in NC so it can be worked on. The fact that your rig is not requesting new work indicates some problem with your installation, if it isn't asking for work from the server, it won't get any.
Regards,
Mark.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I have had this same issue with SETI work not Downloading. IT seems to mostly affect my fastest machines. My Quad Core stays out of seti work as much as it stays in. My Dual core X2 and my Opteron Server both have the same issue. My older PIII and my Laptop seem to get plenty of work.

I run Another project to fill the gaps, I never have any problem getting work from then. The common problem seems to be with the Seti servers, not our machines.

The issue started about three to four weeks ago, and has not improved. I have changed the buffer and connect time with no results. IF I could get more work, I could average 1000 instead of staying in the 500 to 600 range.

PS: I will post in the number crunching area also. My systems are constantly asking for work that never comes or takes hours to finally download. It is a SETI Server issue, as I can get all the work I want fron other projects.

---

9/2/2007 9:02:52 AM||Resuming computation
9/2/2007 9:36:41 AM||Suspending computation - user is active
9/2/2007 9:36:57 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:36:57 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:02 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:02 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:02 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:22 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:22 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:27 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:27 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:27 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:42 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:42 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:47 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:47 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:47 AM|SETI@home|Reason: requested by project


is what it says....

Tim Olivera

Tim,

The problem is you have elected to not allow SETI to run while you are active. This means that you cannot get work either, even if you hit the "update" button. The only way to get work manually is to go to Activity -> Run always before you hit the Update button. You can go back to "Run based on preferences" once BOINC starts getting work.

Of course, with the server issues, it won't make a big difference right now. My suggestion is to leave it. When you are inactive on your computer, BOINC will automatically attempt to get more work. If it has problems downloading, they will usually download eventually once the servers start working right again.

---

Matt,

It occurred to me that the System Connect error we get on downloads might be the old / even server requesting you have created. If we are trying to download an even and the system sends us to the odd, we get the System Connect error.

This is a theory, but it's about as solid of a one that I can come up with at the moment. I observe the behavior more on the even units than the odd units. This is what leads me to believe this might be the issue.

I hope that this information might help in finding out how to fix this issue.

[rant on]
I just do not understand why people are so blatantly hostile towards the project when they should know that there is no guarantees with this project. The people are crunching on their spare CPU cycles, if those cycles aren't used, it's their fault for not wanting to help other projects. This project is here right now, it may stay for many years (hopefully), or if not enough funding, etc. come along it may shut down in the next few months. This is an experimental project, and the credits are worth nothing, the time spent may be worth something of knowledge in the future, but alas after 8 years no sign has been truly found yet, but we continue the search.

Life is too short to fret about your computer not able to download work for SETI. Go out, have some fun, leave your computer to do the work. This software is mostly about setting it and forgetting it. Let it do it's own thing.
[rant off]

Good luck in keeping the project going, Matt, Jeff, Eric, et al.

---

My movie https://vimeo.com/manage/videos/502242

Hi Matt, Eric, et. al,
Thank you all very much for all of the hard work and time that you are spending with the project! It is frustrating when we can not get more work to do, but it is not as though there are not other things to do. Sometimes we get so wrapped up in crunching the numbers that we forget our priorities. Heaven forbid that we should have to shut down this stroke of genius, it has been fun the last eight years or so. Hope the funding remains secure! All of your work is appreciated.
Don Paden

---

Precisely... edited

If you're not even getting any stuck transfers, then the particular problem on your machine is different from the major 'system connect' problem that affects us all equally.

Why not go over to Number Crunching and post (a carefully selected extract from) your message log in one of the threads about download problems - you'll find plenty to choose from.

Better to do the troubleshooting there, rather than in this area which is for Technical News from the project.

Hi Richard

Probably good advice, but I have been to sleep since posting, and woke this morning to find downloads successfully coming in from both SETI projects.

Looks like the old advice that we always give seems to have worked this time. :)

The advice? BE PATIENT!

Regards

lgm

---

I've noticed that starting about 10-12 August my user and host averages started going down with a low between August 20-24 for WUs. Since then I've tried all the workarounds mentioned and have succeeded in getting my machines to do more seti work. I have noticed the "backing off" between attempts to download WUs from minutes to hours and have had to use the retry now button to get work down loaded.

I have also noticed that WUs with a report deadline of 9/11/2007 have been very "small" requiring anywhere from 8 hours down to under two hours work to complete. This is on all machines P III 866, 1ghz and Pentium D 2.66. Now WUs are starting to show requiring more work from half day to almost 2 two days.

Could these "small" WUs been the issue with our machines being idle?

---

Has anyone else had there pending credit increase dramatically.

Mine used to hover around 1800 to 2100. I am now at 7200 pending credits. It never has been so high a value.

Kenn

---

Kenn

What is left unsaid is neither heard, nor heeded.
Ce qui est laissé inexprimé ni n'est entendu, ni est observé.

[rant on]
I just do not understand why people are so blatantly hostile towards the project when they should know that there is no guarantees with this project. The people are crunching on their spare CPU cycles, if those cycles aren't used, it's their fault for not wanting to help other projects. This project is here right now, it may stay for many years (hopefully), or if not enough funding, etc. come along it may shut down in the next few months. This is an experimental project, and the credits are worth nothing, the time spent may be worth something of knowledge in the future, but alas after 8 years no sign has been truly found yet, but we continue the search.

Life is too short to fret about your computer not able to download work for SETI. Go out, have some fun, leave your computer to do the work. This software is mostly about setting it and forgetting it. Let it do it's own thing.
[rant off]

Good luck in keeping the project going, Matt, Jeff, Eric, et al.

Hear, hear!

---

Has anyone else had there pending credit increase dramatically.

Mine used to hover around 1800 to 2100. I am now at 7200 pending credits. It never has been so high a value.

Kenn

There is a new app. for MAC from ALEX.

Check it out in NC forum.

---

Has anyone else had there pending credit increase dramatically.

Mine used to hover around 1800 to 2100. I am now at 7200 pending credits. It never has been so high a value.

Kenn

The reason this is, is because now only 2 people get the results of a WU to work on. Before it was 3, so results came in faster. Now instead of waiting for 1 our of you, you wait for 1, then if that 1 doesn't do it, then you wait for another 1, etc.

Nothing wrong. It's just the nature of how it works. You will eventually get credit, when someone finally finishes a second one to match you.

---

My movie https://vimeo.com/manage/videos/502242

Has anyone else had there pending credit increase dramatically.

Mine used to hover around 1800 to 2100. I am now at 7200 pending credits. It never has been so high a value.

Kenn

The reason this is, is because now only 2 people get the results of a WU to work on. Before it was 3, so results came in faster. Now instead of waiting for 1 our of you, you wait for 1, then if that 1 doesn't do it, then you wait for another 1, etc.

Nothing wrong. It's just the nature of how it works. You will eventually get credit, when someone finally finishes a second one to match you.

1 of his computers is using the old MAC app that has a problem with "weakly similar" results. So a third wu is issued and pending credit going through the roof.
Anders n

---

Hammering on the "Reset Project" button about a hundred times in the space of a half hour finally got a WU to download for me, and crunching underway.

Hell of a way to run a project.

... at a cost to everyone else who simply waited patiently.

Handles on the server are a limited asset. When you hammer the buttons, you get more than your fair share of handles -- to the exclusion of others.

---

Your not the only one, I have 2 system on 24/7 just to crunch but over the last week they have not been able to get work ether! So elect, hard drives and everything that wears out when you leave it on is just setting there doing nothing... I wrote about this problem the other day, it seems like any time theirs a long week end we get no work from Site to crunch.. When they should have everything running at peak and giving everyone something to do we get ZIP, notha, nutin.. At first I thought it was me or my system so I formated the drives and reinstalled everything!! 3 days later and still no work from site!!

9/2/2007 9:02:52 AM||Resuming computation
9/2/2007 9:36:41 AM||Suspending computation - user is active
9/2/2007 9:36:57 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:36:57 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:02 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:02 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:02 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:22 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:22 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:27 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:27 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:27 AM|SETI@home|Reason: requested by project
9/2/2007 9:37:42 AM|SETI@home|Sending scheduler request: Requested by user
9/2/2007 9:37:42 AM|SETI@home|(not requesting new work or reporting completed tasks)
9/2/2007 9:37:47 AM|SETI@home|Scheduler RPC succeeded [server version 511]
9/2/2007 9:37:47 AM|SETI@home|Deferring communication for 11 sec
9/2/2007 9:37:47 AM|SETI@home|Reason: requested by project


is what it says....

Tim Olivera

Reading must be becoming a lost art.

It says: (not requesting new work or reporting completed tasks)

This means that the client isn't asking for new work.

It may be because you've done enough SETI for a while (more than your resource share demands) so it's time to let others catch up.

It may be because you have some work units with tight deadlines, and those need to be finished before more work is download (which may also have tight deadlines).

It could be the "don't crunch while active" rule that has been mentioned elsewhere.

It isn't an issue, it is correct behaviour.

---