seti connection error? "No such file or directory"

[RigorousT]

Here's what I get using the text client (setiathome-3.03.i386-winnt-cmdline.exe) :

SETI@home was developed by David Gedye (Founder),
David Anderson (Director), Dan Werthimer (Chief Scientist),
Leonard Chung, Hiram Clawson, Jeff Cobb, Charles Congdon, Charlie Fenton,
Kyle Granger, Eric Heien, Mike Hill, Michael Kang, Eric Korpela,
Matt Lebofsky, Peter Leiser, Brad Silen, Woody Sullivan, and Adam Wight.

Sending result - connecting to server.
connect: No such file or directory
Can't connect to server; will retry in an hour.

Usually I don't pay attention much after it completes a work unit. Any idea what's going on here?

I'm relatively new to the team.. it's been running fine for the past week.

I think it finished a work unit and tried to send it, but must have had some trouble. Did it corrupt the file? What's up?

Thanks,

RT /(corky)

[edit: added file name I was using, incase that matters]

 

[Poof]

Looks like access to the server is down - here's a quote from the front page of the SETI website:

"Outage alert: There will be a one-hour outage on February 21, 2001, starting at 14:00 GMT. Campus will be installing new networking hardware during this time".

This is why we have caching programs!

 

[RigorousT]

Doh! Good call, Thanks Poof By caching programs, do you mean a proggie like SetiQ? Will something like that integrate with the text client I'm running?

RT

 

[Poof]

Yes to both questions. Setiqueue is one caching program that is best if you have a bunch of machines that need WUs. Setidriver is best for individual machines. And both work with the text client (although I'm not sure if the new Setiqueue can also handle the GUI or not), so you would be all set!

 

[RigorousT]

Cool, I'll check into that!

The SETI servers is back up now, too...

RT

 

[Assimilator1]

yes it does work with the GUI version