Skip to main content
NetApp Knowledge Base

Start operation for Active IQ Management Server service fails due to timeout even though it has actually started

Views:
97
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
OM
Last Updated:

Applies to

  • Active IQ Unified Manager (AIQUM)
  • Red Hat Enterprise Linux (RHEL) / CentOS

Issue

  • systemctl start ocie fails 1 hour later
  • systemctl status ocie indicates that the operation fails due to timeout

Starting Active IQ Management Server service . This may take couple of minutes
ocie.service: start operation timed out. Terminating.
ocie.service: Failed with result 'timeout'.
Failed to start LSB: Active IQ Management Server.

  • /var/log/ocie/access_log.log doesn't have log entries for GET /api/management-server/admin/environment when systemctl start ocie fails

[GET /api/management-server/admin/environment HTTP/1.1] [200] [-] [curl/7.61.1] [*/*] [application/vnd.netapp.v1.hal+json] [644] [15622]

  • AIQUM Web GUI (https://<IP_address>:443) can be accessed normally with a browser
  • Running manually is_ocie_ready.sh returns ocie is started

# /opt/netapp/ocum/scripts/is_ocie_ready.sh localhost
checking localhost:443
ocie is started

  • A log of the proxy server indicates that the access is trying to connect http://localhost.domainname:443/

 

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.