Description
This alert is triggered when the OBProxy service cannot be connected.
Principle
The access to MetaDB depends on OBProxy. OCP-Server checks the IP address and port number of the connection with OBProxy every minute. The connection timeout is 5 seconds. When the connection with OBProxy fails or times out, this alert is triggered.
Alert rule
| Metric | Default threshold | Duration | Detection cycle | Time before clearance |
|---|---|---|---|---|
| None | None | None | 60 seconds | 5 minutes |
Alert information
| Trigger method | Alert level | Scope |
|---|---|---|
| Timed task of OCP | Critical | Service |
Alert templates
Overview: ${alarm_target} ${alarm_name}
Details: ${alarm_target} ${alarm_name}
Overview example: ocp_ip=192.168.0.1:obproxy_address=192.168.0.2:obproxy_port=2888. The OBProxy is unavailable.
Details example: ocp_ip=192.168.0.1:obproxy_address=192.168.0.2:obproxy_port=2888. The OBProxy is unavailable.
${alarm_target} indicates the object that generated the alert, in the ocp_ip=xx:obproxy_address=xx:obproxy_port=xx format. ocp_ip is the IP address of the node where the alert is detected. obproxy_address and obproxy_port are respectively the address and the port number of the OBProxy server that generated the alert.
Impact on the system
OBProxy provides access to the OBServer cluster as the proxy. If OBProxy is unavailable, applications cannot connect to the database through OBProxy.
Possible causes
This problem is commonly found in the following scenarios:
A network communication error occurs.
The obproxy process unexpectedly stops.
Suggested solutions
Check the network connection
Log on to the OCP-Server, and run the following command
netstat -a | grep -i established | grep "${obproxy_address}:${obproxy_port}".If the system returns the result, the network is connected.
Otherwise, the network is disconnected, and you need to further identify the specific cause.
If the disconnection is caused by an OBProxy server failure, we recommend that you replace it.
If the disconnection is caused by your firewall, you need to configure firewall rules.
Check the server process
In the OCP console, select the OBProxy server that returns the error. On the OCP Agent tab, find the target obproxy process in the Processes list and check whether it is normal.
If the process is abnormal, restart the process and check if OBProxy is available. For more information, see "Start the obproxy process" in the OceanBase Database documentation . Alternatively, you can go to the Overview page of the unavailable OBProxy, find the target OBProxy server in the OBProxies list, and then click Restart in the Actions column.