Segfault occurs on masvc process and McAfee Agent services are stopped on Linux systems
Last Modified: 2021-02-18 19:29:15 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.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
Segfault occurs on masvc process and McAfee Agent services are stopped on Linux systems
Technical Articles ID:
KB91265
Last Modified: 2021-02-18 19:29:15 Etc/GMT Environment
McAfee Agent (MA) 5.6.0 Supported Linux operating systems For environment information, see KB51573 - Supported platforms for McAfee Agent 5.x. Problem
At random times, a The The
NOTE: Errors are only seen when logging is set to detailed logging in the McAfee Agent policy before debug messages appear in the Cause
This issue can occur when:
Solution
This issue is resolved in McAfee Agent 5.6.1. Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.
Our product software, upgrades, maintenance releases, and documentation are available on the Product Downloads site.
NOTE: You need a valid Grant Number for access. See KB56057 - How to download product updates and documentation for more information about the Product Downloads site, and alternate locations for some products. Workaround
Restart all McAfee Agent services. Use the following command: Related InformationThis issue was seen with MA 5.6.0, but could potentially occur on earlier versions of MA.
This specific issue only occurs if IPv6 is disabled on the client. To see if any installed network interfaces have IPv6 enabled, run Affected ProductsLanguages:This article is available in the following languages: |
|