OPMN Fails to Start with the Error "Address family not supported by protocol" During Configuration of an FMW 11g Component
(Doc ID 2043406.1)
Last updated on MAY 26, 2020
Applies to:Oracle Fusion Middleware - Version 126.96.36.199.0 and later
Oracle Internet Directory - Version 188.8.131.52.0 to 184.108.40.206.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:
[date_time] [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
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