Search Engine: Elastic

Article ID: 132108, created on Jan 23, 2018, last review on Jan 23, 2018

  • Applies to:
  • Operations Automation 7.1

Symptoms

Customer wanted to decommission old legacy Linux Shared Hosting node where Apache (service, v.3.6) and WebFileManager (service, v.7.1.583) packages are installed. Cleanup tasks were generated, but task "Cleanup packages on host" has failed with an output:

Failed to process DII, input xml:
...
</DII>, exception message: CORBA operation removeIncludeDirective call failed:  input xml: <DII> 

In core.log the cause of failure could be determined more precisely:

[ Service_impl::getService] {module_id="ServiceManagement"; code="10"} Service #38 does not exist.

Service #38 is an Apache service which is configured in WebFileManager properties as apache.service_id. This property is inherited from Apache, but since WebFileManager does not have dependency on Apache, during cleanup Apache package is removed first:

DBG [task:16041021:18712 Thread-33-(ActiveMQ-client-global-threads-434969809):1258 pau]: c.p.p.s.y.e.HostRemovalProcessorBean Processing uninstall for component: 367
...
DBG [task:16041021:18712 Thread-33-(ActiveMQ-client-global-threads-434969809):1258 pau]: c.p.p.s.y.e.OperationProcessorBean prepare deinstall for component 367 (Apache-service)

And only then WebFileManager turn comes:

DBG [task:16041021:18712 Thread-33-(ActiveMQ-client-global-threads-434969809):1258 pau]: c.p.p.s.y.e.HostRemovalProcessorBean Processing uninstall for component: 368

Cause

Operation fails because an entry about dependent service has been already removed with Apache service package. This behavior has been reported as POA-114318: "Node with LSH and WebFileManager can't be removed because wrong cleanup packages order".

Resolution

Manually remove WebFilemanager service before removing the host.

Your Technical Account Manager or PTA team representative may provide more details regarding the status of POA-114318.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF