暂无图片
openGauss轻量版3.1.0报错
我来答
分享
后知后觉
2023-03-27
openGauss轻量版3.1.0报错

执行安装时,报下面错误

[omm@master01 ~]$ gs_install -X /opt/software/open.xml

Parsing the configuration file.

Check preinstall on every node.

Successfully checked preinstall on every node.

Creating the backup directory.

Successfully created the backup directory.

begin deploy..

Installing the cluster.

begin prepare Install Cluster..

Checking the installation environment on all nodes.

begin install Cluster..

Installing applications on all nodes.

Successfully installed APP.

begin init Instance..

encrypt cipher and rand files for database.

Please enter password for database:

Please repeat for database:

begin to create CA cert files

The sslcert will be generated in /opt/software/install/app/share/sslcert/om

NO cm_server instance, no need to create CA for CM.

Cluster installation is completed.

Configuring.

Deleting instances from all nodes.

Successfully deleted instances from all nodes.

Checking node configuration on all nodes.

Initializing instances on all nodes.

Updating instance configuration on all nodes.

Check consistence of memCheck and coresCheck on database nodes.

Configuring pg_hba on all nodes.

Configuration is completed.

Using omm:dbgrp to install database.

Using installation program path : /opt/software/install/app_4e931f9a

$GAUSSHOME points to /opt/software/install/app_4e931f9a, no need to create symbolic link.

Traceback (most recent call last):

  File "/opt/software/om/script/local/Install.py", line 763, in <module>

    functionDict[g_opts.action]()

  File "/opt/software/om/script/local/Install.py", line 694, in startCluster

    dn.start(self.time_out)

  File "/opt/software/om/script/local/../gspylib/component/Kernel/Kernel.py", line 106, in start

    "failure details." "\n" + output)

Exception: [GAUSS-51607] : Failed to start instance. Error: Please check the gs_ctl log for failure details.

[2023-01-08 19:02:45.552][12958][][gs_ctl]: gs_ctl started,datadir is /opt/software/install/data/dn

[2023-01-08 19:02:45.628][12958][][gs_ctl]: waiting for server to start...

.0 LOG:  [Alarm Module]can not read GAUSS_WARNING_TYPE env.

 

0 LOG:  [Alarm Module]Host Name: master01

 

0 LOG:  [Alarm Module]Host IP: master01. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP>

 

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.

2023-01-08 19:02:45.786 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 DB010  0 [REDO] LOG:  Recovery parallelism, cpu count = 2, max = 4, actual = 2

2023-01-08 19:02:45.786 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 DB010  0 [REDO] LOG:  ConfigRecoveryParallelism, true_max_recovery_parallelism:4, max_recovery_parallelism:4

gaussdb.state does not exist, and skipt setting since it is optional.2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]can not read GAUSS_WARNING_TYPE env.

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Host Name: master01

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Host IP: master01. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP>

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Cluster Name: dbCluster

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57

 

2023-01-08 19:02:45.798 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  loaded library "security_plugin"

2023-01-08 19:02:45.800 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  could not create any HA TCP/IP sockets

2023-01-08 19:02:45.800 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  could not create any HA TCP/IP sockets

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0.

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  Failed to initialize the memory protect for g_instance.attr.attr_storage.cstore_buffers (1024 Mbytes) or shared memory (3608 Mbytes) is larger.

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809  0 [BACKEND] FATAL:  could not create shared memory segment: Cannot allocate memory

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809  0 [BACKEND] DETAIL:  Failed system call was shmget(key=15400001, size=3784296776, 03600).

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809  0 [BACKEND] HINT:  This error usually means that openGauss's request for a shared memory segment exceeded available memory or swap space, or exceeded your kernel's SHMALL parameter. You can either reduce the request size or reconfigure the kernel with larger SHMALL.  To reduce the request size (currently 3784296776 bytes), reduce openGauss's shared memory usage, perhaps by reducing shared_buffers.

        The openGauss documentation contains more information about shared memory configuration.

2023-01-08 19:02:45.815 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  FiniNuma allocIndex: 0.

[2023-01-08 19:02:46.630][12958][][gs_ctl]: waitpid 12961 failed, exitstatus is 256, ret is 2

 

[2023-01-08 19:02:46.630][12958][][gs_ctl]: stopped waiting

[2023-01-08 19:02:46.630][12958][][gs_ctl]: could not start server

Examine the log output.

 

[GAUSS-51607] : Failed to start instance. Error: Please check the gs_ctl log for failure details.

[2023-01-08 19:02:45.552][12958][][gs_ctl]: gs_ctl started,datadir is /opt/software/install/data/dn

[2023-01-08 19:02:45.628][12958][][gs_ctl]: waiting for server to start...

.0 LOG:  [Alarm Module]can not read GAUSS_WARNING_TYPE env.

 

0 LOG:  [Alarm Module]Host Name: master01

 

0 LOG:  [Alarm Module]Host IP: master01. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP>

 

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.

2023-01-08 19:02:45.786 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 DB010  0 [REDO] LOG:  Recovery parallelism, cpu count = 2, max = 4, actual = 2

2023-01-08 19:02:45.786 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 DB010  0 [REDO] LOG:  ConfigRecoveryParallelism, true_max_recovery_parallelism:4, max_recovery_parallelism:4

