This Windows limitation also applies to the Rollback section below. You must re‑run a Windows installer on these Nodes to upgrade them. If you have custom functions in cribl/bin/cribl, please move them under $CRIBL_HOME/local/cribl/functions/ before untarring again.įor a distributed deployment, the general order of upgrade is: First upgrade the Leader Node, then upgrade the Edge Nodes, then commit and deploy the changes on the Leader.Ĭurrently, you can't upgrade Windows Edge Nodes via Cribl Edge's UI. In this case, please remove the cribl/bin/cribl directory if it's empty, and untar again. On some Linux systems, tar might complain with: cribl/bin/cribl: Cannot open: File exists. Uncompress the new version on top of the old one. This path requires upgrading only the single/standalone Node: If you do need to roll back, see see Restoring Unencrypted Private Keys below. If you need to roll back to a pre-4.1 version, see Restoring Unencrypted Private Keys. Take appropriate precautions to prevent unauthorized access to these unencrypted private key files. Files in the auth/certs directory are particularly important, such as those in: To safeguard your unencrypted private keys, make a full backup of all Cribl config files.
Having access to the unencrypted files is essential if you later find that you need to roll back to your previous version.
Before upgrading from a pre-4.1 version, make a backup copy of all unencrypted TLS certificate private key files.
0 kommentar(er)
