Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
Open Source
>
Database Related
>
Database Service
&&
Donate
Please sign in before you donate.
Cancel
Sign in
Scan WeChat QR to Pay
Cancel
Complete
Prompt
Switch to Alipay.
OK
Cancel
Watch
Unwatch
Watching
Releases Only
Ignoring
443
Star
1.5K
Fork
1.8K
openGauss
/
openGauss-server
Code
Issues
976
Pull Requests
151
Wiki
Insights
Pipelines
Service
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
Kylin V10 (Lance)系统docker启动opengauss失败
Canceled
#I8EMBM
Bug
dengbin
Opened this issue
2023-11-07 19:00
【启动失败】: 问题描述 在`Kylin Linux Advanced Server V10 (Lance)`系统下面安装docker,然后执行docker run opengauss运行失败 【操作系统和硬件信息】: ``` # cat /etc/os-release NAME="Kylin Linux Advanced Server" VERSION="V10 (Lance)" ID="kylin" VERSION_ID="V10" PRETTY_NAME="Kylin Linux Advanced Server V10 (Lance)" ANSI_COLOR="0;31" # uname -a Linux k3sserver 4.19.90-52.22.v2207.ky10.x86_64 #1 SMP Tue Mar 14 12:19:10 CST 2023 x86_64 x86_64 x86_64 GNU/Linux ``` 【测试环境】: 单机|极简|docker 【数据库版本】: opengauss/opengauss:5.0.0 【docker版本】: ``` # docker version Client: Docker Engine - Community Version: 20.10.23 API version: 1.41 Go version: go1.18.10 Git commit: 7155243 Built: Thu Jan 19 17:33:56 2023 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.23 API version: 1.41 (minimum version 1.12) Go version: go1.18.10 Git commit: 6051f14 Built: Thu Jan 19 17:32:04 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.24 GitCommit: 61f9fd88f79f081d64d6fa3bb1a0dc71ec870523 runc: Version: 1.1.9 GitCommit: v1.1.9-0-gccaecfc docker-init: Version: 0.19.0 GitCommit: de40ad0 ``` 【操作步骤】: 1. `docker pull opengauss/opengauss:5.0.0` 2. `docker run --name opengauss --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -p 15432:5432 opengauss/opengauss:5.0.0` 【日志信息】: ``` Message: The supplied GS_PASSWORD is meet requirements. 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 "C". The default text search configuration will be set to "english". fixing permissions on existing directory /var/lib/opengauss/data ... 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 /var/lib/opengauss/data/base/1 ... The core dump path is an invalid directory 2023-11-07 10:07:08.350 [unknown] [unknown] localhost 140680318771136 0[0:0#0] [BACKEND] WARNING: macAddr is 578/183042050, sysidentifier is 37882601/169567, randomNum is 3304101471 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 /var/lib/opengauss/data --single_node or gs_ctl start -D /var/lib/opengauss/data -Z single_node -l logfile [2023-11-07 10:07:18.920][179][][gs_ctl]: gs_ctl started,datadir is /var/lib/opengauss/data [2023-11-07 10:07:18.944][179][][gs_ctl]: waiting for server to start... .0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 0 LOG: [Alarm Module]Host Name: a046bca9d8e3 0 LOG: [Alarm Module]Host IP: a046bca9d8e3. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP> 0 LOG: [Alarm Module]Get ENV GS_CLUSTER_NAME failed! 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-11-07 10:07:18.995 [unknown] [unknown] localhost 140280615907264 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-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host Name: a046bca9d8e3 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host IP: a046bca9d8e3. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP> 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Get ENV GS_CLUSTER_NAME failed! 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57 2023-11-07 10:07:19.002 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: loaded library "security_plugin" 2023-11-07 10:07:19.002 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets 2023-11-07 10:07:19.002 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0. 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: reserved memory for backend threads is: 220 MB 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: reserved memory for WAL buffers is: 128 MB 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: Set max backend reserve memory is: 348 MB, max dynamic memory is: 8143 MB 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: shared memory 3284 Mbytes, memory context 8491 Mbytes, max process memory 12288 Mbytes 2023-11-07 10:07:19.067 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [CACHE] LOG: set data cache size(402653184) 2023-11-07 10:07:19.111 [unknown] [unknown] localhost 140280615907264 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-11-07 10:07:19.136 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: gaussdb: fsync file "/var/lib/opengauss/data/gaussdb.state.temp" success 2023-11-07 10:07:19.136 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: create gaussdb state file success: db state(STARTING_STATE), server mode(Normal), connection index(1) 2023-11-07 10:07:19.179 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: max_safe_fds = 978, usable_fds = 1000, already_open = 12 The core dump path is an invalid directory 2023-11-07 10:07:19.180 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: user configure file is not found, it will be created. 2023-11-07 10:07:19.186 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: the configure file /usr/local/opengauss/etc/gscgroup_omm.cfg doesn't exist or the size of configure file has changed. Please create it by root user! 2023-11-07 10:07:19.186 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: Failed to parse cgroup config file. [2023-11-07 10:07:24.951][179][][gs_ctl]: gaussDB state is Coredump [2023-11-07 10:07:24.951][179][][gs_ctl]: stopped waiting [2023-11-07 10:07:24.951][179][][gs_ctl]: could not start server Examine the log output. ```
【启动失败】: 问题描述 在`Kylin Linux Advanced Server V10 (Lance)`系统下面安装docker,然后执行docker run opengauss运行失败 【操作系统和硬件信息】: ``` # cat /etc/os-release NAME="Kylin Linux Advanced Server" VERSION="V10 (Lance)" ID="kylin" VERSION_ID="V10" PRETTY_NAME="Kylin Linux Advanced Server V10 (Lance)" ANSI_COLOR="0;31" # uname -a Linux k3sserver 4.19.90-52.22.v2207.ky10.x86_64 #1 SMP Tue Mar 14 12:19:10 CST 2023 x86_64 x86_64 x86_64 GNU/Linux ``` 【测试环境】: 单机|极简|docker 【数据库版本】: opengauss/opengauss:5.0.0 【docker版本】: ``` # docker version Client: Docker Engine - Community Version: 20.10.23 API version: 1.41 Go version: go1.18.10 Git commit: 7155243 Built: Thu Jan 19 17:33:56 2023 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.23 API version: 1.41 (minimum version 1.12) Go version: go1.18.10 Git commit: 6051f14 Built: Thu Jan 19 17:32:04 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.24 GitCommit: 61f9fd88f79f081d64d6fa3bb1a0dc71ec870523 runc: Version: 1.1.9 GitCommit: v1.1.9-0-gccaecfc docker-init: Version: 0.19.0 GitCommit: de40ad0 ``` 【操作步骤】: 1. `docker pull opengauss/opengauss:5.0.0` 2. `docker run --name opengauss --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -p 15432:5432 opengauss/opengauss:5.0.0` 【日志信息】: ``` Message: The supplied GS_PASSWORD is meet requirements. 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 "C". The default text search configuration will be set to "english". fixing permissions on existing directory /var/lib/opengauss/data ... 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 /var/lib/opengauss/data/base/1 ... The core dump path is an invalid directory 2023-11-07 10:07:08.350 [unknown] [unknown] localhost 140680318771136 0[0:0#0] [BACKEND] WARNING: macAddr is 578/183042050, sysidentifier is 37882601/169567, randomNum is 3304101471 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 /var/lib/opengauss/data --single_node or gs_ctl start -D /var/lib/opengauss/data -Z single_node -l logfile [2023-11-07 10:07:18.920][179][][gs_ctl]: gs_ctl started,datadir is /var/lib/opengauss/data [2023-11-07 10:07:18.944][179][][gs_ctl]: waiting for server to start... .0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 0 LOG: [Alarm Module]Host Name: a046bca9d8e3 0 LOG: [Alarm Module]Host IP: a046bca9d8e3. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP> 0 LOG: [Alarm Module]Get ENV GS_CLUSTER_NAME failed! 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-11-07 10:07:18.995 [unknown] [unknown] localhost 140280615907264 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-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host Name: a046bca9d8e3 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host IP: a046bca9d8e3. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP> 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Get ENV GS_CLUSTER_NAME failed! 2023-11-07 10:07:19.000 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57 2023-11-07 10:07:19.002 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: loaded library "security_plugin" 2023-11-07 10:07:19.002 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets 2023-11-07 10:07:19.002 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0. 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: reserved memory for backend threads is: 220 MB 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: reserved memory for WAL buffers is: 128 MB 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: Set max backend reserve memory is: 348 MB, max dynamic memory is: 8143 MB 2023-11-07 10:07:19.004 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: shared memory 3284 Mbytes, memory context 8491 Mbytes, max process memory 12288 Mbytes 2023-11-07 10:07:19.067 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [CACHE] LOG: set data cache size(402653184) 2023-11-07 10:07:19.111 [unknown] [unknown] localhost 140280615907264 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-11-07 10:07:19.136 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: gaussdb: fsync file "/var/lib/opengauss/data/gaussdb.state.temp" success 2023-11-07 10:07:19.136 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: create gaussdb state file success: db state(STARTING_STATE), server mode(Normal), connection index(1) 2023-11-07 10:07:19.179 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: max_safe_fds = 978, usable_fds = 1000, already_open = 12 The core dump path is an invalid directory 2023-11-07 10:07:19.180 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: user configure file is not found, it will be created. 2023-11-07 10:07:19.186 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: the configure file /usr/local/opengauss/etc/gscgroup_omm.cfg doesn't exist or the size of configure file has changed. Please create it by root user! 2023-11-07 10:07:19.186 [unknown] [unknown] localhost 140280615907264 0[0:0#0] 0 [BACKEND] LOG: Failed to parse cgroup config file. [2023-11-07 10:07:24.951][179][][gs_ctl]: gaussDB state is Coredump [2023-11-07 10:07:24.951][179][][gs_ctl]: stopped waiting [2023-11-07 10:07:24.951][179][][gs_ctl]: could not start server Examine the log output. ```
Comments (
6
)
Sign in
to comment
Status
Canceled
Backlog
Confirmed
已答复
Canceled
挂起
Fixing
Done
待回归
测试中
Accepted
Assignees
Not set
liuheng
hengliue
Assignee
Collaborator
+Assign
+Mention
周斌
justbk
Assignee
Collaborator
+Assign
+Mention
Labels
Not set
Projects
Unprojected
Unprojected
Milestones
No related milestones
No related milestones
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (20)
Tags (30)
master
6.0.0
5.0.0
datavec_poc
tp_poc
7.0.0-RC2
7.0.0-RC1
master_bak08271930
bugfix_0725
3.0.0
iud_dev
dev_board
5.1.0
kms
2.0.0
3.1.0
2.1.0
1.1.0
1.0.1
1.0.0
v7.0.0-RC2
v6.0.2
v7.0.0-RC1
v6.0.1
v3.0.6
v6.0.0
v3.0.5B009
v5.0.3
v5.0.2
v6.0.0-RC1
v3.0.5
v5.0.1
v5.1.0
5.1.0
v5.0.0
v3.0.3
v3.1.1
v3.0.2
v3.1.0
v2.0.5
v3.0.1
v2.0.4
v2.0.3
v3.0.0
v2.1.0
v2.0.1
v2.0.0
v1.1.0
v1.0.1
v1.0.0
Planed to start   -   Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
(hours)
参与者(2)
C++
1
https://gitee.com/opengauss/openGauss-server.git
git@gitee.com:opengauss/openGauss-server.git
opengauss
openGauss-server
openGauss-server
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register