Skip to main content
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video.
NetApp Knowledge Base

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

Views:
14
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NFS
  • CIFS

Issue

  • 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 = 1.1.1.1 **[ 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)
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

  • Was this article helpful?