Avoid network timeout error in the agent on unsupported platforms#2001
Merged
Avoid network timeout error in the agent on unsupported platforms#2001
Conversation
chemamartinez
approved these changes
Dec 3, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The agent sets a receiving timeout when operating in TCP mode. This prevents the agent from getting locked if the manager does not respond.
Some old operating systems like Solaris 10 don't support socket timeout. This produces the next error while trying to set up the receiving timeout on startup:
This issue does not prevent the correct functioning of the agent. This PR will switch this error into a level-1 debug log.