Highlighted
Trusted Contributor.
Trusted Contributor.
311 views

autorecovery component does not start

Hi everyone,

when I start the ucmdb server, one of its components, the "autorecovery" cannot start. I get the following errore at wrapper.log

INFO   | jvm 1    | 2018/01/11 13:59:29.589 | 2018-01-11 13:59:29,557  ERROR  [Starter for "autodiscovery" (during Writer server startup). (customer 1, id name: Default Client)] - Failed to start component [autodiscovery]
INFO   | jvm 1    | 2018/01/11 13:59:29.589 | java.lang.NullPointerException
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.hp.ucmdb.discovery.server.wizards.MngZonesRankingStateHolder.updateMngZoneWithProbes(MngZonesRankingStateHolder.java:123)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.hp.ucmdb.discovery.server.wizards.MngZonesRankingStateHolder.updateCache(MngZonesRankingStateHolder.java:91)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.hp.ucmdb.discovery.server.wizards.ZoneBasedDiscoveryManagerImpl.<init>(ZoneBasedDiscoveryManagerImpl.java:111)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.hp.ucmdb.discovery.server.wizards.ZoneBaseDiscoveryManagerFactory.getWizardManagerPerCustomer(ZoneBaseDiscoveryManagerFactory.java:38)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.hp.ucmdb.discovery.server.framework.discovery.manager.AutoDiscoveryUserManagerImpl.startUp(AutoDiscoveryUserManagerImpl.java:2784)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startup(ServiceComponentImpl.java:120)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startupSubsystemManagers(ServiceComponentImpl.java:110)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startUp(ServiceComponentImpl.java:72)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.instance.CustomerInstanceImpl.startComponentLocally(CustomerInstanceImpl.java:105)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.instance.CustomerInstanceImpl.startComponentLocally(CustomerInstanceImpl.java:95)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.instance.Controller$ComponentLifecycleImpl.startComponent(Controller.java:292)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.instance.CustomerController.startComponent(CustomerController.java:493)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.instance.CustomerController.access$200(CustomerController.java:30)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at com.mercury.topaz.cmdb.server.manage.instance.CustomerController$RunnerWrapper.run(CustomerController.java:455)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
INFO   | jvm 1    | 2018/01/11 13:59:29.589 |     at java.lang.Thread.run(Thread.java:745)

Has anyone encountered this error at ucmdb version 10.33?

Thank you,

Anna

0 Likes
1 Reply
Highlighted
Frequent Contributor.
Frequent Contributor.

Re: autorecovery component does not start

Hi Anna

 

Did you ever get to resolve this issue? We are facing the same situation

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.