After DNS Recovery Node Manager Marks Oracle HTTP Server Status as Failed With the Error "java.net.UnknownHostException"
(Doc ID 2651460.1)
Last updated on MARCH 31, 2021
Applies to:Oracle HTTP Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
After DNS failure and recovery, Node Manager marks OHS status as "FAILED" though OHS is up and running.
Due to this, OHS cannot be managed using Node Manager unless it is killed and restarted.
Node Manager console logs shows this:
Issue can be reproduced at will using the below steps:
1. Install and configure standalone/collocated OHS
2. Update etc/hosts file and added new host entry with the actual IP
<actual IP> <DUMMY HOSTNAME>
3. Update the below config files with the DUMMY HOSTNAME
- httpd.conf file
- admin.conf file
- nodemanager.properties filr
4. Start Node Manager and it uses host "DUMMY HOSTNAME"
5. Start OHS
6. Once OHS is up and running, comment out the new host entry from etc/hosts file
7. Now Node Manager console log shows above mentioned errors
8. ohs1.log file shows the above mentioned error
9. Now Node Manager marks OHS as "Failed" and even uncommenting the hosts file does not help. OHS needs to be killed and restarted to recover.
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