This guide describes two issues that were fixed in LogRhythm 7.13, as well as the upgrade procedure from 7.13.x to 188.8.131.52.
The updated components provided in 184.108.40.206 were added to the 7.13.0 GA release downloads on July 17, 2023. If you upgraded using 7.13.0 GA software downloaded after July 17, you do not need to apply this patch.
The Log Volume Report no longer shows inflated MPS and EPS numbers.
Components such as Bulldozer, Carpenter, and GoMaintain can now correctly acquire API consul locks as expected.
Download the Upgrade Components
The 220.127.116.11 release includes an updated installer. The new installer can be downloaded from the LogRhythm Community.
Log in to the Community.
On the main menu bar, click Documentation & Downloads, and then click SIEM.
Click NextGen SIEM, and then click 7.13.0 GA Downloads.
Under 7.13.0 GA Downloads, download the LogRhythm Install Wizard.
Upgrade the 7.13.0 Deployment
Run the LogRhythm Install Wizard just as you would to upgrade a deployment.
Open the Install Wizard directory, and right-click the LogRhythmInstallWizard.exe you downloaded in the steps above.
Click Run as administrator.
The LogRhythm Install Wizard 7.13.0 appears.
The LogRhythm Install Wizard Confirmation dialog box appears.
The License Agreement appears.
Select the check box to accept the terms in the license agreement, and then click Next.
On the configuration page, select the Data Processor configuration.
Under Optional Applications, deselect LRD Agent, and then click Install.
When the installer is finished, verify that the Web services are running.
(Optional.) Upgrade Databases
To resolve issue ENG-38290, your LogRhythm database must be upgraded. If you are a user of the Log Volume Report and need this issue to be resolved in your environment, you must take this step as well.
For instructions on how to run the LogRhythm Database Upgrade tool, refer to the topic Upgrade LogRhythm Databases.
To avoid running the entire Database Upgrade tool, you can simply execute the Logrhythm.LogMart.sql file manually. Updating LogMart alone is sufficient to resolve the issue with the Log Volume Report.