OM August 2023

om@opengauss.org

3 participants
3 discussions

31 Aug '23

1、 https://e.gitee.com/opengaussorg/issues/table?issue=I7N2VP 本issue提出的主备之间超过6s判定时间是不同步的，没有理论依据，在issue下方已进行相关答复，故申请关闭 2、 https://e.gitee.com/opengaussorg/issues/table?issue=I7RNQ1 本issue，提醒用户使用gs_om -t view就可以获取azPrioritty的信息，在issue下已经回复，可以关闭 3、 https://e.gitee.com/opengaussorg/issues/table?issue=I5AUGH 咨询issue，在issue下方已经答复，申请关闭 4、 https://e.gitee.com/opengaussorg/issues/table?issue=I7L8SL 问题长时间复现不了，申请关闭 5、 https://e.gitee.com/opengaussorg/issues/table?issue=I7I66R openssl报错问题，非OM问题，在问题单下方已经给予回复，申请关闭

1 0

gs_om -t start 启动报错，请问是什么原因呢
by 随心所欲 07 Aug '23

07 Aug '23

[omm@node111 ~]$ gs_om -t start Starting cluster. ========================================= ========================================= [GAUSS-53600]: Can not start the database, the cmd is source /home/omm/.bashrc; python3 '/opt/openGauss/om/script/local/StartInstance.py' -U omm -R /opt/openGauss/app -t 300 --security-mode=off,  Error: [FAILURE] node111: [GAUSS-51607] : Failed to start instance. Error: Please check the gs_ctl log for failure details. [2023-08-07 16:21:49.732][24100][][gs_ctl]: gs_ctl started,datadir is /opt/openGauss/data/dn  [2023-08-07 16:21:49.775][24100][][gs_ctl]: waiting for server to start... .0 LOG:  [Alarm Module]can not read GAUSS_WARNING_TYPE env. 0 LOG:  [Alarm Module]Host Name: node111  0 LOG:  [Alarm Module]Host IP: node111. 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: opengauss  0 LOG:  [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 58 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. 0 LOG:  bbox_dump_path is set to /data/core/ 2023-08-07 16:21:49.857 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 DB010  0 [REDO] LOG:  Recovery parallelism, cpu count = 16, max = 4, actual = 4 2023-08-07 16:21:49.857 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 DB010  0 [REDO] LOG:  ConfigRecoveryParallelism, true_max_recovery_parallelism:4, max_recovery_parallelism:4 2023-08-07 16:21:49.863 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]can not read GAUSS_WARNING_TYPE env. 2023-08-07 16:21:49.863 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Host Name: node111  2023-08-07 16:21:49.863 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Host IP: node111. Copy hostname directly in case of taking 10s to use 'gethostbyname' when /etc/hosts does not contain <HOST IP> 2023-08-07 16:21:49.863 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Cluster Name: opengauss  2023-08-07 16:21:49.863 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 58 2023-08-07 16:21:49.866 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  loaded library "security_plugin" 2023-08-07 16:21:49.869 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  could not create any HA TCP/IP sockets 2023-08-07 16:21:49.869 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING:  could not create any HA TCP/IP sockets 2023-08-07 16:21:49.871 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0. 2023-08-07 16:21:49.871 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  reserved memory for backend threads is: 340 MB 2023-08-07 16:21:49.871 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  reserved memory for WAL buffers is: 320 MB 2023-08-07 16:21:49.871 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  Set max backend reserve memory is: 660 MB, max dynamic memory is: 17957 MB 2023-08-07 16:21:49.871 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  shared memory 1734 Mbytes, memory context 18617 Mbytes, max process memory 20480 Mbytes 2023-08-07 16:21:49.871 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  shared memory that key is 15400001 is owned by pid 10413 2023-08-07 16:21:50.032 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [CACHE] LOG:  set data cache  size(100663296) 2023-08-07 16:21:50.386 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  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-08-07 16:21:50.438 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  gaussdb: fsync file "/opt/openGauss/data/dn/gaussdb.state.temp" success 2023-08-07 16:21:50.438 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  create gaussdb state file success: db state(STARTING_STATE), server mode(Normal), connection index(1) 2023-08-07 16:21:50.438 64d0a99d.1 [unknown] 139904269717760 [unknown] 0 dn_6001 00000  0 [BACKEND] LOG:  max_safe_fds = 974, usable_fds = 1000, already_open = 16 bbox_dump_path is set to /data/core/ [2023-08-07 16:21:54.779][24100][][gs_ctl]: waitpid 24103 failed, exitstatus is 0, ret is 2 [2023-08-07 16:21:54.779][24100][][gs_ctl]: stopped waiting [2023-08-07 16:21:54.779][24100][][gs_ctl]: could not start server Examine the log output.. ------------------ 原始邮件 ------------------ 发件人: "om-request" <om-request(a)opengauss.org>gt;; 发送时间: 2023年8月7日(星期一) 下午4:20 收件人: "随心所欲"<348647284(a)qq.com>gt;; 主题: Welcome to the "OM" mailing list     欢迎使用“OM”邮件列表！     Welcome to the "OM" mailing list!     要通过此列表交流，请发送电子邮件至:     To post to this list, send your email to:         om(a)opengauss.org     要退订此列表，请访问：     To unsubscribe from this list, please visit:         https://mailweb.opengauss.org/postorius/lists/om.opengauss.org/

1 0

［om］om默认建库编码为ASCII可能导致错误，希望讨论相关解决方案
by 雷紫薇 04 Aug '23

04 Aug '23

非ASCII时，opengauss的工作流程如下：（1）客户端的gsql直接发送字符串给服务器（假如为gbk）（2）服务器端gaussdb接收后立即讲字符串从客户端编码（gbk）转为服务器端编码（假如为utf8）（3）后续全部按照服务器端编码（utf8）进行解析。但是编码为ASCII时是不会进行任何转换的，客户端发送什么就存储什么，这会引起问题。比如客户端为utf8，服务器为ASCII时， select to_number ('￥9987.65','9999.00'); 会得到错误结果9987.6。由于数据库中存储的结果可能是任何编码，在进行字符处理时，发生错误的概率几乎是一定的。另外，在gaussdb端来进行字符编码转换可能会造成服务器端压力过大，如果由gsql来进行转码动作应该更合适，希望就编码问题进行讨论。来自阿里邮箱Android客户端

1 0

2024

2023

2022

2021

OM August 2023