You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

CentOS 7下GridDB启动失败:gridstore.service控制进程退出码错误

GridDB在CentOS 7启动失败(exit status=5)排查方案

问题描述

在CentOS 7上完成GridDB安装后,执行systemctl start gridstore启动服务失败,报错:

Job for gridstore.service failed because the control process exited with error code. See "systemctl status gridstore.service" and "journalctl -xe" for details.

已执行的排查操作及输出

1. 查看服务状态systemctl status gridstore

gridstore.service - GridDB database server.
Loaded: loaded (/usr/lib/systemd/system/gridstore.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2023-07-29 20:44:57 PKT; 20min ago
Process: 9025 ExecStart=/usr/griddb/bin/gridstore start (code=exited, status=5)

Jul 29 20:44:57 griddb systemd[1]: Starting GridDB database server....
Jul 29 20:44:57 griddb systemd[1]: gridstore.service: control process exited, code=exited status=5
Jul 29 20:44:57 griddb systemd[1]: Failed to start GridDB database server..
Jul 29 20:44:57 griddb systemd[1]: Unit gridstore.service entered failed state.
Jul 29 20:44:57 griddb systemd[1]: gridstore.service failed.

2. 查看系统日志journalctl -xe

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit gridstore.service has begun starting up.
Jul 29 20:42:09 griddb gridstore[8944]: [ FAILED ]
Jul 29 20:42:09 griddb systemd[1]: gridstore.service: control process exited, code=exited status=5
Jul 29 20:42:09 griddb systemd[1]: Failed to start GridDB database server..
-- Subject: Unit gridstore.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit gridstore.service has failed.

-- The result is failed.
Jul 29 20:42:09 griddb systemd[1]: Unit gridstore.service entered failed state.
Jul 29 20:42:09 griddb systemd[1]: gridstore.service failed.
Jul 29 20:42:09 griddb polkitd[701]: Unregistered Authentication Agent for unix-process:8938:10927 (system bus name :1.58, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jul 29 20:43:02 griddb su[8987]: (to gsadm) root on pts/0
Jul 29 20:43:02 griddb su[8987]: pam_unix(su:session): session opened for user gsadm by root(uid=0)
Jul 29 20:44:54 griddb su[8987]: pam_unix(su:session): session closed for user gsadm
Jul 29 20:44:57 griddb polkitd[701]: Registered Authentication Agent for unix-process:9019:27726 (system bus name :1.60 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale e
Jul 29 20:44:57 griddb systemd[1]: Starting GridDB database server....
-- Subject: Unit gridstore.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel


-- Unit gridstore.service has begun starting up.
Jul 29 20:44:57 griddb gridstore[9025]: [ FAILED ]
Jul 29 20:44:57 griddb systemd[1]: gridstore.service: control process exited, code=exited status=5
Jul 29 20:44:57 griddb systemd[1]: Failed to start GridDB database server..
-- Subject: Unit gridstore.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel


-- Unit gridstore.service has failed.


-- The result is failed.
Jul 29 20:44:57 griddb systemd[1]: Unit gridstore.service entered failed state.
Jul 29 20:44:57 griddb systemd[1]: gridstore.service failed.
Jul 29 20:44:57 griddb polkitd[701]: Unregistered Authentication Agent for unix-process:9019:27726 (system bus name :1.60, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jul 29 20:50:01 griddb systemd[1]: Started Session 2 of user root.
-- Subject: Unit session-2.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel


-- Unit session-2.scope has finished starting up.


-- The start-up result is done.
Jul 29 20:50:01 griddb CROND[9101]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 29 20:55:47 griddb systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel


-- Unit systemd-tmpfiles-clean.service has begun starting up.
Jul 29 20:55:47 griddb systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel


-- Unit systemd-tmpfiles-clean.service has finished starting up.


-- The start-up result is done.

解决方案

1. 以gsadm用户手动启动获取详细错误

systemd日志未提供具体失败原因,切换到gsadm用户手动启动,可查看更精准的报错:

su - gsadm
/usr/griddb/bin/gridstore start

常见启动失败原因及处理:

  • 数据目录权限问题:检查/var/lib/gridstore/data目录所有者和权限
    ls -ld /var/lib/gridstore/data
    
    权限异常时修复:
    chown -R gsadm:gsadm /var/lib/gridstore/data
    chmod -R 750 /var/lib/gridstore/data
    
  • 端口被占用:检查GridDB默认端口(10001/10002/20001)是否被占用
    netstat -tulpn | grep -E '10001|10002|20001'
    

2. 查看GridDB专属日志

直接读取GridDB的启动日志或节点日志,获取核心失败原因:

cat /var/lib/gridstore/log/gs_startup.log
cat /var/lib/gridstore/log/gs_node.log

3. 验证配置文件正确性

检查集群配置文件/var/lib/gridstore/conf/gs_cluster.json和节点配置gs_node.json,确保参数(如集群名称、内存分配、节点地址)配置无误。

4. 重新初始化集群(全新安装无数据时操作)

如果是首次安装且未生成数据,可重新初始化后再启动:

su - gsadm
/usr/griddb/bin/gs_node_setup -u admin/admin
systemctl start gridstore

内容的提问来源于stack exchange,提问作者Syed Mudassir Ali

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.07.15 01:46:05