Background Image




PrevPrev Article

NextNext Article

Larger Font Smaller Font Up Down Go comment Print


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


$> cubrid_rel

CUBRID 10.2 ( (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.


# 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.





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 ##################




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.



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



List of Articles
No. Category Subject Date
17 Interfaces How to Configure to Log4J to Log Messages to CUBRID Database 2020.05.12
» Server How to Start CUBRID Automatically upon LINUX Boot 2020.07.17
15 Installation Installing CUBRID and CUBRID Admin on Windows 2020.05.11
14 Installation Installing CUBRID on Linux 2020.05.06
13 Server Introduction to CUBRID Security – Part I file 2020.06.25
12 Server Introduction to CUBRID Security – Part II file 2020.06.26
11 Tools Let’s Take a Look at SQLGate for CUBRID! file 2020.07.23
10 Server Replace the Linux Version CUBRID Default Installation Directory 2020.07.14
9 Tools Reverse Engineering CUBRID Database with ERwin file 2020.07.14
8 Tools Running CUBRID Container Services in Docker, Kubernetes Environment file 2020.07.23
Board Pagination Prev 1 2 3 4 Next
/ 4

Join the CUBRID Project on