Crap, even AP validation have stopped now. All AP's goes to pending, even those finished by wingman too.

Edit: My panic button doesn't work either, the battery is flat, and I don't have a spare battery.

Oiiiiiiii !!!!

Yup, with the AP database down, no assimilation or credits....
But a nice boost when it comes back up.

Even with the DB down (or at least marked as disabled) we did get validation and credit, until the validators also went down a short while ago. My last validated AP was not long ago at all.

Although, I'm not so sure that we can trust what we see on the SSP.

+1

---

rOZZ
Music
Pictures

Guess it's a good thing I got a full 10-day cache before AP got disabled.

I shall cherish every single one of them.

---

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

New tapes loaded, for MB as well as AP, but still no signs of life from AP. DB still down, validators still down, assimilators and splitters still down.

Oiiiiiiii !!!!

[back to fetal position]

It would be nice if someone could at least revive the AP validator so all these Pending APs could receive credit.
Even better would be the Database and splitters...

New tapes loaded, for MB as well as AP, but still no signs of life from AP. DB still down, validators still down, assimilators and splitters still down.

Oiiiiiiii !!!!

[back to fetal position]

It would be nice if someone could at least revive the AP validator so all these Pending APs could receive credit.
Even better would be the Database and splitters...

Doesn't seem to happen (Friday would have been the day though, I don't expect them to work today)

This leads me to believe that the AP DB never really got fixed. It's still something wrong with it. 4 Nov 2014, 23:30:05 UTC] was the exact date and time, when the AP DB first went to the place of fire and brimstone, and by the looks of things, it's still not out of there.

Something tells me there is something scheduled to run at that time. Which can on occasion cause the AP db server to barf all over itself.

---

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

I'm more concerned about the AP validator still being down. As noted earlier, the Vaildator doesn't require any other component to Validate tasks, it doesn't need the DB or anything else to work. I'm now up to around Half a Million in Uncredited AP credits. They are just sitting there, waiting to be lost. Granted tasks are usually Not lost, however, considering recent events I'm growing Nervous.
Very Nervous...

I'm more concerned about the AP validator still being down. As noted earlier, the Vaildator doesn't require any other component to Validate tasks, it doesn't need the DB or anything else to work. I'm now up to around Half a Million in Uncredited AP credits. They are just sitting there, waiting to be lost. Granted tasks are usually Not lost, however, considering recent events I'm growing Nervous.
Very Nervous...

LOL...
I am NOT nervous.
I don't believe I have ever lost a credit for work done here on Seti ever.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I'm more concerned about the AP validator still being down. As noted earlier, the Vaildator doesn't require any other component to Validate tasks, it doesn't need the DB or anything else to work. I'm now up to around Half a Million in Uncredited AP credits. They are just sitting there, waiting to be lost. Granted tasks are usually Not lost, however, considering recent events I'm growing Nervous.
Very Nervous...

LOL...
I am NOT nervous.
I don't believe I have ever lost a credit for work done here on Seti ever.

Actually you have lost credit, and continue to lose credit. You just don't know it. Back when a few of Us discovered this Error, Strange Invalid MB Overflow tasks with truncated Stderr outputs..., I pointed out to you a number of cases where You were affected. You didn't understand the problem and after an attempt to explain it I gave up. The problem is Still there, and I'd expect you to still be effected, as everyone else.

That was a small problem though. What has been going on for the last 3 months is a little larger. Earlier in this thread you will see where at least 2 people had lost tasks that directly affected me. There were probably others that I'm not aware of because they didn't affect me. So, has anyone here experienced anything similar to the last 3 months? Wherein a Database has been repeatedly taken down and rebuilt? I recall a post about one back in 2012, but apparently it was a minor case. Considering the last 3 months, I'd say we are in uncharted territory.

LOL...OK.
In Setiland, we are always looking at uncharted territory.
And I accept that as the lay of the land, so to speak.

If some of the work I have done has gone off into the ether mist, so be it.
I don't think that my efforts have gone to waste very much.

I do get concerned about a major database breach or failure, don't get me wrong on that issue.
I would hate to think that YEARS of work would be lost.
Not a single WU, give or take.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

When, one day...and I state 'when', not 'if'...
We find proof that life other than ours does exist....
You can then argue with me whether the problems along the path have been worth the trouble.

