Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could the service possibly crash sometime when agent is not able to contact the server? #236

Open
StCyr opened this issue Feb 8, 2022 · 0 comments

Comments

@StCyr
Copy link

StCyr commented Feb 8, 2022

It's hard to solve a problem when important details are missing, that why we added this template, to help you and us.

General information

Operating system : Windows 10

OCS Inventory information

Windows agent version : 2.9

Problem's description

I regularly have agents which stop contacting the server.

Initial troubleshooting has shown this is often due to the "OCS Inventory Service" being stopped.

Further analysises show that those agents often (always?) have the following error line in their logs:

ERROR *** AGENT => Failed to send Prolog <Couldn't resolve host name>

The configuration of these agents is OK since simply restarting the service manually makes everything back on track. So, I've the following hypothesis regarding to what happens to these agents:

  1. User boots his computer;
  2. OCS Inventory Service starts the agent;
  3. Agent fails to contact the OCSI server because the networks isn't up yet (we currently need an active VPN session to contact our OCSI server);
  4. Because the agent failed to contact the server, the OCS Inventory Service stops until next reboot.

Do you think this could possibly happen?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant