Can't send WU to Seti server

[Ben98SentraSE]

Had one box running and it said Unknown fatal error 1. Tried it on this box and it does the same thing. Ideas?

 

[A5]

I think the servers are down. I'm getting error -20;0

 

[Ben98SentraSE]

A second box just tried to send a WU and it can't either. Anybody know how to specifically test to see if the Berkeley server that receives results is down?

 

[artemedes]

yep, hope it is temorary.

Do you use any kind of caching program?

other thread:disgust:

 

[Ben98SentraSE]

I tried to setup SetiQueue yesterday but it ain't workin. I have a thread about it in the dist. forum recent...

 

[Ben98SentraSE]

Anybody know what the Seti server's names are so you can test to see if their up with normal network commands?

 

[Ben98SentraSE]

This is the first time this has happened for me. About how often does it happen?

 

[artemedes]

Did you check this page out when you were setting your Setique up? It helped me a lot.

The server doesn't go down very often, and they usually notify us when the have to take it down. The real problem is that is alway longer than they predict and is usually measured in terms of days, not hours. I have my qs' set up to cache a min. of 4 days work. I really like the setiq.log file too. I havn't regretted learning to use it yet.

 

[artemedes]

Forgot to mention that since you have such a nice number of home machines, you only need to set up the caching program on one. (I am assuming that they are networked together) Then the log file will give you completion times for each computer. The only computer that should give you trouble is the one that has both Setiq and S@H running, and that is the only computer that may need to be patched.

 

[Ben98SentraSE]

On that page I am confused by the following:

4. In windows explorer go to the SETIQ directory and make a copy of Wsockhk.dll and call it Wsk2hk.dll
5. Copy both of these to your SETI directory (I use c:\program files\seti@home)

"These" refering to Wsockhk.dll and Wsk2hk.dll? That's what I took it as.

6. Copy Wsockhk.txt from c:\program files\seti@home\setiq to c:\program files\seti@home
7. Next you will need to Edit c:\program Files\seti@home\setiq\Wsockhk.txt, for my setup it should look like this:

Ok, so literally that means to the c:\program files\seti@home\Wsockhk.txt should be unchanged- like the default when you download it? But then c:\program Files\seti@home\setiq\Wsockhk.txt should look different than it????

Step 10 is also repetitive. The very first paragraph says the same thing as the rest of them do.

Also at the top of this page it says he uses port 80 but at the bottom it says he uses port 5512. I've been trying 5512.

Very confusing page

 

[Michael]

If you're running setiq on a LAN machine, you shouldn't have to modify the file.

Michael

 

[TuffGuy]

damn...unknown fatal error 1...seti crash...no retry...damn...

 

[ColinP]

Hi Ben, I wrote that section, what do you mean it's repetetive ???

Hi Ben, I wrote that section, what do you mean it's repetetive ???



You have one machine running SETIQ, it points out to the main S@H servers.
If you have a proxy server point it at that through the QSETI.txt file.
Otherwise it should automatically pick up dial up networking or however else you connect to the internet. You don't have to worry about the wsockhk.dll files if you point the S@H client on the SETIQ machine back to itself port 5512.
All your other machines point at the SETIQ machine port 5512.

Does that help at all ?

get back to me if you need more help,

cheers,

Col.