Re: OPR backend not starting (687 Views)
Reply
Frequent Advisor
cjefferson218
Posts: 73
Registered: ‎09-10-2010
Message 1 of 3 (702 Views)

OPR backend not starting

I am running BAC 8.16 and the opr-backend will not start. This started happening last Friday, there are no changes that I have done to cause it to not work. On a restart of BAC the opr-backend in the Nanny status starts fine, the opr-backend in the HAC status runs through a cycle, starting then stopped then back to starting again as it should but it never gets to running.

 

I hace looked in the logs and the only thing I really see is below:

2012-10-04 14:32:32,164 [HAC-LAUNCHER] (CheckTasksCommand.java:309) INFO  - In updateStatus for 'OPR for 1' will update since
DBState STARTING vs. STOPPED or dbRunID 249 vs. 249
2012-10-04 14:32:32,164 [HAC-LAUNCHER] (DBAdapter.java:533) INFO  - In updateAssignment: Executing prepared statement for OPR of 1
set state=STOPPED(1) stateDuration=0
2012-10-04 14:32:52,196 [HAC-LAUNCHER] (CheckTasksCommand.java:239) INFO  - Service OPR for 1 has no collisions.
2012-10-04 14:32:52,196 [HAC-LAUNCHER] (CheckTasksCommand.java:309) INFO  - In updateStatus for 'OPR for 1' will update since DBState
STOPPED vs. STARTING or dbRunID 249 vs. 249
2012-10-04 14:32:52,196 [HAC-LAUNCHER] (DBAdapter.java:533) INFO  - In updateAssignment: Executing prepared statement for OPR of 1
set state=STARTING(2) stateDuration=0
2012-10-04 14:33:56,402 [CTRL-SVCStarter] (ServiceHandlerImpl.java:150) WARN  - Failed to start service OPR for 1
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'exporter' defined in class path resource
[application-context.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'ciResolverCacheMBean' defined in class path resource [application-context.xml]: Cannot resolve reference to bean 'ciResolverCache' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ciResolverCache' defined in class path resource [application-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException
Caused by:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ciResolverCacheMBean' defined in class path resource
[application-context.xml]: Cannot resolve reference to bean 'ciResolverCache' while setting constructor argument; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ciResolverCache' defined in class path resource
[application-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException
Caused by:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ciResolverCache' defined in class path resource
[application-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException
Caused by:

Please use plain text.
Honored Contributor
parkar
Posts: 2,284
Registered: ‎01-23-2010
Message 2 of 3 (687 Views)

Re: OPR backend not starting

1.Increase opr-backend process memory.
2.When using the OMiAutoView: Use the ci resolver cache ignore list to prevent the resolver from caching superflous CIs.
3.Provide your own custom TQL that reduces the number of total CIs.
4.On large systems it might be neccessary to split a query into multiple queries, to reduce peak memory consumption during the queries.
5.If you still have too many Cis, you need to split your environment.
Increase memory
For a quick solution set content of the <HPBSM>\bin\opr-backend_vm_params.ini file to. Warning: this settings will be lost with next deployment.
-Xms256m -Xmx2000m -XX:NewSize=32m -XX:MaxNewSize=96m -XX:PermSize=64m -XX:MaxPermSize=96mFor more details see Performance and Sizing Guide chapter 4. section System and Software Configuration.
Ignore superflous CIs
Open CI resolver configuration Administration->Platform->Infrastructure Settings->Applications->Operations Management->CI Resolver Settings: Ignore CIs
Edit the XML document and add attributes and types to be ignored.
<Attribute>attributeToBeIgnored</Attribute><CiType>typeToBeIgnored></CiType>Custom TQL
Create a TQL and add all CIs that are under management. Make sure to follow these rules:
1.Every CI that is part of a host must have a containment relationship (container_f) to its host
2.Every host must either have
a.a host host_dnsattribute. Make sure that the attribute is enabled. To do so got the Ci Type manager and
b.One or more ip_address CIs that are related to the host by a contains relationship.
3.Every CI that is part of the TQL must have all attributes visible that is needed for CI Resolution (like labels ("C:", "Company Portal", etc))
4.Business Services usually are not hosted on a system. So there is no need for a containment relationship. Its enough to have them visible in the TQL.
Save this TQL and register it at:
Administration->Platform->Infrastructure Settings->Applications->Operations Management->CI Resolver Settings: CI Resolver TQL
Multiple TQLs
Just follow the step before. But split up your TQL in multiple TQLs where each contains a subset of all CIs. Use a constraint that selects just a part of them, like all hosts that are part of a subnet, or are related to an application group, etc...

Cheers!

Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......
Please use plain text.
Frequent Advisor
cjefferson218
Posts: 73
Registered: ‎09-10-2010
Message 3 of 3 (664 Views)

Re: OPR backend not starting

Thanks I am looking at this now. I already had those performance settings in the ini file.So I am looking at the other things. A new TQL could have caused a problem?

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation