blc05_2bit_guppi_58406_33654_DIAG_3C249_1_0120 has been in the queue since last year it is just over 10 GB in size. I wonder when this will be split

. . If they don't load any older tapes in the meantime it should split within the next 3 or 4 days. It is one of the "youngest" tapes presently loaded.

Stephen

..

some stuck in tape processing ... not FIFO ? but LIFO ?

not seen any BLC 15 14 12 6 5 4 Wu in my cache ...

. . That's because the Blc16 tapes being split are older than the tapes of the other varieties. When they reach the same age tapes the others will begin to split again. 1st the Blc15's because they have the next oldest tapes, then the 14/12s etc.

Stephen

:)

blc05_2bit_guppi_58406_33654_DIAG_3C249_1_0120 has been in the queue since last year it is just over 10 GB in size. I wonder when this will be split

---

You missed the memo?
They expanded "Search for Extraterrestrial Intelligence" to include tasks, and servers.

---

it seems that the "no task available " horror show is back ...

forum is a little bit laggy too ;)

I'm at work so I can't check my system logs, but I noticed an hour or so ago, the statuses for multiple services on the server status page were an hour old. Right now, we have over 700k tasks ready to send, and all splitters are offline. I would suspect with the splitters offline, the backend system will catch up a bit. At least until the pendulum starts to swing the other way again.

---

~Chris

it seems that the "no task available " horror show is back ...

for CPU here

05-Jan-2019 15:40:44 [SETI@home] Sending scheduler request: To fetch work.
05-Jan-2019 15:40:44 [SETI@home] Requesting new tasks for CPU
05-Jan-2019 15:40:57 [SETI@home] Scheduler request completed: got 0 new tasks
05-Jan-2019 15:40:57 [SETI@home] Project has no tasks available
05-Jan-2019 15:53:03 [SETI@home] Sending scheduler request: To fetch work.
05-Jan-2019 15:53:03 [SETI@home] Requesting new tasks for CPU
05-Jan-2019 15:53:12 [SETI@home] Scheduler request completed: got 0 new tasks
05-Jan-2019 15:53:12 [SETI@home] Project has no tasks available
05-Jan-2019 15:57:24 [SETI@home] Computation for task blc16_2bit_guppi_58406_26617_HIP20917_0102.21911.409.21.44.210.vlar_0 finished
05-Jan-2019 15:57:24 [SETI@home] Starting task blc16_2bit_guppi_58406_26617_HIP20917_0102.21911.409.21.44.228.vlar_0
05-Jan-2019 15:57:26 [SETI@home] Started upload of blc16_2bit_guppi_58406_26617_HIP20917_0102.21911.409.21.44.210.vlar_0_r509214313_0
05-Jan-2019 15:57:30 [SETI@home] Finished upload of blc16_2bit_guppi_58406_26617_HIP20917_0102.21911.409.21.44.210.vlar_0_r509214313_0
05-Jan-2019 16:02:50 [SETI@home] update requested by user
05-Jan-2019 16:02:53 [SETI@home] Sending scheduler request: Requested by user.
05-Jan-2019 16:02:53 [SETI@home] Reporting 1 completed tasks
05-Jan-2019 16:02:53 [SETI@home] Requesting new tasks for CPU
05-Jan-2019 16:02:58 [SETI@home] Scheduler request completed: got 0 new tasks
05-Jan-2019 16:02:58 [SETI@home] Project has no tasks available

and then for GPU got some Wu with slow downloading rates and CPU too

forum is a little bit laggy too ;)

---

okay, thks for your reply :)

---

some stuck in tape processing ... not FIFO ? but LIFO ?

not seen any BLC 15 14 12 6 5 4 Wu in my cache ...

. . That's because the Blc16 tapes being split are older than the tapes of the other varieties. When they reach the same age tapes the others will begin to split again. 1st the Blc15's because they have the next oldest tapes, then the 14/12s etc.

Stephen

:)

some stuck in tape processing ... not FIFO ? but LIFO ?

not seen any BLC 15 14 12 6 5 4 Wu in my cache ...

---

It looks as if the stats are beginning to come back to life.

---

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

the results out in the field has been slowly climbing and is at 4.8 now, which I hope means that most people now have have some seti data.

I’ve been getting work regularly since last night. But no stats update on the website.

---

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

I have not seen one single new WU in nearly 36 hours so I'm boosting my rac on Primegrid.

---

All GBT splitters now shut down.

---

Looks like the usual daily glitch has begun. Forums slow & "Project has no tasks available" Scheduler responses.

Edit- and it's been almost an hour since most of the Server stats were updated.

---

Grant
Darwin NT

Went into the other room for some reason and saw that the HDD activity light on Altair was lit up solid. RDP was very slow, and everything was very slow to react/respond, though it eventually did. Not sure what was up with it, but I figured with 53 days since last restart.. might as well, since BOINC had crashed approximately 48 hours ago and even telling the service to stop and start again didn't fix it.

