跳转到主内容

MGWD 会定期出现紧急情况并重新启动;集群节点可能会经常出现紧急情况

Views:
24
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
network
Last Updated:

状态信息

适用于

  • 9.3p13 之前的 ONTAP 版本
  • SNMPv3 监控
  • CHMODE ( CHMODE )

问题

MGWD 报告崩溃并在日志文件中重新启动。还会生成 MGWD 的核心文件。
 

Mon Jan 21 17:00:25 CST [node1: mgwd: kern.vm.mmap.return:notice]: mmap(2) by mgwd (pid 90982) for size 2097152 failed: VMEM limit exceeded, limit 4294967296, error 12.
Mon Jan 21 17:00:25 CST [node1: mgwd: ucore.panicString:error]: 'mgwd: Received SIGABRT (Signal 6) at RIP 0x81ab66bba (pid 90982, uid 0, timestamp 1548111625).'
Mon Jan 21 17:00:50 CST [node 1: spmd: spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 90982 exited as a result of signal signal 6. The subsystem will attempt to restart.

Mon Jan 21 17:01:19 CST [node 1: rastrace_dump: rastrace.dump.saved:debug]: A RAS trace dump for module EVMGR instance 0 was stored in /etc/log/rastrace/EVMGR_0_20190121_17:01:19:946051.dmp.

Mon Jan 21 17:01:50 CST [node 1: coredump_manager: ems.engine.suppressed:debug]: Event 'coredump.findcore.nocore' suppressed 1 times in last 146504 seconds.
Mon Jan 21 17:01:50 CST [node 1: coredump_manager: coredump.findcore.nocore:debug]: No unsaved cores could be found


节点也可能会出现紧急情况并生成核心转储。

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device