Notifications Settings FAQs

How do Notifications Settings log work during failover?

Notifications Settings log informational messages, such as start-up messages, activity updates, and warnings,  to the log file.

The size of NotificationLog_<Cluster>_<Server>.txt is limited to approximately 1000 Kilobytes (K). When the size is exceeded, Notifications Settings messages are logged to new, empty NotificationLog.txt file, and the existing NotificationLog.txt file is renamed to NotificationLog_Backup.txt. If a NotificationLog_<Cluster>_<Server>_Backup.txt file already exists, it is replaced by the new one.

If the Notifications Settings log file is unavailable, for example, if the file is set to read-only or the file permissions change, the Notification Service will continue to run, but it will not log messages.

Service-related informational logging will also go the Citect Alarm Server kernel window.

 

SOEEventAdd function alarms

Citect hardware alarms and user events that are created from the SOEEventAdd function will not be notified upon.

 

Why am I getting duplicate notifications?

If the alarm servers are unable to communicate with each other, they will each assume the Active (or main) state. In the unlikely event that both alarm servers can communicate with the SMTP server, they will both send out notifications.

 

How do I restore Notifications Settings to a previous configuration?

The Notification configuration file is stored in the Notifications folder under the Data > Project directory. Older configuration files are also stored in the same folder as backup files (.bak). To restore notification settings to an earlier version, delete the current configuration file, ( NotificationConfiguration.xml), and rename the desired NotificationConfiguration-<date and time stamped>.bak file to NotificationConfiguration.xml.

NOTE: If you choose to revert to an earlier version of the configuration file for redundant systems, ensure you replace the NotificationConfiguration.xml on all the servers.