Authentication service service fails.

[MichaelMakushev]

Colleagues, this is not the first time a situation has arisen when the authentication service fails.
What do you think this may be connected with?
How can we directly monitor this service in order to respond more quickly to a failure?
What kind of service is this and where is it located in the structure of the SAS system?
Is there any way to manage it without restarting the entire system?

2019-08-04 09:00:04,952 INFO  [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - 2019-08-04 09:00:04,952: getting security manager
2019-08-04 09:00:04,952 INFO  [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - 2019-08-04 09:00:04,952: Logging in for user apprvsvc@saspw
2019-08-04 09:00:05,242 INFO  [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - 2019-08-04 09:00:05,242
2019-08-04 09:00:05,242 INFO  [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - Caught exception
2019-08-04 09:00:05,242 INFO  [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - IllegalStateException
2019-08-04 09:00:05,242 INFO  [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - Cause message is No services are available for: com.sas.svcs.config.client.UrlGeneratorInterface. Is a required process not started?
2019-08-04 09:00:05,243 ERROR [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - 2019-08-04 09:00:05,243: EXCEPTION
2019-08-04 09:00:05,243 ERROR [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - com.sas.analytics.crm.ma.launcher.ExecutionFacade:logon()
java.lang.IllegalStateException: No services are available for: com.sas.svcs.config.client.UrlGeneratorInterface. Is a required process not started?
	at com.sas.svcs.cluster.httpinvoker.AutoDiscoveredHttpService.invoke(AutoDiscoveredHttpService.java:471)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
	at com.sun.proxy.$Proxy268.generateInternalUrl(Unknown Source)
	at com.sas.ci.services.common.authentication.AuthenticationHelper.getAuthUrl(AuthenticationHelper.java:81)
	at com.sas.ci.services.common.authentication.AuthenticationHelper.logon(AuthenticationHelper.java:50)
	at com.sas.ci.services.common.services.CIJavaSession.loginRemoteSession(CIJavaSession.java:64)
	at com.sas.analytics.crm.ma.launcher.ExecutionFacade.logon(ExecutionFacade.java:223)
	at com.sas.analytics.crm.ma.launcher.ExecutionFacade.execute(ExecutionFacade.java:182)
	at com.sas.analytics.crm.ma.launcher.MALauncher.launch(MALauncher.java:596)
	at com.sas.analytics.crm.ma.launcher.MALauncher.wrappedMain(MALauncher.java:186)
	at com.sas.analytics.crm.ma.launcher.wrapper.WrappedLaunchCommand.run(WrappedLaunchCommand.java:42)
	at com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:17)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
	at java.lang.Thread.run(Thread.java:748)
2019-08-04 09:00:05,249 ERROR [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - Additional information: UserID = <apprvsvc@saspw> context = <TRK CM Business Context Subs>
...

2019-08-04 09:00:05,249 ERROR [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - com.sas.analytics.crm.ma.launcher.MALauncher:launch()
com.sas.analytics.crm.ma.launcher.client.LaunchException: 24 Unable to acquire security manager
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.logon(ExecutionFacade.java:289)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.execute(ExecutionFacade.java:182)
at com.sas.analytics.crm.ma.launcher.MALauncher.launch(MALauncher.java:596)
at com.sas.analytics.crm.ma.launcher.MALauncher.wrappedMain(MALauncher.java:186)
at com.sas.analytics.crm.ma.launcher.wrapper.WrappedLaunchCommand.run(WrappedLaunchCommand.java:42)
at com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:17)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: No services are available for: com.sas.svcs.config.client.UrlGeneratorInterface. Is a required process not started?
at com.sas.svcs.cluster.httpinvoker.AutoDiscoveredHttpService.invoke(AutoDiscoveredHttpService.java:471)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at com.sun.proxy.$Proxy268.generateInternalUrl(Unknown Source)
at com.sas.ci.services.common.authentication.AuthenticationHelper.getAuthUrl(AuthenticationHelper.java:81)
at com.sas.ci.services.common.authentication.AuthenticationHelper.logon(AuthenticationHelper.java:50)
at com.sas.ci.services.common.services.CIJavaSession.loginRemoteSession(CIJavaSession.java:64)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.logon(ExecutionFacade.java:223)
... 8 more
2019-08-04 09:00:05,249 ERROR [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - 24 Unable to acquire security manager
2019-08-04 09:00:05,249 ERROR [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - 24 Unable to acquire security manager
com.sas.analytics.crm.ma.launcher.client.LaunchException: 24 Unable to acquire security manager
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.logon(ExecutionFacade.java:289)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.execute(ExecutionFacade.java:182)
at com.sas.analytics.crm.ma.launcher.MALauncher.launch(MALauncher.java:596)
at com.sas.analytics.crm.ma.launcher.MALauncher.wrappedMain(MALauncher.java:186)
at com.sas.analytics.crm.ma.launcher.wrapper.WrappedLaunchCommand.run(WrappedLaunchCommand.java:42)
at com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:17)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: No services are available for: com.sas.svcs.config.client.UrlGeneratorInterface. Is a required process not started?
at com.sas.svcs.cluster.httpinvoker.AutoDiscoveredHttpService.invoke(AutoDiscoveredHttpService.java:471)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at com.sun.proxy.$Proxy268.generateInternalUrl(Unknown Source)
at com.sas.ci.services.common.authentication.AuthenticationHelper.getAuthUrl(AuthenticationHelper.java:81)
at com.sas.ci.services.common.authentication.AuthenticationHelper.logon(AuthenticationHelper.java:50)
at com.sas.ci.services.common.services.CIJavaSession.loginRemoteSession(CIJavaSession.java:64)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.logon(ExecutionFacade.java:223)
... 8 more
2019-08-04 09:00:05,249 INFO [CIAsyncExec-2432] [] [] om.sas.analytics.crm.ma.launcher.log.Log - 2019-08-04 09:00:05,249: FINISHED 
 

[Anand_V]

Hi @MichaelMakushev,

Could you please check if you SAS Web Application servers have started correctly?
You can navigate to <sas-config>/Lev1/Web/WebAppServer/SASServerX_X/logs/server.log for all the JVMs deployed in your environment and validate.
Mostly this service is deployed under SASServer1_1 and if there are issues during startup of this server, you can face many issues.

Once validated, if there are no error's found in the start-up of the server, please check what is the size of activemq data directory. It is under <sas-config>/Lev1/Web/activemq/ directory. Under the data directory you can also check the journal logs to see if there are any errors.

I think this will be a good starting point to start the troubleshooting and check for any errors.

To your question on monitor, you can setup an alert in SAS Environment Manager to notify in-case if any service failure. Here is an link with example to setup alerts.
http://support.sas.com/documentation/cdl/en/evug/69029/HTML/default/viewer.htm#p18n3hxpsz255zn1432pf...

Thanks!

[MAytymbe]

Hello,

I`m faced with this problem too.

Could you please share, how did you solve it?

Thanks

[Anand_V]

May be you can check if your problem is related to the one listed in this KB link? https://support.sas.com/kb/54/366.html