OPMN Fails to Start with the Error "Address family not supported by protocol" During Configuration of an FMW 11g Component
Last updated on JULY 31, 2017
Applies to:Oracle Fusion Middleware - Version 184.108.40.206.0 and later
Oracle Internet Directory - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11g]
Information in this document applies to any platform.
When trying to configure a new OID instance by running the config.sh , it fails with a pop up saying that opmn can not be started.
In this case the issue was noticed when configuring a new OID instance. However this can happen when configuring any 11g FMW product which is managed by OPMN.
The install<timestamp>.log will have the error "An internal operation has failed: Error in starting opmn server. Operation aborted because of a system call failure or internal error "
The complete stack of the error is given below
The opmn.log file will have the following error logged during this time:
[2015-07-21T13:14:12+02:00] [opmn] [ERROR:1]  [ons-listener] ::1;6702: SOCKET (Address family not supported by protocol)
When the opmn.xml was checked for this instance, it was found that "notification-server interface" is set to "any".
If this is changed to ipv4 and then run the config.sh again , it will still fail but this time it will complain that the instance directory is not empty
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