- OM - mailweb.opengauss.org

[Community] 社区非问题issue公示
by 薛蒙恩 01 Sep '23

01 Sep '23

以下issue为非问题，由于在issue下评论后一直无人回复，现根据社区issue处理规范（https://gitee.com/opengauss/QA/blob/master/openGauss%E7%BC%BA%E9%99%B7issue%E5%A4%84%E7%90%86%E6%B5%81%E7%A8%8B.md#5%E7%BC%BA%E9%99%B7issue%E6%92%A4%E9%94%80%E5%8E%9F%E5%88%99 ）对issue问题进行公示，7天后如仍无反馈，将按照处理规范对issue进行关闭。 issue：https://e.gitee.com/opengaussorg/issues/table?issue=I7PW8G 原因：非问题，这个场景比较特殊，扩容操作是只会扩新节点，对于集群的已有节点只会配置些参数啥的，这个场景里相当于需要给当前节点安装cm了，这种是不支持的。提供一种可操作的方法，可以分两步操作： 1先把这两个节点扩成1主1备不带cm的集群 2使用cm_install单独安装cm

1 0

社区问题单申请关闭
by zhangao (S) 31 Aug '23

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>; 发送时间: 2023年8月7日(星期一) 下午4:20 收件人: "随心所欲"<348647284(a)qq.com>; 主题: 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

tc
by openGauss conference 25 May '23

25 May '23

您好！ openGauss TC SIG 邀请您参加 2023-05-25 14:00 召开的zoom会议(自动录制) 会议主题：tc 会议内容：欢迎大家参加5.25下午14:00 ~ 15:30号在openGauss开发者大会线下TC例会，收到海量晓涛总提交议题如下： 1、CM容器化部署问题：https://gitee.com/opengauss/openGauss-OM/issues/I65RJI#note_150… 2、支持固定Error Code的需求：https://gitee.com/opengauss/openGauss-server/issues/I717J5?from=pro… 3、社区文档缺失问题讨论如果有其他想讨论事项，欢迎继续申报会议链接：https://us06web.zoom.us/j/86786465809?pwd=SFpvY1RSR3d1Y0lUQ1l0Q1JvWmlKQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 提前申报议题请编辑：https://etherpad.opengauss.org/p/TC-meetings 更多资讯尽在：https://opengauss.org/zh/ Hello! openGauss TC SIG invites you to attend the zoom conference(auto recording) will be held at 2023-05-25 14:00, The subject of the conference is tc, Summary: 欢迎大家参加5.25下午14:00 ~ 15:30号在openGauss开发者大会线下TC例会，收到海量晓涛总提交议题如下： 1、CM容器化部署问题：https://gitee.com/opengauss/openGauss-OM/issues/I65RJI#note_150… 2、支持固定Error Code的需求：https://gitee.com/opengauss/openGauss-server/issues/I717J5?from=pro… 3、社区文档缺失问题讨论如果有其他想讨论事项，欢迎继续申报 You can join the meeting at https://us06web.zoom.us/j/86786465809?pwd=SFpvY1RSR3d1Y0lUQ1l0Q1JvWmlKQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. Add topics: https://etherpad.opengauss.org/p/TC-meetings More information: https://opengauss.org/en/

1 0

转发: 答复: 安装并启动 openGauss 报错
by yu8home＠163.com 16 May '23

16 May '23

yu8home(a)163.com 发件人： xuxiaoqin (A) 发送时间： 2023-05-16 15:52 收件人： yu8home(a)163.com 主题：答复: 安装并启动 openGauss 报错您好，于会彬 Certification sig组主要受理社区认证相关的主题，你遇到的问题可以咨询下OM sig组。谢谢发件人: yu8home(a)163.com <yu8home(a)163.com> 发送时间: 2023年5月16日 15:33 收件人: blockchain <blockchain(a)opengauss.org>; certification <certification(a)opengauss.org>; cloudnative <cloudnative(a)opengauss.org> 主题: 安装并启动 openGauss 报错 openGauss社区人员，你们好：我叫于会彬，根据公司的要求，想要使用 openGauss 数据库，我是初次使用 openGauss 的小白，在银河麒麟 linux 系统上，安装并启动 openGauss 时报错，详细的报错信息如下，麻烦帮忙看看，麻烦你们了！ junli@junli-kaitianm740z:/data/openGauss/simpleInstall$ ./install.sh -w "J12345678@" -p 8848 && source ~/.bashrc [step 1]: check parameter [step 2]: check install env and os setting [step 3]: change_gausshome_owner [step 4]: set environment variables [step 6]: init datanode ./install.sh:行223: gs_initdb：未找到命令 sed：无法读取 /data/openGauss/data/single_node/postgresql.conf：没有那个文件或目录 [step 7]: start datanode ./install.sh:行229: gs_ctl：未找到命令 import sql file Would you like to create a demo database (yes/no)? no Input no, operation skip. junli@junli-kaitianm740z:/data/openGauss/simpleInstall$ ./install.sh -w "J12345678@" -p 8848 && source ~/.bashrc [step 1]: check parameter [step 2]: check install env and os setting ERROR: the directory /data/openGauss/data/single_node must be dir and empty junli@junli-kaitianm740z:/data/openGauss/simpleInstall$ ./install.sh -w "J12345678@" -p 8848 && source ~/.bashrc [step 1]: check parameter [step 2]: check install env and os setting [step 3]: change_gausshome_owner [step 4]: set environment variables [step 6]: init datanode ./install.sh:行223: gs_initdb：未找到命令 sed：无法读取 /data/openGauss/data/single_node/postgresql.conf：没有那个文件或目录 [step 7]: start datanode ./install.sh:行229: gs_ctl：未找到命令 import sql file Would you like to create a demo database (yes/no)? yes Load demoDB [school,finance] success. [complete successfully]: You can start or stop the database server using: gs_ctl start|stop|restart -D $GAUSSHOME/data/single_node -Z single_node junli@junli-kaitianm740z:/data/openGauss/simpleInstall$ gs_ctl start-D /data/openGauss/data/single_node -Z single_node gs_ctl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by gs_ctl) gs_ctl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by gs_ctl) gs_ctl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /data/openGauss/lib/libpq.so.5) gs_ctl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /data/openGauss/lib/libpq.so.5) gs_ctl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /data/openGauss/lib/libpq.so.5) junli@junli-kaitianm740z:/data/openGauss/simpleInstall$ yu8home(a)163.com

