To assist
in troubleshooting, alternative logging configuration files are provided
for some servers, including metadata servers, OLAP servers, pooled
workspace servers, stored process servers, and workspace servers.
These configuration files, which are named logconfig.trace.xml, provide
high-level logging messages (for example, DEBUG and TRACE messages)
which can be used by SAS Technical Support to help resolve server
issues. The messages are written to the server's rolling log file.
Note: The workspace server is not
initially configured to produce a log file. However, the alternative
logging configuration file creates a rolling log file for this server
for troubleshooting purposes. For details, see
Create a Log File for Workspace Server Troubleshooting.
If SAS Technical Support
requests that you enable detailed logging for server troubleshooting,
follow these steps:
-
Stop the server, if
it is running (for example, if you are enabling detailed logging for
a metadata server or OLAP server).
CAUTION:
Stopping
the metadata server stops other components, including object spawners,
OLAP servers, SAS/CONNECT spawners, and SAS/SHARE servers.
-
Rename the server's
logconfig.xml file to logconfig_orig.xml.
-
Rename the server's
logconfig.trace.xml file to logconfig.xml.
-
Restart the server if
necessary (for example, if you are enabling detailed logging for
a metadata server or OLAP server).
-
When troubleshooting
is completed, stop the server if it is running, rename logconfig.xml
to logconfig.trace.xml, rename logconfig_orig.xml to logconfig.xml,
and restart the server if necessary.
CAUTION:
Do not
use or modify the logconfig.trace.xml logging configuration files
unless you are requested to do so by SAS Technical Support.
Performance issues
can result from the use of these files.