Rhino Alarm List

rhino.uncaught-exception

An uncaught exception has been detected.

rhino.ah.snapshot-age

The oldest activity handler snapshot is too old.

rhino.monitoring.clocksync

Another cluster node is reporting a system clock deviation relative to the local node beyond the maximum permitted threshold. The status of external processes maintaining the system clock on that node (eg. NTP) should be checked.

rhino.node-failure

A node left the cluster for some reason other than a management-initiated shutdown.

rhino.config.save-error

An error occurred while trying to write the file-based configuration for the configuration type specified in the alarm instance.

rhino.config.read-error

An error occurred while trying to read the file-based configuration for the configuration type specified in the alarm instance. Rhino will use defaults from defaults.xml, move the broken configuration aside, and overwrite the config file.

rhino.config.activation-failure

An error occurred while trying to activate the file-based configuration for the configuration type specified in the alarm instance. Rhino will use defaults from defaults.xml, move the broken configuration aside, and overwrite the config file.

rhino.database.no-persistence-config

A persistence resource configuration referenced in rhino-config.xml has been removed at runtime.

rhino.database.no-persistence-instances

A persistence resource configuration referenced in rhino-config.xml has no persistence instances configured, or no configured persistence instances could be instantiated.

rhino.database.persistence-instance-instantiation-failure

Rhino requires a backing database for persistence of state for failure recovery purposes. A persistent instance defines a connection to a database backend. If the persistent instance cannot be instantiated then that connection cannot be made and state cannot be persisted to that instance.

rhino.database.connection-lost

Rhino requires a backing database for persistence of state for failure recovery purposes. If no connection to the database backend is available, state cannot be persisted.

rhino.jdbc.persistence-instance-instantiation-failure

A persistent instance defines the connection to the database backend. If the persistent instance cannot be instantiated then JDBC connections cannot be made.

rhino.state.unlicensed-service

A licensing problem was detected during service activation at startup.

rhino.state.unlicensed-raentity

A licensing problem was detected during resource adaptor entity activation.

rhino.group-rmi.dangling-transaction

A group RMI invocation completed without committing or rolling back a transaction that it started. The dangling transaction will be automatically rolled back by the group RMI server to prevent future issues but these occurrences are software bugs that should be reported.

rhino.kv-store.no-persistence-config

A persistence resource configuration referenced in rhino-config.xml has been removed at runtime.

rhino.kv-store.no-persistence-instances

A persistence resource configuration referenced in rhino-config.xml has no persistence instances configured, or no configured persistence instances could be instantiated.

rhino.kv-store.persistence-instance-instantiation-failure

A persistence instance used by a key/value store cannot be instantiated. If the persistent instance cannot be instantiated then that connection cannot be made and state cannot be persisted to that instance.

rhino.license.over-limit

Rate limiter throttling is active. This throttling and hence this alarm only happens in SDK versions of Rhino, not production versions.

rhino.license.expired

A license installed in Rhino has passed its expiry time.

rhino.license.pending-expiry

A license installed in Rhino is within seven days of its expiry time.

rhino.license.partially-licensed-host

The hardware addresses listed in a host-based license only partially match those on the host.

rhino.license.unlicensed-host

The hardware addresses listed in a host-based license do not match those on the host.

rhino.license.unlicensed-rhino

Rhino does not have a valid license installed.

rhino.license.over-licensed-capacity

The work done by a function exceeds licensed capacity.

rhino.license.unlicensed-function

A particular function is not licensed.

rhino.limiting.below-negative-capacity

A rate limiter is below negative capacity.

rhino.logging.appender-error

An appender has thrown an exception when attempting to pass log messages from a logger to it.

rhino.mlet.loader-failure

The M-Let starter component could not register itself with the platform MBean server. This normally indicates a serious JVM misconfiguration.

rhino.mlet.registration-failure

