BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
sathya66
Barite | Level 11

Hi All,

Trying to access SAS 9.4 grid manager for platform via environment manager but can't see cluseter,hosts,jobs and ques info on the web page. See the screenshot below. How can we configure this. Everything is working except this.

 

 

sathya66_0-1679908791464.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
gwootton
SAS Super FREQ
This error is usually from an issue with the LD_LIBRARY_PATH setting in the SASServer14_1/bin/setenv.sh file missing the versioned path. Make sure your LD_LIBRARY_PATH looks like this (both common and lsf10.1 paths, $LD_LIBRARY_PATH at the end), restart SASServer14 see if the error persists.

LD_LIBRARY_PATH="$GUI_LIBDIR/common/linux-x86_64/:$GUI_LIBDIR/lsf10.1/linux-x86_64/:$LD_LIBRARY_PATH"
--
Greg Wootton | Principal Systems Technical Support Engineer

View solution in original post

14 REPLIES 14
doug_sas
SAS Employee

It could also be that PWS itself is having problems. You can check in the SASServer14_1 logs to see if that gives you any clues.

doug_sas
SAS Employee

This usually indicates that the Platform Web Services web app does not have access to the LSF cluster. Contact tech support to have them check out your deployment.

sathya66
Barite | Level 11
Do we need to run lsf services in Mid-tier or we just need an access to LSF Cluster ?
gwootton
SAS Super FREQ
The middle tier host must be configured as an LSF client, so you need to be able to successfully run LSF commands like lsid on the middle tier host for Platform Web Services (the web application that enables the SAS Grid Manger for Platform web application) to function
--
Greg Wootton | Principal Systems Technical Support Engineer
sathya66
Barite | Level 11

Mid-tier is configured as LSF client but when configuring Mid-tier , I haven't started lsf services . Is it an issue? or we must start the lsf services on mid-tier before configuring mid-tier?
I just started lsf services (ex:lim) but I can't see the cluster,hosts ,jobs,etc info on the web page.

gwootton
SAS Super FREQ
No, LSF clients do not run LSF services, but are able to submit jobs and run other LSF client commands. Are you able to run lsid on the middle tier host successfully?
--
Greg Wootton | Principal Systems Technical Support Engineer
sathya66
Barite | Level 11
yes, I can, see the results below

lsid
IBM Spectrum LSF Standard 10.X.X.X, Oct 16 2019
Copyright International Business Machines Corp. 1992, 2016.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

My cluster name is sas_cluster
My master name is hostname
Cluster in ISV mode : SAS
doug_sas
SAS Employee

It could be that the LSF environment profile (profile.lsf) has not been sourced in the PWS web app server. If the LSF environment variables are not set, LSF commands will not work.

sathya66
Barite | Level 11
LSF environment profile has sourced in PWS web apps server (checked my response file )
gwootton
SAS Super FREQ
You should check your server.log file and PlatformWebServices.log file for errors.
--
Greg Wootton | Principal Systems Technical Support Engineer
sathya66
Barite | Level 11
server.log.

2023-03-28 09:51:27,939 INFO (Catalina-utility-1) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/PlatformWebServices]] No Spring WebApplicationInitializer types detected on classpath
2023-03-28 09:51:28,612 ERROR (Catalina-utility-1) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/PlatformWebServices]] Exception sending context initialized event to listener instance of class [com.platform.pws.listener.StartupListener]
java.lang.UnsatisfiedLinkError: /data/Lev1/Web/WebAppServer/SASServer14_1/sas_webapps/platform.web.services.war/WEB-INF/lib/lsf10.1/linux-x86_64/liblsfservice.so: libsec_ego_default.so: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method) ~[?:1.8.0_252]
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934) ~[?:1.8.0_252]
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817) ~[?:1.8.0_252]
at java.lang.Runtime.load0(Runtime.java:810) ~[?:1.8.0_252]
at java.lang.System.load(System.java:1088) ~[?:1.8.0_252]
at com.platform.gui.pac.batchservice.LSFService.<clinit>(LSFService.java:103) ~[classes/:?]
at com.platform.gui.pac.batchservice.LSFServiceProxy.<init>(LSFServiceProxy.java:16) ~[classes/:?]
at com.platform.gui.pac.batchservice.LSFServiceProxy.getInstance(LSFServiceProxy.java:27) ~[classes/:?]
at com.platform.pws.util.NonShareHelper.<init>(NonShareHelper.java:94) ~[classes/:?]
at com.platform.pws.util.NonShareHelper.getInstance(NonShareHelper.java:227) ~[classes/:?]
at com.platform.pws.listener.StartupListener.contextInitialized(StartupListener.java:87) ~[classes/:?]
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4768) [catalina.jar:9.0.55]
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5230) [catalina.jar:9.0.55]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [catalina.jar:9.0.55]
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726) [catalina.jar:9.0.55]
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698) [catalina.jar:9.0.55]
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696) [catalina.jar:9.0.55]
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:690) [catalina.jar:9.0.55]
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1889) [catalina.jar:9.0.55]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_252]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_252]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_252]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_252]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_252]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_252]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:9.0.55]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
2023-03-28 09:51:28,616 INFO (Catalina-utility-1) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/PlatformWebServices]] Initializing Spring root WebApplicationContext
2023-03-28 09:51:30,706 ERROR (Catalina-utility-1) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/PlatformWebServices]] Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'synchronizeTask' defined in ServletContext resource [/WEB-INF/classes/spring-security-pac.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: Could not initialize class com.platform.gui.pac.batchservice.LSFService
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1619) ~[spring-beans-4.3.26.RELEASE.jar:4.3.26.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553) ~[spring-beans-4.3.26.RELEASE.jar:4.3.26.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481) ~[spring-beans-4.3.26.RELEASE.jar:4.3.26.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312) ~[spring-beans-4.3.26.RELEASE.jar:4.3.26.RELEASE]
gwootton
SAS Super FREQ
This error is usually from an issue with the LD_LIBRARY_PATH setting in the SASServer14_1/bin/setenv.sh file missing the versioned path. Make sure your LD_LIBRARY_PATH looks like this (both common and lsf10.1 paths, $LD_LIBRARY_PATH at the end), restart SASServer14 see if the error persists.

LD_LIBRARY_PATH="$GUI_LIBDIR/common/linux-x86_64/:$GUI_LIBDIR/lsf10.1/linux-x86_64/:$LD_LIBRARY_PATH"
--
Greg Wootton | Principal Systems Technical Support Engineer
AnandVyas
Ammonite | Level 13

Platform web services is a component that has to be deployed on SAS Mid-Tier node in one of the SASServerX_Y App servers. Once it's deployed and started, Mid-Tier node should be registered as a LSF client to the LSF Cluster so that it can query and run the necessary commands to display information on this UI.

Hope this helps!

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 14 replies
  • 4049 views
  • 7 likes
  • 5 in conversation