I'll just go do some crunching on other stuff :-) Can't really complain, in almost 21 years this has been the first really extended outage i've had.

---

I just restarted using SETI again after many years, and the program is new to me. I downloaded it on my laptops, and tasks started running, but the tasks finished, and the program now says no work available to process.
I thought this would automatically upload the old work that had finished, and receive new work.
Do I need to do something, I am not sure what to do now?

We're having an unusually long server maintenance (always starts on Tuesdays). Give it another day or two and you should get some work.

---

I haven't been able to report my completed work from yesterday, even with NNT set and report limit reduced to 20. either hits a timeout or HTTP internal error

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I haven't been able to report my completed work from yesterday, even with NNT set and report limit reduced to 20. either hits a timeout or HTTP internal error

I just had one go through with NNT and then the next failed, so hit or miss.

---

I hope it come back up soon, the servers. I heat my garage with my GPU's, and it is cold in here now. Need work now

I was able to report most of my work (250) all at once just not getting anything in return

Since 2 days or my Boinc client says there is no work to process or something. So today I looked at the Projects tab in the Advanced view and there is one line with a SETI@home Project with 100 (100.00%) in the Resource share field. The Status is empty. When I click on the Update button this field is filled with something like 'Scheduler request pending, request by user', and changes for example to 'Communication deferred 00:04:46'. This keeps counting down and repeats.
I wanted to click on the Remove button, but I read something like Task will be lost, first try to update.

So should I wait a few days or delete this work anyway?

---

I can now get some requests through without NNT. Most fail but some work. But can't actually get any tasks. Whenever it doesn't fail it says the server has no tasks.

---

A short message is NOT unreasonable.

I always have problems with short messages, because in 'one or two sentences' one can impossibly answer all that's happening there. I'd rather they do whatever needs to be fixed, work on it, test it, run it, and then when all the dust is settled and sweat wiped off can Eric sit down and write us a bit of news about it. If it's warranted.

Because the biggest trouble with a short notice is the hundred people answering to it and asking their own questions, which they require need to be answered or there's more complaining about how the project isn't communicating with the people volunteering their hardware.

As for devoting time and money towards this project, no one is demanding you do that, you volunteered. Just as you can demand an update, and they can volunteer to give one to you, or not. At the end of the day it doesn't matter. You're all riled up over things that you can do absolutely nothing about to get fixed. So why bother being angry? Relax, breathe, be as zen as your Ryzen is.

---

I've finally cleared all of mine. They started very slowly, with more misses than hits, but they were going appreciably faster towards the end. I'll leave the hosts on NNT until at least tomorrow (they've all got work from other projects now), to give the servers a chance to digest what they've just been fed.

As for devoting time and money towards this project, no one is demanding you do that, you volunteered.

And as a loyal volunteer, I and the others deserve an update. I profoundly disagree that it is too much to ask for. For all the time and money we put in? Uh nope.

So we'll just have to agree to disagree.

---

I'm putting myself to the fullest possible use, which is all, I think, that any conscious entity can ever hope to do.

I also agree that a simple one-liner would only take a minute for an admin. to type and doesn't even have to explain the issue, just acknowledge that there is one. ie "We're currently having a work distribution issue and are working to identify and resolve it, so in the interim, our weekly outage may be much longer than normal and it may be advisable to obtain work from a backup project."

One minute from a project admin. saves thousands from us fumbling around and checking the threads over and over...

---

I'll just go do some crunching on other stuff :-) Can't really complain, in almost 21 years this has been the first really extended outage i've had.

Kind of disheartening for me, because as a newbie I went out with excitement to recommend the SETI stuff to my group of friends to get them involved, only to have it go down. Most of them sent me emails saying things like, "sorry, not worth my time if it cannot stay up" or, "It's broken, not gonna waste my time." I'll give it another day, but after that, I'll move on.

I understand the feeling. SETI@Home has been running for 20+ years and this is an atypically long weekly maintenance. Hang in there. I hope they'll be back online by end of day, but recovery could take another day as all those hungry PCs try to get data.

---

I am hoping that they revert the cache levels to the original levels. I am thinking that this was maybe an experiment to find the limits of the servers and to identify the weak spots that need revamping with newer, more powerful hardware. Maybe was a stress test to see what would be needed to add the Parkes data or something.

Whatever the reason, I would hope they realize the servers can't cope with this level of work in progress. Before the cache level revision, the servers were fairly well behaved and the outages had leveled out at the 3-4 hour period. I can accept that. They need to get back to that.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

"Communication deferred 00:49:05"
Let's hope the SETI team can get everything up and running soon! :)

. . That's nothing, mine went into backoff for something ridiculous like 5 hours, bl*&^dy ludicrous ...

Stephen

:(

I noticed I had 40-something pending uploads. Told one to retry and all went through on first try.

Scheduler request happened and it took about 30 seconds to respond, but it responded and acknowledged all of them.

Didn't get any new tasks though.

So comms are working, at least.

edit: posting this took 3 minutes, and then clicking edit to add this line also took about 3 minutes. Presuming saving the changes will also take about the same.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Well, one can basically say that the project is still down. Not much happening with uploads, reporting, or new work.
This will take a very long time to recover from.
But I hope we are all having fun while waiting :-)

. . I'll steal your position ... NO!!

Stephen

:-{

I am hoping that they revert the cache levels to the original levels. I am thinking that this was maybe an experiment to find the limits of the servers and to identify the weak spots that need revamping with newer, more powerful hardware. Maybe was a stress test to see what would be needed to add the Parkes data or something.

Whatever the reason, I would hope they realize the servers can't cope with this level of work in progress. Before the cache level revision, the servers were fairly well behaved and the outages had leveled out at the 3-4 hour period. I can accept that. They need to get back to that.

I think I'd go along with 'experimental', though maybe more so than they expected.

Eric Korpela wrote:

I based it on database I/O rates
which, it seemed could handle the change. Long term the rates don't change
but the DB "in process" lookups take longer. If it becomes an issue I'll
drop them.

Even discounting the server upgrade in the middle, I think we've proved that database lookups do take longer. Ergo ...

Server status page has not updated for 6 hours + most servers are gone in the listing, not good.

I just restarted using SETI again after many years, and the program is new to me. I downloaded it on my laptops, and tasks started running, but the tasks finished, and the program now says no work available to process.
I thought this would automatically upload the old work that had finished, and receive new work.
Do I need to do something, I am not sure what to do now?

. . Your timing sucks, we are in the middle of probably the longest outage I can recall. I have only been with the project since 2012 but this is only the second outage I remember that has gone over 24 hours and this one over 30 hours :(

Stephen

:(