Yep, lots and lots of Arecibo VLARs. Even my machines are having difficulty getting new tasks, and my #1 cruncher actually got down to its last GPU task, the first time I can recall that happening. I just went ahead and rescheduled all the available guppis and non-VLAR Arecibo tasks from the CPU to the GPU queue. That freed up enough CPU queue space to be able to accept a bunch of Arecibo VLARs which, in turn, seemed to let a bunch of guppis and Arecibo non-VLAR tasks loose. It looks like that machine is slowly starting to rebuild the GPU queue but who knows how long that'll last. If I have to, I'll just move Arecibo VLARs over to the GPUs. I don't think they do all that badly with the Special App.

. . On my machines they take only about 50% longer ...

Stephen

:(

Ah, we're back. Web site & forums went AWOL for about 10min.

---

Grant
Darwin NT

Yep, network communications unavailable. Looking for work.

---

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

A proud member of the OFA (Old Farts Association)

Don't know how long we'll be back up for though.
Loading a thread (or even a page) is varying between slow & almost comatose.

---

Grant
Darwin NT

Yes, my last post took almost 3 minutes to appear.

---

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

A proud member of the OFA (Old Farts Association)

Don't know how long we'll be back up for though.
Loading a thread (or even a page) is varying between slow & almost comatose.

. . Hey .. my ISP has been down for about 12 hours, everything is empty and the outage is about to start :(

. . Bummer dude!

Stephen

:(

. . I am surprised this thread is not full of messages since the outrage. All three machines "No Tasks Available". Maybe I am the only one getting this ??

Stephen

??

. . I am surprised this thread is not full of messages since the outrage. All three machines "No Tasks Available". Maybe I am the only one getting this ??

Stephen

??

You're not the only 1 this time, but at least my caches got very near full before that happened. ;-)

Cheers.

. . I am surprised this thread is not full of messages since the outrage. All three machines "No Tasks Available". Maybe I am the only one getting this ??

Stephen

??

You're not the only 1 this time, but at least my caches got very near full before that happened. ;-)

Cheers.

. . Only one of my machines got much work before the famine. The other had barely enough to get through an hour.

. . But I am now convinced this thread is haunted. For over an hour "No tasks", but a few minutes after posting that message all machine got new work ... eerie :)

Stephen

<shudder> :)

. . I am surprised this thread is not full of messages since the outrage. All three machines "No Tasks Available". Maybe I am the only one getting this ??

Stephen

??

You're not the only 1 this time, but at least my caches got very near full before that happened. ;-)

Cheers.

Mine went from getting the maintenance message to reporting and filling up.

10/3/2017 6:21:21 PM	SETI@home	Project is temporarily shut down for maintenance
10/3/2017 6:47:09 PM	SETI@home	Sending scheduler request: To report completed tasks.
10/3/2017 6:47:09 PM	SETI@home	Reporting 50 completed tasks
10/3/2017 6:47:09 PM	SETI@home	Requesting new tasks for CPU
10/3/2017 6:47:12 PM	SETI@home	Scheduler request completed: got 50 new tasks

Maybe having max_tasks_reported set to 50 has something to do with my hosts high success rate?
I did have on host report 46 and only receive 38. It did get 8 tasks on the next request 5 min later, but otherwise nothing to odd for me.

---

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

. . I am surprised this thread is not full of messages since the outrage. All three machines "No Tasks Available". Maybe I am the only one getting this ??

Stephen

??

You're not the only 1 this time, but at least my caches got very near full before that happened. ;-)

Cheers.

2-3 further requests after that post my caches were full.

Cheers.

I think I am going to have to set the max_task_reported tag. I updated all the crunchers after the project came back up and the log said all were successful. I then took down Numbskull for the rebuild but now that I have checked the hosts, I see that the reported tasks for it didn't take.

I also had something strange occur again on the Linux cruncher. I've seen it one time before. If a task is unsuccessful in downloading and the log says either task * was supposed to be 720XXX bytes and it got 0 bytes or the task is missing its header, then BOINC crashes the machine and it reboots. Anybody else see that? Is this a known bug or is it something that has to be reported?

---

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

A proud member of the OFA (Old Farts Association)

My Linux boxes have yet to have a crash, so I haven't seen that happen.

That is what I expected with Linux since it is a lot more bullet-proof than Windows. Been rock solid up until the first event last week where something in BOINC got corrupted and it crashes the machine after a failed task download. When I bring BOINC back up, ( it is not autostarted), it will run for about 10-20 seconds and when it attempts to retrieve the previously errored download task, it immediately dumps the machine again. That to me sound like something wrote to memory where it shouldn't have. But I know nothing about troubleshooting Linux, and don't know what tools I am supposed to use. I have all kinds of tools for Windows to figure out what went wrong and know how to use them. But with Linux, I don't have a clue where to start.

---

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

A proud member of the OFA (Old Farts Association)

I also had something strange occur again on the Linux cruncher. I've seen it one time before. If a task is unsuccessful in downloading and the log says either task * was supposed to be 720XXX bytes and it got 0 bytes or the task is missing its header, then BOINC crashes the machine and it reboots. Anybody else see that? Is this a known bug or is it something that has to be reported?

Last Tuesday evening I got a couple with "Exit status -186 (0xFFFFFF46) ERR_RESULT_DOWNLOAD" and a Stderr with output like this:

WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>30mr08aa.13309.5798.9.36.5</file_name>
  <error_code>-200 (wrong size)</error_code>
</file_xfer_error>

That was the first and only time I've had D/L issues on any of my Linux hosts. However, they didn't cause any BOINC or system crash as far as I know.

That is what I expected with Linux since it is a lot more bullet-proof than Windows. Been rock solid up until the first event last week where something in BOINC got corrupted and it crashes the machine after a failed task download. When I bring BOINC back up, ( it is not autostarted), it will run for about 10-20 seconds and when it attempts to retrieve the previously errored download task, it immediately dumps the machine again. That to me sound like something wrote to memory where it shouldn't have. But I know nothing about troubleshooting Linux, and don't know what tools I am supposed to use. I have all kinds of tools for Windows to figure out what went wrong and know how to use them. But with Linux, I don't have a clue where to start.

Check first your disk is not full !
If not try to delete the wrong wu....

---

No, the disk is fine. Only using 6.5GB out of 215GB. It seems to clear itself up after a few BOINC restarts with the no state file found for task so and so.

---

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

A proud member of the OFA (Old Farts Association)

No, the disk is fine. Only using 6.5GB out of 215GB. It seems to clear itself up after a few BOINC restarts with the no state file found for task so and so.

Is this the BOINC 7.8.2 machine(s)? If so might be the slot directories issue

---

BOINC blog

I think I am going to have to set the max_task_reported tag. I updated all the crunchers after the project came back up and the log said all were successful. I then took down Numbskull for the rebuild but now that I have checked the hosts, I see that the reported tasks for it didn't take.

I also had something strange occur again on the Linux cruncher. I've seen it one time before. If a task is unsuccessful in downloading and the log says either task * was supposed to be 720XXX bytes and it got 0 bytes or the task is missing its header, then BOINC crashes the machine and it reboots. Anybody else see that? Is this a known bug or is it something that has to be reported?

I had to enable it for another project and never bothered to unset it for most of my hosts.

---

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

I remember when there was trouble with that a few years ago when we had to set that to report tasks. Somewhere along the way cc_config.xml got set back to defaults.

---

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

A proud member of the OFA (Old Farts Association)