Does anyone know what has changed to cause the outage to be so short?

---

I'm curious about this too!

I'll guess that recent memory upgrades and memory mismatch fixes played a small part in getting the whole system to run better, but I'm guessing that there is something else going on. A process change ?? A faster backup tool??

I'm very curious, I hope you get an answer.

When you are playing with large DB's you can make measurable performance improvements by putting the DB index's on different storage hardware than the actual database(s). The more you can keep those indexes and databases in ram on a system the faster it will be too.

It is also possible that there has been a version update of the Data Base Management System(s) that has made measurable differences.

Or they could have migrated the file system onto newer/faster NAS systems.

Or..... its spring and everything is blooming.....

:0

Tom

---

A proud member of the OFA (Old Farts Association).

so you don't know

---

so you don't know

Yup.
I do know that they went through a RAM upgrade a couple of months ago. It didn't work quite right the first attempt on the RAM upgrade but did, the next Tuesday. But once they got that in place we seem to be having shorter outages. But I won't swear that is "when it changed".

Tom

---

A proud member of the OFA (Old Farts Association).

Since yesterdays outage, one of my PCs will not connect to SETI and is out of work with lots of completed WU's. Whenever I try to force it to update, I get the following lines in the event log:

22/05/2019 21:46:43 | SETI@home | update requested by user
22/05/2019 21:46:47 | SETI@home | Fetching scheduler list
22/05/2019 21:46:56 | | Project communication failed: attempting access to reference site
22/05/2019 21:46:58 | | Internet access OK - project servers may be temporarily down.

My other two PCs are connecting Ok so clearly not a project server issue. My PC that will not connect to SETI is connecting to Cosmology so not a BOINC or internet issue at my end.

Any ideas?

---

My other two PCs are connecting Ok so clearly not a project server issue. My PC that will not connect to SETI is connecting to Cosmology so not a BOINC or internet issue at my end.

Any ideas?

Have you re-booted that system?
Does it have 3rd party AV/internet security on it?

---

Grant
Darwin NT

My other two PCs are connecting Ok so clearly not a project server issue. My PC that will not connect to SETI is connecting to Cosmology so not a BOINC or internet issue at my end.

Any ideas?

Have you re-booted that system?
Does it have 3rd party AV/internet security on it?

Yes I have rebooted twice and no to 3rd party AV/internet security software.

---

I would have you set http_debug in the Event Log options from the Manager Options menu and then post the output from when your client tries to connect to the project. That should show what's failing on your connect attempts.

---

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

A proud member of the OFA (Old Farts Association)

I would have you set http_debug in the Event Log options from the Manager Options menu and then post the output from when your client tries to connect to the project. That should show what's failing on your connect attempts.

I have no idea how to do that. I can display the Event Log (Ctrl Shift E) but it does not seem to have any options. My Boinc is version 7.2.28 (x64).

---

You are using an old version of BOINC. The menus have changed considerably over time with the later version. Try SHIFT-CTRL-F to access the Event Log logging options.

---

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

A proud member of the OFA (Old Farts Association)

You are using an old version of BOINC. The menus have changed considerably over time with the later version. Try SHIFT-CTRL-F to access the Event Log logging options.

That does nothing on my version

---

Are you using the Simplified View or the Advanced View with the Manager?

[Edit] I've looked back through the forums and CTRL-SHIFT-F was the correct way to access the Event Log options back on BOINC 7.2.42.

Think you need to post your question over in the Questions and Answers forum and hope for Jord or one of the old-timers still using ancient BOINC versions for how to access the Options for the Event Log.

---

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

A proud member of the OFA (Old Farts Association)

You are using an old version of BOINC. The menus have changed considerably over time with the later version. Try SHIFT-CTRL-F to access the Event Log logging options.

That does nothing on my version

Hi Mike,

Try SHIFT-CTRL-E. Actually, it is SHIFT-CTRL-F to access the options. The other one access the event log.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

You are using an old version of BOINC. The menus have changed considerably over time with the later version. Try SHIFT-CTRL-F to access the Event Log logging options.

That does nothing on my version

Hi Mike,

Try SHIFT-CTRL-E.

Have a great day! :)

Siran

He can pull up the Event Log that way. But that does not give him access to the logging options.

---

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

A proud member of the OFA (Old Farts Association)

You are using an old version of BOINC. The menus have changed considerably over time with the later version. Try SHIFT-CTRL-F to access the Event Log logging options.

That does nothing on my version

Hi Mike,

Try SHIFT-CTRL-E.

Have a great day! :)

Siran

He can pull up the Event Log that way. But that does not give him access to the logging options.

Hi Keith,

Yep. :D I saw that and modified my post. Thanks. :)

Have a great day! :)

Siran

[edit]
And, under the Options menu there is a button for the log settings.
[/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

You must be in Simple View. https://boinc.berkeley.edu/wiki/Simple_view says that

Advanced level: you can control what messages are shown

Shift into Advanced View with SHIFT-CTRL-A and then do the CTRL-SHIFT-F.

---

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

A proud member of the OFA (Old Farts Association)

You must be in Simple View. https://boinc.berkeley.edu/wiki/Simple_view says that

Advanced level: you can control what messages are shown

Shift into Advanced View with SHIFT-CTRL-A and then do the CTRL-SHIFT-F.

By default I am in advanced view, but I have tried CTRL-SHIFT-F in both simple and advanced views and nothing happens.

I do not even have an options menu, just: file, view, tools, activity, advanced, help.

Curiously I have three PCs all running the same version of Bionc etc and the other 2 are still working fine.

---

Sorry I cannot help you further. I suggest you ask for help in the Questions and Answers forum.

---

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

A proud member of the OFA (Old Farts Association)

I really wanted the answer to the original question, before the thread got hijacked.

What have they done to the seti system to allow them much shorter weekly outages?? Maybe there is a better place to ask this question, but I would still like to know.