Skip to main content
NetApp Knowledge Base

Callhome: MAXIMUM EXITS THRESHOLD OF A PROCESS (shibd) MANAGED BY SPM IS REACHED

Views:
88
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
8/1/2025, 5:51:39 PM

Applies to

  • ONTAP 9
  • SAML Authentication

Issue

  • The shibd service, responsible for SAML authentication, attempted to start but failed repeatedly.
  • The following AutoSupport message is generated:
[Node1: spmd: callhome.spm.process.maxexit:error]: Call home for MAXIMUM EXITS THRESHOLD OF A PROCESS MANAGED BY SPM IS REACHED
  • The spmd log shows:
Wed Jun 04 2025 16:35:34 +09:00 [kern_spmd:info:2607] 0x801209e00: 0: INFO: spmd::ProcessControlManager: dumpExitConditions:src/process_control_manager.cc:1052 process (shibd:73366) exited normally with status 254
Wed Jun 04 2025 16:35:34 +09:00 [kern_spmd:info:2607] 0x801209e00: 0: WARNING: spmd::ProcessControlManager: onProcessExit:src/process_control_manager.cc:1120 process 92cce3c4-09e2-41e3-831b-aa9328e80c3e is slow-restartable because restarting more than 10 in 3600 seconds.
  • The shibd service was tried to start but failed.
  • The EMS log shows:
Wed Jun 04 16:35:34 +0900 [Node1: spmd: callhome.spm.process.maxexit:error]: Call home for MAXIMUM EXITS THRESHOLD OF A PROCESS MANAGED BY SPM IS REACHED
  • The audit log shows:
Wed Jun 04 2025 16:35:31 +09:00 [kern_audit:info:3256] 8503e800000054b4 :: File:  http :: 192.168.1.1:58034 :: File:admin :: POST /api/security/authentication/cluster/saml-sp?verify_metadata_server=false&return_timeout=30 : ["X-Dot-Client-App: SMv4"] {"certificate":{"ca":"File","serial_number":"183AAAAAAAAAAAA"},"idp_uri":***,"host":"192.168.1.10"} :: Pending
Wed Jun 04 2025 16:35:32 +09:00 [kern_audit:info:3256] 8503e800000054b4 :: File:  http :: 192.168.1.1:58034 :: File:admin :: POST /api/security/authentication/cluster/saml-sp?verify_metadata_server=false&return_timeout=30 : ["X-Dot-Client-App: SMv4"] {"certificate":{"ca":"File","serial_number":"183AAAAAAAAAAAA"},"idp_uri":***,"host":"192.168.1.10"} :: Success:
  • The SAML configuration was not completed successfully:

Wed Jun 04 16:35:33 +0900 [Node1: mgwd: saml.cfg.setup.incomplete:notice]: SAML SP configuration creation was not completed successfully.
Wed Jun 04 16:35:34 +0900 [Node1: mgwd: mgmtgwd.jobmgr.jobcomplete.failure:info]: Job "SAML Master Job" [id 476] (SAML Master Job) completed unsuccessfully: SAML job failed, Reason: For a given user and application, if the "-second-authentication-method" parameter is specified, only one such login method is supported. (5636159).

Wed Jun 04 16:42:53 +0900 [Node1: mgwd: saml.cfg.setup.incomplete:notice]: SAML SP configuration creation was not completed successfully.
Wed Jun 04 16:42:53 +0900 [Node1: mgwd: mgmtgwd.jobmgr.jobcomplete.failure:info]: Job "SAML Master Job" [id 477] (SAML Master Job) completed unsuccessfully: SAML job failed, Reason: IdP metadata downloaded from the provided URL has malformed XML. (12320808).

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.