PVSS00event - PARAM/SEVERE - recursion detected in sum alert use -dbg sumAlertCheck to get detailed informations
Enclosed you'll find the explanation for a log-message which can occur during runtime or when configuring _alert_hdl-configs. The log-message is written to the PVSS_II.log-file.
PVSS00event (0), 2009.10.28 12:18:54.777, PARAM,SEVERE, 86, Invalid value, recursion detected in sum alert System1:mainpanels_geographical_overview_1.Warning. use -dbg sumAlertCheck to get detailed informations
Log-message with symbolic names:
PVSS00event (0), <TIMESTAMP>, PARAM,SEVERE, 86, Invalid value, recursion detected in sum alert <DPE-name> use -dbg sumAlertCheck to get detailed informations
This log-message describes that a indirect recursion at summary alerts was detected.
The summary alert at the datapoint-element <DPE-name> is deactivated at the event-manager.
If a direct recursion is detected you get a similar log-message where the involved summary alerts are listed.
A direct recursion is configured when the summary alert at the datapoint-element DPE-A refers to the summary alert at DPE-B and vice versa.
In this case a indirect recursion is detected and therefore you have to use the mentioned debug-level “-dbg sumAlertCheck” to get detailed information concering the summary alert configured at the datapoint-element <DPE-name>.
To get detailed information you have to perform the following steps:
-- activate the debug-flag “-dbg sumAlertCheck” for the event-manager
-- try to activate the summary alert for the datapoint-element <DPE-name>, the information concerning the summary alerts will be written to the event-manager logfile PVSS00event0-log
-- deactivate the debug-flag for the event-manager with “-dbg none”
-- copy the file from the log-directory of your project into another directory
-- open the file with a text-editor
-- search for “DBGLEVEL=sumAlertCheck(49)” or “recursion check for: <DPE-name>” to go to the beginning of the log-output for the summary-alert-check
-- the summary alert and its assigned alerts is listed
-- each level of the summary alert is marked by an indentation
-- in the last line of the output you should see the datapoint-element which is involved in the recursion
-- search for this datapoint-element in the log-output to find the cause for the recursion
To get rid of this problem please modify the configuration of the summary alerts.