openGauss支持以脚本方式进行极简安装,极简安装包括单节点安装和一主一备节点安装。
从openGauss开源社区下载对应平台的安装包
解压安装包,检查安装目录及文件是否齐全。在安装包所在目录执行以下命令:
[root@localhost ~]# cd /opt
[root@localhost opt]# mkdir openGauss
[root@localhost opt]# ls
openGauss openGauss-3.1.1-openEuler-64bit.tar.bz2 patch_workspace
[root@localhost opt]# tar -jxf openGauss-3.1.1-openEuler-64bit.tar.bz2 -C openGauss/
.
.
.
tar: ./share/postgresql/postgresql.conf.sample:时间戳 2023-01-06 09:36:25 是未来的 3241974.33647889 秒之后
tar: ./share/postgresql/performance_views.sql:时间戳 2023-01-06 09:36:20 是未来的 3241969.329454592 秒之后
tar: ./share/postgresql/snowball_create.sql:时间戳 2023-01-06 09:36:29 是未来的 3241978.329262687 秒之后
tar: ./share/postgresql/pg_cast_oid.txt:时间戳 2023-01-06 09:36:20 是未来的 3241969.329202685 秒之后
tar: ./share/postgresql/tmp/udstools.py:时间戳 2023-01-06 09:36:25 是未来的 3241974.329119449 秒之后
tar: ./share/postgresql/tmp:时间戳 2023-01-06 09:39:10 是未来的 3242139.329099462 秒之后
tar: ./share/postgresql:时间戳 2023-01-06 09:39:11 是未来的 3242140.329066682 秒之后
tar: ./share/llvmir/GaussDB_expr.ir:时间戳 2023-01-06 09:36:20 是未来的 3241969.328677367 秒之后
tar: ./share/llvmir:时间戳 2023-01-06 09:39:12 是未来的 3242141.328643249 秒之后
tar: ./share:时间戳 2023-01-06 09:39:11 是未来的 3242140.328618308 秒之后
tar: ./simpleInstall/finance.sql:时间戳 2023-01-06 09:39:13 是未来的 3242142.328535652 秒之后
tar: ./simpleInstall/README.md:时间戳 2023-01-06 09:39:13 是未来的 3242142.328477377 秒之后
tar: ./simpleInstall/school.sql:时间戳 2023-01-06 09:39:13 是未来的 3242142.328415969 秒之后
tar: ./simpleInstall/install.sh:时间戳 2023-01-06 09:39:13 是未来的 3242142.327986469 秒之后
tar: ./simpleInstall:时间戳 2023-01-06 09:39:13 是未来的 3242142.32793454 秒之后
tar: ./version.cfg:时间戳 2023-01-06 09:39:13 是未来的 3242142.32787418 秒之后
[root@localhost opt]#
执行tree命令,显示类似如下信息:
[root@localhost opt]# tree -d openGauss
openGauss
├── bin
├── etc
│ └── kerberos
├── include
│ └── postgresql
│ └── server
│ ├── access
│ │ ├── obs
│ │ ├── parallel_recovery
│ │ └── ustore
│ │ └── undo
│ ├── alarm
│ ├── bulkload
│ ├── catalog
│ ├── cjson
│ ├── client_logic
│ ├── cm
│ ├── commands
│ ├── communication
│ ├── datatype
│ ├── db4ai
│ ├── executor
│ │ └── exec
│ ├── fmgr
│ ├── foreign
│ ├── gssignal
│ ├── gstrace
│ ├── gtm
│ ├── hotpatch
│ ├── instruments
│ ├── knl
│ │ └── knl_guc
│ ├── lib
│ ├── libcomm
│ ├── libpq
│ ├── mb
│ ├── nodes
│ ├── optimizer
│ ├── parser
│ ├── pgxc
│ ├── port
│ ├── portability
│ ├── postmaster
│ ├── replication
│ ├── rewrite
│ ├── ssl
│ ├── storage
│ │ ├── buf
│ │ ├── cstore
│ │ ├── item
│ │ ├── lock
│ │ ├── mot
│ │ └── smgr
│ ├── streaming
│ ├── tcop
│ ├── tde_key_management
│ ├── threadpool
│ ├── utils
│ ├── vecexecutor
│ └── workload
├── jre
│ ├── bin
│ └── lib
│ ├── amd64
│ │ ├── jli
│ │ └── server
│ ├── cmm
│ ├── ext
│ ├── images
│ │ └── cursors
│ ├── jfr
│ ├── management
│ └── security
│ └── policy
│ ├── limited
│ └── unlimited
├── lib
│ ├── krb5
│ │ └── plugins
│ │ └── kdb
│ ├── libsimsearch
│ └── postgresql
│ ├── java
│ ├── pg_plugin
│ ├── pgxs
│ │ ├── config
│ │ └── src
│ │ └── makefiles
│ └── proc_srclib
├── share
│ ├── llvmir
│ ├── postgresql
│ │ ├── db4ai
│ │ │ └── snapshots
│ │ ├── extension
│ │ ├── timezone
│ │ │ ├── Africa
│ │ │ ├── America
│ │ │ │ ├── Argentina
│ │ │ │ ├── Indiana
│ │ │ │ ├── Kentucky
│ │ │ │ └── North_Dakota
│ │ │ ├── Antarctica
│ │ │ ├── Arctic
│ │ │ ├── Asia
│ │ │ ├── Atlantic
│ │ │ ├── Australia
│ │ │ ├── Brazil
│ │ │ ├── Canada
│ │ │ ├── Chile
│ │ │ ├── Etc
│ │ │ ├── Europe
│ │ │ ├── Indian
│ │ │ ├── Mexico
│ │ │ ├── Mideast
│ │ │ ├── Pacific
│ │ │ └── US
│ │ ├── timezonesets
│ │ ├── tmp
│ │ └── tsearch_data
│ └── sslcert
│ ├── gsql
│ └── om
└── simpleInstall
124 directories
[root@localhost opt]#
本节描述安装前需要进行的环境准备。建议部署openGauss的各服务器具有等价的软硬件配置。
下面列出了openGauss服务器应具备的最低硬件要求。在实际产品中,硬件配置的规划需考虑数据规模及所期望的数据库响应速度。请根据实际情况进行规划。
功能调试建议32GB以上。性能测试和商业部署时,单实例部署建议128GB以上。复杂的查询对内存的需求量比较高,在高并发场景下,可能出现内存不足。此时建议使用大内存的机器,或使用负载管理限制系统的并发。
功能调试最小1×8 核 2.0GHz。性能测试和商业部署时,建议1×16核 2.0GHz。CPU超线程和非超线程两种模式都支持。说明:个人开发者最低配置2核4G, 推荐配置4核8G。目前,openGauss仅支持ARM服务器和基于X86_64通用PC服务器的CPU。
用于安装openGauss的硬盘需最少满足如下要求:至少1GB用于安装openGauss的应用程序。每个主机需大约300MB用于元数据存储。预留70%以上的磁盘剩余空间用于数据存储。建议系统盘配置为Raid1,数据盘配置为Raid5,且规划4组Raid5数据盘用于安装openGauss。有关Raid的配置方法在本节中不做介绍。请参考硬件厂家的手册或互联网上的方法进行配置,其中Disk Cache Policy一项需要设置为Disabled,否则机器异常掉电后有数据丢失的风险。openGauss支持使用SSD盘作为数据库的主存储设备,支持SAS接口和NVME协议的SSD盘,以RAID的方式部署使用。
300兆以上以太网。建议网卡设置为双网卡冗余bond。有关网卡冗余bond的配置方法在本节中不做介绍。请参考硬件厂商的手册或互联网上的方法进行配置。
openEuler 20.3LTS(推荐采用此操作系统)
麒麟V10 Asianux 7.5
openEuler 20.3LTS
CentOS 7.6
Asianux 7.6
说明:当前安装包只能在英文操作系统上安装使用。
Linux文件系统
剩余inode个数 > 15亿(推荐)
工具
bzip2
openGauss的软件依赖要求如表1 软件依赖要求所示。
建议使用上述操作系统安装光盘或者源中,下列依赖软件的默认安装包,若不存在下列软件,可参看软件对应的建议版本。
表 1 软件依赖要求
所需软件 | 建议版本 |
---|---|
libaio-devel | 建议版本:0.3.109-13 |
flex | 要求版本:2.5.31 以上 |
bison | 建议版本:2.7-4 |
ncurses-devel | 建议版本:5.9-13.20130511 |
glibc-devel | 建议版本:2.17-111 |
patch | 建议版本:2.7.1-10 |
redhat-lsb-core | 建议版本:4.1 |
readline-devel | 建议版本:7.0-13 |
libnsl(openEuler+x86环境中) | 建议版本 :2.28-36 |
安装软件依赖包
[root@localhost ~]# yum install -y libaio-devel \
> flex \
> bison \
> ncurses-devel \
> glibc-devel \
> patch \
> redhat-lsb-core \
> readline-devel \
> libnsl
Last metadata expiration check: 0:10:26 ago on 2023年03月17日 星期五 22时02分48秒.
Package flex-2.6.4-3.oe2203.x86_64 is already installed.
Package bison-3.8.2-1.oe2203.x86_64 is already installed.
Package glibc-devel-2.34-70.oe2203.x86_64 is already installed.
Package patch-2.7.6-12.oe2203.x86_64 is already installed.
No match for argument: redhat-lsb-core
Error: Unable to find a match: redhat-lsb-core
[root@localhost ~]#
可以看到,系统提示没有找到匹配的redhat-lsb-core
包。
经过在openEuler官方镜像仓库查看得知,openEuler不存在这个包,不影响后续安装数据库。
说明:
测试环境下通常会关闭防火墙以避免部分网络因素影响,视实际需求做配置。
在root权限下停止防火墙
[root@localhost ~]# systemctl stop firewalld
[root@localhost ~]#
在root权限下关闭防火墙自启动
[root@localhost ~]# systemctl disable firewalld
Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
Removed /etc/systemd/system/multi-user.target.wants/firewalld.service.
[root@localhost ~]#
说明:
执行disable命令关闭防火墙的同时,也取消了开机自启动。
在root权限下修改配置文件。
[root@localhost ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/sysconfig/selinux
[root@localhost ~]#
[root@localhost ~]# cat /etc/sysconfig/selinux
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these three values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted
[root@localhost ~]#
说明:
重启后生效。
[root@localhost ~]# setenforce 0
setenforce: SELinux is permissive
[root@localhost ~]#
说明:
即时生效,但重启后会自动开启。
[root@localhost ~]# hostnamectl set-hostname gaussdb1
[root@localhost ~]# echo "192.168.0.21 gaussdb1" >>/etc/hosts
[root@localhost ~]# groupadd dbgroup
创建用户组dbgroup下的普通用户omm,并设置普通用户omm的密码,密码建议设置为Omm@123。
[root@localhost ~]# useradd -g dbgroup omm
[root@localhost ~]#
[root@localhost ~]# passwd omm
更改用户 omm 的密码 。
新的密码:
无效的密码: 密码少于 8 个字符
重新输入新的密码:
抱歉,密码不匹配。
passwd: 鉴定令牌操作错误
[root@localhost ~]#
[root@localhost ~]# passwd omm
更改用户 omm 的密码 。
新的密码:
无效的密码: 密码少于 8 个字符
重新输入新的密码:
passwd:所有的身份验证令牌已经成功更新。
[root@localhost ~]#
[root@gaussdb1 ~]# chown -R omm:dbgroup /opt/openGauss
[root@gaussdb1 ~]#
[root@localhost ~]# echo "* soft nofile 1000000" >>/etc/security/limits.conf
[root@localhost ~]# echo "* hard nofile 1000000" >>/etc/security/limits.conf
[root@gaussdb1 opt]# reboot
[root@gaussdb1 ~]# su - omm
上一次登录: 五 3月 17 22:29:56 CST 2023 pts/0 上
Welcome to 5.10.0-60.18.0.50.oe2203.x86_64
System information as of time: 2023年 03月 17日 星期五 22:33:56 CST
System load: 0.00
Processes: 152
Memory used: 8.2%
Swap used: 0%
Usage On: 8%
IP address: 192.168.0.21
IP address: 192.168.122.1
Users online: 2
To run a command as administrator(user "root"),use "sudo " .
[omm@gaussdb1 ~]$
进入解压后目录下的simpleInstall
[omm@gaussdb1 ~]$ cd /opt/openGauss/simpleInstall
[omm@gaussdb1 simpleInstall]$
[omm@gaussdb1 simpleInstall]$ sh install.sh -w Gs.initdb
[step 1]: check parameter
[step 2]: check install env and os setting
[step 3]: change_gausshome_owner
[step 4]: set environment variables
[step 6]: init datanode
The files belonging to this database system will be owned by user "omm".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
creating directory /opt/openGauss/data/single_node ... ok
creating subdirectories ... in ordinary occasionok
creating configuration files ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1024MB
Begin init undo subsystem meta.
[INIT UNDO] Init undo subsystem meta successfully.
creating template1 database in /opt/openGauss/data/single_node/base/1 ... The core dump path is an invalid directory
2023-03-18 00:12:25.778 [unknown] [unknown] localhost 140147207374400 0[0:0#0] [BACKEND] WARNING: macAddr is 12/690964518, sysidentifier is 796975/1210449937, randomNum is 2522021905
ok
initializing pg_authid ... ok
setting password ... ok
initializing dependencies ... ok
loading PL/pgSQL server-side language ... ok
creating system views ... ok
creating performance views ... ok
loading system objects' descriptions ... ok
creating collations ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
initialize global configure for bucketmap length ... ok
creating information schema ... ok
loading foreign-data wrapper for distfs access ... ok
loading foreign-data wrapper for log access ... ok
loading hstore extension ... ok
loading foreign-data wrapper for MOT access ... ok
loading security plugin ... ok
update system tables ... ok
creating snapshots catalog ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
freezing database template0 ... ok
freezing database template1 ... ok
freezing database postgres ... ok
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run gs_initdb.
Success. You can now start the database server of single node using:
gaussdb -D /opt/openGauss/data/single_node --single_node
or
gs_ctl start -D /opt/openGauss/data/single_node -Z single_node -l logfile
[step 7]: start datanode
[2023-03-18 00:12:37.321][2266][][gs_ctl]: gs_ctl started,datadir is /opt/openGauss/data/single_node
[2023-03-18 00:12:37.343][2266][][gs_ctl]: waiting for server to start...
.0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.
0 LOG: [Alarm Module]Host Name: gaussdb1
0 LOG: [Alarm Module]Host IP: gaussdb1. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain
0 LOG: [Alarm Module]Cluster Name: dbCluster
0 LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57
0 WARNING: failed to open feature control file, please check whether it exists: FileName=gaussdb.version, Errno=2, Errmessage=No such file or directory.
0 WARNING: failed to parse feature control file: gaussdb.version.
0 WARNING: Failed to load the product control file, so gaussdb cannot distinguish product version.
The core dump path is an invalid directory
2023-03-18 00:12:37.399 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: when starting as multi_standby mode, we couldn' t support data replicaton.
gaussdb.state does not exist, and skipt setting since it is optional.2023-03-18 00:12:37.409 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.
2023-03-18 00:12:37.409 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host Name: gaussdb1
2023-03-18 00:12:37.409 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host IP: gaussdb1. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain
2023-03-18 00:12:37.409 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Cluster Name: dbCluster
2023-03-18 00:12:37.409 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57
2023-03-18 00:12:37.415 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: loaded library "security_plugin"
2023-03-18 00:12:37.417 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
2023-03-18 00:12:37.417 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
2023-03-18 00:12:37.420 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] WARNING: No explicit IP is configured for listen_addresses GUC.
2023-03-18 00:12:37.420 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0.
2023-03-18 00:12:37.420 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: reserved memory for backend threads is: 220 MB
2023-03-18 00:12:37.420 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: reserved memory for WAL buffers is: 128 MB
2023-03-18 00:12:37.420 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: Set max backend reserve memory is: 348 MB, max dynamic memory is: 8142 MB
2023-03-18 00:12:37.420 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: shared memory 3285 Mbytes, memory context 8490 Mbytes, max process memory 12288 Mbytes
2023-03-18 00:12:37.484 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [CACHE] LOG: set data cache size(402653184)
2023-03-18 00:12:37.531 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [SEGMENT_PAGE] LOG: Segment-page constants: DF_MAP_SIZE: 8156, DF_MAP_BIT_CNT: 65248, DF_MAP_GROUP_EXTENTS: 4175872, IPBLOCK_SIZE: 8168, EXTENTS_PER_IPBLOCK: 1021, IPBLOCK_GROUP_SIZE: 4090, BMT_HEADER_LEVEL0_TOTAL_PAGES: 8323072, BktMapEntryNumberPerBlock: 2038, BktMapBlockNumber: 25, BktBitMaxMapCnt: 512
2023-03-18 00:12:37.555 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: gaussdb: fsync file "/opt/openGauss/data/single_node/gaussdb.state.temp" success
2023-03-18 00:12:37.555 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: create gaussdb state file success: db state(STARTING_STATE), server mode(Normal), connection index(1)
2023-03-18 00:12:37.581 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: max_safe_fds = 976, usable_fds = 1000, already_open = 14
The core dump path is an invalid directory
2023-03-18 00:12:37.584 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: user configure file is not found, it will be created.
2023-03-18 00:12:37.591 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: the configure file /opt/openGauss/etc/gscgroup_omm.cfg doesn't exist or the size of configure file has changed. Please create it by root user!
2023-03-18 00:12:37.591 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [BACKEND] LOG: Failed to parse cgroup config file.
2023-03-18 00:12:37.625 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] WARNING: Failed to obtain environment value $GAUSSLOG!
2023-03-18 00:12:37.625 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] DETAIL: N/A
2023-03-18 00:12:37.625 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] CAUSE: Incorrect environment value.
2023-03-18 00:12:37.625 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] ACTION: Please refer to backend log for more details.
2023-03-18 00:12:37.628 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] WARNING: Failed to obtain environment value $GAUSSLOG!
2023-03-18 00:12:37.629 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] DETAIL: N/A
2023-03-18 00:12:37.629 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] CAUSE: Incorrect environment value.
2023-03-18 00:12:37.629 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] ACTION: Please refer to backend log for more details.
2023-03-18 00:12:37.630 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] WARNING: Failed to obtain environment value $GAUSSLOG!
2023-03-18 00:12:37.630 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] DETAIL: N/A
2023-03-18 00:12:37.630 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] CAUSE: Incorrect environment value.
2023-03-18 00:12:37.630 [unknown] [unknown] localhost 139709877147200 0[0:0#0] 0 [EXECUTOR] ACTION: Please refer to backend log for more details.
[2023-03-18 00:12:38.630][2266][][gs_ctl]: done
[2023-03-18 00:12:38.630][2266][][gs_ctl]: server started (/opt/openGauss/data/single_node)
import sql file
Would you like to create a demo database (yes/no)? yes
Load demoDB [school,finance] success.
[complete successfully]: You can start or stop the database server using:
gs_ctl start|stop|restart -D $GAUSSHOME/data/single_node -Z single_node
[omm@gaussdb1 simpleInstall]$
上述命令中,-w是指初始化数据库密码(gs_initdb),安全需要必须设置。
如果安装报错:gs_initdb: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory。
解决方法(root用户执行):
[root@gaussdb1 ~]# cd /usr/lib64
[root@gaussdb1 lib64]#
[root@gaussdb1 lib64]# ls libreadline*
libreadline.so.8 libreadline.so.8.1
[root@gaussdb1 lib64]#
[root@gaussdb1 lib64]# ln -s libreadline.so.8 libreadline.so.7
[root@gaussdb1 lib64]#
[root@gaussdb1 lib64]# ll libreadline*
lrwxrwxrwx. 1 root root 16 3月 17 22:49 libreadline.so.7 -> libreadline.so.8
lrwxrwxrwx. 1 root root 18 11月 27 2021 libreadline.so.8 -> libreadline.so.8.1
-rwxr-xr-x. 1 root root 336K 11月 27 2021 libreadline.so.8.1
[root@gaussdb1 lib64]#
安装执行完成后,使用ps和gs_ctl检查进程是否正常
$ ps ux | grep gaussdb
执行ps命令,显示类似如下信息:
[omm@gaussdb1 simpleInstall]$ ps ux | grep gaussdb
omm 2358 9.3 21.8 5767796 758068 ? Ssl 23:09 0:23 /opt/openGauss/bin/gaussdb -D /opt/openGauss/data/single_node
omm 2704 0.0 0.0 6352 2188 pts/0 S+ 23:13 0:00 grep --color=auto gaussdb
[omm@gaussdb1 simpleInstall]$
$ gs_ctl query -D $GAUSSHOME/data/master -M primary
$ gs_ctl query -D $GAUSSHOME/data/master -M standby
执行gs_ctl命令,显示类似如下信息:
[omm@gaussdb1 simpleInstall]$ gs_ctl query -D /opt/openGauss/data/single_node
[2023-03-17 23:16:55.609][2917][][gs_ctl]: gs_ctl query ,datadir is /opt/openGauss/data/single_node
HA state:
local_role : Normal
static_connections : 0
db_state : Normal
detail_information : Normal
Senders info:
No information
Receiver info:
No information
[omm@gaussdb1 simpleInstall]$
点赞,你的认可是我创作的动力!
⭐️ 收藏,你的青睐是我努力的方向!
✏️ 评论,你的意见是我进步的财富!