Clarity

Hello,
We just upgraded from 12.1.2 to 13.2 on a new hardware infrastructure. When I attempted to run SQL trace via the new method with v13 and beyond from the GUI, security.logs, i am seeing two errors happening.
When I access the page and select Logs\Edit Configuration:
1. There is an error waiting for me: Error: nsa.invalidConfig
2. Once I copy the XML file under the Appenders section and then save i recieve a second error:
Error:nsa.invalidConfig System error. Contact system administrator.

Has this happened to anyone else? How can we fix it? I have opened a case with Support but ofcourse wanted to throw it out there on the boards.
Thanks all.
Chintal

Are you following the attached steps ?

NJ

Yes. I should have stated that. After step 6 i am receiving the error.

Hi cshah,

Please try the following in order to fix your config:

1. Stop the Clarity services
2. Connect to Clarity server:
$clarity\.setup\templates\config
3. Copy logger.xml
4. Navigate to $clarity\config
5. Replace the existing logger.xml file with the one you copied above in 2.
6. Start back the services, connect to NSA and retry to enable the SQL trace

Please let me know how it goes.

Regards
Nika

Thanks Nika. From the time I posted this issue, and worked to resolve it with our CA partner as well, we discovered our services in general were unstable in our new dev, we could not start them from the cmd prompt. The only option was to re-install the application which then made this error go away.
Thank you though and although i'm hoping the same does not occur for Test, we have a solution. :grin:

Hello Nika,

I am not facing any error while doing the SQL trace, but trace file is not getting generated in the logs. we have tried so many times with no sucess.


Regards
Pawan Katiyar

Hi Pawan,

Please check in your properties.xml for the below tag

Please check your properties.xml file on your Clarity app server;

<logger alternateDirectory="/opt/ca/clarity/logs" dynamicConfigurationEnabled="true" traceEnabled="false" traceJDBCEnabled="false" multitenantErrorReportingEnabled="false"/>
if the above is same then change to
<logger alternateDirectory="/opt/ca/clarity/logs" dynamicConfigurationEnabled="true" traceEnabled="true" traceJDBCEnabled="true" multitenantErrorReportingEnabled="false"/>


3. reload the file using command admin general upload-config
4. restart clarity services

See if this helps.

Regards
Suman Pramanik