I did have over 180 of them 19ap11ad's here, though they are starting to disappear from my list now (down to 160 currently).

Cheers.

I've just done that...
All 124 of my invalid results belong to the 19ap11 group
I've a total of 84 inconclusive results:
of which 24 are from the 19ap11ad
The remaining 60 are from a number of dates, but none have the "Legacy setiathome_enhanced V6 mode." line in their stderr output.

The other inconclusives come from:
01ja13ac (2)
01jl12ad (2)
01jl12ad (1)
02fe13ad (1)
03ja12ad (1)
03se12ad (1)
04fe13ab (3)
04jl12ac (3)
05au12ab (1)
05jl12aa (2)
06no10ac (2)
12no12ac (2)
13au10ab (1)
15dc12ac (2)
16jl12aa (1)
17dc12ad (1)
17oc14aa (1)
19oc14ad (1)
20no14aa (1)
21mr11ag (3)
23jn12ac (1)
25au12ae (1)
25jn12ac (1)
26fe12ad (1)
26ja13ac (3)
26jl12aa (7)
28dc12ac (5)
28fe13ab (3)
28fe13ac (6)
29ja13aa (1)
29my12ad (1)
30oc12ab (1)

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Just completed a couple of _9s- WUs.....'completed, can't validate' and under the errors indent, 'too many results'. Wow, what a surprise.

---

Don't take life too seriously, as you'll never come out of it alive!

http://setiathome.berkeley.edu/result.php?resultid=3913709373
http://setiathome.berkeley.edu/result.php?resultid=3913110250
http://setiathome.berkeley.edu/result.php?resultid=3913031937
http://setiathome.berkeley.edu/result.php?resultid=3912962635
http://setiathome.berkeley.edu/result.php?resultid=3912863532

---

http://setiathome.berkeley.edu/result.php?resultid=3913709373
http://setiathome.berkeley.edu/result.php?resultid=3913110250
http://setiathome.berkeley.edu/result.php?resultid=3913031937
http://setiathome.berkeley.edu/result.php?resultid=3912962635
http://setiathome.berkeley.edu/result.php?resultid=3912863532

Nothing to do with this thread - those are all perfectly normal workunits, which have validated for two users, but which host 7431929 has failed to complete satisfactorily. If that's your computer (it shows as 'anonymous'), it needs some TLC - a reboot would be a good start, and then check the usual suspects of dust, temperature, power and so on.

Has anyone been able to contact any SETI staff to look into this?

Has anyone been able to contact any SETI staff to look into this?

yep. The answer was "Jeff is on the case".
In my understanding it means no new such work will be splitted.

Has anyone been able to contact any SETI staff to look into this?

yep. The answer was "Jeff is on the case".
In my understanding it means no new such work will be splitted.

Thanks for letting us know Raistmer.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

So....WTH is this?
01jl12ad.5031.1294.140733193388035.12.95
Legacy setiathome_enhanced V6 mode....

Now we have a New batch of these....things?
I just trashed over a dozen of the 19ap11ad tasks and now this.

So....WTH is this?
01jl12ad.5031.1294.140733193388035.12.95
Legacy setiathome_enhanced V6 mode....

Now we have a New batch of these....things?
I just trashed over a dozen of the 19ap11ad tasks and now this.

Oh, oh. That does look like trouble. It doesn't appear that I've gotten any from that "01jl12ad.5031" channel, but I have successfully processed at least 60 tasks from that same tape, with a different 2nd node in the name. Such as "01jl12ad.16672", "01jl12ad.11174", "01jl12ad.11188", "01jl12ad.15978", and "01jl12ad.21345". It looks like I got all of those more than a day ago, whereas yours looks pretty fresh. Maybe that's why the splitters are stopped.

EDIT: "01jl12ad.23349" and "01jl12ad.24502" look to be OK, too. Those ran on my daily driver.

Hmmmm, now it appears the Splitters have sputtered back to life. I just received a few New APs.
Maybe there is hope.