1 0

2023.3.14 TC会议
by openGauss conference 08 Mar '23

08 Mar '23

您好！ openGauss TC SIG 邀请您参加 2023-03-14 09:30 召开的Zoom会议(自动录制) 会议主题：2023.3.14 TC会议会议内容：请大家积极申报议题，谢谢会议链接：https://us06web.zoom.us/j/84749039722?pwd=aFhIbWt5M2M0WDkwblkzL0srQ1N1UT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 提前申报议题请编辑：https://etherpad.opengauss.org/p/TC-meetings 更多资讯尽在：https://opengauss.org/zh/ Hello! openGauss TC SIG invites you to attend the Zoom conference(auto recording) will be held at 2023-03-14 09:30, The subject of the conference is 2023.3.14 TC会议, Summary: 请大家积极申报议题，谢谢 You can join the meeting at https://us06web.zoom.us/j/84749039722?pwd=aFhIbWt5M2M0WDkwblkzL0srQ1N1UT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. Add topics: https://etherpad.opengauss.org/p/TC-meetings More information: https://opengauss.org/en/

1 0

gs_checkos A6检查项无法消除warning
by 刘恒 16 Jan '23

16 Jan '23

issue:https://gitee.com/opengauss/openGauss-OM/issues/I63ACP 该问题不是问题，我自己已经在本地已经通过好几次测试，由于联系不到提单人，特向社区公示7天

1 0

12.15 TC例会
by openGauss conference 12 Dec '22

12 Dec '22

您好！ openGauss TC SIG 邀请您参加 2022-12-15 10:00 召开的Zoom会议(自动录制) 会议主题：12.15 TC例会会议内容：议题1：ogtop工具介绍及发布形态 - 民生银行朱彬会议链接：https://us06web.zoom.us/j/88685745284?pwd=dkRnREpQVlFYcXozZzJBVks3ejg5dz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 提前申报议题请编辑：https://etherpad.opengauss.org/p/TC-meetings 更多资讯尽在：https://opengauss.org/zh/ Hello! openGauss TC SIG invites you to attend the Zoom conference(auto recording) will be held at 2022-12-15 10:00, The subject of the conference is 12.15 TC例会, Summary: 议题1：ogtop工具介绍及发布形态 - 民生银行朱彬 You can join the meeting at https://us06web.zoom.us/j/88685745284?pwd=dkRnREpQVlFYcXozZzJBVks3ejg5dz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. Add topics: https://etherpad.opengauss.org/p/TC-meetings More information: https://opengauss.org/en/

1 0

2022.9.14 openGauss TC例会
by openGauss conference 14 Sep '22

14 Sep '22

您好！ openGauss TC SIG 邀请您参加 2022-09-14 10:50 召开的Zoom会议(自动录制) 会议主题：2022.9.14 openGauss TC例会会议链接：https://us06web.zoom.us/j/83392226982?pwd=NXdPbVhlbGtWcFFsMUVBTWY2UmRIZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 提前申报议题请编辑：https://etherpad.opengauss.org/p/TC-meetings 更多资讯尽在：https://opengauss.org/zh/ Hello! openGauss TC SIG invites you to attend the Zoom conference(auto recording) will be held at 2022-09-14 10:50, The subject of the conference is 2022.9.14 openGauss TC例会, You can join the meeting at https://us06web.zoom.us/j/83392226982?pwd=NXdPbVhlbGtWcFFsMUVBTWY2UmRIZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. Add topics: https://etherpad.opengauss.org/p/TC-meetings More information: https://opengauss.org/en/

1 0