暂无图片
moddb启动报错
我来答
分享
昨夜流星划过
2024-07-23
moddb启动报错

gs_ctl started,datadir is /opt/mogdb/data
[2024-07-23 03:30:15.757][29527][][gs_ctl]: waiting for server to start...
.0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.

0 LOG: [Alarm Module]Host Name: smmforflow

0 LOG: [Alarm Module]Host IP: smmforflow. 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: mogdb1

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.
0 LOG: SSE4.2 is not supported, disable codegen.
2024-07-23 03:30:15.855 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: when starting as multi_standby mode, we couldn't support data replicaton.
2024-07-23 03:30:15.864 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.

2024-07-23 03:30:15.864 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host Name: smmforflow

2024-07-23 03:30:15.864 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host IP: smmforflow. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP>

2024-07-23 03:30:15.864 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Cluster Name: mogdb1

2024-07-23 03:30:15.885 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: loaded library "security_plugin"
2024-07-23 03:30:15.885 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: loaded library "tidrangescan"
2024-07-23 03:30:15.886 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
2024-07-23 03:30:15.886 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
2024-07-23 03:30:15.909 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0.
2024-07-23 03:30:15.910 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] WARNING: Failed to initialize the memory protect for g_instance.attr.attr_storage.cstore_buffers (16 Mbytes) or shared memory (3489 Mbytes) is larger.
2024-07-23 03:30:15.910 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: shared memory that key is 26000001 is owned by pid 29020
2024-07-23 03:30:16.121 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [CACHE] LOG: set data cache size(12582912)
2024-07-23 03:30:16.231 [unknown] [unknown] localhost 47088554085952 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: 49, BktBitMaxMapCnt: 512
2024-07-23 03:30:16.331 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: mogdb: fsync file "/opt/mogdb/data/gaussdb.state.temp" success
2024-07-23 03:30:16.331 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: create gaussdb state file success: db state(STARTING_STATE), server mode(Primary), connection index(1)
2024-07-23 03:30:16.543 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: max_safe_fds = 99976, usable_fds = 100000, already_open = 14
2024-07-23 03:30:16.548 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: the configure file /opt/mogdb/app/etc/gscgroup_omm.cfg doesn't exist or the size of configure file has changed. Please create it by root user!
2024-07-23 03:30:16.548 [unknown] [unknown] localhost 47088554085952 0[0:0#0] 0 [BACKEND] LOG: Failed to parse cgroup config file.
.[2024-07-23 03:30:17.762][29527][][gs_ctl]: waitpid 29530 failed, exitstatus is 256, ret is 2

[2024-07-23 03:30:17.762][29527][][gs_ctl]: stopped waiting
[2024-07-23 03:30:17.762][29527][][gs_ctl]: could not start server
Examine the log output.
INFO[2024-07-23T03:30:17.764] ========================================
Warning: New version '1.6.1' is available, you are using ptk version '1.4.5'.
You can upgrade ptk via command: 'ptk self upgrade'
You can also set environment by 'export PTK_NO_CHECK_VERSION=true' to disable this warning
gs_ctl: Process exited with status 1    moddb启动报错,是什么问题?

我来答
添加附件
收藏
分享
问题补充
1条回答
默认
最新
吾亦可往
  • WARNING: failed to open feature control file, please check whether it exists: FileName=gaussdb.version, Errno=2, Errmessage=No such file or directory.:表示未能打开特性控制文件,需要检查该文件是否存在。
  • WARNING: failed to parse feature control file: gaussdb.version.:解析特性控制文件失败。
  • WARNING: Failed to load the product control file, so gaussdb cannot distinguish product version.:加载产品控制文件失败,导致 gaussdb 无法区分产品版本。
  • WARNING: could not create any HA TCP/IP sockets:无法创建任何 HA TCP/IP 套接字。
  • WARNING: Failed to initialize the memory protect for g_instance.attr.attr_storage.cstore_buffers (16 Mbytes) or shared memory (3489 Mbytes) is larger.:初始化内存保护失败,共享内存较大。
  • the configure file /opt/mogdb/app/etc/gscgroup_omm.cfg doesn't exist or the size of configure file has changed. Please create it by root user!:配置文件 /opt/mogdb/app/etc/gscgroup_omm.cfg 不存在或其大小已更改,需要由 root 用户创建。
  • Failed to parse cgroup config file.:解析 cgroup 配置文件失败。


要解决这些问题,可以尝试以下步骤:


  1. 确认 gaussdb.version 文件是否存在于指定的路径,如果不存在,需要创建该文件。
  2. 检查共享内存的设置,确保其大小合适或调整相关参数。
  3. 由 root 用户创建 /opt/mogdb/app/etc/gscgroup_omm.cfg 文件。
  4. 检查 cgroup 配置文件,解决解析失败的问题。


如果问题仍然存在,建议进一步查看日志中的其他信息,或者参考 GaussDB 的相关文档、咨询技术支持人员以获取更准确的解决方案。


另外,启动超时也可能导致类似的报错。如果是超时导致启动失败,可以执行如下命令,设置启动超时时间(默认为 300 秒):gs_om -t start --time-out=300


还有一种可能是磁盘 I/O 繁忙,导致数据库 gaussmaster 进程进入正常监听的时间超出指定时间(默认为 60 秒)。如果是这种情况,可以检查是否有其他程序占用大量磁盘 I/O,退出不需要的程序以减少磁盘 I/O 阻塞。


同时,确保目录权限足够,例如对/tmp 目录、数据库数据目录有足够的权限;检查配置的端口是否被占用;确认系统防火墙是否开启导致数据库启动失败;检查组成数据库的各台机器之间的互信关系是否正常;若数据库控制文件损坏,可根据具体情况进行相应的恢复操作。


需注意,具体的解决方法可能因实际情况而异,以上步骤仅供参考

暂无图片 评论
暂无图片 有用 0
回答交流
提交
问题信息
请登录之后查看
邀请回答
暂无人订阅该标签,敬请期待~~
暂无图片墨值悬赏