Architecting, installing and maintaining your SAS environment

Unable to start Metadata Services SAS 9.4

Accepted Solution Solved
Reply
Occasional Contributor
Posts: 14
Accepted Solution

Unable to start Metadata Services SAS 9.4

Hello Gurus,

 

We are running SAS 9.4 M2 version hosted on Red Hat Linux OS. We were are facing issue with starting the Metadata services. Getting the error as:

 

Log Name : SASMeta_MetadataServer_console.log

NOTE: The tcpSockRead call failed. The system error is 'The connection was reset by a peer.'.
ERROR: Could not find extension: (tkcache)

Any clues or advice on how to fix this.

 

Regards,

Sudipta.


Accepted Solutions
Solution
‎05-12-2016 09:55 PM
Occasional Contributor
Posts: 14

Re: Unable to start Metadata Services SAS 9.4

Posted in reply to sudipta_goswami

To All,

 

Tech Support helped us on working on this. During the upgrade the server side usage version got changed which casued the issue.

 

This is now fixed.

 

Thanks to Tech Support.

View solution in original post


All Replies
Trusted Advisor
Posts: 1,307

Re: Unable to start Metadata Services SAS 9.4

Posted in reply to sudipta_goswami

Hi,

 

I would align with SAS technical support for this. Specially if it is a Production environment.

 

In the meantime you can:

 

1- the tk errors are generally (not always, related to problem of libraries for SAS Foundation.

 

You could check this by running the SAS Operational Qualification Tool on your Metadata Server https://www.google.nl/url?sa=t&source=web&rct=j&url=https://support.sas.com/documentation/installcen...

If so,

 

Check if you un-installed or updated a library that is part of SAS pre-requisites. If you get the list of the currently installed libraries with you, and you compare the list with SAS foundation system requirements.

 

2- either way, you will need some additional information of the error, by stopping your metadata service, extending the logs if your metadata server to a DEBUG level, then starting it again, and you will be able to see additional information

Occasional Contributor
Posts: 14

Re: Unable to start Metadata Services SAS 9.4

Posted in reply to JuanS_OCS

Hello Juan,

 

How do I enable the Debug Level loggin for the Metadata server. Can you please share the procedure in doing it.

 

Regards,

Sudipta.

Trusted Advisor
Posts: 1,307

Re: Unable to start Metadata Services SAS 9.4

Posted in reply to sudipta_goswami

Hi,

 

on the metadata server, under the config/LevN/SASMeta/MetadataServer you should be able to find some configuration files named as logconfig.xml, logconfig.apm.xml, logconfig.trace.xml. Those files describe how the logging is configured on your SAS service.

 

If none of them are referenced under the sasv9.cfg or sasv9_usermods.cfg files, then the logconfig.xml is the one by default and the one you will need to modify.

 

Enable More Detailed Logging for Server Troubleshooting: http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#p0hchigzq8wvtrn1tnll...

 
To increase the logging level
    0. make a copy of your logconfig.xml
  1. Open the spawner's logconfig.xml file, and locate the following lines:
    <logger name="XXX"> 
       <level value="Info">
    </logger>
  2. Change <level value="Info"> to <level value="Debug">
  3. Restart the service.
     
     

 

 

 

Occasional Contributor
Posts: 14

Re: Unable to start Metadata Services SAS 9.4

Posted in reply to JuanS_OCS

Hi Juan,

 

I didn't find any spawner's logconfig.xml file under config/LevN/SASMeta/MetadataServer/.

 

Also today I observed one more log entry at SASMeta_MetadataServer.log

 

ERROR [00000008] :sas - The server definition has a usage version of 2.0.  The server can only load definitions less than version 2.0.0.

 

Is there any way we can know from where the metadata server is attempting to load the server definition.

 

regards,

Sudipta. 

Solution
‎05-12-2016 09:55 PM
Occasional Contributor
Posts: 14

Re: Unable to start Metadata Services SAS 9.4

Posted in reply to sudipta_goswami

To All,

 

Tech Support helped us on working on this. During the upgrade the server side usage version got changed which casued the issue.

 

This is now fixed.

 

Thanks to Tech Support.

☑ This topic is solved.

Need further help from the community? Please ask a new question.

Discussion stats
  • 5 replies
  • 1681 views
  • 0 likes
  • 2 in conversation