The CDR Resource Adaptor generates alarms when unexpected failures occur.

Alarms raised by the CDR Resource Adaptor signal failure conditions that usually require administrator intervention to resolve. They are grouped into the following categories:

Configuration and usage alarms

Error conditions signaled by alarms in this category are not related to any particular stream managed by the resource adaptor. The alarm Instance ID(s) are equal to the entity name, except for the cdr.stream.missing alarm type. The Instance ID for the cdr.stream.missing alarm type also contains the name of missing or unconfigured streams; its format is

entity name : stream name
Alarm type When…​ Actions to take 
cdr.misconfiguration
raised

The resource adaptor is unable to activate due to an invalid configuration.

cleared

The resource adaptor is deactivated.

  • Examine the Rhino logs for detailed information.

  • Change the configuration.

  • Deactivate, then activate the CDR resource adaptor entity.

 
cdr.stream.missing
raised

The service requested an operation on a stream unknown to the CDR resource adaptor entity.

cleared

The resource adaptor is deactivated.

  • Check that the expected stream is configured.

  • Change the configuration.

  • Notify the CDR resource adaptor entity of the configuration changes.

  • Deactivate, then activate the CDR resource adaptor entity; or clear the alarm administratively.

 
cdr.stream.nodefault
raised

The service requested an operation on the default stream, but the default stream is not configured.

cleared

The resource adaptor is deactivated or the default stream is configured.

  • Check resource adaptor configuration.

  • Set a valid default stream name.

CDR stream IO failure alarms

Alarms in this category are raised when error conditions occur during CDR write or CDR file archive operations. These alarms are raised and cleared on a per CDR stream basis. That is, an alarm can be raised due to a CDR write failure on a given CDR stream while other CDR streams are operational and successfully fulfill CDR write requests.

CDR write failure alarms

These alarms are raised when a CDR stream write thread encounters failures writing to CDR files. The format of the alarm Instance ID(s) is:

entity name : stream name : write thread sequence

where write thread sequence is a sequence number assigned to each CDR stream write thread.

Alarm type When…​ Actions to take 
cdr.write-timeout
raised

A CDR could not be written and flushed to disk within the configured WriteTimeout.

cleared

The write thread has been operating normally with no timeouts for at least 2*WriteTimeout milliseconds.

  • Check that the CDR directory is accessible and that the disk is not overloaded.

  • Check that Rhino has available spare CPU time.

 
cdr.write-failure
raised

An I/O error has occurred when creating a CDR file, writing to a CDR file, or closing a CDR file.

cleared

A CDR is successfully written to disk without errors.

  • Examine the Rhino logs for detailed error information,

  • Correct the underlying error.

  • Manually recover CDR data if necessary.

 
cdr.write-thread-failure
raised

The CDR write thread exits unexpectedly. Suggests a bug in the CDR resource adaptor code.

cleared

The resource adaptor is deactivated.

  • Deactivate, then activate the CDR resource adaptor entity.

  • Contact OpenCloud support for further diagnosis.

CDR file archive failure alarms

These alarms are raised when the CDR archive thread encounters failures archiving CDR files. The format of the alarm
Instance ID(s) is:

entity name : stream name : archive thread sequence

where archive thread sequence is a sequence number assigned to each CDR stream archive thread.

Alarm type When…​ Actions to take 
cdr.archive-failure
raised

Execution of the CDR ArchiveCommand fails, or the command returns a non-zero exit code.

cleared

A CDR file is successfully archived without errors.

  • Examine the Rhino logs for detailed error information.

  • Correct the underlying error.

  • Manually process any CDR files that were not processed automatically if necessary.

 
cdr.archive-thread-failure
raised

The CDR archive thread exits unexpectedly. Suggests a bug in the CDR resource adaptor code.

cleared

The resource adaptor is deactivated.

  • Deactivate, then activate the CDR resource adaptor entity.

  • Contact OpenCloud support for further diagnosis.

 
cdr.archive-queue-size
raised

The queue size for archiver thread exceeds the warning level set in the configuration. Suggests that the archive command execution time is too high for current load.

cleared

The queue size for archiver thread decreases below the safe level set in the configuration.

Note
See also
The ArchiveQueueSizeAlarmRaise and ArchiveQueueSizeAlarmClear configuration properties.

  • Examine the Rhino logs for problems executing the archive command.

  • Investigate the run time of archive command.
Previous page Next page