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

Agent did not connect or did not find a matching profile. Please make sure that agent can connect to collector, and that agent settings system profile name is valid

Hi ,

I have got an Issue where the agent could connect for a while and then it gives the error message

"Agent did not connect or did not find a matching profile. Please make sure that agent can connect to collector, and that agent settings system profile name is valid "

and the agents stops working , but if I uninstall the agent and reinstall it ,initially it works fine but after a while (a day approx) it gives the message above

what could be causing the problem ? we recently moved the dtserver and the collector to our own servers

7 REPLIES 7

Babar_Qayyum
Leader

Hello Sajidh,

It seems to be an unusual problem as you described.

Is this only with the same agent or you noticed with others also?

Share the Agent logs and the agent status view screenshot where we can see the profile name, JVM version and license status of this agent.

Regards,

Babar

all three agents has the same problem , this is how the agent logs look like

Babar_Qayyum
Leader

Hello Sajidh,

First of all telnet the port number 9998 from your agents machine to collector 100.112.144.89.

Secondly, if you have a firewall between agents and collector (not recommended) then open the 'Agents View' dashboard and add the 'Average Instrumentation Response Time' & 'Maximum Instrumentation Response Time' from the header with the right click and share the screenshot.

Regards,

Babar

Hi Babar

telnet doesnt work for the IP , but it works for the qualified domain name , meanwhile the agents seems be like working only for 30hrs and then it gives the error above,

Hello Sajidh,

If this is the case then can you use the FQDN with the port instead of IP address and check the behaviour for the next 30 hours whether it disconnect or not.

If possible for you, just try to restart the collector once before or after the above exercise.

Regards,

Babar

Hello Babar

I have added the FQDN in the agent configuration , for some reason it gets replaced with that IP address , any clue about why this happens ?

Thanks

Sajidh

Hello Sajidh,

Do you have multiple NIC on agents host?

Try the following from the 'Agent Mapping' for each agent.

Specify a case insensitive pattern for the host name of the Agent. The host name is set by the Agent and depends on the configuration of the host's name resolution mechanism. Use host patterns for example to define mappings for clustered servers which can be distinguished by their host or IP address.

Regards,

Babar