My Oracle Support Banner

OTD Failover Group Not Starting With VIP Configured For Listener (Doc ID 2182982.1)

Last updated on JULY 31, 2018

Applies to:

Oracle Traffic Director - Version and later
Information in this document applies to any platform.


On : version

Starting OTD failover group fails with following error using wlst.

wls:/offline> props = {'domain-home': '/apps/ignite/binaries/runtime/igtotd/domains/igtotd_domain', 'instance': '', 'log-verbose': 'true'}
wls:/offline> otd_startFailover(props)
Traceback (innermost last):
  File "", line 1, in ?
  File "/apps/ignite/binaries/igtotd/fmw/otd/plugins/wlst/otd-wlst-dependencies.jar!/wlstScriptDir/", line 147, in otd_startFailover
  at oracle.otd.admin.jmx.handlers.LinuxFailoverGroupHandler.updateKADConfig(
  at oracle.otd.admin.jmx.handlers.LinuxFailoverGroupHandler.startFailover(
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(
  at java.lang.reflect.Method.invoke(

oracle.otd.admin.exceptions.AdminException: oracle.otd.admin.exceptions.AdminException: OTD-68181 Error initializing failover: OTD-68118 Atleast one http-listener should have ip as *..

The issue can be reproduced at will with the following steps:

1. Create failover group as per OTD documentation.
2. Configure OTD server Listerner with VIP in IP Address column
3. Starting failover group through WLST fails when Listener is configured with VIP.
4. When changed the IP Address of the listeners from VIP to "*", it starts fine



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.