SETI@home scheduler is down until further notice.

I too am a C.T.O. to a bank here in toronto. Knowing what I know about seti, instead of complaining I made a $500 donation just in case they need some new hardware. I always thought europeans were more compassionate. You guys are doing a great job and hope this helps out.

Let's all understand something here.
We all may think that we know how to run the project better - want them to open up all the source code and details so that we can "fix" them.
But - there is the rub. For every great programmer - there are MANY wanna be programmers that will give their suggestions.

Simple suggestion - a new PRIVATE thread to the admins - if you want to volunteer your services - state your credentials - and KNOW that you will not have ANY say (and that is how it SHOULD be).

For myself - willing to help how I may. 20 years AF experience as a tech controller - and now a geek. Not an expert - but I think outside the box (a lot of the time because I don't know any better).

For this project - the scheduler has been the issue - bandwidth - who cares - so - you get your downloads slow - but you GET them if the scheduler isn't crammed.

Solutions are many. Bigger work units. Larger queues again with a SET mandatory cool down (half queue until the workstation can try to contact the server). I also see some systems out there with literally thousands of WU each - and tons of errors because of timeouts - what's up with that????

Seem to be getting WU pretty good right now - but systems are set crazy - WHY - when I have 2 completed workunits out of 200 - am I contacting the server for more work??????? AGAIN - PLEASE - set - if possible - a MANDATORY COOL DOWN - half queue - and OPEN THE QUEUE. Let me have 5 days of work - and - you won't hear a PEEP for 2 and a half days. That should ease the congestion on the scheduler. Once again - slow downloads - don't matter.

Finally - wondering...why..I download faster and more reliably STILL from a proxy server. Baffling. You use a Linux architecture - Linux boxes, Apple boxes haven't had much trouble. Proxy servers are likely running Apache (again...same TCP/IP stack). What's with windoooooows? ECN? Congestion notification has seemed to make some difference here - maybe about as reliable as my proxy - may be something to look into.

Ya'll do what you do - and I respect you for it. However - please - it is REALLY nonsensical for my systems to be requesting workunits when they are essentially 99 or 98 percent FULL. Again - a mandatory cooldown would work wonders - bandwidth be damned.
____________

While I love SETI, I don't mind downtime, as it just give World Community Grid more CPU cycles! I appreciate all that the SETI folks have done, and wish I was in a place to continue $$ support, but do have an idea I can afford to give!

As an only occasional visitor here, please forgive me if this has been considered but rejected...

It seems that some cloud provider would have some spare CPU cycles / bandwidth they could parse out to SETI without impacting paying customers, but could still legitimately be a tax write-off. Since much a SETI processing does not have to be real-time, off-peak processing would be fine. The bandwidth needed, while a significant added load to a University network, could possibly go basically unnoticed on some cloud networks (think Berkeley vs Google or Amazon).

There may be some issues in virtualizing the systems (they are Sun servers, yes?) but it seems that there must be an option...?

Has this been considered? Not feasible? No cloud providers willing?
What would it take to make this happen?

To those of you having trouble you should come over to the Number crunching forum. You are more than welcome to start a thread and ask for help. Boinc options and settings can be a bit hectic, confusing or downright hidden. If you have found yourself without work units to crunch, chances are it could have been avoided. So come on over:)

To most of you posting in this thread, welcome to the boards!

And to those of you showing people the door, shame on you.

I will continue to wait for this downtime. Perhaps the scheduler server has just been up for too long. Maybe restarting would help. In all cases restarting can help a bit freeing up useless swap and main memory. The way I see it is that it hasn't been restarted in so long and huge amounts of RAM is being cluttered up. Just my suggestion. And will patiently wait

I will continue to wait for this downtime. Perhaps the scheduler server has just been up for too long. Maybe restarting would help. In all cases restarting can help a bit freeing up useless swap and main memory. The way I see it is that it hasn't been restarted in so long and huge amounts of RAM is being cluttered up. Just my suggestion. And will patiently wait

I'll have 8 task to go and then my seti guf is empty:(
Are there again problems??? What I don't understand is that
some users at Seti@Netherlands deliver more then 14000 task
work in 4 hours..then they get more then the 100 task a time
That is not honnestly against the other users if I may say.

Sorry just got 70 task;)