Skip to main content
NetApp Knowledge Base

AIQUM server is not reachable intermittently and acquisition fails at times

Views:
341
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • Active IQ Unified Manager (AIQUM) 9.8+
  • All OS versions

Issue

  • AIQUM server is not reachable at times
  • Even if the GUI is accessible, acquisition of clusters fail intermittently
  • As a result, AIQUM displays old data  (for eg: disk space utilization) not matching with the current ONTAP figures
  • acq.log has several occcurence of "Data source is already performing a poll of netappstorageperformance. Therefore this poll is skipped." for different clusters
  • This can happen after an upgrade
  • After a reboot the issue is resolved for some time
  • You may see the below error

oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/ocie.service,task=java,pid=3879248,uid=997 out of memory: killed process 3879248 (java) total=vm:8816112kb, anon=rss:4154524kb, file-rss:0kb, shmem-rss:0kb, UID:997 pgtables:9072kb oom_score_adj:0 ocie.service: A process of this unit has been killed by the OOM killer. ocie.service: Main process exited, code=killed, status=9/KILL Stopping Active IQ Manamgent Server service ocie

 

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.