McAfee Agent for Linux fails to find the system configured proxy
Last Modified: 2021-09-09 11:39:21 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
McAfee Agent for Linux fails to find the system configured proxy
Technical Articles ID:
KB93394
Last Modified: 2021-09-09 11:39:21 Etc/GMT Environment
McAfee Agent (MA) 5.6.x
Problem
McAfee Agent on Linux systems that use a proxy to reach ePO fail to complete the agent to server communication interval (ASCI). The McAfee Agent fails to detect the system configured proxy during installation. The errors below are recorded in the ahclient.Debug: Proxy configuration setting "Use System Proxy" ahclient.Debug: Trying to make the spipe connection via proxy. proxy_detect.Info: no system proxy, proxy detect returns rc <7> ahclient.Debug: No proxy found for site https://eposerver:443/spipe/pkg?AgentGuid={a28a53b0-a1dc-11ea-127e-020017029e7b} Solution
This issue is resolved in McAfee Agent 5.7.2, which is available from either the ePO Software Manager or the Product Downloads site. For more information, see the McAfee Agent 5.7.0 release notes. To view other known and resolved issues, see KB93773 - McAfee Agent 5.7.x Known Issues. NOTE: You need a valid Grant Number to access the update. Workaround
Force the agent to use the proxy server for communication with ePO.
Affected ProductsLanguages:This article is available in the following languages: |
|