The M-Let starter component could not register an MBean for a configured m-let. This normally indicates an error in the m-let configuration file.

rhino.rem.missing

This version of Rhino is supposed to contain an embedded instance of REM but it was not found, most likely due to a packaging error.

rhino.rem.startup

There was an unexpected problem while starting the embedded REM. This could be because of a port conflict or packaging problem.

rhino.rem.insufficient-java-version

Rhino Element Manager requires Java 1.8, but Rhino was started using Java 1.7

rhino.remote-timer-server.bind-error

The remote timer server is unable to bind a socket listener within the configured range of ports. The Rhino configuration may need to be checked and an alternate or wider range of ports allowed.

rhino.runtime.unsupported.jvm

This JVM is not a Sun/Oracle JVM. The Rhino SDK will raise this alarm but a Rhino Production instance will refuse to start.

rhino.runtime.unsupported.javamajorversion

This Java version is not a supported major version. The Rhino SDK will raise this alarm but a Rhino Production instance will refuse to start.

rhino.runtime.unsupported.javaupdateversion

This Java version is older than the minimum recommended update. A Rhino instance will start, but will always raise this alarm.

rhino.runtime.slee

SLEE event-routing functions failed to start after node restart

rhino.runtime.long-filenames-unsupported

Filenames with the maximum length expected by Rhino are unsupported on this filesystem. Unexpected deployment errors may occur as a result

rhino.sas.connection.lost

Attempting to reconect to SAS server

rhino.sas.queue.full

SAS message queue is full. Some events have not been reported to SAS

rhino.snmp.no-bind-addresses

The SNMP agent listens for requests received on all network interfaces that match the requested SNMP configuration. If no suitable interfaces can be found that match the requested configuration, then the SNMP agent cannot process any SNMP requests.

rhino.snmp.bind-failure

The SNMP agent attempts to bind a UDP port on each configured SNMP interface to receive requests. If no ports could be bound, the SNMP agent cannot process any SNMP requests.

rhino.snmp.partial-failure

The SNMP agent attempts to bind a UDP port on each configured SNMP interface to receive requests. If this succeeds on some (but not all) interfaces, the SNMP agent can only process requests received via the interfaces that succeeded.

rhino.snmp.general-failure

This is a catchall alarm for unexpected failures during agent startup. If an unexpected failure occurs, the state of the SNMP agent is unpredictable and requests may not be successfully processed.

rhino.snmp.notification-address-failure

This alarm represents a failure to determine an address from the notification target configuration. This can occur if the notification hostname is not resolvable, or if the specified hostname is not parseable.

rhino.snmp.duplicate-oid-mapping

Multiple parameter set type configurations for in-use parameter set types map to the same OID. All parameter set type mappings will remain inactive until the conflict is resolved.

rhino.snmp.duplicate-counter-mapping

Multiple counters in the parameter set type configuration map to the same index. The parameter set type mappings will remain inactive until the conflict is resolved.

rhino.scattercast.update-reboot-required

Reboot needed to make scattercast update active.

rhino.state.service-activation

The service threw an exception during service activation at startup.

rhino.session-ownership-store.no-persistence-config

The persistence resource configuration referenced in rhino-config.xml has been removed at runtime.

rhino.session-ownership-store.no-persistence-instances

The persistence resource configuration referenced in rhino-config.xml has no persistence instances configured, or no configured persistence instances could be instantiated.

rhino.session-ownership-store.persistence-instance-instantiation-failure

A persistence instance used by the session ownership store cannot be instantiated. If the persistent instance cannot be instantiated then that connection cannot be made and state cannot be persisted to that instance.

rhino.threshold-rules.rule-failure

A threshold rule trigger or reset rule failed.

rhino.threshold-rules.unknown-parameter-set

A threshold rule trigger or reset rule refers to an unknown statistics parameter set.

rhino.watchdog.no-exit

