Post upgrade to 9.1 SP2 some servers have encountered problems with escalations not running despite all the settings appearing to be correct. Disable-Escalations was not set to T Disable-Escalations-Global was not set to T Server group config was correct Escalation thread settings were correct The reason turned out to be a new configuration parameter introduced in SP2 called Operating-Mode. This new option is intended to help improve upgrade performance by providing a quick way to disable a group of features during the upgrade process. Unfortunately, if the installer does not complete for some reason, this setting may be left in place with a value set that disables escalations and other processes. |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. For normal server operations this option should either not be present (check the ar.cfg and centralized configuration form) or should be set to 0. Value 1 indicates the server is in upgrade mode and will not run escalations, archiving etc. In this case delete the options or use Java Driver to issue the following commands to reset: ssi 1 463 2 0 |