Jump to content

Best method for Agent repair?


j-gray
 Share

Recommended Posts

I have a number of workstations, both OS X and Windows 7, where they stop communicating with the ERA Server.

 

The clients continue to function -they pull updates, the status pages and error pages look normal and the trace.log files don't indicate any errors.

 

For all intents and purposes, the clients appear to be working and configured the same as other working clients. They simply don't update their status in the ERA console.

 

Is there a good method to reset/refresh/repair the agent?  My only remedy so far is to uninstall the agent and reinstall it via 3rd party remote tools, which is cumbersome.

 

Any suggestions appreciated.

Link to comment
Share on other sites

  • ESET Staff

Have you checked status.html log of problematic AGENTS for last connection time? There is a chance AGENT is actually not running which will be indicated by old last replication time. In case there will be recent time, problem will be most probably on SERVER's side. What version/platform/DB type are you using? Any chance you using ERA Proxy (not HTTP Proxy)?

We have had similar problems with ERA 6.3 (+ MySQL) where main client's view in Webconsole stopped refreshing it's content. Please check also client details view in Webconsole whether it contains correct data, especially last connection time. Quick fix for this issue was restart of SERVER's service .. have you tried it?

Link to comment
Share on other sites

Have you checked status.html log of problematic AGENTS for last connection time? There is a chance AGENT is actually not running which will be indicated by old last replication time. In case there will be recent time, problem will be most probably on SERVER's side. What version/platform/DB type are you using? Any chance you using ERA Proxy (not HTTP Proxy)?

We have had similar problems with ERA 6.3 (+ MySQL) where main client's view in Webconsole stopped refreshing it's content. Please check also client details view in Webconsole whether it contains correct data, especially last connection time. Quick fix for this issue was restart of SERVER's service .. have you tried it?

 

Hi Martin

 

How do I check the status.html log of problematic agents? 

Link to comment
Share on other sites

  • ESET Staff

As of now, the only way is to check it locally on the machine.

Navigate to : C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs to see it.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...