AnsweredAssumed Answered

Wily Mom dashboard greyout/intermittent disconnect from collectors

Question asked by sumit_cs on Feb 20, 2014
Latest reply on Jan 28, 2016 by Hiko_Davis

Hi,

We are facing real wobbly issues with Wily Mom dasbord gtting greyout, all of collectors getting disconncted from mom.

Following is what we have tried till date but nothing seem to be directng us to anywhere:

transport.ovverride.isengard.high.concurrency.pool.max.size=10

transport.outgoingMessageQueueSize=6000

I have been keeping a close tract of ntp offset and tough have noticed few collector are 1.3ish sec offset from Mom but not for long.

We are using datastore frm SAN (a sngle lun is formed of multiple datastore) but vmware report shows that we arent doing that muc of I/O intensive activity.

Though I asked about vmotion to which they said it is enaled for Mom and collector but the havent been vmotiond for a while.

So following are my queries:

Is there a way to check from vmware guest (collctor & mom) that they have been vmotioned.

Wha is ping time, can it b different from ntp offset status, if I cnfigure simple ping for round trip pkts, will that data also account for ping time. I mean ping time i wily term but we have t make infrastructure team to understand that tere ca b something wrng wit n/w (though mom & collector are in same subnet)

following are the error message which I usually see when wily is wobbly :

[error] [PO Route Down Executor] [Manager] Uncaught Exception in Enterprise Manager: In thread PO Route Down executor and the message is java.lang.NullPointerException

[Manager Cluster] Waited 15000 ms But did no receive respone for the mssage com.wily.isengrd.messageprimitves.servics.MessageServiceCallMessage.

ny help will be useful specially if we can find out whether Mom was vmotoned.

thanks

sumit

 

 

 

Outcomes