暂无图片
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


请输入正文
提交
相关推荐
大佬们,有懂OpenGauss分布式数据库的吗,CN节点状态为down,是怎么回事呢,重启集群还是同样的状态,看日志看不到有用信息?
回答 1
先确定你的安装介质是哪个?是GaussDBforopenGauss?开源的openGauss没有分布式版本。商业版本有。
在UOS上安装失败? CPU:kirin990
回答 4
建议安装openEular20.03版本,和openGauss5.0.1的兼容性是最好的。
DCF是不是分布式库?开源的openGauss没有这个特性吧?
回答 1
开源社区2.1版本已经支持是针对单分片来说的,不同的备节点分配不同的职责,实现故障下的自主选主。
openGauss 5.0安装过程中输入的密码是omm的密码吗?
回答 1
是的
openGauss对软硬件的要求是什么?
回答 2
软件配置要求软件类型配置描述操作系统ARM:openEuler20.3LTS(推荐采用此操作系统)麒麟V10x86:openEuler20.3LTSCentOS7.6文件系统在EulerOS操作系统下
jdbc5 dbeaver
回答 1
好棒
openguass数据库,创建表的时候表字段为大写,为什么之后就成小写了。
回答 2
如果明确需要大写,请使用双引号。
opengauss支持单机多实例吗?
回答 6
已采纳
标准常规部署是不支持单机多实例的;但如果真想在单机上部署多个实例,则需要修改很多配置,比如进程信息、端口信息这些;再有,就是在linux上使用docker的形式,启动多个docker的方式来实现多实例
OpenGaussdb 数据库连接时碰到了schema的问题
回答 3
谢谢大佬彭冲,加上currentSchema已经好了,多谢章宇文,你说的还没试
opengauss_2.0.1_企业版_主备_安装报错
回答 1
内存给8G,一主一备,玩玩看吧。
问题信息
请登录之后查看
邀请回答
暂无人订阅该标签,敬请期待~~