AP is back, time to get those RAC's back up.

---

Again we have 3 AP splitters working on another file together, 01jl11ad this time. :-(

Cheers.

Well this is somewhat interesting. I was expecting that the huge surge in backlogged APs getting validated all of the sudden, RACs would explode 5-50x... but it seems to have not done that at all. Rather, at least from what I can see, it has gone back to roughly normal before the DB crashed in the first place. My host average--after being a flat line for 33 days--is now only down about 13% from what it was flat-lined at.

Just not the result I was expecting. I would guess third-party calculations will show a huge spike, but the project doesn't seem to be doing the same.

*shrug* Science is getting done though, and the credits don't matter in the grand scheme of things.

---

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

I had over 600 validated Astropulse tasks and I would have expected my credit to be up by at least 200K. However, it didn't even come close to that. It looks like the total credit has not (yet ?) been incremented by the sum of the credit for the validated tasks. Has anyone else noticed something similar ?

Tom

---

Oops, maybe it was not that bad. I forgot that there were a lot of tasks that had already been validated, but not yet been purged. However, I still think the increase in credit should have been a little higher.

Tom

I had over 600 validated Astropulse tasks and I would have expected my credit to be up by at least 200K. However, it didn't even come close to that. It looks like the total credit has not (yet ?) been incremented by the sum of the credit for the validated tasks. Has anyone else noticed something similar ?

Tom

---

God Bless CreditNew:

9 Dec 2014, 5:06:05 UTC Completed and validated 5.34 1.05 490.39 AstroPulse v7 Anonymous platform (NVIDIA GPU)

---

Woohoo!! My RAC is climbing again! Just a quick question, will everything be alright with Bruno?

---

rOZZ
Music
Pictures

I think my RAC got a swallow or two of "Red Bull". It is starting to fly up.

---

Eric in news: Validators and assimilators and splitters are back on. New Astropulse work should be flowing soon.

How will it go...

Nom, nom, nom, feeding frenzy.

That is how it will go.... :-)

There's not much feeding frenzy going on, it's not easy getting APs and it's not because the demand is high. Looking at the cricket, the load isn't much higher compared with when there's was only MBs to download.

Yeah, it's like 1 AP for every 30-40 MB coming out. Don't quote me on that number but looking at 300 download and only 17 were aps that is how it feels. Maybe it's just slow to get going?

Woohoo!! My RAC is climbing again! Just a quick question, will everything be alright with Bruno?

Bruno has been or is going to be replace with a spare machine they acquired.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

