Hey all, I experienced a problem today with Visual Analytics, after I was notified by end-users that they could no longer log-in to the Visual Analytics web interface. I tried myself to login, but the webpage would just sit there waiting for a response from the server after I clicked 'Submit'. I could not rectify this problem until I restarted all the SAS servers (using the sas.servers shell script - we are running SAS on Linux). After the SAS servers restarted, I was then able to login without any issue. Naturally, the first place I started to look was the logs. Below are a couple excerpts from log files: /opt/sas94/config/Lev1/Web/Logs/SASServer1_1/SASLogon9.4.log: 2019-03-28 13:20:46,724 [tomcat-http--9] ERROR com.sas.svcs.security.authentication.tickets.TicketsController - error.authentication.credentials.bad org.jasig.cas.ticket.TicketCreationException: error.authentication.credentials.bad 2019-03-28 14:52:13,541 [tomcat-http--17] ERROR com.sas.svcs.security.authentication.tickets.TicketsController - service.not.authorized org.jasig.cas.services.UnauthorizedServiceException: service.not.authorized 2019-03-28 14:57:48,033 [tomcat-http--37] ERROR org.jasig.cas.util.HttpClient - Read timed out java.net.SocketTimeoutException: Read timed out 2019-03-28 15:04:57,975 [tomcat-http--42] ERROR com.sas.svcs.security.authentication.web.ServiceValidateController - TicketException generating ticket for: [callbackUrl: http://---.---.--:7980/SASVisualDataBuilder/j_spring_cas_security_proxyreceptor] org.jasig.cas.ticket.TicketCreationException: error.authentication.credentials.bad /opt/sas94/config/Lev1/Web/Logs/SASServer1_1/SASWorkflowServices9.4.log: 2019-03-28 14:29:36,073 [localhost-startStop-11] WARN [unknown] com.sas.services.session.SessionContext - Forced destruction of the session context by the Session Service. Session Context=c6e9db05ebcb3989:8c0b137:169410bff6b:-5a77 2019-03-28 14:29:36,090 [localhost-startStop-11] WARN [unknown] com.sas.services.session.SessionContext - Forced destruction of the session context by the Session Service. Session Context=c6e9db05ebcb3989:8c0b137:169410bff6b:-5a74 2019-03-28 14:37:11,094 [localhost-startStop-12] WARN [unknown] com.sas.services.session.SessionContext - Forced destruction of the session context by the Session Service. Session Context=0984e9a11770c629:36ef812a:169c591ffbf:-552c 2019-03-28 14:37:11,104 [localhost-startStop-12] WARN [unknown] com.sas.services.session.SessionContext - Forced destruction of the session context by the Session Service. Session Context=0984e9a11770c629:36ef812a:169c591ffbf:-5529 2019-03-28 15:00:27,562 [localhost-startStop-12] WARN [unknown] com.sas.services.session.SessionContext - Forced destruction of the session context by the Session Service. Session Context=aa6521b502c3500d:-cf6827e:169c5a2f91e:-5a9e 2019-03-28 15:00:27,578 [localhost-startStop-12] WARN [unknown] com.sas.services.session.SessionContext - Forced destruction of the session context by the Session Service. Session Context=aa6521b502c3500d:-cf6827e:169c5a2f91e:-5aa1 The logs from 'SASLogon9.4.log' seem suspect to me. From what I've gathered through pure observation, the following URL that it mentions is the address that credentials are sent to when you click 'Submit' when logging in and from the looks of it, it generates some sort of authentication ticket. That appears to be, if not the cause of the problem, at least a symptom: http://---.---.--:7980/SASVisualDataBuilder/j_spring_cas_security_proxyreceptor Does anyone have any idea what may have been the problem? Any ideas or other places to look (log files) would be greatly appreciated! Thanks!
... View more