cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Host going to unmonitored state

dambala_rosyla1
Participant

Hi Team,

We have installed Dynatrace oneagent on Solaris nodemanager server for which the host is going to unmonitored state after 15 mins and again coming back to monitored state after 1 day. This happened for 6 solaris hosts out of 10 and we installed on 3 hosts a day and the same issue occured two days. We thought it is unable to communicate with Active Gate but after seeing the logs we could see there is a connection established. Then what is making the host going into unmonitored state and coming back to monitored state automatically after a day.

Please suggest what may be the root cause for this issue.

Thanks&Regards,

Rosy



7 REPLIES 7

ChadTurner
DynaMight Guru
DynaMight Guru

interesting, can you confirm that firewall isnt blocking it, and that any security app isnt blocking it?

-Chad

dambala_rosyla1
Participant

Log.txtHi,

There are no firewalls blocking the connection. If I see the agent logs I found the following attached:

Can you please tell what is making the agent inactive and active again automatically?

Thank you for providing the log. I would open up a support ticket. Are you using a DEMO version of Dynatrace? Can you check and ensure your trial is valid or if you have purchased dynatrace, that you have enough licenses for host units/hours? Have you tried to uninstall and reinstall the oneagent? what version of the oneagent are you using? what version is your cluster at?

-Chad

wolfgang_beer
Dynatrace Leader
Dynatrace Leader

Please create a support ticket for that situation, this does not match the designed behavior.

Thanks,

Wolfgang

sorin_zaharov
Organizer

Hi,

Have you been able to resolve this issue?

Br,

Sorin

Sorin Z

peter_fisser
Contributor

Do you have enough HU ? if not monitoring will be auto disabled ..

Yes, we have enough HU licenses. The problem was how Dynatrace needs to be instrumented when deploying on a Weblogic administered through NodeManager and running on Solaris. The issue was fixed.

Sorin Z