Matt wrote about it again today in the technical forum

Once again not much hardware/server stuff to report. I guess the ap_validator "2" is failing due to seg faults. A fact that is obscured on the server status page (due to automatic parsing of configuration files) is that the ap_validator "2" does strictly astropulse_v5 workunits, while ap_validator "1" validates older astropulse workunits. In any case, I warned Josh, he's looking into it, etc. Probably a broken result file/database entry is causing it to seg fault and quit before doing very much.

---

3/6/2009 2:39:59 PM|SETI@home|Sending scheduler request: To fetch work. Requesting 106296 seconds of work, reporting 0 completed tasks
3/6/2009 2:40:04 PM|SETI@home|Scheduler request completed: got 0 new tasks
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work sent
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work is available for SETI@home Enhanced
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work available for the applications you have selected. Please check your settings on the web site.

Now I can panic.

---

me@rescam.org

3/6/2009 2:39:59 PM|SETI@home|Sending scheduler request: To fetch work. Requesting 106296 seconds of work, reporting 0 completed tasks
3/6/2009 2:40:04 PM|SETI@home|Scheduler request completed: got 0 new tasks
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work sent
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work is available for SETI@home Enhanced
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work available for the applications you have selected. Please check your settings on the web site.

Now I can panic.

Nah, that's normal. There'll be more work along in a second.

But "Current result creation rate NULL/sec NULL/sec"? THAT I can panic about.

3/6/2009 2:39:59 PM|SETI@home|Sending scheduler request: To fetch work. Requesting 106296 seconds of work, reporting 0 completed tasks
3/6/2009 2:40:04 PM|SETI@home|Scheduler request completed: got 0 new tasks
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work sent
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work is available for SETI@home Enhanced
3/6/2009 2:40:04 PM|SETI@home|Message from server: No work available for the applications you have selected. Please check your settings on the web site.

Now I can panic.

Nah, that's normal. There'll be more work along in a second.

But "Current result creation rate NULL/sec NULL/sec"? THAT I can panic about.

There was plenty of work to be found, but it was all at BETA.

---

me@rescam.org

No DB dump today??

---

Clk2HlpSetiCty:::PayIt4ward

No DB dump today??

Quick action by the Berkeley Boyz! There was a dump about 25 minutes after your post.

James.. same procedure as every year.. *

Ops.. no.. this was an other story.. ;-D



[* Dinner for One [german] / Dinner for One [US/UK]]**

[** For the young under us.. ;-D]

---

I see the AP2 validator is up and running. I hope it stay's running for another 57 hours so i can send in my AP 5.3. Or I might panic then.

---

[/quote]

Old James

I have just received credit for 12 pending v5 AP wus that's about 14,000 credit but waiting on wingmen for another 40+ v5 AP, I wonder what credit Mark has got?

---

I've only got three in pending and none of them validated but at least one of them got looked at so they could send it out again. My wingman screwed it up and I've been waiting 3 or 4 days for it to get reissued.

---

PROUD MEMBER OF Team Starfire World BOINC

I've got:

10 pending
3 granted
5 cleared and gone
19 in-progress/queued

That's my ap_v5 experience so far.

---

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

I see "ap_validate2" is not running again and "waiting for validation" is increasing. Hopefully will be looked at on today's downtime. Had been working for a while recently.

---

I see "ap_validate2" is not running again and "waiting for validation" is increasing. Hopefully will be looked at on today's downtime. Had been working for a while recently.

Then it appears the AP team still hasn't found/fixed the problem. Matt mentioned last week that the script that builds the server status page goes through every 10 minutes and restarts all the processes that have issues. ap_validate2 is specifically for ap_v5, and it gets a few jobs done, and then segfaults, and doesn't get "kicked" until the script runs through again. It is doing something, just not as much as it could be doing.

---

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

I've got:

10 pending
3 granted
5 cleared and gone
19 in-progress/queued

That's my ap_v5 experience so far.

Mine is:

12 pending
6 cleared and gone
4 in progress/cached

Since 28 Feb

2 cleared and gone
7 pending
1 crunching
2 waiting

Look how many recordings they've loaded on the splitters (Server status page)!

Are the crew all planning to go on vacation together, or something?

Are the crew all planning to go on vacation together, or something?

I suspect they just want more uninterrupted time to try to eliminate server issues (or eliminate those ants ... LOL).

Are the crew all planning to go on vacation together, or something?

I suspect they just want more uninterrupted time to try to eliminate server issues (or eliminate those ants ... LOL).

I think they're trying to refocus all efforts into getting the Nitpicker running in time for their 10th anniversary. Matt has been hinting at this a couple of times in his Tech News already. Next month is the big deadline, and I don't know how much work they have ahead of them.

---

I was going to make some comment last week about there being 50+ "tapes" online. Must have gotten all that new storage working properly. I still think we need more MB splitters though. When I change my venue to non-ap_v5, I keep getting no work available or just one MB at a time. I'm pretty sure I'm not the only one.

Still wondering why all I get is ap_v5 even though all are selected. Seems like the scheduler doesn't want me to have anything else..

---

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

Still wondering why all I get is ap_v5 even though all are selected. Seems like the scheduler doesn't want me to have anything else..

Do re-issued tasks get priority when work is being sent out?

It could be that the thousands of APv5's getting quota trashed every night are clogging the pipes.

/edit, Not sure more splitters are needed since the ready to send is usually full. Perhaps more feeder cache space.