Error: VA 7.3 - Can't start LASR server - Authentication server error

[GertNissen]

Hi all VA System Admin Experts 😉

Would very much appreciate your input on this matter, as our VA environment has been down since friday - has been runnning fine for long ;-(

Environment: VA 7.3 SMP on Windows server 2012R2, all SAS Windows services are running

2 LASR servers

• LASR Analytic Server – sasvasmp (DOWN)
• Public LASR Analytic Server – sasvasmp (RUNNING)

Error: Can't start LASR (public can start)

When run in SAS Display Manager

1 libname ml sasiola startserver=
2 (
3 PATH="D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator
3 ! \sigfiles"
4 LOGGING
5 )
6
7 host="sasvasmp.XXXX.net" port=10010
8 signer="http://sasvasmp.XXXX.net:80/SASLASRAuthorization"
9 ;
NOTE: No tag was specified in the LIBNAME statement. The default tag (WORK) is used to name and
identify tables in the LASR Analytic Server. You can specify a tag as a data set option.
ERROR: Unable to register LASR server with authentication service.
ERROR: Libref ML is not assigned.
ERROR: Error in the LIBNAME statement.

Logfiles:   

\SAS\Config\Lev1\Web\Logs\SASServer12_1\SASLASRAuthorization7.3.log

Only "Error delegating 'createClob' call"

\SAS\Config\Lev1\Web\Logs\SASServer12_1\SASVisualAnalyticsViewer7.3.log

[VIEWER ] ERROR [tomcat-http--36] 2019-07-23 07:14:14,725 [ST-917-5JYwqIYtiZf4gWADWIWP-cas:TIGR] com.sas.bidata.error.DataErrorHandler - AuthorizationFailure
com.sas.lasr.LASRAuthorizationException: ERROR: The signature is not valid, access denied.

Signon to http://sasvasmp.XXXX.net:80/SASLASRAuthorization is working for my user (AND Public LASR is starting with auth enabled)

If LASR Authorization Service is removed in SMC, 

it will start the LASR server but all data is inaccessible (Error: Datasource has no content or is not available in memory)

SAS Note 

http://support.sas.com/kb/52/315.html

D:\SAS\Config\Lev1\Web\activemq\data has been deleted, with no effect

Signature files

SAS Note: http://support.sas.com/kb/51/624.html

D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles

From: LASR.2592927925.0.saslasr.log

ID=1,PID=20476,SASTime=1879493636.3,Time=Tue Jul 23 09:33:56 2019,User=gnis,Host=SASVASMPPRD,LASRServer=D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles\/_T_9A8CF0A6_5837BA8/LASR.2592927925.0.saslasr,Port=10010,RawCmd=action=ServerInfo,ExeCmd=action=ServerInfo,JnlMsg=,StatusMsg=Command successfully completed.,RunTime=        0.00

ID=2,PID=20476,SASTime=1879493636.3,Time=Tue Jul 23 09:33:56 2019,User=gnis,Host=SASVASMPPRD,LASRServer=D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles\/_T_9A8CF0A6_5837BA8/LASR.2592927925.0.saslasr,Port=10010,RawCmd=action=ServerVersion,ExeCmd=action=ServerVersion,JnlMsg=,StatusMsg=Command successfully completed.,RunTime=        0.00

ID=3,PID=20476,SASTime=1879493636.4,Time=Tue Jul 23 09:33:56 2019,User=gnis,Host=SASVASMPPRD,LASRServer=D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles\/_T_9A8CF0A6_5837BA8/LASR.2592927925.0.saslasr,Port=10010,RawCmd=action=Terminate,ExeCmd=action=Terminate,JnlMsg=,StatusMsg=Command successfully completed.,RunTime=        0.00

From: LASR.2523228033.0.saslasr.log

ID=1,PID=20548,SASTime=1879423936,5,Time=Mon Jul 22 14:12:16 2019,User=gnis,Host=SASVASMPPRD,LASRServer=D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles\/_T_9665677B_237D7E48/LASR.2523228033.0.saslasr,Port=10010,RawCmd=action=ServerInfo,ExeCmd=action=ServerInfo,JnlMsg=,StatusMsg=Command successfully completed.,RunTime=        0,00

ID=2,PID=20548,SASTime=1879423936,5,Time=Mon Jul 22 14:12:16 2019,User=gnis,Host=SASVASMPPRD,LASRServer=D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles\/_T_9665677B_237D7E48/LASR.2523228033.0.saslasr,Port=10010,RawCmd=action=ServerVersion,ExeCmd=action=ServerVersion,JnlMsg=,StatusMsg=Command successfully completed.,RunTime=        0,00

ID=3,PID=20548,SASTime=1879424161,7,Time=Mon Jul 22 14:16:01 2019,User=gnis,Host=SASVASMPPRD,LASRServer=D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles\/_T_9665677B_237D7E48/LASR.2523228033.0.saslasr,Port=10010,RawCmd=action=ServerVersion,ExeCmd=action=ServerVersion,JnlMsg=,StatusMsg=Command successfully completed.,RunTime=        0,00

[alexal]

@GertNissen ,

That message about createClob can be ignored. It feels like the SAS session cannot reach the LASR authorization service. On your compute server create D:\http_logger.xml (I hope you have access to write files to D:\) with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<log4sas:configuration xmlns:log4sas="http://www.sas.com/rnd/Log4SAS/" debug="true">
   <appender class="FileAppender" name="File">
      <param name="File" value="D:\out.log" />
      <param name="Append" value="false" />
      <param name="ImmediateFlush" value="true" />
      <layout>
         <param name="ConversionPattern" value="%d %-5p %c [%t] %X{Client.ID}:%u - %m" />
      </layout>
   </appender>
   <logger name="App.tk.HTTPC">
      <level value="TRACE" />
   </logger>
   <logger name="HTTP">
      <level value="TRACE" />
   </logger>
   <logger name="Perf">
      <level value="Error" />
   </logger>
   <logger name="App">
      <level value="Debug" />
   </logger>
   <logger name="App.Program">
      <level value="Debug" />
   </logger>
   <logger name="Audit.Authentication">
      <level value="Error" />
   </logger>
   <root>
      <level value="error" />
      <appender-ref ref="File" />
   </root>
</log4sas:configuration>

Start the workspace server using a command shown below:

D:\SAS\Config\Lev1\SASApp\WorkspaceServer\WorkspaceServer.sh -logconfigloc D:\http_logger.xml -nodms

Try to start the LASR server and show me SAS log from a console as well as D:\out.log:

libname ml sasiola startserver=( PATH="D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles" LOGGING ) host="sasvasmp.XXXX.net" port=10010 signer="http://sasvasmp.XXXX.net:80/SASLASRAuthorization";

[GertNissen]

Thanks @alexal 

Not sure if I'm following your steps correctly?

I don't have write access to 😧 but changed to K: in XML code

Submitted the start Workspace server on CMD (pointing to k:\)

D:\SAS\Config\Lev1\SASApp\WorkspaceServer\WorkspaceServer.bat -logconfigloc K:\http_logger.xml -nodms

Submitted the LASR start code from EG (connected to sasvasmp)

But I dont think I'm hitting the 'new' Workspaceserver ??

No output (or file) in k:\out.log ?

[GertNissen]

Still struggling with understanding the problem and finding a solution 

Found these, perhaps it would help investigation...

Like Public LASR can start, also Env Lasr can start - only 'LASR' that can't start

D:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\sigfiles\

ERROR: The LASR Analytic Server image does not contain any tables.

[GertNissen · Accepted solution]

oouupps ;-( sorry

We found the error, and it was actually visible in my first screen shot - well hidden behind the grey overlay.

Somehow we managed to get a third (unknown origin) LASR server using the same port as our existing LASR server.

Not 100% sure where it came from, but bravely (aka desperate) deleted the new unknow LASR server and now our "old" LASR starts again, autoload works again and the users have confirmed everything is working 🙂

That might explain why Public LASR, EnvMan LASR was working, while only LASR LASR was not.