![]() ![]() Workaround: Clear URL base path in Settings > General Settings > Advanced or specify an empty baseURL key in cribl.yml. The log may also contain checksum mismatch warnings. Problem: In Cribl Stream 4.1.2–4.1.3, if you define the baseURL key on a Leader, Worker Nodes don't get the latest config version from the Leader. v.4.1.2–4.1.3 – Worker Nodes don't update from Cribl Stream Leader Workaround: Roll back to a previous stable version, such as 4.1.0. ![]() When this happens, you cannot manage or monitor Cribl Stream environments. Following a 4.1.1 or 4.1.2 upgrade, the Leader can become non-responsive to UI requests due to a steady 100% CPU utilization. This change can have a negative impact in larger environments with many Worker Processes. Problem: In 4.1.1, to improve product security, we changed how we manage our RPC traffic from Leaders and Workers. – v.4.1.1–4.1.2 – Perf bug: RPC consuming excessive CPU compiling expressions Workaround: In the Event Breaker, move the logic that adjusts _raw into a Pre-Processing Pipeline. Problem: The Kubernetes Logs Event Breaker incorrectly breaks events with out-of-order timestamps. – v.4.1.0–4.1.2 – Kubernetes Logs Event Breaker Incorrectly Breaks Events These users will also have the ability to deploy a Worker Group or Fleet. Workaround: Apply the GroupFull policy for users that need to be able to Commit changes. ![]() These users should be able to Commit, but not Deploy, changes. create new Sources) but are unable to Commit their changes. Problem: Users having the GroupEdit policy are able to make changes (e.g. ![]() – v.4.0.0–4.1.2 – GroupEdit is not able to commit changes Workaround: Do not use this option in v.4.1.2. Problem: The AES-256-GCM encryption option introduced in v.4.1.2 included a security vulnerability. – v.4.1.2 – AES-256-GCM security vulnerability If this is not possible, upgrade Edge Nodes separately using the boostrap script. Workaround: The Edge Nodes and Workers must connect to the leader using the host/ port/ tls connection details. Problem: A Fleet's upgrade from a Leader can result in errors when the Edge Nodes use different host/ port/ tls settings than Worker Nodes. – All Versions through 4.2.0- Fleet Upgrade Errors This page lists known issues affecting Cribl Stream and/or Cribl Edge. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |