# MaxScale 24.02.7 Release Notes

This document describes the changes in release 24.02.7, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please see [Upgrading MaxScale](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-management/deployment/upgrading-maxscale).

For any problems you encounter, please consider submitting a bug report on [our Jira](https://jira.mariadb.org/projects/MXS).

## New Features

* [MXS-5606](https://jira.mariadb.org/browse/MXS-5606) Add MAXSCALE\_USER and MAXSCALE\_PASSWORD environment variables
* [MXS-5052](https://jira.mariadb.org/browse/MXS-5052) Allow encrypt\_binlog=ON and innodb\_encrypt\_log=ON with Data-at-rest encryption when rebuilding with --async-rebuild-server

## Bug fixes

* [MXS-5920](https://jira.mariadb.org/browse/MXS-5920) MaxCtrl/REST-API should tell if password encryption is enabled
* [MXS-5915](https://jira.mariadb.org/browse/MXS-5915) MaxScale 24.02.6 is not compatible with MariaDB 12.0.2: Monitor fails with 'Cannot convert field ON to boolean'
* [MXS-5911](https://jira.mariadb.org/browse/MXS-5911) Upgrade Connector/C to 3.3.16 and 3.4.6
* [MXS-5910](https://jira.mariadb.org/browse/MXS-5910) Error 1047 when trying to run semi-sync replication through Maxscale
* [MXS-5897](https://jira.mariadb.org/browse/MXS-5897) Failing COM\_STMT\_PREPAREs that don't generate an ID aren't discarded from the history
* [MXS-5882](https://jira.mariadb.org/browse/MXS-5882) Initial config not stored for servers
* [MXS-5865](https://jira.mariadb.org/browse/MXS-5865) Run-time modification of users\_refresh\_time and users\_refresh\_interval are not immediately taken into use
* [MXS-5837](https://jira.mariadb.org/browse/MXS-5837) MaxScale 24.02.5 crashes with fatal signal 6 (std::length\_error in maxbase::load\_file<std::string>) on Ubuntu 24.04
* [MXS-5769](https://jira.mariadb.org/browse/MXS-5769) Watchdog timeout diagnostics are not detailed enough
* [MXS-5760](https://jira.mariadb.org/browse/MXS-5760) Authentication failure on all backends does not immediately close sessions
* [MXS-5733](https://jira.mariadb.org/browse/MXS-5733) MaxScale allows unlimited COM\_CHANGE\_USER attempts
* [MXS-5721](https://jira.mariadb.org/browse/MXS-5721) Configuration setting names use the old mariabackup name when the executable name is now mariadb-backup
* [MXS-5703](https://jira.mariadb.org/browse/MXS-5703) List of read-only builtin functions is out-of-date
* [MXS-5673](https://jira.mariadb.org/browse/MXS-5673) Config sync does not mark resources as modified
* [MXS-5653](https://jira.mariadb.org/browse/MXS-5653) MaxScale 24.02.6 GUI does not reflect parameter changes from Configuration Synchronization
* [MXS-5641](https://jira.mariadb.org/browse/MXS-5641) Confusing log message when the wrong connection holds on to the master server lock
* [MXS-5635](https://jira.mariadb.org/browse/MXS-5635) The variable disk\_space\_threshold should be dynamic for Servers
* [MXS-5559](https://jira.mariadb.org/browse/MXS-5559) maxctrl does not obfuscate password in ps output

## Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the [Limitations](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-quickstart-guides/mariadb-maxscale-limitations-guide) guide.

## Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded [here](https://mariadb.com/downloads/#mariadb_platform-mariadb_maxscale).

## Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version of MaxScale.

The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

<sub>*This page is: Copyright © 2025 MariaDB. All rights reserved.*</sub>

{% @marketo/form formid="4316" formId="4316" %}