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 SEPTEMBER 06, 2017
Applies to:Oracle Secure Backup - Version 10.4.0.2 and later
Information in this document applies to any platform.
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 :
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:23:46 (qtp) host ??? (::ffff:XXX.YYY.ZZZ.CCC) identity as OSB host CLIENT is suspect
Customer uses IP MultiPathing software (IPMP on Solaris) and one of the IPMP interfaces failed over to another interface with another IP address.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document