Administering Logging for SAS Servers |
To assist in troubleshooting, alternative logging configuration files are provided for some servers, including metadata servers, OLAP servers, pooled workspace servers, stored process servers, table 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).
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.
Note: You can also adjust logging dynamically by using the Server Management features of SAS Management Console. See Using SAS Management Console to Monitor SAS Servers.
Performance issues can result from the use of these files.
Copyright © 2011 by SAS Institute Inc., Cary, NC, USA. All rights reserved.