OHS Error: Script Failed, exit Code 255 during adcfgclone appsTier on Run FS

[nauman]

Dear Erman,

I am in a process of cloning. Complete adcfgclone went well on Run FS, But it gave issue while configuring the OHS. Messages in Error Logs are appended below:-

ApplyLog
---------


Script Executed in 131379 milliseconds, returning status 255
Error: scripts failed, exit code 255

OHST2Apply Error Log
------------------------

Warning failed to start component EBS_WEB_xxx
oracle.as .config.provisionException: HTTP Status code=408:0 of 1 processess started
.
.
.
Severe Error Clone 20218 Cloning is not successful
Sever Cause CLONE 20218 An internal opertaion failed
Sever Action Provide the clone log and error file for inversigation
Oracle.as.t2p.exceptions.FMWT2PpasteconfigException: java,lang.exception: unable to start OHS Component
...
Caused by java.lang.exception: unable to start OHS component
at oracle.as.clone.ohs.imp.OHSComponentApplyClonerImpl.dopastepasteconfig(OHSComponentApplyClonerImpl.java:213)
Severe: java.lang.exception: unable to start OHS Component

OHST2Apply Log File
----------------------

INFO: unable to start OHS component. Root cause can be found from OHS logfile -----/--/--/console~OHS~1.log


console~OHS~1.log File LOgs
---------------------------------

Errors will be logged into ../../../../EBS_WEB_xxx.log
Audit init
Unable to resolve address for localhost:6700
ONS runtime exiting
httpd stopped


EBS_WEB_xxx.log
-------------------


OHS Notification: machine hostname: host address: pid: user: {virtual host:main} caught SIGTERM, shutting down


I have list down all the logfile in the chronological order for your better understanding.

Please suggest me the root cause of the issue

Thanks & regards

[ErmanArslansOracleBlog]

This seems related with -> Bug 19724121 - ERROR OCCUR ON ADOP PHASE=FS_CLONE

Probably, adcfgclone and adop's fs_clone does something in common.. It seems they do similar things for copying the filesystem.. So this bug looks related with the error you get.

The key is OHSComponentApplyClonerImpl.java , line 213.

Follow this note and consider if you can apply the workaround on your cloned instance or not ->
"PM.error Occurred On adop phase=fs_clone (Doc ID 1939065.1)"

This was my 1st suggestion.

The 2nd suggestion is the following;

-Fix all missing prerequisites as per Note 250262.1 RDA 4 - Health Check / Validation Engine Guide .
- Issue the command:  export CONFIG_JVM_ARGS="-Xms1024m -Xmx1024m"
- run adcfgclone again.

[nauman]

Thanks for the update.

I have searched for this error and found out that i need to check my hosts file.

Unable to resolve address for localhost:6700

I have observed that 127.0.0.1 local host entries are commented out. So I uncomment them and started the cloning process again.

If it doesnt went well then i will follow the workaround suggested by you.

Thanks & regrads

[nauman]

Dear Erman,

My issue has been resolved by setting the hosts file.

Thanks for your continued support.

Regards

[ErmanArslansOracleBlog]

Good :)

Interesting, actually I saw that localhost there, but did not give this possibility to that.. As I saw the exact same error stack (ending with OHSComponentApplyClonerImpl.java , line 213) documented in "PM.error Occurred On adop phase=fs_clone (Doc ID 1939065.1)".

Thanks for sharing the solution Nauman.