原作者:邓秋爽
- 适用范围
- 问题概述
- 问题原因
- 详细详解方案
- 1、Mogdb启动失败,出现无法读取gaussdb.state错误
- 2、Mogdb并无相关日志记录
- 3、查看Mogdb data_directory目录下的gaussdb.state为空
- 4、重新移除gaussdb.state文件,再次启动Mogdb正常
适用范围
openGauss、MogDB 3.0.3
问题概述
Mogdb gaussdb.state文件异常导致Failed to read gaussdb.state: 2Failed to set gaussdb.state with UNKNOWN_STATE。
问题原因
MogDB gaussdb.state文件异常,可能跟强制关闭Mogdb数据库等有关系。
详细详解方案
关于gaussdb.state文件的描述资料很少,该文件是openGauss、MogDB数据库的数据文件,数据文件出现异常会导致数据库无法启动,可以通过rm该文件,重启MogDB、openGauss数据库会重新生成该文件;至于该文件为什么异常猜测更大可能跟强制断电、异常关闭数据库有关。
1、Mogdb启动失败,出现无法读取gaussdb.state错误
[omm@ora121c-node01 data]$ gs_ctl start
[2023-03-12 16:46:34.304][6561][][gs_ctl]: gs_ctl started,datadir is /data/mogdb/data
[2023-03-12 16:46:34.370][6561][][gs_ctl]: waiting for server to start...
.0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.
0 LOG: [Alarm Module]Host Name: ora121c-node01
0 LOG: [Alarm Module]Host IP: 192.168.56.60
0 LOG: [Alarm Module]Cluster Name: mogdb_cluster1
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-03-12 16:46:34.501 [unknown] [unknown] localhost 47030036713152 0[0:0#0] 0 [BACKEND] LOG: when starting as multi_standby mode, we couldn't support data replicaton.
Failed to read gaussdb.state: 2Failed to set gaussdb.state with UNKNOWN_STATE[2023-03-12 16:46:35.371][6561][][gs_ctl]: waitpid 6564 failed, exitstatus is 256, ret is 2
[2023-03-12 16:46:35.371][6561][][gs_ctl]: stopped waiting
[2023-03-12 16:46:35.371][6561][][gs_ctl]: could not start server
Examine the log output.
2、Mogdb并无相关日志记录
[omm@ora121c-node01 data]$ ls -lt /data/mogdb/log/pg_log/dn_6001|more
total 14124
-rw------- 1 omm omm 15975 Mar 8 00:51 postgresql-2023-03-08_005114.log
-rw------- 1 omm omm 15855 Mar 8 00:51 postgresql-2023-03-08_005112.log
-rw------- 1 omm omm 15623 Mar 8 00:51 postgresql-2023-03-08_005110.log
-rw------- 1 omm omm 15907 Mar 8 00:51 postgresql-2023-03-08_005108.log
-rw------- 1 omm omm 86016 Mar 8 00:50 postgresql-2023-03-08_000000.log
-rw------- 1 omm omm 446699 Mar 7 23:59 postgresql-2023-03-07_194519.log
-rw------- 1 omm omm 44364 Mar 7 19:45 postgresql-2023-03-07_193431.log
-rw------- 1 omm omm 203172 Mar 6 16:39 postgresql-2023-03-06_144859.log
-rw------- 1 omm omm 296852 Mar 1 12:00 postgresql-2023-03-01_091343.log
-rw------- 1 omm omm 952335 Mar 1 09:13 postgresql-2023-03-01_000000.log
-rw------- 1 omm omm 167463 Feb 28 23:59 postgresql-2023-02-28_222939.log
-rw------- 1 omm omm 1447046 Feb 11 14:15 postgresql-2023-02-11_000000.log
-rw------- 1 omm omm 2235281 Feb 10 23:59 postgresql-2023-02-10_020157.log
-rw------- 1 omm omm 768 Feb 10 02:00 postgresql-2023-02-10_020017.log
-rw------- 1 omm omm 768 Feb 10 01:59 postgresql-2023-02-10_015943.log
-rw------- 1 omm omm 350240 Feb 8 23:59 postgresql-2023-02-08_201819.log
-rw------- 1 omm omm 202768 Feb 8 20:18 postgresql-2023-02-08_201810.log
-rw------- 1 omm omm 59635 Feb 8 20:18 postgresql-2023-02-08_200333.log
-rw------- 1 omm omm 567526 Jan 21 05:47 postgresql-2023-01-21_000000.log
-rw------- 1 omm omm 1796597 Jan 20 23:59 postgresql-2023-01-20_054108.log
-rw------- 1 omm omm 704695 Jan 14 19:06 postgresql-2023-01-14_114339.log
-rw------- 1 omm omm 26849 Jan 14 11:43 postgresql-2023-01-14_114234.log
-rw------- 1 omm omm 31662 Jan 14 11:42 postgresql-2023-01-14_114039.log
-rw------- 1 omm omm 31788 Jan 14 11:40 postgresql-2023-01-14_113014.log
-rw------- 1 omm omm 103319 Jan 14 11:30 postgresql-2023-01-14_103947.log
-rw------- 1 omm omm 344064 Jan 1 12:07 postgresql-2023-01-01_084455.log
-rw------- 1 omm omm 871107 Dec 31 15:36 postgresql-2022-12-31_044454.log
-rw------- 1 omm omm 26991 Dec 31 04:44 postgresql-2022-12-31_044441.log
-rw------- 1 omm omm 422186 Dec 31 04:44 postgresql-2022-12-31_000000.log
-rw------- 1 omm omm 944172 Dec 30 23:59 postgresql-2022-12-30_132642.log
-rw------- 1 omm omm 212936 Dec 29 02:27 postgresql-2022-12-29_000000.log
-rw------- 1 omm omm 1008929 Dec 28 23:59 postgresql-2022-12-28_123902.log
-rw------- 1 omm omm 419516 Dec 27 14:39 postgresql-2022-12-27_101041.log
-rw-------. 1 omm omm 45040 Dec 26 21:47 postgresql-2022-12-26_212959.log
3、查看Mogdb data_directory目录下的gaussdb.state为空
[omm@ora121c-node01 data]$ ls -l
total 4984
drwx------ 3 omm omm 20 Jan 14 11:40 asp_data
drwx------. 12 omm omm 4096 Feb 10 14:21 base
-rw-------. 1 omm omm 4407 Dec 26 21:29 cacert.pem
-rw------- 1 omm omm 0 Mar 8 00:50 core-mogdb-11882-2023_03_08_00_50_40-bbox.lz4
-rw------- 1 omm omm 1238 Mar 8 00:51 core-mogdb-30756-2023_03_08_00_51_08-bbox.lz4
-rw------- 1 omm omm 1238 Mar 8 00:51 core-mogdb-30934-2023_03_08_00_51_12-bbox.lz4
-rw------- 1 omm omm 1238 Mar 8 00:51 core-mogdb-31054-2023_03_08_00_51_14-bbox.lz4
drwx------ 2 omm omm 129 Mar 8 00:51 ffic_log
-rw------- 1 omm omm 0 Mar 8 00:51 gaussdb.state
drwx------. 2 omm omm 4096 Mar 8 00:51 global
-rw-------. 1 omm omm 354 Dec 26 21:29 gs_gazelle.conf
drwx------ 3 omm omm 20 Jan 14 11:40 gs_profile
-rw-------. 1 omm omm 4915200 Dec 26 21:29 gswlm_userinfo.cfg
-rw-------. 1 omm omm 20218 Dec 26 21:29 mot.conf
drwx------. 2 omm omm 25 Dec 26 21:29 pg_clog
drwx------. 2 omm omm 25 Dec 26 21:29 pg_csnlog
-rw-------. 1 omm omm 0 Mar 12 16:46 pg_ctl.lock
drwx------. 2 omm omm 6 Dec 26 21:29 pg_errorinfo
-rw------- 1 omm omm 4750 Dec 31 04:43 pg_hba.conf
-rw-------. 1 omm omm 4682 Dec 31 02:41 pg_hba.conf.bak
-rw-------. 1 omm omm 1024 Dec 26 21:29 pg_hba.conf.lock
-rw-------. 1 omm omm 1636 Dec 26 21:29 pg_ident.conf
drwx------. 4 omm omm 37 Dec 26 21:29 pg_llog
drwx------. 2 omm omm 6 Dec 26 21:29 pg_location
drwx------. 2 omm omm 66 Mar 8 00:50 pg_logical
drwx------. 4 omm omm 34 Dec 26 21:29 pg_multixact
drwx------. 2 omm omm 25 Mar 8 00:51 pg_notify
drwx------ 3 omm omm 20 Jan 14 11:40 pg_perf
drwx------. 3 omm omm 20 Dec 31 02:42 pg_replslot
drwx------. 2 omm omm 6 Dec 26 21:29 pg_serial
drwx------. 2 omm omm 6 Dec 26 21:29 pg_snapshots
drwx------. 2 omm omm 6 Mar 8 00:51 pg_stat_tmp
drwx------. 2 omm omm 18 Dec 27 10:14 pg_tblspc
drwx------. 2 omm omm 6 Dec 26 21:29 pg_twophase
-rw-------. 1 omm omm 4 Dec 26 21:29 PG_VERSION
drwx------. 3 omm omm 4096 Feb 11 11:25 pg_xlog
-rw------- 1 omm omm 34486 Feb 10 14:28 postgresql.conf
-rw-------. 1 omm omm 34486 Feb 10 14:28 postgresql.conf.bak
-rw-------. 1 omm omm 1024 Dec 26 21:29 postgresql.conf.lock
-rw-------. 1 omm omm 65 Mar 8 00:51 postmaster.opts
-rw-------. 1 omm omm 0 Dec 26 21:29 postmaster.pid.lock
-rw-------. 1 omm omm 4410 Dec 26 21:29 server.crt
-rw-------. 1 omm omm 1766 Dec 26 21:29 server.key
-rw-------. 1 omm omm 56 Dec 26 21:29 server.key.cipher
-rw-------. 1 omm omm 24 Dec 26 21:29 server.key.rand
drwx------ 3 omm omm 20 Jan 14 11:40 sql_monitor
drwx------. 5 omm omm 63 Mar 8 00:51 undo
4、重新移除gaussdb.state文件,再次启动Mogdb正常
[omm@ora121c-node01 data]$ file /data/mogdb/data/gaussdb.state
/data/mogdb/data/gaussdb.state: data
[omm@ora121c-node01 data]$ mv gaussdb.state /tmp
[omm@ora121c-node01 data]$ gs_ctl start
[2023-03-12 16:47:47.695][6822][][gs_ctl]: gs_ctl started,datadir is /data/mogdb/data
[2023-03-12 16:47:47.758][6822][][gs_ctl]: waiting for server to start...
.0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.
0 LOG: [Alarm Module]Host Name: ora121c-node01
0 LOG: [Alarm Module]Host IP: 192.168.56.60
0 LOG: [Alarm Module]Cluster Name: mogdb_cluster1
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-03-12 16:47:47.898 [unknown] [unknown] localhost 47471135817408 0[0:0#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.2023-03-12 16:47:47.902 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.
2023-03-12 16:47:47.902 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host Name: ora121c-node01
2023-03-12 16:47:47.902 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host IP: 192.168.56.60
2023-03-12 16:47:47.902 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Cluster Name: mogdb_cluster1
2023-03-12 16:47:47.908 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: loaded library "security_plugin"
2023-03-12 16:47:47.909 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
2023-03-12 16:47:47.912 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0.
2023-03-12 16:47:47.912 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: reserved memory for backend threads is: 220 MB
2023-03-12 16:47:47.912 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: reserved memory for WAL buffers is: 128 MB
2023-03-12 16:47:47.912 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: Set max backend reserve memory is: 348 MB, max dynamic memory is: 11064 MB
2023-03-12 16:47:47.912 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: shared memory 363 Mbytes, memory context 11412 Mbytes, max process memory 12288 Mbytes
2023-03-12 16:47:47.952 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [CACHE] LOG: set data cache size(402653184)
2023-03-12 16:47:47.983 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [CACHE] LOG: set metadata cache size(134217728)
2023-03-12 16:47:48.055 [unknown] [unknown] localhost 47471135817408 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: 25, BktBitMaxMapCnt: 512
2023-03-12 16:47:48.118 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: mogdb: fsync file "/data/mogdb/data/gaussdb.state.temp" success
2023-03-12 16:47:48.118 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: create gaussdb state file success: db state(STARTING_STATE), server mode(Normal), connection index(1)
2023-03-12 16:47:48.119 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: max_safe_fds = 976, usable_fds = 1000, already_open = 14
2023-03-12 16:47:48.127 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: the configure file /data/mogdb/app/etc/gscgroup_omm.cfg doesn't exist or the size of configure file has changed. Please create it by root user!
2023-03-12 16:47:48.127 [unknown] [unknown] localhost 47471135817408 0[0:0#0] 0 [BACKEND] LOG: Failed to parse cgroup config file.
[2023-03-12 16:47:48.767][6822][][gs_ctl]: done
[2023-03-12 16:47:48.767][6822][][gs_ctl]: server started (/data/mogdb/data)
正常启动之后gaussdb.state文件不为空
[omm@ora121c-node01 data]$ ll
total 4988
drwx------ 3 omm omm 20 Jan 14 11:40 asp_data
drwx------. 12 omm omm 4096 Feb 10 14:21 base
-rw-------. 1 omm omm 4407 Dec 26 21:29 cacert.pem
-rw------- 1 omm omm 0 Mar 8 00:50 core-mogdb-11882-2023_03_08_00_50_40-bbox.lz4
-rw------- 1 omm omm 1238 Mar 8 00:51 core-mogdb-30756-2023_03_08_00_51_08-bbox.lz4
-rw------- 1 omm omm 1238 Mar 8 00:51 core-mogdb-30934-2023_03_08_00_51_12-bbox.lz4
-rw------- 1 omm omm 1238 Mar 8 00:51 core-mogdb-31054-2023_03_08_00_51_14-bbox.lz4
drwx------ 2 omm omm 129 Mar 8 00:51 ffic_log
-rw------- 1 omm omm 72 Mar 12 17:48 gaussdb.state
drwx------. 2 omm omm 4096 Mar 12 17:48 global
-rw-------. 1 omm omm 354 Dec 26 21:29 gs_gazelle.conf
drwx------ 3 omm omm 20 Jan 14 11:40 gs_profile
-rw-------. 1 omm omm 4915200 Dec 26 21:29 gswlm_userinfo.cfg
-rw-------. 1 omm omm 20218 Dec 26 21:29 mot.conf
drwx------. 2 omm omm 25 Dec 26 21:29 pg_clog
drwx------. 2 omm omm 25 Dec 26 21:29 pg_csnlog
-rw-------. 1 omm omm 0 Mar 12 17:48 pg_ctl.lock
drwx------. 2 omm omm 6 Dec 26 21:29 pg_errorinfo
-rw------- 1 omm omm 4750 Dec 31 04:43 pg_hba.conf
-rw-------. 1 omm omm 4682 Dec 31 02:41 pg_hba.conf.bak
-rw-------. 1 omm omm 1024 Dec 26 21:29 pg_hba.conf.lock
-rw-------. 1 omm omm 1636 Dec 26 21:29 pg_ident.conf
drwx------. 4 omm omm 37 Dec 26 21:29 pg_llog
drwx------. 2 omm omm 6 Dec 26 21:29 pg_location
drwx------. 2 omm omm 34 Mar 12 17:48 pg_logical
drwx------. 4 omm omm 34 Dec 26 21:29 pg_multixact
drwx------. 2 omm omm 25 Mar 12 17:48 pg_notify
drwx------ 3 omm omm 20 Jan 14 11:40 pg_perf
drwx------. 3 omm omm 20 Dec 31 02:42 pg_replslot
drwx------. 2 omm omm 6 Dec 26 21:29 pg_serial
drwx------. 2 omm omm 6 Dec 26 21:29 pg_snapshots
drwx------. 2 omm omm 6 Mar 12 17:48 pg_stat_tmp
drwx------. 2 omm omm 18 Dec 27 10:14 pg_tblspc
drwx------. 2 omm omm 6 Dec 26 21:29 pg_twophase
-rw-------. 1 omm omm 4 Dec 26 21:29 PG_VERSION
drwx------. 3 omm omm 4096 Feb 11 11:25 pg_xlog
-rw------- 1 omm omm 34486 Feb 10 14:28 postgresql.conf
-rw-------. 1 omm omm 34486 Feb 10 14:28 postgresql.conf.bak
-rw-------. 1 omm omm 1024 Dec 26 21:29 postgresql.conf.lock
-rw-------. 1 omm omm 65 Mar 12 17:48 postmaster.opts
-rw-------. 1 omm omm 0 Dec 26 21:29 postmaster.pid.lock
-rw-------. 1 omm omm 4410 Dec 26 21:29 server.crt
-rw-------. 1 omm omm 1766 Dec 26 21:29 server.key
-rw-------. 1 omm omm 56 Dec 26 21:29 server.key.cipher
-rw-------. 1 omm omm 24 Dec 26 21:29 server.key.rand
drwx------ 3 omm omm 20 Jan 14 11:40 sql_monitor
drwx------. 5 omm omm 63 Mar 12 17:48 undo
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。




