These log messages are the result of some external process contacting CAS incorrectly. For example, trying to establish a binary connection to the CAS server on the HTTP port (8777) instead of the binary port (5570), or a port scanner just trying to connect on every port on a given server to see what ports are open for security testing. Do you see the errors in places where the downtime did not occur? If these are causing your CAS server to go down, you should identify where those errant connections are coming from and put a stop to them. You could probably turn up the logging on the CAS server to get some more information on where those connections are coming from. That said, I'm not sure these connections are the cause of the downtime, so you may wish to engage SAS Technical Support.
... View more