If
the metadata server is not responding to client requests, follow these
steps:
-
Use one of the following
methods to stop the server:
-
Use the Metadata Manager in SAS
Management Console, or use the
metadata server script. In this situation, these are the preferred methods for
stopping the server.
-
(Windows only) If you cannot stop
the server using the Metadata Manager or the script, then stop the
Windows service. If you cannot stop the service, then use the Windows
Task Manager to stop the server process.
-
(UNIX only) If you cannot stop
the server using the Metadata Manager or the script, use one of the
following commands to stop the server process:
kill -2 server-process-id
kill -15 server-process-id
If the process fails
to stop, use the following command:
kill -9 server-process-id
For more information,
see “Exiting or Interrupting Your SAS Session in UNIX Environments”
in the
SAS Companion for UNIX Environments.
Verify that the process
has successfully stopped.
-
Review the entries in
the metadata server log to determine the cause of the problem. For
example, the log might indicate an issue in your operating environment.
By default, the log
is located in
SAS-configuration-directory/Lev1/SASMeta/MetadataServer/Logs. Your site might
have selected the option to write all server logs to a single directory,
such as
SAS-configuration-directory/Lev1/Logs.
If the log identifies
an issue in your environment, resolve the issue, if possible.
-
-
If you still cannot
start the server, review the log again and resolve any issues, if
possible.
-
If you are unable to
resolve the issue and start the server, you will need to use manual
steps to start it. You will then be able to use the metadata server
recovery facility to restore the server from a backup. For instructions,
see SAS Note 43649.
CAUTION:
If the
server cannot be started, do not attempt to re-initialize the server
or perform a recovery without reading SAS Note 43649.