July 21, 2004

"The log files are currently being compressed, after thats done the project should return to normal."

Sorry double post

At least they are working on it, as the server is sometimes down.

Let's hope it's getting better (many CPU's waiting for work)
> The announcement above was posted 7 hours ago and I must admit you were
> absolutely right. Everything is back to normal!!!
> Hydnum Repandum </br>
> Open SETI Initiative
>

Thank you

Hydnum.Repandum needs a good old fashioned "shut up."

Shut up.

?

And repeating yourself adds to your abnormality, how?
----------------------
Jordâ„¢

?

Can we please please have some abnormality? I have not seen a single w/u for 3 days! Do you really need 24h for compressing some database logs?
Hydnum Repandum
==========

Whats so abnormal about that, thats been pretty much the norm for a lot of people ... And from looking at your Credits it looks like you have gotten more than your fair share of WU's since the Project went Live ...

It really would be nice if they(the seti team)would post more news on the homepage about what is going on. Then we would not have to speculate about what is happenning. I don't mind being patient as long as I know why!!!



My operat~1 system unders~1 long filena~1 , does yours?

They should set up webcams so we can SEE if they are fixing the problems or just playing solitare and having a coffee!

^ Click Here ^ ^ Click Here ^ ^ Click Here ^

I know people complained about Classic not being updated much. It went months and months between updates. Now we get fairly frequent updates on the main page, although maybe not quite as much as we might like, but it is 20 steps in the right direction. Plus Rom and I think at least one or 2 other developers have posted on the message boards responding DIRECTLY to us about what was going on. Rom has done this a lot. To me that goes a lot further than just putting general status messages on the home page. It's hard to ask for too much more, especially considering the more time they spend coddling our every demands to know what is being done at every moment is less time they spend working on stuff.

The reason is that there are things that they have work to do. That is reason enough to be patient.

And as far as those log files go, I don't know how big they are, but considering the amount of activity this project has seen I would imagine they are quite large. And if any of you have tried compressing files in the gigabyte range and above at the highest compression levels and methods, then you know that it can take hours and hours. About the time they posted that message the web page started responding very slowly and continued to do to until sometime into the evening and night. Sometime though, through course of last night and the speed of this site shot up through the roof and it has been responding fast ever since. So although I cannot be sure, I am inclined to believe that the slowdown yesterday was due to that compression and it was finished when the website responded normally again. Just conjecture, but it makes sense.

Chris


> It really would be nice if they(the seti team)would post more news on the
> homepage about what is going on. Then we would not have to speculate about
> what is happenning. I don't mind being patient as long as I know why!!!
>
>
>
> My operat~1 system unders~1 long filena~1 , does yours?
>
>
>

If it is responding normally again, why am I getting this?

SETI@home - 2004-07-22 15:40:12 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-22 15:40:54 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-07-22 15:40:54 - No schedulers responded
SETI@home - 2004-07-22 15:40:54 - Deferring communication with project for 2 hours, 32 minutes, and 48 seconds


I have not got any work for a few days but the No schedulers responded message is new for me today





My operat~1 system unders~1 long filena~1 , does yours?

It means the schedulers aren't responding for some reason. Could be busy. Could be offline. Can't tell you specifically. I've gotten it fairly often the last couple of days. I've also goten no work available a lot. I've also downloaded 2 or 3 workunits and my computers still continue to process. Although one hasn't finished it's cache because it keeps restarting on me so BOINC doesn't run until I get home at like midnight to logon and restart it again, but oh well. :)

Chris

> If it is responding normally again, why am I getting this?
>
> SETI@home - 2004-07-22 15:40:12 - Sending request to scheduler:
> http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
> SETI@home - 2004-07-22 15:40:54 - Scheduler RPC to
> http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi failed
> SETI@home - 2004-07-22 15:40:54 - No schedulers responded
> SETI@home - 2004-07-22 15:40:54 - Deferring communication with project for 2
> hours, 32 minutes, and 48 seconds
>
>
> I have not got any work for a few days but the No schedulers responded message
> is new for me today
>
>

One of my Boinc computers likes to restart itself occasionally, but I have a keyboard and mouse plugged in so it'll just boot back up, set so it'll just go into windows and start where it left off :)

Well the computer that restarts itself is the one that has the keyboard and mouse. It just doesn't always have me to there to get it back into Windows so it can happily go back to processing. The one without the keyboard, mouse, and everything else (except the network card which it actually needs) also boots up just fine if it needs to and I can use one computer to log the other one on. But I so rarely have to do that it doesn't really matter. :)

My main concern is recovering data from what appears to be a bad hard drive that I used as a backup drive while reformatting and reinstalling windows on another computer. If I can ever get that done I try fixing it with a low level format. Then once I have another working hard drive I can resurect another computer for SETI and Bryce.

Chris



> One of my Boinc computers likes to restart itself occasionally, but I have a
> keyboard and mouse plugged in so it'll just boot back up, set so it'll just go
> into windows and start where it left off :)
>
>