@all,
well the gremlins are back:-(

09/12/2014 23:15:54 | SETI@home | Sending scheduler request: Requested by user.
09/12/2014 23:15:54 | SETI@home | Reporting 2 completed tasks
09/12/2014 23:15:54 | SETI@home | Requesting new tasks for NVIDIA GPU
09/12/2014 23:16:16 | SETI@home | Scheduler request failed: Couldn't connect to server
09/12/2014 23:16:30 | | Project communication failed: attempting access to reference site
09/12/2014 23:16:31 | | Internet access OK - project servers may be temporarily down.
09/12/2014 23:17:45 | SETI@home | Computation for task 10oc14aa.15931.3748.438086664200.12.58_2 finished
09/12/2014 23:17:45 | SETI@home | Starting task 20no14aa.15664.20926.438086664199.12.103_0
09/12/2014 23:17:48 | SETI@home | Started upload of 10oc14aa.15931.3748.438086664200.12.58_2_0
09/12/2014 23:17:52 | SETI@home | Finished upload of 10oc14aa.15931.3748.438086664200.12.58_2_0

1st no tasks available, stats 5 hrs behind due to maint, now when apparently tasks ARE to hand, the bleeding server aint..
Bah humbug..
Regards,

---

Cliff,
Been there, Done that, Still no damm T shirt!

Back with a vengeance - dead for the last 6 hours, I make it.

---

Yes, there certainly are several different error messages being throw back at me here. :-(

Cheers.

If you try looking at your task list, you will find it takes a while to pull up. In addition, the creation rate is far to low for even normal operation. It looks like something is locking the data base and the software needs a good kick to clear it.

---

[snip]
1st no tasks available, stats 5 hrs behind due to maint, now when apparently tasks ARE to hand, the bleeding server aint..
Bah humbug..

I was seeing the same thing, then I remembered something that improved the odds back in the days before the co-lo:

2014-12-09 18:27:28 SETI@home Reporting 5 completed tasks, requesting new tasks
2014-12-09 18:27:50 SETI@home Scheduler request failed: Couldn't connect to server
2014-12-09 18:35:50 SETI@home Reporting 5 completed tasks, requesting new tasks
2014-12-09 18:36:12 SETI@home Scheduler request failed: Couldn't connect to server
2014-12-09 18:54:42 SETI@home Reporting 5 completed tasks, requesting new tasks
2014-12-09 18:55:19 SETI@home Scheduler request failed: Failure when receiving data from the peer
2014-12-09 19:09:34 SETI@home Reporting 5 completed tasks, not requesting new tasks
2014-12-09 19:09:59 SETI@home Scheduler request completed
2014-12-09 19:15:04 SETI@home Requesting new tasks
2014-12-09 19:15:11 SETI@home Scheduler request completed: got 0 new tasks

So I got my tasks reported by going No New Tasks. After waiting 303 seconds, the scheduler responded normally.

edit: of course, 45 minutes is the span from start to finish on the above log snippets, and a lot can change in 45 minutes server-side. So maybe what I did.. didn't even matter. *shrug*

---

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

[snip]
1st no tasks available, stats 5 hrs behind due to maint, now when apparently tasks ARE to hand, the bleeding server aint..
Bah humbug..

I was seeing the same thing, then I remembered something that improved the odds back in the days before the co-lo:

2014-12-09 18:27:28 SETI@home Reporting 5 completed tasks, requesting new tasks
2014-12-09 18:27:50 SETI@home Scheduler request failed: Couldn't connect to server
2014-12-09 18:35:50 SETI@home Reporting 5 completed tasks, requesting new tasks
2014-12-09 18:36:12 SETI@home Scheduler request failed: Couldn't connect to server
2014-12-09 18:54:42 SETI@home Reporting 5 completed tasks, requesting new tasks
2014-12-09 18:55:19 SETI@home Scheduler request failed: Failure when receiving data from the peer
2014-12-09 19:09:34 SETI@home Reporting 5 completed tasks, not requesting new tasks
2014-12-09 19:09:59 SETI@home Scheduler request completed
2014-12-09 19:15:04 SETI@home Requesting new tasks
2014-12-09 19:15:11 SETI@home Scheduler request completed: got 0 new tasks

So I got my tasks reported by going No New Tasks. After waiting 303 seconds, the scheduler responded normally.

edit: of course, 45 minutes is the span from start to finish on the above log snippets, and a lot can change in 45 minutes server-side. So maybe what I did.. didn't even matter. *shrug*

I got my tasks reported 1st up, but now (even using that trick) just results in timeouts. :-(

Cheers.

Still haven't gotten handed any new tasks after 4 more requests, but all the requests are completing properly. Looking at the cricket, it sure doesn't seem things are back up and running smoothly after the maintenance this time around.

Probably some DB query that is taking unusually long to run (purging many many many completed AP WUs, perhaps?).

I did see just after the data driven webpages came back up that for MB, "received in last hour" was nearly 200k.

---

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

It's dead Jim, it's dead...

So it would seem, at least the SSP seems frozen, and trying to look at tasks takes you out into space.

Later, Jim ... (lol)

It's dead Jim, it's dead...

So it would seem, at least the SSP seems frozen, and trying to look at tasks takes you out into space.

Later, Jim ... (lol)

It might be back.

After several hours of

Scheduler request failed: HTTP internal server error

I am now seeing

Message from server: Project has no tasks available

Well, at least it is a start :)


Edit: Wishful thinking I guess. After three AP downloads it is back to

Scheduler request failed: HTTP internal server error

Another case of never call a no hitter