ODA_BASE on Node0 Hangs after short time and needs force reset

[eslamkamelmorsi]

Dear Erman,

We have ODA X5-2 it was taking too long to shutdown ODA_BASE on Node 0 and now it hangs after starting for one or two hours, needing force reset to node 0

our environment:
Virtual Deployment
Stand alone (no cluster)
Node 0 has two VMs (Main ODA_BASE VM and Weblogic Server VM)
Node 1 has two other VMs with no problem

each time after starting I got this error
OAKERR:6000 Exception encountered in the module getMasterNode
OAKERR:6002 Master node was not found

I started the oakd manually

the system works fine for some time then hangs
after that
running any oakcli command gives the same error again
OAKERR:6000 Exception encountered in the module getMasterNode
OAKERR:6002 Master node was not found

Now I am not able to even PING on the ODA_BASE on node 0
I can PING on DOM0 on Node 0 BUT cannot create any connection to it (SSH)

Thanks in advance ,,,


Update 1:
The ODA_BASE is available now but repos are not shown correctly and no VMs are shown

[root@]# oakcli show repo

          NAME                       TYPE            NODENUM  FREE SPACE     STATE           SIZE
          odarepo1                   local           0               N/A     N/A         N/A
          odarepo2                   local           1               N/A     N/A         N/A

[root@]# oakcli show vm
          NAME                      NODENUM         MEMORY          VCPU            STATE           REPOSITORY

stopped and started the ODA_BASE every thing runs fine for some time
but then the same loop of errors

Need help :(

[ErmanArslansOracleBlog]

Did you check my article on this?

Here is the link:

http://ermanarslan.blogspot.com.tr/2017/01/oda-investigating-oakcli-problem.html

So if you read the article above, you will see that I m analyzing the relevant logs for diagnosing the issue.
So without the logs, we can't proceed.

Anyways, first read the above note, check you are encountering the same problem.. If the problem given in the above note is the same as yours, apply the fix documented in that note.
If not, send me the relevant logs:

oakcli.log , odabaseagent.log, oakd.log and etc.