跳转到主内容

Coming soon...New Support-Specific categorization of Knowledge Articles in the NetApp Knowledge Base site to improve navigation, searchability and your self-service journey.

更换后的控制器未完成交还、并持续出现崩溃并重新启动

Views:
5
Visibility:
Public
Votes:
0
Category:
aff-series<a>2009年343072</a>
Specialty:
hw
Last Updated:

适用场景

  • AFF-220
  • 控制器更换

问题描述

更换后启动新控制器时出现多个错误:
 
[node_name: grep: ucore.panicString:error]: 'grep: Received SIGSEGV (Signal 11) at RIP 0 accessing address 0 (pid 16312, uid 0, timestamp 1666706268)'
[node_name: spmd: spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 12575 exited as a result of signal signal 11. The subsystem will attempt to restart.
[node_name: mgwd: ucore.panicString:error]: 'mgwd: Received SIGSEGV (Signal 11) at RIP 0x800451da0 accessing address 0x103cb54de6 (pid 16357, uid 0, timestamp 1666706315)'
[node_name: ucoreman: ucore.panicString:error]: 'ucoreman: Received SIGSEGV (Signal 11) at RIP 0x80022b160 accessing address 0x80022b160 (pid 17920, uid 0, timestamp 1666706513)'
[node_name: spmd: spm.ucoreman.process.exit:notice]: Usercore Manager (ucoreman) with ID 17920 exited as a result of signal signal 11. The service will attempt to restart.
[node_name: corefs: ucore.panicString:error]: 'corefs: Received SIGSEGV (Signal 11) at RIP 0x80021d000 accessing address 0xffffffffffffff8b (pid 18017, uid 0, timestamp 1666706512)'
[node_name: vifmgr: ucore.panicString:error]: 'vifmgr: Received SIGSEGV (Signal 11) at RIP 0x800451e90 accessing address 0xffffffffffffff85 (pid 18387, uid 0, timestamp 1666706563)'
[node_name: spmd: spm.vifmgr.process.exit:EMERGENCY]: Logical Interface Manager(VifMgr) with ID 18387 aborted as a result of signal signal 11. The subsystem will attempt to restart.
[node_name: ucoreman: ucore.panicString:error]: 'ucoreman: Received SIGILL (Signal 4) at RIP 0x2097a2 (pid 18398, uid 0, timestamp 1666706562).'
[node_name: spmd: callhome.spm.process.maxexit:error]: Call home for MAXIMUM EXITS THRESHOLD OF A PROCESS MANAGED BY SPM IS REACHED

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