Skip to main content
NetApp Knowledge Base

Acquisition server does not stay started on Oncommand Unified Manager 9.5 on RHEL 7.x or OVA

Last Updated:

Applies to

  • OnCommand Unified Manager 9.5 
  • RHEL 7.x
  • Virtual Appliance


After an upgrade from Unified Manager 9.4 to 9.5 the "ocieau" service does not stay online.

OCUM / Oncommand Unified Manager 9.x is not able to monitor all the clusters, due to the acquisition services being down.
OCIEAU services does not stay online on RHEL 7.x
Acquisition stops after upgrade of Oncommand Unified Manager.

Check for the status of the ocieau services :

 systemctl status ocieau.service
* ocieau.service - LSB: OnCommand Insight Essentials AU
 Loaded: loaded (/opt/netapp/systemd/system/ocieau; enabled; vendor preset: disabled)
 Active: inactive (dead) since Mon 2019-01-21 10:39:20 CET; 23min ago
 Process: 16276 ExecStop=/opt/netapp/systemd/system/ocieau stop (code=exited, status=0/SUCCESS)
 Process: 15656 ExecStart=/opt/netapp/systemd/system/ocieau start (code=exited, status=0/SUCCESS)
 Main PID: 15656 (code=exited, status=0/SUCCESS)

Jan 21 10:37:53 %SystemName% systemd[1]: Starting LSB: OnCommand Insight Essentials AU...
Jan 21 10:37:53 %SystemName% ocieau[15656]: Starting NetApp OnCommand Insight Essentials Acqisition service ocieau
Jan 21 10:37:53 %SystemName% ocieau[15656]: NetApp OnCommand Insight Essentials Acquisition service started successfully
Jan 21 10:37:53 %SystemName% systemd[1]: Started LSB: OnCommand Insight Essentials AU.
Jan 21 10:39:20 %SystemName% systemd[1]: Stopping LSB: OnCommand Insight Essentials AU...
Jan 21 10:39:20 %SystemName% ocieau[16276]: NetApp OnCommand Insight Essentials Acquisition service already stopped
Jan 21 10:39:20 %SystemName% systemd[1]: Stopped LSB: OnCommand Insight Essentials AU.

In the OCUMserver.log there is a listing of 

 Waiting for next changelog update.

%datestamp% ERROR [oncommand] [pool-21-thread-3] [c.n.i.c.u.AcquisitionUnitStatusUtil] Unable to invoke AU EJB Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: Connection refused (Connection refused)]
        at com.netapp.ipc.common.util.AcquisitionUnitStatusUtil.getAcquisitionUnitStartTime(
        at com.netapp.ipc.common.util.AcquisitionUnitStatusUtil.isAcquisitionUnitRunning(
        at com.netapp.scalemonitor.service.DiskMonitorService.monitor(
        at com.netapp.scalemonitor.ScaleMonitor.monitorDiskSpace(
        at com.netapp.scalemonitor.ScaleMonitorConfiguration$
        at java.util.concurrent.Executors$
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
        at java.util.concurrent.ScheduledThreadPoolExecutor$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: javax.naming.ServiceUnavailableException: null
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(
        at com.sun.jndi.toolkit.url.GenericURLContext.lookup(
        at javax.naming.InitialContext.lookup(
        at javax.naming.InitialContext.lookup(
        ... 15 common frames omitted
Caused by: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: Connection refused (Connection refused)
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(
        at sun.rmi.transport.tcp.TCPChannel.createConnection(
        at sun.rmi.transport.tcp.TCPChannel.newConnection(
        at sun.rmi.server.UnicastRef.newCall(
        at sun.rmi.registry.RegistryImpl_Stub.lookup(
        at com.sun.jndi.rmi.registry.RegistryContext.lookup(
        ... 21 common frames omitted
Caused by: Connection refused (Connection refused)
        at Method)

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.