暂无图片
docker 启动 opengauss 2.0 报错
我来答
分享
D
Dataplus
2021-04-09
docker 启动 opengauss 2.0 报错

用云和恩墨的docker镜像启动 opengauss 2.0 报错:

[root@localhost opt]# docker container logs ef265242664a 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 "en_US.UTF-8". The default text search configuration will be set to "english". fixing permissions on existing directory /var/lib/opengauss/data ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 32MB creating configuration files ... ok The core dump path is an invalid directory 2021-04-09 08:06:08.980 [unknown] [unknown] localhost 140561108207360 0 [BACKEND] WARNING: macAddr is 578/2886926346, sysidentifier is 37923859/712305, randomNum is 1175051889 creating template1 database in /var/lib/opengauss/data/base/1 ... ok The core dump path is an invalid directory initializing pg_authid ... ok The core dump path is an invalid directory setting password ... ok The core dump path is an invalid directory initializing dependencies ... ok The core dump path is an invalid directory loading PL/pgSQL server-side language ... ok The core dump path is an invalid directory creating system views ... ok The core dump path is an invalid directory creating performance views ... ok The core dump path is an invalid directory loading system objects' descriptions ... ok The core dump path is an invalid directory creating collations ... ok The core dump path is an invalid directory creating conversions ... ok The core dump path is an invalid directory creating dictionaries ... ok The core dump path is an invalid directory setting privileges on built-in objects ... ok The core dump path is an invalid directory initialize global configure for bucketmap length ... ok The core dump path is an invalid directory The core dump path is an invalid directory creating information schema ... ok The core dump path is an invalid directory loading foreign-data wrapper for distfs access ... ok The core dump path is an invalid directory loading foreign-data wrapper for hdfs access ... ok The core dump path is an invalid directory loading foreign-data wrapper for log access ... ok The core dump path is an invalid directory loading hstore extension ... ok The core dump path is an invalid directory loading foreign-data wrapper for MOT access ... ok The core dump path is an invalid directory loading security plugin ... ok The core dump path is an invalid directory update system tables ... ok The core dump path is an invalid directory vacuuming database template1 ... ok The core dump path is an invalid directory copying template1 to template0 ... ok The core dump path is an invalid directory copying template1 to postgres ... ok The core dump path is an invalid directory freezing database template0 ... ok The core dump path is an invalid directory freezing database template1 ... ok The core dump path is an invalid directory 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 [2021-04-09 08:06:34.211][145][][gs_ctl]: gs_ctl started,datadir is /var/lib/opengauss/data [2021-04-09 08:06:34.387][145][][gs_ctl]: waiting for server to start... .0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 0 LOG: [Alarm Module]Host Name: host_opengauss_5432 0 LOG: [Alarm Module]Host IP: 172.19.0.10 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: 52 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: Failed to initialze environment for codegen. The core dump path is an invalid directory 2021-04-09 08:06:34.711 [unknown] [unknown] localhost 140326800242432 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.2021-04-09 08:06:34.711 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 2021-04-09 08:06:34.711 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: [Alarm Module]Host Name: host_opengauss_5432 2021-04-09 08:06:34.711 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: [Alarm Module]Host IP: 172.19.0.10 2021-04-09 08:06:34.711 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: [Alarm Module]Get ENV GS_CLUSTER_NAME failed! 2021-04-09 08:06:34.712 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 52 2021-04-09 08:06:34.712 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: Transparent encryption disabled. 2021-04-09 08:06:34.718 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: loaded library "security_plugin" 2021-04-09 08:06:34.718 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets 2021-04-09 08:06:34.725 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] WARNING: No explicit IP is configured for listen_addresses GUC. 2021-04-09 08:06:34.725 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0. 2021-04-09 08:06:34.725 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: reserved memory for backend threads is: 220 MB 2021-04-09 08:06:34.725 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: reserved memory for WAL buffers is: 128 MB 2021-04-09 08:06:34.725 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: Set max backend reserve memory is: 348 MB, max dynamic memory is: 11097 MB 2021-04-09 08:06:34.725 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: shared memory 330 Mbytes, memory context 11445 Mbytes, max process memory 12288 Mbytes 2021-04-09 08:06:34.768 [unknown] [unknown] localhost 140326800242432 0 0 [CACHE] LOG: set data cache size(402653184) 2021-04-09 08:06:34.791 [unknown] [unknown] localhost 140326800242432 0 0 [CACHE] LOG: set metadata cache size(134217728) 2021-04-09 08:06:34.876 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: gaussdb: fsync file "/var/lib/opengauss/data/gaussdb.state.temp" success 2021-04-09 08:06:34.876 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: create gaussdb state file success: db state(STARTING_STATE), server mode(Normal) 2021-04-09 08:06:34.906 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: max_safe_fds = 984, usable_fds = 1000, already_open = 6 The core dump path is an invalid directory 2021-04-09 08:06:34.913 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: user configure file is not found, it will be created. 2021-04-09 08:06:34.922 [unknown] [unknown] localhost 140326800242432 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! 2021-04-09 08:06:34.922 [unknown] [unknown] localhost 140326800242432 0 0 [BACKEND] LOG: Failed to parse cgroup config file. [2021-04-09 08:06:35.391][145][][gs_ctl]: gaussDB state is Coredump [2021-04-09 08:06:35.391][145][][gs_ctl]: stopped waiting [2021-04-09 08:06:35.391][145][][gs_ctl]: could not start server
复制
我来答
添加附件
收藏
分享
问题补充
1条回答
默认
最新
李宏达