I state that without any possible denial of this project's validity.
It may or may not be the best possible approach to find what we are looking for.
There are other methods, many of which are also being explored as we speak.

This happens to be the search I can help with the most.
And have done so for almost 15 years without a doubt in my mind that I am contributing to the most advanced search of the heavens possible by mankind.

I have no doubts about it whatsoever.

If I did, I could hit 9 switches and shut down many killawatts of processing immediately.

Not gonna happen, because I am committed (or should be...LOL) to this project as long as I breath or as long as it runs.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I find it amazing at how many people don't support the Seti project as a whole and are only concerned about how many credits they receive for towards their time.

Lets face it, the project is designed for science, not for showing how many credits you can get!

With AP being down their are about 2500 WU/hr not getting crunched. Which translated to MB workunits should be about 57,000 WU/hour. And yet looking at the MB graphs there is little to NO change in the amount of work being done on that project.

Come on guys, are you really so concerned about your credits that you would rather change to a different project than to support this one, as a whole?

I'm sure the MB guys would be more than happy to help with AP work if the tables were turned.

---

I find it amazing at how many people don't support the Seti project as a whole and are only concerned about how many credits they receive for towards their time.

Lets face it, the project is designed for science, not for showing how many credits you can get!

With AP being down their are about 2500 WU/hr not getting crunched. Which translated to MB workunits should be about 57,000 WU/hour. And yet looking at the MB graphs there is little to NO change in the amount of work being done on that project.

Come on guys, are you really so concerned about your credits that you would rather change to a different project than to support this one, as a whole?

I'm sure the MB guys would be more than happy to help with AP work if the tables were turned.

The kitties just are happy when the kibble bowls are full.
It is not required that they be one manner of task or the other.
The project simply Blinds me with science.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I find it amazing at how many people don't support the Seti project as a whole and are only concerned about how many credits they receive for towards their time.

Lets face it, the project is designed for science, not for showing how many credits you can get!

With AP being down their are about 2500 WU/hr not getting crunched. Which translated to MB workunits should be about 57,000 WU/hour. And yet looking at the MB graphs there is little to NO change in the amount of work being done on that project.

Come on guys, are you really so concerned about your credits that you would rather change to a different project than to support this one, as a whole?

I'm sure the MB guys would be more than happy to help with AP work if the tables were turned.

Maybe a look at the Applications list may help explain it for you;
http://setiathome.berkeley.edu/apps.php
Look at the SETI@home v7 section and see if you can find a Mac OSX GPU App.
Now look down at the AstroPulse v7 section, down near the bottom. Look at the 7.04 (opencl_ati_mac) entry.
OMG, it's much higher than the other AstroPulse v7 entries. Seems there are quite a few Macs that can run GPU APs but not GPU MBs. That means when the APs run out those Macs will Not be running GPU MBs. Does that help?

Also, a number of people are aware that the current SETI@home v7 work has already been analyzed at least once, usually 2 or 3 times. The chances of finding anything new the 3rd time around is rather slim. Add to that, a lot of people with mid-range or lower ATI cards experience Screen lag when running SETI@home v7 tasks and have decided to avoid them. My ATI cards experience screen lag with MBs lower than around 0.2 Angle Range making the computer annoying to use. That number '57,000' is interesting, how did you come up with it? For the Mid-range and lower ATI cards there isn't that much runtime difference between non-shortie MBs and APs, maybe 2 or 3 times?

Anyway, one would question who's more concerned with their credit, the person that decides not to run the same task for the 3rd time, or the one that decides to run the same tasks over and over when the only apparent outcome is to generate credit.
Whatever.

IF you have been paying attention......
We are aware of the fact that we are 'reprocessing' WUs that have been done before.

It has been discussed more than once here.

Given the miniscule chance of a signal we are looking for, the chances of finding it on a second or third pass is about the same. So there is ample reason and justification for doing so.
If new work was available, of course it would make more sense to run that through the first pass attempt.

You are not shocking anybody with some new revelation here, Tbar...

Quit whining.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

IF you have been paying attention......
We are aware of the fact that we are 'reprocessing' WUs that have been done before.

It has been discussed more than once here.

Given the miniscule chance of a signal we are looking for, the chances of finding it on a second or third pass is about the same. So there is ample reason and justification for doing so.
If new work was available, of course it would make more sense to run that through the first pass attempt.

You are not shocking anybody with some new revelation here, Tbar...

Quit whining.

