CRL Log Events

This section lists event log messages related to the loading of CRLs.

The CRL at location [x] appears to no longer have an update entry.

This log entry indicates an error in the settings file structure. While it can potentially appear frequently, it indicates that a serious problem exists.

Loading CRL for issuer [x] from file [y].

This entry appears once for each downloaded CRL file. This is likely to appear either at system startup or after a new CRL is configured and successfully downloaded. This entry appears again if the CRL is later updated.

Successfully loaded CRL for issuer [x] from file [y].

This is a follow-up entry from the “Loading CRL” message entry indicating success.

Failed to load CRL for issuer [x] from file [y].

This is a follow-up entry from the “Loading CRL” message entry indicating failure.

The issuer for this CRL could not be found. To ensure the proper loading of this CRL, install the issuer and restart the validation service.

This failure entry occurs once when the system attempts to load a CRL and fails due to inability to find the CRL's issuer. This message can repeat if an updated version of the CRL is downloaded and the issuer is still missing.

Checking for new CRL at location [x].

This message appears when an update for a given CRL is detected and is about to be downloaded. This only occurs when the CRL update period has expired and an updated CRL with a newer timestamp exists at the configured URL.

Note: Some systems may not support timestamps, thus causing this entry to appear once every configured update period

Skipping CRL at location [x]. This version is not newer than the file [y].

This message appears when the CRL update period expires but the file at the configured URL does not have a later timestamp than the file currently on disk.

This message can potentially appear once every update period per CRL.

The downloaded file does not appear to be a valid CRL.

This message appears when a downloaded file appears not to be a valid CRL. This message can potentially appear once every update period if the remote file is not a valid CRL file.

The CRL at location [x] was saved to the file [y].

This message appears when an updated CRL file is downloaded and saved to disk. If the remote system does not support timestamp reporting, this message can potentially appear once per update period.

An unknown error occurred attempting to update the CRL at location [x].

This message can appear when an unspecified error occurs attempting to download a CRL. This message can appear once per update period.