How To Clear Log In Sas

SAS administrators are faced with multiple challenges in society to keep SAS environments running optimally. In an platonic world, an ambassador would just need to focus on maintaining a healthy environment through standard best practices. Unfortunately, the reality is that things tin can and exercise go incorrect.

At this point, everyone looks to the SAS admin and in turn, we look to our best friends, the multitude of logs that are created by the SAS platform. In one case you open the log file, you can begin with the basics of searching for 'ERRORS' to get your troubleshooting going. While the default logging levels provide a substantial amount of information, we also have the ability to modify these levels to adapt the amount of information gathered in SAS logs.

When information technology comes to troubleshooting, the logs that yous seek out will ultimately be the ones most relevant to your current event. I can't sit hither and signal you to a golden log that will solve all your bug, just what I did want to go over are a few of import ones that tin exist critical to a properly running surroundings. Note that the log paths listed will be for Windows environments.

Metadata server log

The metadata server is where it all begins. Information technology allows a centralized location for storing data used past the various SAS applications as well as users and groups and their access levels to the organization. It is the most disquisitional part of the SAS platform, and then information technology is merely natural that we want to kickoff with the Metadata server and ostend it is upwards and running without errors. Nosotros can find the Metadata log in the post-obit path:

Configuration-directory\SASMeta\MetadataServer\Logs

Two examples when yous would seek out these item logs are if the Metadata server failed to start or when a user is continually being prompted for credentials, which leads to authentication errors. If the logs are not providing enough information, you can at present conform logging levels by post-obit this SAS note: https://support.sas.com/kb/51/911.html

When information technology comes to logs, one aspect to exist aware of when changing logging levels is that while you gain the do good of additional data, it too comes at a cost. The cost, in this case, would be your disk space and some performance from the webapps themselves. Make certain to return your logs to their previous levels later on resolving your issues.

Object Spawner

Adjacent in line is the Object Spawner. When a user runs code, whether it be through Enterprise Guide or SASStudio, the Object Spawner is responsible for listening for the request so launching a server; be it a workspace server, pooled workspace server or stored process. In lodge for the spawner to get the server definitions, it must first access the metadata config file which specifies the information needed to connect to the Metadata Server. The default location for the Object Spawner log in a Windows surroundings is as follows:

sas-configuration-directory\ObjectSpawner\logs

If you notice yourself seeking out these logs for troubleshooting, be certain you are looking at the right log file, depending on your electric current issue, as y'all have two types (initialization log and rolling log) that are hands identifiable if you know what to wait for.

Looking at Effigy 1, items one and ii are considered the 'Initialization' log and contain relevant data or errors with regards to the launching of the Object Spawner. Particular 3 is considered the 'Rolling' log, as they keep the log from the spawner, noted by the same process ID 14256 every bit the previous 24-hour interval. You may look in the rolling file log if a workspace server fails to validate.

SASLogon9.4

We now move onto logs produced by SAS's Spider web Awarding logon manager. Any time you try to admission a spider web application within SAS, you will be directed to a universal logon page that handles the authentication asking for web applications. Afterward successfully authenticating, a user can access all SAS spider web apps for which they have the permissions.

sas-configuration-directory \Lev1\Web\Logs\SASServer1_1\SASLogon9.4.log

The errors that you run into in the SASLogon9.iv file don't have to do with failed log-in attempts when trying to get onto your spider web app with a wrong username or password. Rather information technology volition accost issues with sign-in mechanisms existence used similar Windows SSPI or third-party single sign-on products, such as PAM authentication in Linux. Also, be enlightened that the SAS Logon Manager just works for the services registered in Metadata Server.

Logs aren't ever about the errors

Yous can use the logs to gather general information such equally, "which user signed into Enterprise Guide?", by looking at the SAS Metadata Server log or "Is the Web Application Server instance up?" via the server.log in Web\WebAppServer\SASServer1_1\log directory, past looking for 'Server startup in ….ms'. Linux makes it easier to go along an eye on this using the tail -f command to see real-time changes to the file.

Lastly, regular clean-up of log files is recommended in order to continue fresh, upwardly-to-appointment logs. This ways either deleting quondam logs or compressing and archiving for auditing purposes. When it comes to the cumulative logs, it will let easier discovery of pertinent information without having a file with months of information. You can write your own scripts to automate the clean-up merely be careful non to clean logs while SAS services are running and files are still in use by SAS. Linux environments allow you to use the logrotate utility to manage log rollover, compression and removal of older rotated files.

SAS logs can become overwhelming, but with time and experience, knowing which log to pursue based on the symptoms becomes easier and allows for a SAS admin to speedily diagnose and resolve issues that they may encounter.

Source: https://www.zencos.com/blog/sas-logs-administration/