Hmmmm, now it appears the Splitters have sputtered back to life. I just received a few New APs.
Maybe there is hope.

Well, I got 4 MBs for the CPUs about 20 minutes ago, but nothing since. Hopefully, there's enough in the queue on my xw9400 to get it through the night. It'll be interesting to see how things look in the morning. It's past my bedtime. :^)

"Project has no tasks available" appears to be the current standard response.

---

Grant
Darwin NT

01jl12ad.5031.2930.140733193388035.12.113_2
01jl12ad.5031.2930.140733193388035.12.118_2
01jl12ad.5031.2930.140733193388035.12.18_2
01jl12ad.5031.394287.140733193388035.12.200_2

All Invalid.

---

Grant
Darwin NT

Sure looks as if there's another rogue tape out there - 01JL12*** is certainly producing more than its fair share of invalid results, and those I've looked at all have the message about "Legacy V6" in their stderr report :-(

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

It looks as if tape 01jl12ad has been around since at least Wednesday (14 Jan), and so far I've seen validated tasks from

01jl12ad.11188.xxxxx.438086664202.12.xxx
01jl12ad.15978.xxxxx.438086664200.12.xxx
01jl12ad.20573.xxxxx.438086664199.12.xxx
01jl12ad.21345.xxxxx.438086664204.12.xxx
01jl12ad.22792.xxxxx.438086664195.12.xxx
01jl12ad.23421.xxxxx.438086664205.12.xxx
01jl12ad.24502.xxxxx.438086664206.12.xxx
01jl12ad.28015.xxxxx.438086664197.12.xxx
01jl12ad.31815.xxxxx.438086664207.12.xxx
01jl12ad.4776.xxxxx.438086664208.12.xxx

It only seems to be the 5031.xxxxx.140733193388035 channel which is being split in v6 mode - I've had a few of those, too.

Looks like my xw9400 downloaded a half dozen of the 01jl12ad.5031 files overnight, all of them _2 or _3. Guess I'll abort them later on if the "legacy V6" issue continues to remain consistent for that channel.

I was wondering if these specific rogue channels might be ones that were initially just partially split a few years ago, but then their tapes were pulled and put back on the shelf before the channels completed, leaving some sort of channel "characteristics" file or database entry hanging around that the current splitters are now referencing. Is that possible?

The third element in an MB WU name is a block number, and it normally advances by 409 for each subsequent group of WUs. So TBar's 01jl12ad.5031.1294.140733193388035.12.95 is in the 4th group from that channel. That made it practical to search backwards and find examples from the preceding 3 groups.

01jl12ad.5031.67.140733193388035.12.250 from the first group, and 01jl12ad.5031.476.140733193388035.12.237 from the second group have normal autocorr parameters, but 01jl12ad.5031.885.140733193388035.12.59 from the third group is getting v6 processing.

LoL, I did the above in brute force fashion by trial and error. Using the task name search from a task list page is much easier...

                                                                   Joe

So something happened to the splitter parameters - on one tape only - between 16 Jan 2015, 20:26:26 UTC and 16 Jan 2015, 20:28:00 UTC?

The cricket graph dropped sharply around that time, and there are some posts in 'panic mode' about some odd figures on the SSP. But it's hard to build a coherent explanation from those scraps.

So something happened to the splitter parameters - on one tape only - between 16 Jan 2015, 20:26:26 UTC and 16 Jan 2015, 20:28:00 UTC?

The cricket graph dropped sharply around that time, and there are some posts in 'panic mode' about some odd figures on the SSP. But it's hard to build a coherent explanation from those scraps.

The oddness of the server status has happened 4 times now. With the current one at [As of 17 Jan 2015, 21:00:05 UTC] being the 4th. Each spike on the haveland status is an instance of the server status going wonky.
If it is related to the splitter processes I would guess we will see tasks generated within the time stamps of the server status odd numbers. Could it be related to the temp WU storage area getting full?

---

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