The system property watchdog.no_exit is set, enabling override of default node termination behaviour on failed watchdog conditions. This can cause catastrophic results and should never be used.

rhino.watchdog.forward-timewarp

A forward timewarp was detected.

rhino.watchdog.reverse-timewarp

A reverse timewarp was detected.

rhino.uncaught-exception

WARNING

Uncaught exception thrown by thread %s: %s

An uncaught exception has been detected.

When an uncaught exception has been thrown.

Never, must be cleared manually or Rhino restarted with the source of the uncaught exception corrected.

rhino.ah.snapshot-age

WARNING

Oldest activity handler snapshot is older than %s, snapshot is %s (from %d), creating thread: %s

The oldest activity handler snapshot is too old.

When the age of the oldest activity handler snapshot is greater than the threshold set by the rhino.ah.snapshot_age_warn system property (30s default).

When the age of the oldest snapshot is less than or equal to the threshold.

rhino.monitoring.clocksync

WARNING

Node %d is reporting a local clock time deviation beyond the maximum expected threshold of %dms

Another cluster node is reporting a system clock deviation relative to the local node beyond the maximum permitted threshold. The status of external processes maintaining the system clock on that node (eg. NTP) should be checked.

When a cluster node reports a local clock time deviation relative to the local node beyond the maximum permitted threshold.

When the clock deviation returns to a value at or below the threshold.

rhino.node-failure

MAJOR

Node %d has left the cluster

A node left the cluster for some reason other than a management-initiated shutdown.

When the cluster state listener detects a node has left the cluster unexpectedly.

When the failed node returns to the cluster.

rhino.config.activation-failure

MAJOR

Error activating configuration from file %s. Configuration was replaced with defaults and old configuration file was moved to %s.

An error occurred while trying to activate the file-based configuration for the configuration type specified in the alarm instance. Rhino will use defaults from defaults.xml, move the broken configuration aside, and overwrite the config file.

When an exception occurs while activating a file-based configuration.

Never, must be cleared manually.

rhino.config.read-error

MAJOR

Error reading configuration from file %s. Configuration was replaced with defaults and old configuration file was moved to %s.

An error occurred while trying to read the file-based configuration for the configuration type specified in the alarm instance. Rhino will use defaults from defaults.xml, move the broken configuration aside, and overwrite the config file.

When an exception occurs while reading a configuration file.

Never, must be cleared manually.

rhino.config.save-error

MAJOR

Error saving file based configuration: %s

An error occurred while trying to write the file-based configuration for the configuration type specified in the alarm instance.

When an exception occurs while writing to a configuration file.

Never, must be cleared manually.

rhino.database.connection-lost

MAJOR

Connection to %s database failed: %s

Rhino requires a backing database for persistence of state for failure recovery purposes. If no connection to the database backend is available, state cannot be persisted.

When the connection to a database backend is lost.

When the connection is restored.

rhino.database.no-persistence-config

CRITICAL

Persistence resource config for %s has been removed

A persistence resource configuration referenced in rhino-config.xml has been removed at runtime.

When an in-use persistence resource configuration is removed by a configuration update.

When the persistence resource configuration is restored.

rhino.database.no-persistence-instances

CRITICAL

Persistence resource config for %s has no active persistence instances

A persistence resource configuration referenced in rhino-config.xml has no persistence instances configured, or no configured persistence instances could be instantiated.

When an in-use persistence resource configuration has no active persistence instances.

When at least one active persistence instance exists for the persistence resource configuration.

rhino.database.persistence-instance-instantiation-failure

MAJOR

Unable to instantiate persistence instance %s for database %s

Rhino requires a backing database for persistence of state for failure recovery purposes. A persistent instance defines a connection to a database backend. If the persistent instance cannot be instantiated then that connection cannot be made and state cannot be persisted to that instance.

When a persistent instance configuration change occurs but instantiation of that persistent instance fails.

When a correct configuration is installed.

