Fortinet black logo

Release Notes

What's New in 6.4.3

What's New in 6.4.3

This release includes several code improvements in phMonitor, App Server and Linux Agent areas.

This release also updates Rocky Linux OS to 8.8 and includes published Rocky Linux OS updates until August 7, 2023. The list of updates can be found at https://errata.rockylinux.org/.

FortiSIEM Rocky Linux Repositories (os-pkgs-cdn.fortisiem.fortinet.com and os-pkgs-r8.fortisiem.fortinet.com) have also been updated to include fixes until July 14, 2023. Therefore, FortiSIEM customers in versions 6.4.1 and above, can upgrade only their Rocky Linux versions by following the procedures described in the FortiSIEM OS Update Procedure Guide.

If you are running 6.4.0, 6.4.1, or 6.4.2, Fortinet highly recommends upgrading to 6.7.7 or 7.0.1 or later, instead of upgrading to 6.4.3. If you must upgrade to 6.4.3, then the next upgrade should be to 6.7.7 or 7.0.1 or later, otherwise the Supervisor/Worker upgrade will fail. This is because of bug fix to 915077 which is in 6.7.5 or later, but not back ported to 6.6.4.

Previous
Next

What's New in 6.4.3

This release includes several code improvements in phMonitor, App Server and Linux Agent areas.

This release also updates Rocky Linux OS to 8.8 and includes published Rocky Linux OS updates until August 7, 2023. The list of updates can be found at https://errata.rockylinux.org/.

FortiSIEM Rocky Linux Repositories (os-pkgs-cdn.fortisiem.fortinet.com and os-pkgs-r8.fortisiem.fortinet.com) have also been updated to include fixes until July 14, 2023. Therefore, FortiSIEM customers in versions 6.4.1 and above, can upgrade only their Rocky Linux versions by following the procedures described in the FortiSIEM OS Update Procedure Guide.

If you are running 6.4.0, 6.4.1, or 6.4.2, Fortinet highly recommends upgrading to 6.7.7 or 7.0.1 or later, instead of upgrading to 6.4.3. If you must upgrade to 6.4.3, then the next upgrade should be to 6.7.7 or 7.0.1 or later, otherwise the Supervisor/Worker upgrade will fail. This is because of bug fix to 915077 which is in 6.7.5 or later, but not back ported to 6.6.4.

Previous
Next