I'm just pointing out Facts. The person I responded to appeared to be Whining.
Just because a few of us are aware the MBs are being rehashed doesn't mean the person I responded to does. In fact, I'd say most people running MBs are not aware of the rehashing. Just as there appears to be a large number of people, including Yourself, that doesn't understand there is a whole OS platform out there that can only run GPU APs.
Just pointing out the Facts.

IF you have been paying attention......
We are aware of the fact that we are 'reprocessing' WUs that have been done before.

It has been discussed more than once here.

Given the miniscule chance of a signal we are looking for, the chances of finding it on a second or third pass is about the same. So there is ample reason and justification for doing so.
If new work was available, of course it would make more sense to run that through the first pass attempt.

You are not shocking anybody with some new revelation here, Tbar...

Quit whining.

I'm just pointing out Facts. The person I responded to appeared to be Whining.
Just because a few of us are aware the MBs are being rehashed doesn't mean the person I responded to does. In fact, I'd say most people running MBs are not aware of the rehashing. Just as there appears to be a large number of people, including Yourself, that doesn't understand there is a whole OS platform out there that can only run GPU APs.
Just pointing out the Facts.

Most Seti users are not aware of anything at all concerning the day to day operations or lack therof with the project, Tbaby.
It is a fraction of a percent of us who even monitor such things.
OR bother to post here on the boards about it.
I am not bashing you...just saying that rehashing what is already well documented is called beating a dead horse.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Most Seti users are not aware of anything at all concerning the day to day operations or lack therof with the project, Tbaby.
It is a fraction of a percent of us who even monitor such things.
OR bother to post here on the boards about it.
I am not bashing you...just saying that rehashing what is already well documented is called beating a dead horse.

As it has been stated by the SETI@home staff. Creating "busy work" would be scientifically irresponsible. So if they have a reason to resplit a data set 50 times I don't see any issue. I'll process whatever they throw at me.

---

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

Most Seti users are not aware of anything at all concerning the day to day operations or lack therof with the project, Tbaby.
It is a fraction of a percent of us who even monitor such things.
OR bother to post here on the boards about it.
I am not bashing you...just saying that rehashing what is already well documented is called beating a dead horse.

As it has been stated by the SETI@home staff. Creating "busy work" would be scientifically irresponsible. So if they have a reason to resplit a data set 50 times I don't see any issue. I'll process whatever they throw at me.

Same here, buddy. Same here.
I trust Eric implicitly.
We have discussed this. He has assured me that nothing going out of the Seti servers has any invalid reasons for being sent.
I believe he would let the whole 9 yards idle rather than be accused of sending out busy work.

Just ain't gonna happen on HIS watch, I can assure you. If tasks are coming out of Seti, they have a valid reason to be crunched.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Most Seti users are not aware of anything at all concerning the day to day operations or lack therof with the project, Tbaby.
...just saying that rehashing what is already well documented is called beating a dead horse.

Hmmmm, first you say....then you contradict it.
Whatever.

My response contained much more than what you seem to be attempting beat to death.
Whatever.

Most Seti users are not aware of anything at all concerning the day to day operations or lack therof with the project, Tbaby.
...just saying that rehashing what is already well documented is called beating a dead horse.

Hmmmm, first you say....then you contradict it.
Whatever.

My response contained much more than what you seem to be attempting beat to death.
Whatever.

I contradicted myself? NOT.
I was simply discussing current project status with another concerned Setizen.
And don't think I was too wordy to that effect.

If you have anything of significance to add here, please do so.
But, I believe all the bases have been covered.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I find it amazing at how many people don't support the Seti project as a whole and are only concerned about how many credits they receive for towards their time.

Lets face it, the project is designed for science, not for showing how many credits you can get!

With AP being down their are about 2500 WU/hr not getting crunched. Which translated to MB workunits should be about 57,000 WU/hour. And yet looking at the MB graphs there is little to NO change in the amount of work being done on that project.

Come on guys, are you really so concerned about your credits that you would rather change to a different project than to support this one, as a whole?

I'm sure the MB guys would be more than happy to help with AP work if the tables were turned.

When the server side parts go offline crunching does not stop on all the hosts. There is just a delay in validating the completed work as it is turned in. MY fastest machines that do AP only are still running down there cache of AP before they switch over to MB. However my MB only machines do not switch over to AP when there is no MB work to do.

---

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