FS_CLONE failed at slave server

Now Again we are facing the FS_CLONE issue during the post up gradation steps below is the error
nter the APPS password: [UNEXPECTED]ADOP exited with interrupt.
[STATEMENT] Please run adopscanlog utility, using the command
"adopscanlog -latest=yes"
to get the list of the log files along with snippet of the error message corresponding to each log file.
adop exiting with status = 1 (Fail)
[appluat@apdbablog02 ~]$ adop phase=fs_clone force=yes
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Validating credentials...
Initializing...
Run Edition context : /u17/home/apdba/fs2/inst/apps/apdba_apdbablog02/appl/admin/apdba_apdbablog02.xml
Patch edition context: /u17/home/apdba/fs1/inst/apps/apdba_apdbablog02/appl/admin/apdba_apdbablog02.xml
Patch file system freespace: 72.15 GB
Validating system setup...
Node registry is valid.
Logfile location /u17/home/apdba/fs2/inst/apps/apdba_apdbablog02/logs/appl/rgf/TXK/verifyssh.log
xml output = /u17/home/apdba/fs2/inst/apps/apdba_apdbablog02/logs/appl/rgf/TXK/out.xml
Remote execution is operational.
Checking for pending adop sessions...
No pending session exists.
Staging new adop session...
===========================================================================
ADOP (C.Delta.6)
Session ID: 23
Node: apdbablog02
Phase: fs_clone
Log: /u17/home/apdba/fs_ne/EBSapps/log/adop/23/adop_20151104_001935.log
===========================================================================
Verifying the existence of context files in database...
Checking if adop can continue with available nodes in the configuration...
Log: /u17/home/apdba/fs_ne/EBSapps/log/adop/23/fs_clone_20151104_001935/apdba_apdbablog02
Returning SUCCESS
Validating configuration on admin node: [apdbablog02]...
xml output = /u17/home/apdba/fs_ne/EBSapps/log/adop/23/fs_clone_20151104_001935/apdba_apdbablog02/remote_execution_result_20151104_002014.xml
[ERROR] Remote execution failed on Node: "apdbablog02".
[ERROR] Tasks have failed or are incomplete in the admin node
[ERROR] Unable to continue with other available nodes:"apdbablog07,apdbablog08,apdbablog09,apdbablog14,apdbablog15".
[UNEXPECTED]Error: While executing "txkADOPValidation" on all other nodes.
[UNEXPECTED]Execution failed when performing remote action.
Summary report for current adop run -
Node apdbablog02:
- Fs_clone Status: NOT STARTED
Node apdbablog09:
- Fs_clone Status: NOT STARTED
Node apdbablog14:
- Fs_clone Status: NOT STARTED
Node apdbablog07:
- Fs_clone Status: NOT STARTED
Node apdbablog08:
- Fs_clone Status: NOT STARTED
Node apdbablog15:
- Fs_clone Status: NOT STARTED
HINT : For more details, please run adop -status -detail
[STATEMENT] Please run adopscanlog utility, using the command
"adopscanlog -latest=yes"
to get the list of the log files along with snippet of the error message corresponding to each log file.
adop exiting with status = 2 (Fail)
[appluat@apdbablog02 ~]$
Action Plan:
Issue: ERROR: Domain is in edit mode.
Please perform the following action plan:
1. Start the admin server on the run file system (if not started already).
2. Login in to WLS Admin Console (http(s)://hostname.domain:<adminport>/console)
3. Click on "Release Configuration" button at "Change Center" on the top left corner.
4. Logout of WLS console
5. Rerun the adop fs_clone
===============================
We are getting the below error in ADOPValidations_detailed.log
-----------------------------
ERROR: The following required ports are in use:
-----------------------------
6801 : WLS OAEA Application Port
Corrective Action: Free the listed ports and retry the adop operation.
Completed execution : ADOPValidations.java
When released the port and reran the fs_clone, still it is error out with above validation error.
Ports are established with connection after release the port.
[appluat@apdbablog02 apdba_apdbablog02]$ lsof -i tcp:6801
[appluat@apdbablog02 apdba_apdbablog02]$ netstat -na |grep 6801
[appluat@apdbablog02 apdba_apdbablog02]$
[appluat@apdbablog02 apdba_apdbablog02]$
[appluat@apdbablog02 apdba_apdbablog02]$
[appluat@apdbablog02 apdba_apdbablog02]$ lsof -i tcp:6801
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 18619 appluat 773u IPv6 195806295 0t0 TCP apdbablog02.apdba.com:40243->apdbablog02.apdba.com:acnet (ESTABLISHED)
java 19276 appluat 464u IPv6 195806296 0t0 TCP apdbablog02.apdba.com:acnet->apdbablog02.apdba.com:40243 (ESTABLISHED)
java 19276 appluat 483u IPv6 195802994 0t0 TCP apdbablog02.apdba.com:acnet (LISTEN)
[appluat@apdbablog02 apdba_apdbablog02]$ netstat -na |grep 6801
tcp 0 0 ::ffff:10.2.217.31:6801 :::* LISTEN
tcp 0 0 ::ffff:10.2.217.31:40243 ::ffff:10.2.217.31:6801 ESTABLISHED
tcp 0 0 ::ffff:10.2.217.31:6801 ::ffff:10.2.217.31:40243 ESTABLISHED
[appluat@apdbablog02 apdba_apdbablog02]$
Action Plan:
We did not have any issue after doing a complete bounce of services.
FS_CLONE completed successfully