The setting in under options in cc_config.xml.
<max_tasks_reported>100</max_tasks_reported>

---

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

A proud member of the OFA (Old Farts Association)

If I try to report more than 100 tasks a time, I will get the comms error and a backoff. 100 seems to be my magic number. I'm 95% successful every time.

. . which file is that setting in again? I am sure mine is still over 100 (might be 128) but until now I could not see anyone stating a number which was consistently working ...
Stephen

cc_config
<max_tasks_reported>100</max_tasks_reported>

---

The setting in under options in cc_config.xml.
<max_tasks_reported>100</max_tasks_reported>

. . Well there you have it, mine is now set to 99 and yet still gets 'http internal server error'

. . OK, I set it on the Linux box as well and there EVERY report attempt was successful. I will try another value on the Windows box.

. . I dropped it to 69 but still getting the http internal server error. It seems there is something else at play on this box.

Stephen

<shrug>

The setting in under options in cc_config.xml.
<max_tasks_reported>100</max_tasks_reported>

ive tried. still no dice. nothing but http internal server error

---

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

All reported now. Not getting any cpu work. Still crunching through my gpu rescheduled tasks.

---

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

A proud member of the OFA (Old Farts Association)

All reported now. Not getting any cpu work. Still crunching through my gpu rescheduled tasks.

. . Now only one box out of 4 is not reporting work so overall things are kind of OK. But this box will be OOW soon if things don't improve.

Stephen

:(

Downloads are starting but all are hanging up in backoff.

---

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

A proud member of the OFA (Old Farts Association)

I was getting worried that they were all stuck in a cluster-f over 05jl06ef, but they seemed to have worked themselves free again.

Look at the size of the file
05jl06ef 272.67 GB

It might be weird to split that one considering the size. usually the files are around 50GB.

Must have been removed. I went to have a look at it but would not see it. It would have been impressive to see it munch through a file that big

Yeah, it finally wrapped up a bit ago. I think all told it took over 24 hours to fully process for both MB and AP.

In passive I wish I had of seen it. I will keep a close eye on the MB work from now on. I hope it wasn't a one off

---

Stuck downloads finally cleared. The logjam is over.

---

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

A proud member of the OFA (Old Farts Association)

Downloads are starting but all are hanging up in backoff.

Yeah.
Got home to find work allocated, but both systems in back-off forever mode due to downloads not happening. Retried pending transfers & now things are working once more (at least until the Ready-to-send buffer is empty again anyway).

---

Grant
Darwin NT

(at least until the Ready-to-send buffer is empty again anyway).

Which may not take too long as I just had 4 noise bombs.

---

Grant
Darwin NT

All reported now. Not getting any cpu work. Still crunching through my gpu rescheduled tasks.

. . Now only one box out of 4 is not reporting work so overall things are kind of OK. But this box will be OOW soon if things don't improve.
Stephen
:(

. . Update, that machine was finally able to report and had a wonderful experience. Without any prompting on my part three consecutive work reports/requests resulted in ghost resends. Within 15 mins the machine has recovered 60 ghosts when it needed them most. Now only 20 outstanding.

. . I also noticed some new tapes have been mounted for splitting, and UnixChick they are still for the same day/night. But a new variety ... blc36's. These will be very slow (relatively speaking).

Stephen

:)

Amazing how one day of data collection can give us enough files to work on for months... I can't remember when we started working on this day of data. It looks like we have at least another 2 or 3 weeks worth of data now.

Thanks Stephen for recovering the ghosts, I'm glad the recovery is going well.

Amazing how one day of data collection can give us enough files to work on for months... I can't remember when we started working on this day of data. It looks like we have at least another 2 or 3 weeks worth of data now.

Thanks Stephen for recovering the ghosts, I'm glad the recovery is going well.

. . I am stickler for ghost recovery, it is only fair to your wingmen and not that hard to do. It's also better for the project generally as it prevents further database bloat.

. . In fairness though, we have processed quite a few Arecibo tapes while we have been gnawing on this particular GBT bone :)

Stephen

:)

Unable to contact servers to report work without timeouts.

---

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

A proud member of the OFA (Old Farts Association)

i was able to report some tasks shortly after it came back, but looks like its down again. no COMMs.

no biggie, i'm sure it'll come back eventually.

someone somewhere posted that this would be normal now right? a second outage on Wednesdays? i could be misremebering.

---

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

I wonder if they took the site down to patch a website software vulnerability.

---

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

A proud member of the OFA (Old Farts Association)

Unable to contact servers to report work without timeouts.

Yep

---

i was able to report some tasks shortly after it came back, but looks like its down again. no COMMs.

no biggie, i'm sure it'll come back eventually.

someone somewhere posted that this would be normal now right? a second outage on Wednesdays? i could be misremebering.

. . Well if nothing else this project has proven the existence of black holes ... it keeps falling into them :)

{edit}
. . OK, this machine was finally able to report the 69 task limit I set it to but now it is 'no tasks available'. Very typical post outage behaviour ...

Stephen

<shrug>

Slowly coming back to life.

---