LogConfigSweeper tool for automated log and configuration data collection

[L2Fly]

Hello everyone, I just found this article https://communities.sas.com/t5/SAS-Communities-Library/Sweep-up-my-SAS-logs/ta-p/257385 (LogConfigSweeper tool) and wonder if anyone has any experience using it.  If you have, how easy is the install?  Is it easy to uninstall if you decide not to use it? ...

thanks again

[ShelleySessoms · Accepted solution]

SAS Tech Support would be a helpful resource, if none of your peers here can help answer these questions.

[L2Fly]

Thank you @ShelleySessoms for your reply.  I will do that and also I did send you an email since the article I found was posted by you.  Thanks again

[ShelleySessoms]

You are welcome, @L2Fly. I did forward your message to @GerryNelson, the author of the article. If he has any information to share, he will.

I do know there is no video to accompany the article. I wish you the best of luck with this information!

[L2Fly]

Thank you @ShelleySessoms and thanks for forwarding my message to Gerry.

[GerryNelson]

The tool is very easy to install and use. Just unzip the files to a directory. In addition if you wish to uninstall you can just delete the directory and its files. I hope that helps.

[L2Fly]

Perfect @GerryNelson and thanks for your reply.  That's all I needed.

[Jlochoa]

Hello Everyone,

I installed the LogConfigSweeper utility on a Five Linux SAS Server enviornment that is comprised of the following

1-Metadata Server

2-SASEMTM - Compute Server with "ObjectSpawner" directory located in SAS-configuration-directory/Lev1/

3-SASAPP - Computer Server with "ObjectSpawner2" directory located in SAS-configuration-directory/Lev1/

4-SASECCSA - Compute Server with "ObjectSpawner3" directory located in SAS-configuration-directory/Lev1/

5-WebServer

When executing SAS-configuration-directory/Lev1/LogConfigSweeper.sh objectspawner -output /tooloutput on 2-SASEMTM the zipped file is created with all of the logs located in SAS-configuration-directory/Lev1/ObjectSpawner/Logs directory.

However, executing the LogConfigSweeper utility on 3-SASAPP or 4-SASECCSA for ObjectSpawner files the zip file is empty. It appears the LogConfigSweeper utility does not recognize or find the appropriate logs because of the "ObjectSpawner2" or "ObjectSpawner3" directory names.

Does the "logconfigsweeper.jar" executable require modification?

Cheers,

Jose

[GerryNelson]

Hi Jose.

The tool currently only supports the default paths.  I have requested that this feature be added to the tool, but I don't have a timeframe of when that would be completed.

Gerry 

[ronan]

Hi,

Thanks for providing the LogConfigSweeper tool, this looks very promising.

I wasn't able to collect the logs on either a Unix (AIX) OA 9.4 (Metadata-Compute) or a second Linux MidTier machine.

In both cases, the SASConfig directory is named <path>/SASCFG/Lev0 ("zero") which, although correct, differs from the Lev1 default naming scheme : might this difference be the cause of the issue ?

The LogConfigSweeper sucessfully creates  the target folder then stops unexpectedly, folder still empty. 

./LogConfigSweeper.sh -output logconfigsweeper

logconfigsweeper/20190111-162631
Output File Path: logconfigsweeper/20190111-162631
[logconfigsweeper/20190111-162631]
***** STARTED SAS LOGCONFIGSWEEPER TOOL (version 1.0)*****