I have to limit the number of results I report at time, otherwise i get nothing but Scheduler errors ...

Having a less verbose std_err report per task in the sched_request file might help with that one.

How do I configure that?

---

Grant
Darwin NT

I have to limit the number of results I report at time, otherwise i get nothing but Scheduler errors ...

Having a less verbose std_err report per task in the sched_request file might help with that one.

How do I configure that?

Speak to the developer of whichever app you're using - it might even be in documentation.

An extra command line parameter of -v0 (or it might be -v 0) might help with that - it might be wise to experiment offline in a test bench environment first.

An extra command line parameter of -v0 (or it might be -v 0) might help with that - it might be wise to experiment offline in a test bench environment first.

Ah, I've vague memories of v settings when looking at optimisation in the readmes.
Thanks.

---

Grant
Darwin NT

Just looked at the readme's for both the MB cpu and SoG apps. -v 1 is the default reporting and -v 0 disables almost all outputs.

---

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

A proud member of the OFA (Old Farts Association)

. . Well looking at the tapes splitting it looks like being a dry old weekend ...

Stephen

:(

Looks like they added a bit more data overnight. When I went to bed the splitters only had about 1250 channels left to do. Now the unsplit channels are over 2000.

We are going to need more than that though to make it through to Monday.

. . Absotively ...

Stephen

:)

Looks like we got more data for the weekend. Still haven't seen the old Arecibo data Eric said Jeff was trying to massage into shape for splitting.

---

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

A proud member of the OFA (Old Farts Association)

Well that sucks- an errored WU.

<message>
finish file present too long
</message>

---

Grant
Darwin NT

Had a few of those myself last week. Sucks.

---

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

A proud member of the OFA (Old Farts Association)

I have to limit the number of results I report at time, otherwise i get nothing but Scheduler errors ...

Having a less verbose std_err report per task in the sched_request file might help with that one.

Interesting, I only have a 5Mb/612k connection here and after maintenance have ~3000 tasks to report and have no errors. It seems the server has about a 1 minute time limit to report, so I only send 200-250 each update. Staggering the computers helps get them in so that I can get new tasks back.

Interesting, I only have a 5Mb/612k connection here and after maintenance have ~3000 tasks to report and have no errors. It seems the server has about a 1 minute time limit to report, so I only send 200-250 each update. Staggering the computers helps get them in so that I can get new tasks back.

I might try it without the limit (or at least raise it considerably) on the number reported each Scheduler contact after next week's outage- it's presently 60.
I can't remember when the issue started occurring, it might have been before I got my Fibre connection. Since then things are considerably quicker than they were.

---

Grant
Darwin NT

More files have been loaded up. There's now about 2 days worth at the previous return rate, probably closer to 3 at the current rate of return.

---

Grant
Darwin NT

Glitch time again bad lag

See that there is glitch/break again in the Haveland graphs again that coincides with the lag/slowness of the project website.

---

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

A proud member of the OFA (Old Farts Association)

See that there is glitch/break again in the Haveland graphs again that coincides with the lag/slowness of the project website.

Yeah, it was real tangled up for a while last night. Rig was going into deep backoff due to not being able to contact the server. Getting to be a nightly thingy.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Yeah, it was real tangled up for a while last night. Rig was going into deep backoff due to not being able to contact the server. Getting to be a nightly thingy.

Been that way for months, it's just the last few days that it's moved to a later time slot.
Generally it hasn't occurred on Sundays (that's today, here) so we'll see what happens later on.

---

Grant
Darwin NT

Normally happens between 5pm and 6pm here in Adelaide, uploads stick and forums don't load..

Normally happens between 5pm and 6pm here in Adelaide, uploads stick and forums don't load..

A I look at a globe it is obvious that you folks are upside down. that could readily explain it.

---

Generally it hasn't occurred on Sundays (that's today, here) so we'll see what happens later on.

So now it's on Sundays too...

---

Grant
Darwin NT

Generally it hasn't occurred on Sundays (that's today, here) so we'll see what happens later on.

So now it's on Sundays too...

Yeah, it was a train wreck last night again.
That was Caturday night here.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I was about to panic because the number of channels to do got down to 1300 (or about 12 hours of channels for the splitters to do), but someone has been busy this weekend because we now have over 5300 channels lined up :-)

---

~Chris