Would it be possible to implement some process on another server that pings a keep-alive message on the scheduler. If no answer it would restart the scheduler process?
If this is not possible why not utilize the large community to restart the server remotely (if remotely possible)?
Would it be possible to implement some process on another server that pings a keep-alive message on the scheduler. If no answer it would restart the scheduler process?
If this is not possible why not utilize the large community to restart the server remotely (if remotely possible)?
Nice concept, but...
Matt had some discussion about UPS systems and the Seti servers a while back.
Unfortunately, it's not only the scheduling server itself that goes down, but could also be a number of other servers/processes that can go down and bring the whole thing to a halt. And if they go down in the wrong order, bringing everything back up in the right order often cannot be done by remote connection.
At least not with the remote power switching capability that exists in the server closet at this time.
And, due to security reasons, even if remote restart were possible, I don't think that ability would ever be given out to anybody in the Seti community.
____________
******
"Ask not, what your kitty can do for you. Ask what you can do for your kitty."