CDR resource adaptor generates alarms related to CDR write and CDR file archive failures.

For all of these alarm types use the CDR resource adaptor entity name as the alarm instanceID:

Alarm type When raised When cleared Action to take

cdr.write-timeout

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

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

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

A CDR is successfully written to disk without errors.

Examine the Rhino logs for detailed error information and correct the underlying error. Manually recover CDR data if necessary.

cdr.archive-failure

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

A CDR file is successfully archived without errors.

Examine the Rhino logs for detailed error information and correct the underlying error. Manually process any CDR files that were not processed automatically if necessary.

cdr.write-thread-failure

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

The RA is deactivated.

Deactivate, then activate the CDR RA entity. Contact OpenCloud support for further diagnosis.

cdr.archive-thread-failure

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

The RA is deactivated.

Deactivate, then activate the CDR RA entity. Contact OpenCloud support for further diagnosis.
Previous page Next page