rhino.jdbc.persistence-instance-instantiation-failure

MAJOR

Unable to instantiate persistence instance %s for JDBC configuration with JNDI name %s

A persistent instance defines the connection to the database backend. If the persistent instance cannot be instantiated then JDBC connections cannot be made.

When a persistent instance configuration change occurs but instantiation of that persistent instance fails.

When a correct configuration is installed.

rhino.state.unlicensed-raentity

MAJOR

No valid license for resource adaptor entity "%s" found. The resource adaptor entity has not been activated.

A licensing problem was detected during resource adaptor entity activation.

During Rhino startup if a resource adaptor entity is configured to be in the active state but there is no valid license for it.

Never, must be cleared manually.

rhino.state.unlicensed-service

MAJOR

No valid license for service "%s" found. The service has not been activated.

A licensing problem was detected during service activation at startup.

During Rhino startup if an service is configured to be in the active state but there is no valid license for it.

Never, must be cleared manually.

rhino.group-rmi.dangling-transaction

WARNING

Group RMI invocation %s completed leaving an active transaction dangling: %s. Please report this bug to Metaswitch support.

A group RMI invocation completed without committing or rolling back a transaction that it started. The dangling transaction will be automatically rolled back by the group RMI server to prevent future issues but these occurrences are software bugs that should be reported.

When a group RMI invocation completes leaving an active transaction dangling.

Never, must be cleared manually.

rhino.kv-store.no-persistence-config

CRITICAL

Persistence resource config for %s has been removed

A persistence resource configuration referenced in rhino-config.xml has been removed at runtime.

When an in-use persistence resource configuration is removed by a configuration update.

When the persistence resource configuration is restored.

rhino.kv-store.no-persistence-instances

CRITICAL

Persistence resource config for %s has no active persistence instances

A persistence resource configuration referenced in rhino-config.xml has no persistence instances configured, or no configured persistence instances could be instantiated.

When an in-use persistence resource configuration has no active persistence instances.

When at least one active persistence instance exists for the persistence resource configuration.

rhino.kv-store.persistence-instance-instantiation-failure

MAJOR

Unable to instantiate persistence instance %s for key/value store %s

A persistence instance used by a key/value store cannot be instantiated. If the persistent instance cannot be instantiated then that connection cannot be made and state cannot be persisted to that instance.

When a persistent instance configuration change occurs but instantiation of that persistent instance fails.

When a correct configuration is installed.

rhino.license.expired

MAJOR

License with serial "%s" has expired

A license installed in Rhino has passed its expiry time.

When a license expires and there is no superseding license installed.

When the license is removed or a superseding license is installed.

rhino.license.over-licensed-capacity

MAJOR

Over licensed capacity for function "%s".

The work done by a function exceeds licensed capacity.

When the amount of work processed by the named function exceeds the licensed capacity.

When the amount of work processed by the function becomes less than or equal to the licensed capacity.

rhino.license.over-limit

MAJOR

Rate limiter throttling active, throttled to %d events/second

Rate limiter throttling is active. This throttling and hence this alarm only happens in SDK versions of Rhino, not production versions.

When there is more incoming work than allowed by the licensed limit so Rhino starts rejecting some.

When the total input rate (both accepted and rejected work) drops below the licensed limit.

rhino.license.partially-licensed-host

MINOR

Host "%s" is not fully licensed. Not all hardware addresses on this host match those licensed. Please request a new license for host "%s".

The hardware addresses listed in a host-based license only partially match those on the host.

When a host-based license with invalid host addresses is installed.

When the license is removed, or a superseding license is installed.

rhino.license.pending-expiry

MAJOR

License with serial "%s" is due to expire on %s

A license installed in Rhino is within seven days of its expiry time.

Seven days before a license will expire and there is no superseding license installed.

When the license expires, the license is removed, or a superseding license is installed.

rhino.license.unlicensed-function

MAJOR

