OSB: Pinghost fails with "Error: can't connect to Oracle Secure Backup service daemon on CLIENT (address XXX.YYY.ZZZ.AAA) - observiced not running" (Doc ID 1631694.1)

Last updated on APRIL 16, 2017

Applies to:

Oracle Secure Backup - Version 10.4.0.2 and later
Information in this document applies to any platform.

Symptoms

An OSB client fails to backup or communicate with observiced. Running obtool on the client fails.
Running an ontool pinghost against the client fails with the error : 

  Error: can't connect to Oracle Secure Backup service daemon on CLIENT (address XXX.YYY.ZZZ.AAA) - observiced not running
  CLIENT (address XXX.YYY.ZZZ.AAA): no services are available
  Error: can't connect to Oracle Secure Backup service daemon on CLIENT (address XXX.YYY.ZZZ.BBB) - observiced not running
  CLIENT (address XXX.YYY.ZZZ.BBB): no services are available

In the observiced log on the admin server we see a massive number of following messages :  

2014/03/03.00:22:46 host CLIENT failed trust checks, component observiced on fd 8 - identity of host is suspect (OSB network security manager)
2014/03/03.00:23:46 (qtp) host ??? (::ffff:XXX.YYY.ZZZ.CCC) identity as OSB host CLIENT is suspect

Changes

Customer uses IP MultiPathing software (IPMP on Solaris) and one of the IPMP interfaces failed over to another interface with another IP address.

Note : this can be caused on other platforms - using other IP multipathing software - as well

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms