Skip to main content
NetApp Knowledge Base

Stopping Oncommandsvc on AIQUM Windows fails in a situation where cluster monitoring failed

  1. Last updated
  2. Save as PDF
Views:
41
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • Active IQ Unified Manager (AIQUM) 9.x
  • Windows platform

Issue

  • AIQUM cluster acquisition fails
  • CPU and memory usage are consistently high and intermittently GUI is not reachable
  • This can happen after upgrading to a newer version
  • Stopping Oncommandsvc on AIQUM Windows fails
  • Running sc query Oncommandsvc from the command prompt shows STOP_PENDING:

SERVICE_NAME: Oncommandsvc
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 3 STOP_PENDING
                                (NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x2
        WAIT_HINT          : 0xbb8

  • Even before attempting to stop the service, au.log repeatedly shows warnings:

WARN  [Timer-0] c.o.s.a.f.m.s.SchedulerTask (SchedulerTask.java:187) - Data source is already performing a poll of netappfoundation. Therefore this poll is skipped.

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.