Hello everyone, We are tracking a recurring issue with our CAS service and are wondering if anyone in the community has experienced similar behavior.
Our environment is a single local Linux server. We originally deployed CAS v7.2.2 in May, and the system ran stably with no incidents until September. The issue has now occurred 4 times since September. Our CAS service will, on occasion, become completely unresponsive. Here are the characteristics we've noticed: - The outage consistently occurs during periods of low user activity (typically nights or weekends). - When it happens, the application stops responding to any requests, and no new entries are written to the application log file. - Once the system is in this state, a standard restart of the CAS service often gets stuck and does not complete successfully. - The only successful workaround we have found is to block all HTTP incoming traffic before attempting the service restart. - There are no obvious spikes in server resources (CPU, memory, disk, or network) when the incident occurs. We are actively investigating this issue with our UNICON consultant. Has anyone encountered this specific behavior, particularly the need to block inbound traffic to achieve a successful restart? Any shared experiences or guidance would be greatly appreciated. Thank you! -- - Website: https://apereo.github.io/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/4334c7e6-25c3-45dd-b45d-bc7e1c93636en%40apereo.org.
