Skip to main content
NetApp Knowledge Base

Repeated secd crashes after upgrading ONTAP 9, clients unable to connect

Last Updated:

Applies to

  • ONTAP 9
  • NFS
  • CIFS


  • Following an ONTAP upgrade, repeated secd panics are observed
  • The following EMS events may be reported:
    • [Node01: secd: ucore.panicString:error]: 'secd: Received SIGSEGV (Signal 11) at RIP 0x807bbae58 accessing address 0x8 (pid 12291, uid 0, timestamp 1633946180)'
    • [Node01: spmd: spm.secd.process.exit:EMERGENCY]: Security daemon with ID 12291 exited as a result of signal signal 11. The service will attempt to restart.
    • [Node01: secd: secd.cifsAuth.problem:error]: vserver () General CIFS authentication problem. Error: User authentication procedure failed CIFS SMB2 Share mapping - Client Ip = **[ 0] FAILURE: CIFS authentication failed [ 0] 'Vserver' configuration not available
  • The following is seen in secd:
  • [kern_secd:info:99840] [SECD SERVER THREAD] SECD: Configuration not available. Sending systemerr to RPC with proc ID 151 and request ID 0
  • Clients are unable to connect via NFS or CIFS (this may be either intermittent or persistent)

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.