If SAS^® Metadata Server fails to start, review the SASMetadataServer*.log file for the following fatal errors:

2015-02-12T12:11:25,652 FATAL [00000013] :sas - Could not load any GSSAPI libraries. Ensure that the dynamic loader 
contains path configurations for the location of your library.
2015-02-12T12:11:25,652 FATAL [00000013] :sas - tksecgss_dl_init failed completely.

The fatal errors in the log indicate that SAS Metadata Server searched for, but did not find, the libgssapi_krb5.so library, which is typically located in the /lib64 directory. Libgssapi_krb5.so is a library from Massachusetts Institute of Technology (MIT)/Kerberos that helps ensure secure communications. The Generic Security Services Application Programming Interface (GSSAPI) enables applications to use Kerberos 5 or other security mechanisms in their communications. For more information, see MIT Kerberos Documentation.

To fix the issue, you must provide a resolvable path to libgssapi_krb5.so. Follow these steps to provide the correct path:

1. Log on as the root user and create a link to the actual library by submitting the following commands:
   
   # cd /lib64 # ls /lib64/libgssapi_krb*
   The commands generate output similar to this:
   /lib64/libgssapi_krb5.so.x /lib64/libgssapi_krb5.so.x.x
2. Review the output that is generated and locate the library with a number extension that matches the x.x number extension shown in the example above.

Note: Because the output does not return a file named libgssapi_krb5.so, which is the file that SAS Metadata Server searches for, you receive the fatal errors.

3. While in the same directory as Step 1 (/lib64), submit the following command to create a link to libgssapi_krb5.so.x.x (x.x is the number from the output in Step 1):
   
   # ln -s libgssapi_krb5.so.x.x libgssapi_krb5.so
4. Start SAS Metadata Server by submitting the following invocation command:
   
   SAS-configuration-directory/Lev1/SASMeta/MetadataServer/MetadataServer.sh start
5. Review the SASMetadataServer*.log file to confirm that SAS Metadata Server starts and that fatal errors are eliminated.
6. If you are working with a metadata cluster, repeat Step 3 to create the required link. Then, start SAS Metadata Server one node at a time by submitting the command in Step 4.
   

Note: After you start the second node, your cluster should be available online.

Operating System and Release Information