There are no valid licenses installed for function "%s" and version "%s".

A particular function is not licensed.

When a unit of an unlicensed function is requested.

When a license is installed that licenses a particular function, and another unit is requested.

rhino.license.unlicensed-host

MINOR

"%s" is not licensed. Hardware addresses on this host did not match those licensed, or hostname has changed. Please request a new license for host "%s".

The hardware addresses listed in a host-based license do not match those on the host.

When a host-based license with invalid host addresses is installed.

When the license is removed, or a superseding license is installed.

rhino.license.unlicensed-rhino

MAJOR

Rhino platform is no longer licensed

Rhino does not have a valid license installed.

When a license expires or is removed leaving Rhino in an unlicensed state.

When an appropriate license is installed.

rhino.limiting.below-negative-capacity

WARNING

Token count in rate limiter "%s" capped at negative saturation point on node %d. Too much work has been forced. Alarm will clear once token count >= 0.

A rate limiter is below negative capacity.

By a rate limiter when a very large number of units have been forcibly used and the internal token counter has reached the biggest possible negative number (-2,147,483,648).

When the token count becomes greater than or equal to zero.

rhino.logging.appender-error

MAJOR

An error occurred logging to an appender: %s

An appender has thrown an exception when attempting to pass log messages from a logger to it.

When an appender throws an AppenderLoggingException when a logger tries to log to it.

When the problem with the given appender has been resolved and the logging configuration is updated.

rhino.mlet.loader-failure

MAJOR

Error registering MLetLoader MBean

The M-Let starter component could not register itself with the platform MBean server. This normally indicates a serious JVM misconfiguration.

During Rhino startup if an error occurred registering the m-let loader component with the MBean server.

Never, must be cleared manually or Rhino restarted.

rhino.mlet.registration-failure

MINOR

Could not create or register MLet: %s

The M-Let starter component could not register an MBean for a configured m-let. This normally indicates an error in the m-let configuration file.

During Rhino startup if an error occurred starting a m-let configured.

Never, must be cleared manually or Rhino restarted with updated configuration.

rhino.rem.insufficient-java-version

MINOR

This Java version (%s) is insufficient for starting the embedded Rhino Element Manager. REM requires Java 1.8.

Rhino Element Manager requires Java 1.8, but Rhino was started using Java 1.7

During Rhino startup if running on Java 1.7 and embedded REM is enabled.

Never, must be cleared manually, Rhino restarted using Java 1.8, or embedded REM disabled.

rhino.rem.missing

MINOR

Rhino Element Manager classes not found, embedded REM is disabled.

This version of Rhino is supposed to contain an embedded instance of REM but it was not found, most likely due to a packaging error.

During Rhino startup if the classes could not be found to start the embedded REM.

Never, must be cleared manually.

rhino.rem.startup

MINOR

Could not start embedded Rhino Element Manager

There was an unexpected problem while starting the embedded REM. This could be because of a port conflict or packaging problem.

During Rhino startup if an error occurred starting the embedded REM.

Never, must be cleared manually or Rhino restarted with updated configuration.

rhino.remote-timer-server.bind-error

CRITICAL

Unable to bind remote timer server to %s %s

The remote timer server is unable to bind a socket listener within the configured range of ports. The Rhino configuration may need to be checked and an alternate or wider range of ports allowed.

If the remote timer server cannot bind a socket listener within the configured range of ports.

Never, must be cleared manually.

rhino.runtime.long-filenames-unsupported

WARNING

Filenames with a length of %s characters are unsupported on this filesystem. Unexpected deployment errors may occur as a result

Filenames with the maximum length expected by Rhino are unsupported on this filesystem. Unexpected deployment errors may occur as a result

During Rhino startup if the long filename check fails.

Never, must be cleared manually or Rhino restarted after being installed on a filesystem supporting long filenames.

rhino.runtime.slee

CRITICAL

