Seti Queue goes brain dead.

[Eponymous]

For some reason since about 10pm ALL my WU's are getting the following message from Berkeley:

3:41am: s@h_wrk Sending Result: SendRequest to shserver2.ssl.berkeley.edu failed: Invalid server response


Now the brain dead part: SETI Queue retries and retries to send the same "broken" WU over and over....
It won't skip it and go to the next one in the list.

Why won't it round robin on who to send out next?

I have a bunch of WU's to send but it is stuck on this broken one.

And I can't even go in and tell SETI Queue to skip it. Now I have to drive to work. Find the bastard.
Delete it. And restart SETI Queue.

:|

 

[aphoenixrises]

Wow wish I could help but I am having difficulties as well. I dumped everything and reloaded seti then went with GlI and instead of the queue I downloaded seti monitor from zdnet. This downlaod has worked where the queue downlaod would not for me.
Wonder if anyone else here is using it? So far so good. But when the connections get bad again well see.