Joined: 16 Dec 09
We have moved the scheduling server to another machine in
order to free up CPU and memory for the DB server. Active
clients will fail 10 times to connect to the old scheduling
server and then will self correct by contacting the master URL.
To force the correction right away, simply detach and then
(re)attach the project.
©2017 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.