Skip to content

Failed To Start SAS Metadata: UNABLE TO OPEN/READ MESSAGE FILE USING THE -MSG PATHSERROR

Problem Statement
SAS Metadata Failed To Start on Linux machine running on GFS2.

Error message
-sh-4.1$ /sasconfig/Meta/meta3/Lev1/SASMeta/MetadataServer/MetadataServer.sh -start
Waiting up to 600 seconds for Metadata Server to listen to port 8561.
Server is started (pid 8529)...
Server is stopped
Log files are located at: /sasconfig/Meta/meta3/Lev1/SASMeta/MetadataServer/Logs

Metadata server failed to start, check the log for errors.
Log files are located at: /sasconfig/Meta/meta3/Lev1/SASMeta/MetadataServer/Logs

From appliation log (/sasconfig/Meta/meta3/Lev1/SASMeta/MetadataServer/Logs/SASMeta_MetadataServer_console_sastestmetacl01.log):
UNABLE TO OPEN/READ MESSAGE FILE USING THE -MSG PATHSERROR: File is locked, but no other information is available. File =/sas94/sashome/SASFoundation/9.4/sasmsg/msgdir.msg. System Error Code = 38.

Solution

  • Stop all NFS-related services
  • Stop GFS2 service and ensure all filesystems unmounted on all servers
  • Start GFS2 service on all servers
  • Start SAS application

Reference

Conclusion
File locking is causing the issue. Thus, I need to clear the locking by restarting NFS & GFS2 service which the filesystems are used by SAS Metadata application.

Comments

Post a Comment

Your email is never published nor shared. Required fields are marked *