Hello,

02/03/2006 17:31:47|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
02/03/2006 17:31:47|SETI@home|Reason: To fetch work
02/03/2006 17:31:47|SETI@home|Requesting 8640 seconds of new work
02/03/2006 17:31:52|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
02/03/2006 17:31:52|SETI@home|No work from project
02/03/2006 17:42:03|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
02/03/2006 17:42:03|SETI@home|Reason: To fetch work
02/03/2006 17:42:03|SETI@home|Requesting 8640 seconds of new work
02/03/2006 17:42:08|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
02/03/2006 17:42:08|SETI@home|New host venue: home
02/03/2006 17:42:08|SETI@home|No work from project

Can help me?

---

From the technical news:

February 28, 2006 - 21:15 UTC
We had a planned outage today to remove a couple more items from the server closet (the Classic SETI@home data server and several large, heavy disk arrays which contained the old science database). In order to safely do so, we wanted to power down several important machines so they wouldn't accidentally get bumped and go down ungracefully.
The Bay Area is having a rough winter, and a storm today brought lightning which knocked out power to the entire campus, including our lab, around 8am. Most of the servers went down without a hitch. And with the power off anyway we went ahead and cleaned up the closet as planned. We can now get behind the racks again without painful contortion.

Powering up the entire network is painful, as servers need to revive in a set order, and many hidden mounting issues come to light (that only get tickled by a reboot). Plus some drives needed some fsck'ing. Everything eventually booted up just fine, except for the master science database.

One of the fibre channel loops disappeared on this particular server. Bad cable? Bad GBIC? Not sure just yet, as the terminal wasn't working well enough to give us all the boot diagnostics. We hooked up a laptop and fought with hyperterm to see these messages, but by the time we got that working the machine booted just fine for no explicable reason... but all the metadevices needed to be resynced. This resync could take up to 24 hours, during which the master science database will be down. That means no splitting and no assimilating, and we'll probably run out of work to send before too long. Oh well.

Thanks very much.

---

From the technical news:

February 28, 2006 - 21:15 UTC
We had a planned outage today to remove a couple more items from the server closet

{BIG SNIP}

This resync could take up to 24 hours, during which the master science database will be down. That means no splitting and no assimilating, and we'll probably run out of work to send before too long. Oh well.

So, this means that you do not expect to be able to send out any more work units for the next 24 - 36 hours?

Of course, there is always the time to catch up with all the remotes that will be requesting work (like my two boxes). Let's be reasonable. Even if your equipment is lightning fast in repairing work units to send to the world, there is only so much information that will go across a data pipe at a time.

It seems as if all is going well with your restoration at the moment. Many congrats to you and the team.

Curious. Based on past experience, can you foresee and additional bumps in the road to recovery? After all, each box has it's own personality and every network connector, card, and cable is like a small child that loves to prank when they can. All of this I know much too well.

So if you were on my side, how long would you expect my processors to be idle waiting on work from you?

---

So if you were on my side, how long would you expect my processors to be idle waiting on work from you?

As long as the user is willing, and I'd hope they would have patience. They will send work when they can. If my processors sit idle waiting for work, I have two choices: 1) join another project or 2) wait for the WUs to come.

It's a volunteer project; it's not that big of a deal to have CPUs sitting idle waiting. It's not like it's wasting time and money (free projects transcend capitalistic ideals). If it's not good enough for you, then don't contribute.

---

From the technical news:

February 28, 2006 - 21:15 UTC
We had a planned outage today to remove a couple more items from the server closet

{BIG SNIP}

This resync could take up to 24 hours, during which the master science database will be down. That means no splitting and no assimilating, and we'll probably run out of work to send before too long. Oh well.

So, this means that you do not expect to be able to send out any more work units for the next 24 - 36 hours?

Of course, there is always the time to catch up with all the remotes that will be requesting work (like my two boxes). Let's be reasonable. Even if your equipment is lightning fast in repairing work units to send to the world, there is only so much information that will go across a data pipe at a time.

It seems as if all is going well with your restoration at the moment. Many congrats to you and the team.

Curious. Based on past experience, can you foresee and additional bumps in the road to recovery? After all, each box has it's own personality and every network connector, card, and cable is like a small child that loves to prank when they can. All of this I know much too well.

So if you were on my side, how long would you expect my processors to be idle waiting on work from you?

Since I'm attached to several project my CPU is never idle.

I suspect, that with this lenghty failure that it will be another 12hrs before things start moving again and another 24 to 48 before everything is normal again and everyones cache is full.

Keep an eye on the Server Status Page as an indicater of progress. When the Spliters go back on line we should see Results ready to send and the Current result creation rate numbers to start increasing.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

So if you were on my side, how long would you expect my processors to be idle waiting on work from you?

As long as the user is willing, and I'd hope they would have patience. They will send work when they can. If my processors sit idle waiting for work, I have two choices: 1) join another project or 2) wait for the WUs to come.

It's a volunteer project; it's not that big of a deal to have CPUs sitting idle waiting. It's not like it's wasting time and money (free projects transcend capitalistic ideals). If it's not good enough for you, then don't contribute.

Personally, I find your response quite offensive. I have been involved as a volunteer for Seti much longer than you and have demonstrated more patience than you have even had a chance to show.

I'm not sure who urinated in your Post Toasties prior to offering your unwanted and unneeded response, but next time I would appreciate it if you would simply refrain from responding to anything that I post unless you are willing to do so in a more civil manner.

Mine was a simple question to the fine people that allow us to be a part of this. Since you are not one of them, I do not see where your input is of any consequence...

---

Personally, I find your response quite offensive. I have been involved as a volunteer for Seti much longer than you and have demonstrated more patience than you have even had a chance to show.

I'm not sure who urinated in your Post Toasties prior to offering your unwanted and unneeded response, but next time I would appreciate it if you would simply refrain from responding to anything that I post unless you are willing to do so in a more civil manner.

Mine was a simple question to the fine people that allow us to be a part of this. Since you are not one of them, I do not see where your input is of any consequence...

Oh, so it's how long you've been a member that means so much. I'm not so sure about the patience thing, as obviously I am demonstrating more than you right now. If that's so offensive, then perhaps you should practice a little more patience.

My post was quite civil, I assure you. If you do not want to read my responses, or worse yet, become so offended to the simple information I offer, then I suggest simply not reading them and limiting your mind to only what you want to see.

Mine was a simple answer as to the choices one has. The reality of the situation. If you choose not to see it, then that's your choice. I simply pointed them out.

---

Oh, so it's how long you've been a member that means so much. I'm not so sure about the patience thing, as obviously I am demonstrating more than you right now.

And you base that statement on what data? You logic escapes me.

If that's so offensive, then perhaps you should practice a little more patience.

Again, huh? It seems as if you use the word 'Patience' quite a bit, but you base your statements on virtually no tangible data.

My post was quite civil, I assure you.

This, like many things in life, is open to interpretation. I found it to be rather rude and completely out of context. After all, it was not directed toward you and you really had no reason to attack me for my question to someone else.

If you do not want to read my responses, or worse yet, become so offended to the simple information I offer, then I suggest simply not reading them and limiting your mind to only what you want to see.

Mine was a simple answer as to the choices one has. The reality of the situation. If you choose not to see it, then that's your choice. I simply pointed them out.

You still don't get it do, you? It is not the information you provided as much as the way in which you delivered it.

We all know this is a project we choose to do and we can all bow out an any time. That is not the point at all. Your choice of words and tone of delivery was completely out of line and totally uncalled for.

---