Table of Contents
Advertisement
Self Tests
When this happens, CMS administrator(s) and CMS auditor(s) should work
together with the Operating System administrator to resolve the disk space or file
permission issue(s). When the IT problem is resolved, the auditor should make
sure that the last audit log entries are signed. If not, they should be preserved by
manual signing (see "Signing Log Files" on page 275), archived, and removed to
prevent audit verification failures in the future. When all is well, the CMS
administrator(s) can then restart CMS.
Self Tests
CMS has added functionality to allow for self tests of the server. The current
implementation contains a small set of self-tests, created as plug-ins. You can
expand the number of self tests by creating new self test plug-ins using the CMS
SDK.
The self-tests are run at start up and can also be run on demand. The start up self
tests run when the server starts up, and will keep the server from starting up if a
critical self-test fails. The on-demand self tests are run by clicking the self tests
button in a new CMS window interface page.
To run an on-demand self test:
Log in to the CMS console (see "Logging Into the CMS Console" on page 247).
1.
Select Netscape Certificate Management System at the top of the left pane.
2.
Select the Self Tests tab.
3.
Click Run.
4.
The self-tests that are configured for this subsystem will run. If any critical
self-tests fail, the server will stop.
The On-Demand Self Tests Results window appears showing the logged
events for this run of the self-tests.
Self Test Logging
A new log,
reports for both the start up self tests and the on-demand self tests. You can
configure this log by changing the setting for the log in the
"Modifying Self Test Configuration," on page 283 for details.
282
Netscape Certificate Management System Administrator's Guide • February 2003
, has been added to the log directory which contains
selftest.log
file. See
CMS.cfg
Advertisement
Table of Contents
