NotOk Databus cluster is not running, no nodes are connected: Kafka Nodes (displayed in Device status)
Last Modified: 2022-08-24 08:47:30 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.
NotOk Databus cluster is not running, no nodes are connected: Kafka Nodes (displayed in Device status)
Technical Articles ID:
KB92496
Last Modified: 2022-08-24 08:47:30 Etc/GMT EnvironmentSIEM Application Data Monitor (ADM) 11.3.x SIEM Database Event Monitor (DEM) 11.3.x SIEM Data Streaming Bus (DSB) 11.3.x SIEM Event Receiver (Receiver) 11.3.x Problem
The device status in the Device properties page displays as When you run the command
System Change
This issue occurs when an upgrade has been performed from 10.x to 11.3.x. You might also see it after you perform an upgrade from 11.1.x to 11.3.x. Cause
The databus hasn't started following the upgrade.
Solution
To resolve this issue, do the following:
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision. Workaround
Technical Support can perform a workaround through a remote session to address this issue. To request this workaround, open a Service Request and provide this article number in the "Problem Description" field. To create a Service Request, log on to the ServicePortal:
Affected ProductsLanguages:This article is available in the following languages: |
|