- OM - mailweb.opengauss.org

2024-4-23 openGauss TC会议
by openGauss conference 18 Apr '24

18 Apr '24

您好！ TC 邀请您参加 2024-04-23 16:00 召开的zoom会议(自动录制) 会议主题：2024-4-23 openGauss TC会议会议内容：请大家积极申报议题。会议链接：https://us06web.zoom.us/j/89109464581?pwd=QwgbTFUaz3AIDbuEqSBUBduUaNx861.1 会议纪要：https://etherpad.opengauss.org/p/TC-meetings 更多资讯尽在：{portal_zh} Hello! TC invites you to attend the zoom conference(auto recording) will be held at 2024-04-23 16:00, The subject of the conference is 2024-4-23 openGauss TC会议, Summary: 请大家积极申报议题。 You can join the meeting at https://us06web.zoom.us/j/89109464581?pwd=QwgbTFUaz3AIDbuEqSBUBduUaNx861.1. Add topics at https://etherpad.opengauss.org/p/TC-meetings. More information: {portal_en}

1 0

[Community] [Community]社区撤销issue公示
by 薛蒙恩 12 Mar '24

12 Mar '24

以下issue联系不到提单人，现根据社区issue处理规范(https://gitee.com/opengauss/QA/blob/master/op… gs_om响应时间慢 https://e.gitee.com/opengaussorg/issues/table?issue=I8IRQR 该问题搭建与用户一样的环境多次验证无问题，与提单人联系确认为用户环境问题，提供了环境问题排查方法，后再联系提单人无回应。 _______________________________________________ Community mailing list -- community(a)opengauss.org To unsubscribe send an email to community-leave(a)opengauss.org

1 0

2024.3.13 TC会议
by openGauss conference 05 Mar '24

05 Mar '24

您好！ TC 邀请您参加 2024-03-13 10:00 召开的zoom会议(自动录制) 会议主题：2024.3.13 TC会议会议内容：欢迎大家参加openGauss TC会议，如有议题请发送至 tc(a)opengauss.org 会议链接：https://us06web.zoom.us/j/85155825564?pwd=coNbOPPlYSZDRRsqrtPWbrWGbY9z0b.1 会议纪要：https://etherpad.opengauss.org/p/TC-meetings 更多资讯尽在：{portal_zh} Hello! TC invites you to attend the zoom conference(auto recording) will be held at 2024-03-13 10:00, The subject of the conference is 2024.3.13 TC会议, Summary: 欢迎大家参加openGauss TC会议，如有议题请发送至 tc(a)opengauss.org You can join the meeting at https://us06web.zoom.us/j/85155825564?pwd=coNbOPPlYSZDRRsqrtPWbrWGbY9z0b.1. Add topics at https://etherpad.opengauss.org/p/TC-meetings. More information: {portal_en}

1 0

2024/2/1 openGauss TC会议
by openGauss conference 30 Jan '24

30 Jan '24

您好！ TC 邀请您参加 2024-02-01 16:00 召开的zoom会议(自动录制) 会议主题：2024/2/1 openGauss TC会议会议内容：欢迎大家参加本次TC会议，已收集到一下议题，如有新增议题，请发送至tc(a)opengauss.org 1. openGauss SIG组运作规则对齐，汇报人：梅相如 2. openGauss社区Q1交付需求分工，汇报人：冯伟/熊小军 3. openGauss 24年版本需求规划，汇报人：杨艳明会议链接：https://us06web.zoom.us/j/84990843720?pwd=axtOobEsmTCPIcfcVJbjwno9QYRznO.1 会议纪要：https://etherpad.opengauss.org/p/TC-meetings 更多资讯尽在：{portal_zh} Hello! TC invites you to attend the zoom conference(auto recording) will be held at 2024-02-01 16:00, The subject of the conference is 2024/2/1 openGauss TC会议, Summary: 欢迎大家参加本次TC会议，已收集到一下议题，如有新增议题，请发送至tc(a)opengauss.org 1. openGauss SIG组运作规则对齐，汇报人：梅相如 2. openGauss社区Q1交付需求分工，汇报人：冯伟/熊小军 3. openGauss 24年版本需求规划，汇报人：杨艳明 You can join the meeting at https://us06web.zoom.us/j/84990843720?pwd=axtOobEsmTCPIcfcVJbjwno9QYRznO.1. Add topics at https://etherpad.opengauss.org/p/TC-meetings. More information: {portal_en}

1 0

[Community] 问题单关闭公示
by 薛蒙恩 11 Sep '23

11 Sep '23

以下问题已分析为非问题或者信息缺失无法进一步分析，但提单人无回应，现根据社区issue处理规范进行公示，7天后无反馈将进行关闭处理： issue： https://e.gitee.com/opengaussorg/issues/table?issue=I7Y8CG 描述：安装集群，输入错误的密码后，Oops， unhandled type 3 ('unimplemented') 分析：多次尝试未复现，分析了代码，两个关键处的ssh链接均有释放，需要多提供些预安装的日志信息和报错堆栈，当前信息无法支撑进一步定位。已回复相关初步定位方案，但长时间未收到回复。公示关闭。

1 0

2023-9-11 TC会议
by openGauss conference 05 Sep '23

05 Sep '23

您好！ openGauss TC SIG 邀请您参加 2023-09-11 09:30 召开的zoom会议(自动录制) 会议主题：2023-9-11 TC会议会议内容：会议议题： 1. 新增技术委员会成员评审；（南大通用吴明远、中国联通柴鹏、华为王磊） 2. 金融行业SIG成立评审； - （兴业银行李斌、熊小军）如果有新增议题，请发邮件至tc(a)opengauss.org 会议链接：https://us06web.zoom.us/j/87529603646?pwd=SEprRjRiSExUd0IwRGZ3NlFoVjFsdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在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-09-11 09:30, The subject of the conference is 2023-9-11 TC会议, Summary: 会议议题： 1. 新增技术委员会成员评审；（南大通用吴明远、中国联通柴鹏、华为王磊） 2. 金融行业SIG成立评审； - （兴业银行李斌、熊小军）如果有新增议题，请发邮件至tc(a)opengauss.org You can join the meeting at https://us06web.zoom.us/j/87529603646?pwd=SEprRjRiSExUd0IwRGZ3NlFoVjFsdz09. 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

[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>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