For the complete documentation index, see llms.txt. This page is also available as Markdown.

An overview of Asserts

Command Centre - Errors › An overview of Asserts

An ASSERT is a generic internal error signal that surfaces in the Command Centre logs or client.

Example ASSERT error message

Resolution

Search for the word ASSERT in the logs, then check whether a patch exists or the issue is fixed in a newer version. If it is not clear, raise a new work item with R&D.

Log locations:

Server asserts when alarms are processed by a Macro

Symptom: the server asserts when alarms are processed via a Macro and the alarm source does not have an Alarm Zone field.

Affected versions: v8.00.1252 MR7, v8.10.1253 MR6, v8.20.1218 MR4, v8.30.1299 MR2, v8.40.1252 Full Release.

Cause: one of the fixes implemented in the versions above caused this anomaly. It only affects sites that use a Macro to process alarms in Command Centre.

This assert only happens if you are using a Macro to process alarms and an alarm with no alarm source exists in the Alarm Viewer at the time of processing. Example: a Command Centre generated alarm, such as a report that failed.

Workaround:

  • Do not use a Macro to process alarms.

  • Turn off Assert dumps if using Macros, but this is not ideal.

Fix (status as recorded on 2021-09-27): "Fixed in v8.40 MR1 - due for release next week." "Fixed in 8.00+ and will be included in next MR which will be in the new year. Meanwhile Server only patch is available for any affected sites."


🔗 Related

Last updated

Was this helpful?