Alert description
Some system parameters in OCP require a restart for the changes to take effect. When OCP's scheduled inspection detects that parameters marked as "Restart Required" have been modified but the restart has not been performed, this alert is triggered to remind the administrator to restart the OCP service for the parameters to take effect.
Alert principle
Parameter |
Value |
|---|---|
| Monitoring Metrics | N/A |
| Monitoring Expression | N/A |
| Metric Collection | N/A |
| Metric Source | OCP Application Internal Events |
| Collection Cycle | N/A |
When OCP starts, it loads system parameters into memory. Modifications to system parameters only affect the database value, not the memory value. Additionally, OCP initiates a scheduled inspection task to compare parameters marked as "needRestart" (needRestart() == true) in memory with the database. If any inconsistent parameters are found, it indicates that a parameter has been modified but the change has not taken effect due to the lack of a restart, and this alert event is triggered.
Rule information
Monitoring Metrics |
Default Threshold |
Duration |
Detection Cycle |
Elimination Cycle |
|---|---|---|---|---|
| N/A | N/A | N/A | N/A | 300 Seconds |
Alert information
Alert Trigger Method |
Alert Level |
Scope |
|---|---|---|
| Event Trigger | Reminder | Service |
Alert template
Alert overview
- Template: ${alarm_target} ${alarm_name}
- Example: svr_ip=xxx.xxx.xxx.xxx The system parameter modification takes effect after a restart.
Alert Details
- Template: Server: ${host}, Alert: System parameter modification requires a restart to take effect, Parameter name: ${system_parameter}.
- Example: Server: xxx.xxx.xxx.xxx, Alert: System parameters need to be restarted to take effect after modification, Parameter name: [ocp.site.url, server.port].
Impact on the system
If you modify a system parameter and do not restart the system, the following impacts may occur:
Configuration inconsistency: The configuration values recorded in the database do not match the actual running values, which may lead to misjudgment of system behavior by operations personnel.
Unexpected feature non-availability: Some parameters that require a restart to take effect (such as port numbers or site URLs) did not work as expected, impacting system functionality.
Cause
The administrator has modified system parameters that require a restart to take effect through the OCP console or API, but has not yet restarted the OCP service.
Forgetting to restart the system after batch modifying system parameters.
Solution
Confirm the alert information: Locate the parameter to be modified based on the server IP address (host) and parameter name (system_parameter) in the alert.
Confirm parameter changes: On the System Parameter Management page of the OCP console, confirm which parameters have been modified but have not taken effect, and assess whether an immediate restart is required.
Restart the OCP service: Select an appropriate time window (preferably during off-peak hours) to restart the service on the corresponding OCP node for the parameters to take effect. If it is a multi-node deployment, you need to restart all OCP nodes one by one.
Verify the fix: After the restart is complete, confirm that the parameter has taken effect as expected. The alert will automatically clear within its clearance cycle (300 seconds).