Hi,
I'm using a linux machine, but I'm pretty sure this is not OS specific so I'm posting a link here in case anyone has a similar problem or a solution:

http://setiathome.berkeley.edu/forum_thread.php?id=61681

If you think you may be able to help I'd be extremely grateful since I have a huge number of completed WUs which are starting to pass their deadlines but cant be uploaded.

---

Uploading doesn't use the scheduler, so that should work without a problem. You won't be able to report or download new work, as those processes do use the scheduler, and according to the server status page, the scheduling server is down.
Uploading merely transfers data from your hard drive to a hard drive at Seti.

The message is somewhat self-explanatory: "Scheduler request failed". As in we cannot contact the scheduler. There's not much you can do about that, but have patience and wait until it is available. Do know that everyone has this problem. It's not just you.

What's the cause? Well, hardware woes, what else? ;-)

---

ok, thanks. I'll just keep waiting then.

I was concerned as it has been having this problem (number or redirects hit maximum amount) for some time now and had never had it before during the scheduled server outages.

I was concerned as it has been having this problem (number or redirects hit maximum amount) for some time now and had never had it before during the scheduled server outages.

I don't get that message any longer. Did you meanwhile reboot that machine (or otherwise flush the TCP/IP stack/DNS buffer)? There's been some shuffling around of machines and IP addresses at the server side.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Ah, superb. I've just restarted and no longer get the 'redirects hit maximum' error, just the standard 'Couldn't connect to server' due to the scheduled downtime. Hopefully the WUs will now send when the servers re-open on Friday. I guess the server IPs must have changed during the longer downtime a couple of weeks back and I needed to restart to clear the DNS cache.

Thanks for the help!