SLEE event-routing functions failed to start after node restart

SLEE event-routing functions failed to start after node restart

During Rhino startup if SLEE event-routing functions fail to restart.

Never, must be cleared manually or the node restarted.

rhino.runtime.unsupported.javamajorversion

WARNING

This Java version (%s) is not supported for Rhino production instances. Supported versions are: %s

This Java version is not a supported major version. The Rhino SDK will raise this alarm but a Rhino Production instance will refuse to start.

During Rhino SDK startup if an unsupported JVM was detected.

Never, must be cleared manually or Rhino restarted with a supported Java version.

rhino.runtime.unsupported.javaupdateversion

MINOR

This Java version (%s) is older than the minimum recommended update (%s)

This Java version is older than the minimum recommended update. A Rhino instance will start, but will always raise this alarm.

During Rhino startup if an old Java version was detected.

Never, must be cleared manually or Rhino restarted with a supported Java version.

rhino.runtime.unsupported.jvm

WARNING

This JVM (%s) is not supported for Rhino production instances. Supported JVMs are: %s

This JVM is not a Sun/Oracle JVM. The Rhino SDK will raise this alarm but a Rhino Production instance will refuse to start.

During Rhino SDK startup if an unsupported JVM was detected.

Never, must be cleared manually or Rhino restarted with a supported JVM.

rhino.sas.connection.lost

MAJOR

Connection to SAS server at %s:%d is down

Attempting to reconect to SAS server

When SAS client loses connection to server

On reconnect

rhino.sas.queue.full

WARNING

SAS message queue is full

SAS message queue is full. Some events have not been reported to SAS

When SAS facility outgoing message queue is full

When the queue is not full for at least sas.queue_full_interval

rhino.snmp.bind-failure

MAJOR

The SNMP agent could not be started on node %d: no addresses were successfully bound.

The SNMP agent attempts to bind a UDP port on each configured SNMP interface to receive requests. If no ports could be bound, the SNMP agent cannot process any SNMP requests.

When the SNMP Agent attempts to start listening for requests, but no port in the configured range on any configured interface could be used.

When the SNMP Agent is stopped.

rhino.snmp.duplicate-counter-mapping

WARNING

Duplicate counter mappings in parameter set type %s

Multiple counters in the parameter set type configuration map to the same index. The parameter set type mappings will remain inactive until the conflict is resolved.

When a in-use parameter set type has a configuration with duplicate counter mappings.

When the conflict is resolved, either by changing the relevant counter mappings, or if the parameter set type is removed from use.

rhino.snmp.duplicate-oid-mapping

WARNING

Duplicate parameter set type mapping configurations for OID %s

Multiple parameter set type configurations for in-use parameter set types map to the same OID. All parameter set type mappings will remain inactive until the conflict is resolved.

When multiple in-use parameter set types have a configuration that map to the same OID.

When the conflict is resolved, either by changing the OID mappings in the relevant parameter set type configurations, or if a parameter set type in conflict is removed from use.

rhino.snmp.general-failure

MINOR

The SNMP agent encountered an error during startup: %s

This is a catchall alarm for unexpected failures during agent startup. If an unexpected failure occurs, the state of the SNMP agent is unpredictable and requests may not be successfully processed.

When the SNMP Agent attempts to start listening for requests, but there is an unexpected failure not covered by other alarms.

When the SNMP Agent is stopped.

rhino.snmp.no-bind-addresses

MAJOR

The SNMP agent could not be started on node %d: no suitable bind addresses available.

The SNMP agent listens for requests received on all network interfaces that match the requested SNMP configuration. If no suitable interfaces can be found that match the requested configuration, then the SNMP agent cannot process any SNMP requests.

When the SNMP Agent attempts to start listening for requests, but no suitable network interface addresses can be found to bind to.

When the SNMP Agent is stopped.

rhino.snmp.notification-address-failure

MAJOR

