跳转到主内容

检测到 spm.xxx.process.exit" 警报

Views:
18
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
core<a>2008732097</a>
Last Updated:

适用场景

ONTAP 9

问题描述

  • EMS日志中显示的消息:

Apr 14 21:39:08 UTC [node_name: spmd: spm.servprocd.process.exit:alert]: Service processor daemon (servprocd) with ID 4532 exited as a result of normal exit (1). This server will attempt to restart.
Apr 14 21:39:10 UTC [node_name: servprocd: mdb.recovery.successful:debug]: params: {'name': 'servprocd'}
Apr 14 21:48:07 UTC [node_name: nphmd: hm.alert.cleared:info]: params: {'alert_id': 'SPLinkDownAlert', 'alerting_resource': 'SP Config', 'detailed_info': 'Alert Id = SPLinkDownAlert , Alerting Resource = SP Config', 'monitor': 'controller'}

May 16 00:28:05 JST [node_name: nphmd: ucore.panicString:error]: 'nphmd: Received SIGSEGV (Signal 11) at RIP 0x800c88974 accessing address 0xffffffffffffffe8 (pid 5987, uid 0, timestamp 1621092485)'
May 16 00:28:09 JST [node_name: spmd: spm.nphmd.process.exit:alert]: Controller Health Monitor process (nphmd) with ID 5987 exited as a result of signal 11. This server will attempt to restart.

 

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

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.