System restart fixed it. I also--for some reason--had to fix the date and mash the 'update now' button for internet time. I don't know why or when it happened, but the clock became +78640 seconds from what it should have been, which was too far out of the range for w32time to adjust which required manual adjustment to get it close, and then 'update now' will do it properly.

Anyway, did that, and restarted, and looks like BOINC came back up just fine.

2019-01-04 01:48:39 SETI@home [sched_op_debug] Starting scheduler request
2019-01-04 01:48:39 SETI@home Sending scheduler request: To fetch work. Requesting 3454 seconds of work, reporting 6 completed tasks
2019-01-04 01:48:40 Project communication failed: attempting access to reference site
2019-01-04 01:48:41 Internet access OK - project servers may be temporarily down.
2019-01-04 01:48:44 SETI@home Scheduler request succeeded: got 1 new tasks
2019-01-04 01:48:44 SETI@home [sched_ops_debug] Server version 709
2019-01-04 01:48:44 SETI@home Project requested delay of 303.000000 seconds
2019-01-04 01:48:44 [sched_op_debug] handle_scheduler_reply(): got ack for result 26dc18ac.28654.1550684.6.33.97.vlar_0
2019-01-04 01:48:44 [sched_op_debug] handle_scheduler_reply(): got ack for result blc16_2bit_guppi_58405_85309_GJ687_0026.28254.818.22.45.101.vlar_0
2019-01-04 01:48:44 [sched_op_debug] handle_scheduler_reply(): got ack for result 29dc18aa.13524.19290.16.43.51_1
2019-01-04 01:48:44 [sched_op_debug] handle_scheduler_reply(): got ack for result blc16_2bit_guppi_58405_85972_GJ687_0028.24700.818.21.44.119.vlar_0
2019-01-04 01:48:44 [sched_op_debug] handle_scheduler_reply(): got ack for result blc16_2bit_guppi_58405_86306_HIP85612_0029.19316.409.21.44.81.vlar_1
2019-01-04 01:48:44 [sched_op_debug] handle_scheduler_reply(): got ack for result blc16_2bit_guppi_58405_85972_GJ687_0028.1839.818.21.44.134.vlar_2
2019-01-04 01:48:44 SETI@home [sched_op_debug] Deferring communication for 5 min 3 sec
2019-01-04 01:48:44 SETI@home [sched_op_debug] Reason: requested by project
2019-01-04 01:48:46 SETI@home Started download of blc16_2bit_guppi_58406_25930_HIP20901_0100.24062.818.21.44.133.vlar
2019-01-04 01:48:49 SETI@home Finished download of blc16_2bit_guppi_58406_25930_HIP20901_0100.24062.818.21.44.133.vlar

Still weird that it says comms failed...but completes the comms anyway, uploads WUs, and downloads new ones without issues. It is only during scheduler request that it immediately says that it failed.

I'm aware of the scheduler being hammered after maintenance..or an unscheduled outage, but my logs show this behavior for several months now. what's up with that?

---

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

And to add to that, splitter output is less than demand- now that work is finally going out again (In-progress is about halfway to it's usual level), the splitters can't keep up. Ready-to-send is rapidly declining.
Hopefully the splitters will get a move along before we run out.

---

Grant
Darwin NT

24 hours later and the recovery has only just started. And even then, it's at an extremely slow pace.
And even after that bit of recovery, we're still behind where we usually are after the weekly outage. Almost 4.5 million in progress, another 600k to go till things are back to normal.

Given the difficulties still occurring in getting work, that could be a long way off yet.
Things haven't been good for a few weeks now, but it looks like they are starting to come to a head.

---

Grant
Darwin NT

Yes, you can't view your Tasks. So you have no idea how many you have unless you have a third party tool like BoincTasks. ...

Yeah, I've been running Fred's BoincTasks for years (in spite of its instability on at least my Win10, it's the only decent game in town for centrally monitoring multiple crunchers) so no big deal.
Of course BT can't deal with credit granted, validation state or the status of wingmen so some web functions remain useful.
Just thought it was curious to see a result like that (perhaps indicative of new development, to shed load on the DB when needed?)

---

Yes, you can't view your Tasks. So you have no idea how many you have unless you have a third party tool like BoincTasks.

You could always physically count the number you have in your cache, possible now with the small amount of work that has been delivered. Would only take ten fingers and ten toes.

You also can't see if a task is validated, inconclusive, errored or pending. Viewing tasks is one of the purposes of having the replica database to relief the I/O stress on the main database by anyone wanting to view their current task cache.

I don't know whether turning off task viewing is allowing the replica lag to finally start reducing from its peak. I still believe the replica being brought back online is the root cause of all the projects troubles lately in delivering work.

---

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

A proud member of the OFA (Old Farts Association)

Unable to handle request
This feature is turned off temporarily

While trying to get status of tasks ...

---