Author: Manyoung Joung
This article is applied to CUBRID 10.2.
1. CUBRID 10.2 Installation
CUBRID product installation creates and installs a CUBRID user:
#>useradd cubrid $>su - cubrid $>sh CUBRID-10.2-lastest-Linux.x86_64.sh $> cubrid_rel CUBRID 10.2 (10.2.0.8797-d56a158) (64bit release build for Linux) (Dec 5 2019 21:42:17)
2. CUBRID Operation Setting
CUBRID needs to be configured in $CUBRID/conf/cubrid.conf to start the database when the cubrid service starts. The following configuration is an example of registering the demodb and testdb databases to run.
$>vi $CUBRID/conf/cubrid.conf : # Any combinations are available with server, broker, manager and heartbeat. service=server,broker,manager # The list of database servers in all by 'cubrid service start' command. # This property is effective only when the above 'service' property contains 'server' keyword. server=demodb,testdb
3. Auto start SCRIPT and setting
The CUBRID daemon script uses the cubrid script located in $CUBRID/share/init.d and edits'ex)CUBRID_USER=cubrid' in the script as the user information that installed the CUBRID product.
$> cd $CUBRID/share/init.d $> vi cubrid ### CUBRID USER NAME VALUE ################## CUBRID_USER=cubrid
4. Setting up chkconfig
Copy the script written above to the /etc/init.d directory location and set the cubrid daemon as below in the root user.
#> cp /home/cubrid/CUBRID/share/init.d/cubrid /etc/init.d/ #> chkconfig --add cubrid #> chkconfig --level 03456 cubrid on #> chkconfig –list | grep cubrid cubrid 0:on 1:off 2:on 3:on 4:on 5:on 6:on
5. CUBRID Process Confirmation
Reboot the server and check the CUBRID Service operation in which the cubrid daemon is registered.
#> reboot check cub_auto_start OK in booting daemon. #> su - cubrid $> cubrid service status @ cubrid master status ++ cubrid master is running. @ cubrid server status Server demodb (rel 10.2, pid 4068) Server testdb (rel 10.2, pid 4118) @ cubrid broker status NAME PID PORT AS JQ REQ TPS QPS LONG-T LONG-Q ERR-Q ================================================================================ * query_editor 4159 30000 5 0 0 0 0 0/60.0 0/60.0 0 * broker1 4169 33000 5 0 0 0 0 0/60.0 0/60.0 0 @ cubrid manager server status ++ cubrid manager server is running.
6. Stopping CUBRID SERVICE
Server shutdown recommends stopping the CUBRID service and downing the server.
#>su - cubrid $>cubrid service stop @ cubrid server stop: demodb @ cubrid server stop: testdb Server demodb notified of shutdown. This may take several minutes. Please wait. ++ cubrid server stop: success @ cubrid broker stop ++ cubrid broker stop: success @ cubrid manager server stop ++ cubrid manager server stop: success @ cubrid master stop ++ cubrid master stop: success $>cubrid service status @ cubrid master status ++ cubrid master is not running. @ cubrid server status ++ cubrid master is not running. @ cubrid broker status ++ cubrid broker is not running. @ cubrid manager server status ++ cubrid manager server is not running. $>ps –ef | grep cubrid cubrid 4722 4721 0 14:52 pts/0 00:00:00 -bash cubrid 4776 4722 0 14:52 pts/0 00:00:00 ps -ef
Installing CUBRID and CUBRID Admin on Windows