用-v选项把数据目录做持久化,看一下pg_log/ 日志

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


请输入正文
提交
相关推荐
opengauss Datakit 5.0.0迁移
回答 1
暂无文字回复
openGauss数据类型?
回答 1
一、常用数据类型1、数值类型(1)整型类型 TINYINT   占用1字节   对应关键字为TINYINT、INT1 S
Ubuntu系统20.04可以安装opengauss吗?
回答 3
在执行 gsgucreload 命令时,OpenGauss报告它无法找到静态配置文件。这个错误信息提示:“realpath(/usr/local/opengauss/bin/clu
Mogdb/opengauss 分区表的一个分区 用什么方法能导出来
回答 6
学习
opengauss使用JDBC进行开发时无法进行密态连接
回答 5
你是不是驱动包不对?
opengauss在omm用户安装完最后一步启动失败,不知道是什么问题,听说是cpu直通问题
回答 5
如果是X86的CPU,执行一下lscpu命令,看看指令集列表里有没有rdtscp,如果没有,那么大概率是因为这是个虚拟机,而对应的虚拟机管理平台没有开通这个虚拟机的CPU直通。openGauss的MO
openGauss产品定位是什么?
回答 1
已采纳
产品定位openGauss是一款支持SQL2003标准语法,支持主备部署的高可用关系型数据库。多种存储模式支持复合业务场景,新引入提供原地更新存储引擎。NUMA化数据结构支持高性能。Paxos一致性日
opengauss 5.0.0 支持使用sqlalchemy连接吗?
回答 5
大佬sqlalchemy连接opengauss5.0可以指导一下方法
openGauss执行预安装操作时报错
回答 3
操作系统里装的python版本太高,目前只支持3.6/3.7/3.9的,而且还要下对应的数据库安装包。如果非得装3.11,需要按照官方文档手动安装相关python依赖库psutilnetifacesc
openGauss的备份恢复方案有哪几种?
回答 2
按备份与恢复类型可分为:逻辑备份与恢复、物理备份与恢复。逻辑备份与恢复适合于数据量小的场景。用于表备份恢复。备份工具:gsdump、gsdumpall恢复工具:gsrestore备份、恢复工具:gsb