gaussdb.state does not exist, and skipt setting since it is optional.2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]can not read GAUSS_WARNING_TYPE env.

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Host Name: master01

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Host IP: master01. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP>

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Cluster Name: dbCluster

 

2023-01-08 19:02:45.795 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57

 

2023-01-08 19:02:45.798 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  loaded library "security_plugin"

2023-01-08 19:02:45.800 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  could not create any HA TCP/IP sockets

2023-01-08 19:02:45.800 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  could not create any HA TCP/IP sockets

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0.

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  Failed to initialize the memory protect for g_instance.attr.attr_storage.cstore_buffers (1024 Mbytes) or shared memory (3608 Mbytes) is larger.

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809  0 [BACKEND] FATAL:  could not create shared memory segment: Cannot allocate memory

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809  0 [BACKEND] DETAIL:  Failed system call was shmget(key=15400001, size=3784296776, 03600).

2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809  0 [BACKEND] HINT:  This error usually means that openGauss's request for a shared memory segment exceeded available memory or swap space, or exceeded your kernel's SHMALL parameter. You can either reduce the request size or reconfigure the kernel with larger SHMALL.  To reduce the request size (currently 3784296776 bytes), reduce openGauss's shared memory usage, perhaps by reducing shared_buffers.

        The openGauss documentation contains more information about shared memory configuration.

2023-01-08 19:02:45.815 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  FiniNuma allocIndex: 0.

[2023-01-08 19:02:46.630][12958][][gs_ctl]: waitpid 12961 failed, exitstatus is 256, ret is 2

 

[2023-01-08 19:02:46.630][12958][][gs_ctl]: stopped waiting

[2023-01-08 19:02:46.630][12958][][gs_ctl]: could not start server

Examine the log output.

我来答
添加附件
收藏
分享
问题补充
1条回答
默认
最新
DarkAthena
Failed to initialize the memory protect for g_instance.attr.attr_storage.cstore_buffers (1024 Mbytes) or shared memory (3608 Mbytes) is larger. 2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809 0 [BACKEND] FATAL: could not create shared memory segment: Cannot allocate memory 2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809 0 [BACKEND] DETAIL: Failed system call was shmget(key=15400001, size=3784296776, 03600). 2023-01-08 19:02:45.804 63baa2d5.1 [unknown] 140188304712832 [unknown] 0 dn_6001 42809 0 [BACKEND] HINT: This error usually means that openGauss's request for a shared memory segment exceeded available memory or swap space, or exceeded your kernel's SHMALL parameter. You can either reduce the request size or reconfigure the kernel with larger SHMALL. To reduce the request size (currently 3784296776 bytes), reduce openGauss's shared memory usage, perhaps by reducing shared_buffers.
复制

调小cstore_buffers 和 shared_buffer
或者调大操作系统内核的SHMALL参数

暂无图片 评论
暂无图片 有用 0
打赏 0
回答交流
Markdown


请输入正文
提交
相关推荐
OpenGaussdb 数据库连接时碰到了schema的问题
回答 3
谢谢大佬彭冲,加上currentSchema已经好了,多谢章宇文,你说的还没试
通过 gs_check -i CheckDBConnection检查数据库的实例连接,出现 ERROR: Execute SSH command on host 服务器私网IP faild. The exception is:
回答 2
你好,你可以通过L参数选项本地运行该命令的方式解决此问题gscheckUommiCheckClusterStateL
安装插件需要先在编译openGauss-server的时候介绍-enable-xxx-fdw插件,但安装非编译的openGauss-server怎么安装插件呢?
回答 1
单独编译插件之后,手工将相应的so库文件拷贝到openGauss的lib文件夹下,还有插件相关的sql文件和control文件拷贝到相应的extension目录下即可。更多详细可以参考如下链接(复制链
opengauss安装报错
回答 2
试试设一下环境变量呗。参考如下:vi.bashprofile加入下面两行,路径根据实际添加exportPGHOME/opt/openGauss/appexportPGDATA/opt/openGaus
在UOS上安装失败? CPU:kirin990
回答 4
建议安装openEular20.03版本,和openGauss5.0.1的兼容性是最好的。
opengauss集群修改IP后gs_om显示还是旧的IP,这个是如何修改呢?
回答 5
已采纳
postgresql.confpghba.confclusterconfig.xml(用于生成staticconfiguration)/etc/hosts都已经修改没问题gsomtstop和gsomt
openGauss数据库故障定位思路?
回答 1
从报错提示入手,具体可以看看报错日志;openGauss也提供了一些视图来存其运行状态;还有就是收集core文件进行分析。具体参考官方的建议思路:日志。数据库日志记录了数据库服务端启动、运行或停止时出
麒麟V10安装opengauss
回答 4
我安装完成之后,怎么验证安装是否完成,有哪些基础操作,比如创建表,添加数据这些
请问一下 opengauss 不支持 C 的 window 函数吗
回答 2
例如在postgis中的CREATEORREPLACEFUNCTIONSTClusterDBSCAN(geometry,epsfloat8,minpointsint)RETURNSintAS'$lib
opengauss表空间所在目录满了,新增加目录,处理步骤?
回答 3
opengauss表空间就是文件系统,按照文件系统扩容维护就行,lv之类的。
问题信息
请登录之后查看
邀请回答
暂无人订阅该标签,敬请期待~~