Audit apps report "Failed SSL Certification"

  • 3609083
  • 14-Jul-2006
  • 26-Apr-2012

Environment

Novell Audit 2.0.0
Novell Audit 2.0.1
Novell Audit 2.0.2

Situation

The nproduct.log file contains the following errors:
Fri Jul 14 14:14:09 2006 [Novell Audit Platform Agent]: Failing primary connection for application Modular Authentication Service.
Fri Jul 14 14:14:09 2006 [Novell Audit Platform Agent]: Failed SSL Certification
Fri Jul 14 14:14:09 2006 [Novell Audit Platform Agent]: Attempting to re-establish connection to secure log server for application eDirInst.
Fri Jul 14 14:14:09 2006 [Novell Audit Platform Agent]: Server reports logging protocol version: 4
Fri Jul 14 14:14:09 2006 [Novell Audit Platform Agent]: Failing primary connection for application eDirInst.
Fri Jul 14 14:14:09 2006 [Novell Audit Platform Agent]: Failed SSL Certification
Fri Jul 14 14:17:14 2006 [Novell Audit Platform Agent]: Attempting to re-establish connection to secure log server for application eDirInst.
Fri Jul 14 14:17:14 2006 [Novell Audit Platform Agent]: Server reports logging protocol version: 4
Fri Jul 14 14:17:14 2006 [Novell Audit Platform Agent]: Failing primary connection for application eDirInst.
Fri Jul 14 14:17:14 2006 [Novell Audit Platform Agent]: Failed SSL Certification
How do you fix the above errors and problems?

Resolution

There are two different things that can be causing this problem. They are as follows:
1.) The Log Application reporting the error is disabled in the Secure Logging Server (SLS). What this means is that instead of having a green dot next to the name of the application, there is a red circle with a white horizontal dash through the middle of it. What this means is that this application will no longer be able to send data to the SLS. If the log application is red, please do the following steps:
a.) Login to iManager. Typically this is done athttp:///nps/iManager.html.
b.) Click on the "Auditing and Logging" link. Click on the "Logging Server Options". Browse to your Secure Logging Server (SLS) object. Normally the SLS is located in the "Logging Services" container just off of root. Once you have your SLS, click on the "OK" button.
c.) Click on the "General" tab and select"Summary". Scroll down to the "Log Applications" section and look for the log application that is in red and not green. Click on the red button and make it turn green. Click on the"OK" or "Apply" button.
d.) Stop and start your SLS.
2.) If the Log Application (such as eDirectory) has a green dot next to it but these messages continue to appear, it is possible that the channel was recently enabled. If that is the case, then shutdown and start the SLS (lengine). If the SLS has been restarted and these errors persist, delete the log application object and recreate it using the appropriate .LSC file. Below are listed the steps on how to delete and recreate your log application object.
a.) Login to iManager. Typically this is done athttp:///nps/iManager.html.
b.) Click on the "Auditing and Logging" link. Click on the "Logging Server Options". Browse to your Secure Logging Server (SLS) object. Normally the SLS is located in the "Logging Services" container just off of root. Once you have your SLS, click on the "OK" button.
c.) Click on the "Log Applications" tab. Put a check mark next to the log application you wish to delete. Click on the "Application Actions" link and click on"Delete". You may be prompted to confirm you selection.
d.) Once the application has been deleted, put a check mark next to "Applications" and click on the "Application Actions" link. Select "New". Put in the name of the application. Then browse out to where your LSC file is contained. If you have a Novell Audit CD, the LSC files are in the \NetWare\base\system\naudit directory. Some of the names are edir_en.lsc (this is the log application for eDirectory), win_en.lsc, sss_en.lsc, etc. Once you have selected your LSC file, click on the OK button.
e.) Now that you have your log application installed, shutdown and restart the SLS (lengine).

Feedback service temporarily unavailable. For content questions or problems, please contact Support.