Failed to create notification target for address "%s".

This alarm represents a failure to determine an address from the notification target configuration. This can occur if the notification hostname is not resolvable, or if the specified hostname is not parseable.

During SNMP agent start if a notification target address cannot be determined (e.g. due to a hostname resolution failing).

When the SNMP Agent is stopped.

rhino.snmp.partial-failure

MINOR

The SNMP agent failed to bind to the following addresses: %s

The SNMP agent attempts to bind a UDP port on each configured SNMP interface to receive requests. If this succeeds on some (but not all) interfaces, the SNMP agent can only process requests received via the interfaces that succeeded.

When the SNMP Agent attempts to start listening for requests, and only some of the configured interfaces successfully bound a UDP port.

When the SNMP Agent is stopped.

rhino.scattercast.update-reboot-required

CRITICAL

Scattercast endpoints have been updated. A cluster reboot is required to apply the update. An automatic reboot has been triggered, Manual intervention required if the reboot fails.

Reboot needed to make scattercast update active.

When scattercast endpoints are updated.

On node reboot.

rhino.state.service-activation

MAJOR

Service "%s" failed to reactivate successfully.

The service threw an exception during service activation at startup.

During Rhino startup if a service is configured to be in the active state but throws an exception while handling the activation request.

If the service is manually reactivated successfully, or uninstalled.

rhino.session-ownership-store.no-persistence-config

CRITICAL

Persistence resource config has been removed

The persistence resource configuration referenced in rhino-config.xml has been removed at runtime.

When an in-use persistence resource configuration is removed by a configuration update.

When the persistence resource configuration is restored.

rhino.session-ownership-store.no-persistence-instances

CRITICAL

Persistence resource config has no active persistence instances

The persistence resource configuration referenced in rhino-config.xml has no persistence instances configured, or no configured persistence instances could be instantiated.

When an in-use persistence resource configuration has no active persistence instances.

When at least one active persistence instance exists for the persistence resource configuration.

rhino.session-ownership-store.persistence-instance-instantiation-failure

MAJOR

Unable to instantiate persistence instance %s

A persistence instance used by the session ownership store cannot be instantiated. If the persistent instance cannot be instantiated then that connection cannot be made and state cannot be persisted to that instance.

When a persistent instance configuration change occurs but instantiation of that persistent instance fails.

When a correct configuration is installed.

rhino.threshold-rules.rule-failure

WARNING

Threshold rule %s trigger or reset condition failed to run

A threshold rule trigger or reset rule failed.

When a threshold rule condition cannot be evaluated, for example it refers to a statistic that does not exist.

When the threshold rule condition is corrected.

rhino.threshold-rules.unknown-parameter-set

WARNING

Threshold rule %s refers to unknown statistics parameter set '%s'

A threshold rule trigger or reset rule refers to an unknown statistics parameter set.

When a threshold rule condition cannot be evaluated because it refers to a statistics parameter set that does not exist.

When the threshold rule condition is corrected.

rhino.watchdog.forward-timewarp

WARNING

Forward timewarp of %sms detected at %s

A forward timewarp was detected.

When the system clock is detected to have progressed by an amount exceeding the sum of the watchdog check interval and the maximum pause margin.

Never, must be cleared manually.

rhino.watchdog.no-exit

CRITICAL

System property watchdog.no_exit is set, watchdog will be terminated rather than killing the node if a failed watchdog condition occurs

The system property watchdog.no_exit is set, enabling override of default node termination behaviour on failed watchdog conditions. This can cause catastrophic results and should never be used.

When the watchdog.no_exit system property is set.

Never, must be cleared manually.

rhino.watchdog.reverse-timewarp

WARNING

Reverse timewarp of %sms detected at %s

A reverse timewarp was detected.

When the system clock is detected to have progressed by an amount less than the difference between the watchdog check interval and the reverse timewarp margin.

Never, must be cleared manually.