Stop the OBProxy process
Log on to the load-balancer and delete the IP address of OBProxy.
Log on to the sys tenant as the root user from OceanBase Client (OBClient).
Run the
SHOW PROCESSLISTcommand to view connections and verify that OBProxy has zero connections.Log on to the server where OBProxy is installed, run the following command in the command-line tool to view the status of the OBProxy process:
ps -ef | grep obproxy | grep '^admin' | grep -v grepNote
OBProxy is installed under the admin user. Therefore, you can use the
'^admin'filter in the command.
Run the following commands to kill the processes associated with OBProxy.
The
./bin/obproxyd.shprocess is the daemon of OBProxy. It automatically starts the OBProxy process when the OBProxy process quits abnormally.kill -15 [ daemon process PID] kill -15 [OBProxy process PID]
Start the OBProxy process
Log on to the server where OBProxy is installed, run the following command in the command-line tool to start the daemon. The daemon automatically starts the OBProxy process.
The value of the
[obproxy directory]placeholder may vary with the OBProxy version. In earlier versions, it isobproxy. In the latest version, it isobproxy-<version number>.
Run the following command in OBClient to view the status of the OBProxy process:
ps -ef | grep obproxy | grep '^admin'Note
OBProxy is installed under the admin user. Therefore, you can use the
'^admin'filter in the command.
Log on to the sys tenant as the root user from OBClient. Run the following command to verify whether you can connect to the OceanBase cluster:
obclient -uroot@sys#[cluster name] -P2883 -h127.1 -p[password] -Doceanbase -c