-
【用户体验】网络好卡 预审不通过场景描述： 网络好卡 建议方案： 场景描述： 网络好卡 建议方案：
-
【功能建议】云服务器界面通知调整 未采纳场景描述：弹性云服务器界面有近期更新的提示，但提示对大部分用户无用 [图片] 建议方案：建议将近期的更新都收纳到右上角的“最新动态”中 场景描述：弹性云服务器界面有近期更新的提示，但提示对大部分用户无用 [图片] 建议方案：建议将近期的更新都收纳到右上角的“最新动态”中
-
【用户体验】不显示价格 已实现不显示价格[图片] 不显示价格[图片]
-
【产品缺陷】投诉华为云 已实现场景描述： 安装个系统，搞了2天没搞定，华为现在都养着一群什么人了 建议方案： 严重影响我业务，每年花那么多钱，还不如关闭华为云算了 场景描述： 安装个系统，搞了2天没搞定，华为现在都养着一群什么人了 建议方案： 严重影响我业务，每年花那么多钱，还不如关闭华为云算了
- 场景描述： ubuntu的版本号太旧， 很早之前就提出了, 具体单号见: 工单编号：TS202312263JAM6XDJ2IFQ 及你们提交的单号：IV202312260061 建议方案： 场景描述： ubuntu的版本号太旧， 很早之前就提出了, 具体单号见: 工单编号：TS202312263JAM6XDJ2IFQ 及你们提交的单号：IV202312260061 建议方案：
- 场景描述： 续费中的“统一到期日”功能，增加具体日期。 建议方案： 续费中的“统一到期日”功能，增加具体日期。针对部分资源续费日期即使都统一到1日，但是仍然相差几个月的情况，增加续费到某个具体日期，取所有资源的最大续费日期即可。方便用户一次续费解决多个资源续费周期问题。 场景描述： 续费中的“统一到期日”功能，增加具体日期。 建议方案： 续费中的“统一到期日”功能，增加具体日期。针对部分资源续费日期即使都统一到1日，但是仍然相差几个月的情况，增加续费到某个具体日期，取所有资源的最大续费日期即可。方便用户一次续费解决多个资源续费周期问题。
-
【功能建议】手机如何进服务器系统 已实现手机登录云服务器桌面 手机登录云服务器桌面
- 场景描述： 我之前买了2个云电脑，现在1个不用了，可以把钱退了吗，或者能不能挪到现在的云电脑上，期限变长。感谢 建议方案： 场景描述： 我之前买了2个云电脑，现在1个不用了，可以把钱退了吗，或者能不能挪到现在的云电脑上，期限变长。感谢 建议方案：
-
【产品缺陷】opengauss 预审不通过场景描述：关机久了第ecs [omm@ecs-e982 ~]$ gs_om -t startStarting cluster.==================================================================================[GAUSS-53600]: Can not start the database, the cmd is source /home/omm/.bashrc; python3 '/opt/huawei/wisequery/script/local/StartInstance.py' -U omm -R /opt/gaussdb/app -t 300 --security-mode=off, Error:[FAILURE] ecs-e982:[GAUSS-51607] : Failed to start instance. Error: Please check the gs_ctl log for failure details.[2024-06-07 14:33:54.615][8584][][gs_ctl]: gs_ctl started,datadir is /gaussdb/data/db1 [2024-06-07 14:33:54.641][8584][][gs_ctl]: waiting for server to start....0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 0 LOG: [Alarm Module]Host Name: ecs-e982 0 LOG: [Alarm Module]Host IP: 127.0.0.1 0 LOG: [Alarm Module]Cluster Name: dbCluster 0 LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 55 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.The core dump path is an invalid directory2024-06-07 14:33:54.697 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 DB010 0 [REDO] LOG: Recovery parallelism, cpu count = 2, max = 4, actual = 22024-06-07 14:33:54.697 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 DB010 0 [REDO] LOG: ConfigRecoveryParallelism, true_max_recovery_parallelism:4, max_recovery_parallelism:42024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Host Name: ecs-e982 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Host IP: 127.0.0.1 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Cluster Name: dbCluster 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 55 2024-06-07 14:33:54.701 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: loaded library "security_plugin"2024-06-07 14:33:54.702 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 01000 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 01000 0 [BACKEND] WARNING: No explicit IP is configured for listen_addresses GUC.2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0.2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 01000 0 [BACKEND] WARNING: Failed to initialize the memory protect for g_instance.attr.attr_storage.cstore_buffers (16 Mbytes) or shared memory (2089 Mbytes) is larger.2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 42809 0 [BACKEND] FATAL: could not create shared memory segment: Cannot allocate memory2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 42809 0 [BACKEND] DETAIL: Failed system call was shmget(key=26000001, size=2191319040, 03600).2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 42809 0 [BACKEND] HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space, or exceeded your kernel's SHMALL parameter. You can either reduce the request size or reconfigure the kernel with larger SHMALL. To reduce the request size (currently 2191319040 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers. The PostgreSQL documentation contains more information about shared memory configuration.2024-06-07 14:33:54.710 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: FiniNuma allocIndex: 0.[2024-06-07 14:33:55.642][8584][][gs_ctl]: waitpid 8587 failed, exitstatus is 256, ret is 2 [2024-06-07 14:33:55.642][8584][][gs_ctl]: stopped waiting[2024-06-07 14:33:55.642][8584][][gs_ctl]: could not start serverExamine the log output..[omm@ecs-e982 ~]$ 建议方案： 场景描述：关机久了第ecs [omm@ecs-e982 ~]$ gs_om -t startStarting cluster.==================================================================================[GAUSS-53600]: Can not start the database, the cmd is source /home/omm/.bashrc; python3 '/opt/huawei/wisequery/script/local/StartInstance.py' -U omm -R /opt/gaussdb/app -t 300 --security-mode=off, Error:[FAILURE] ecs-e982:[GAUSS-51607] : Failed to start instance. Error: Please check the gs_ctl log for failure details.[2024-06-07 14:33:54.615][8584][][gs_ctl]: gs_ctl started,datadir is /gaussdb/data/db1 [2024-06-07 14:33:54.641][8584][][gs_ctl]: waiting for server to start....0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 0 LOG: [Alarm Module]Host Name: ecs-e982 0 LOG: [Alarm Module]Host IP: 127.0.0.1 0 LOG: [Alarm Module]Cluster Name: dbCluster 0 LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 55 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.The core dump path is an invalid directory2024-06-07 14:33:54.697 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 DB010 0 [REDO] LOG: Recovery parallelism, cpu count = 2, max = 4, actual = 22024-06-07 14:33:54.697 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 DB010 0 [REDO] LOG: ConfigRecoveryParallelism, true_max_recovery_parallelism:4, max_recovery_parallelism:42024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env. 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Host Name: ecs-e982 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Host IP: 127.0.0.1 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Cluster Name: dbCluster 2024-06-07 14:33:54.698 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 55 2024-06-07 14:33:54.701 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: loaded library "security_plugin"2024-06-07 14:33:54.702 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 01000 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 01000 0 [BACKEND] WARNING: No explicit IP is configured for listen_addresses GUC.2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: InitNuma numaNodeNum: 1 numa_distribute_mode: none inheritThreadPool: 0.2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 01000 0 [BACKEND] WARNING: Failed to initialize the memory protect for g_instance.attr.attr_storage.cstore_buffers (16 Mbytes) or shared memory (2089 Mbytes) is larger.2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 42809 0 [BACKEND] FATAL: could not create shared memory segment: Cannot allocate memory2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 42809 0 [BACKEND] DETAIL: Failed system call was shmget(key=26000001, size=2191319040, 03600).2024-06-07 14:33:54.707 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 42809 0 [BACKEND] HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space, or exceeded your kernel's SHMALL parameter. You can either reduce the request size or reconfigure the kernel with larger SHMALL. To reduce the request size (currently 2191319040 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers. The PostgreSQL documentation contains more information about shared memory configuration.2024-06-07 14:33:54.710 6662a9d2.1 [unknown] 281462765977616 [unknown] 0 dn_6001 00000 0 [BACKEND] LOG: FiniNuma allocIndex: 0.[2024-06-07 14:33:55.642][8584][][gs_ctl]: waitpid 8587 failed, exitstatus is 256, ret is 2 [2024-06-07 14:33:55.642][8584][][gs_ctl]: stopped waiting[2024-06-07 14:33:55.642][8584][][gs_ctl]: could not start serverExamine the log output..[omm@ecs-e982 ~]$ 建议方案：
-
【功能建议】好难用啊 连不上服务器 预审不通过场景描述： 香港服务器 连不上，你们网站的能连上 难用的要死 卡卡卡 建议方案： 场景描述： 香港服务器 连不上，你们网站的能连上 难用的要死 卡卡卡 建议方案：
-
【功能建议】阿里云备案域名，无法华为云使用，超时 预审不通过场景描述：看图，测试2天的结果，应该是这个原因 [图片] 建议方案： 场景描述：看图，测试2天的结果，应该是这个原因 [图片] 建议方案：
-
【用户体验】开机失败 预审不通过急用开机失败 急用开机失败
- 场景描述： SSL证书服务器设置后，所有解析指向的域名https访问都默认访问到设置的SSL网站了 [图片] [图片] [图片] 建议方案： 解析指向服务器的域名，没有绑定SSL的，HTTPS访问时隔离，没有设置就不要访问 场景描述： SSL证书服务器设置后，所有解析指向的域名https访问都默认访问到设置的SSL网站了 [图片] [图片] [图片] 建议方案： 解析指向服务器的域名，没有绑定SSL的，HTTPS访问时隔离，没有设置就不要访问
-
【功能建议】操作不友好 预审不通过使用界面应该可以切换，傻瓜模式与专业模式，我想用个服务器找了半天，使用界面藏得太深 使用界面应该可以切换，傻瓜模式与专业模式，我想用个服务器找了半天，使用界面藏得太深
- 请求参数: sell_mode; API: ListFlavorSellPolicies; 产品: ECS; 问题类别: 参数说明不详细 问题描述: 与帮助文档不一致 请求参数: sell_mode; API: ListFlavorSellPolicies; 产品: ECS; 问题类别: 参数说明不详细 问题描述: 与帮助文档不一致
上滑加载中
推荐直播
-
HDC深度解读系列 - Serverless与MCP融合创新，构建AI应用全新智能中枢2025/08/20 周三 16:30-18:00
张昆鹏 HCDG北京核心组代表
HDC2025期间，华为云展示了Serverless与MCP融合创新的解决方案，本期访谈直播，由华为云开发者专家(HCDE)兼华为云开发者社区组织HCDG北京核心组代表张鹏先生主持，华为云PaaS服务产品部 Serverless总监Ewen为大家深度解读华为云Serverless与MCP如何融合构建AI应用全新智能中枢
回顾中 -
关于RISC-V生态发展的思考2025/09/02 周二 17:00-18:00
中国科学院计算技术研究所副所长包云岗教授
中科院包云岗老师将在本次直播中，探讨处理器生态的关键要素及其联系，分享过去几年推动RISC-V生态建设实践过程中的经验与教训。
回顾中 -
一键搞定华为云万级资源，3步轻松管理企业成本2025/09/09 周二 15:00-16:00
阿言 华为云交易产品经理
本直播重点介绍如何一键续费万级资源，3步轻松管理成本，帮助提升日常管理效率！
回顾中
热门标签