Update :: BIFIT Mitigator

Update to v26.08

Mon, 01 Jan 0001 00:00:00 +0000

The update to version v26.08 is performed according to the standard procedure, however, before starting MITIGATOR, additional steps are required. In /srv/mitigator/.env, set the variable MITIGATOR_MASTER_SECRET. It contains master secret used to encrypt sensitive settings. Set it to an arbitrary string consistent across all cluster instances. It is recommended to generate the password using the following command: openssl rand -hex 32 Info The value of MITIGATOR_MASTER_SECRET must be preserved during MITIGATOR updates and after restores from backup. In case of its loss, sensitive settings have to be reconfigured. An example of such settings is two-factor authentication (2FA).

Update to v26.04

Mon, 01 Jan 0001 00:00:00 +0000

Warning In MITIGATOR v26.04, default settings for network interfaces have changed. For installations with more than four network ports, it may be necessary to increase the value of packet_mempool_size in data-plane.conf. Read more. Warning Starting from MITIGATOR v26.04, Linux kernel version 5.0 or higher is required for TAP interface operation. If you use traffic redirection to a TAP interface in the operating system, before updating MITIGATOR ensure that your OS uses the required kernel version, otherwise the TAP interface will not work.

Update to v25.12

Mon, 01 Jan 0001 00:00:00 +0000

The update to version v25.12 is performed according to the standard procedure, however, before starting MITIGATOR, additional steps are required. Traffic bypass during congestion is now managed only through the web interface, so before starting MITIGATOR: Remove the congestion_bypass parameter from the dataplane.conf file, if it was set. The file may be empty if the dataplane parameters have not been changed previously. # Enable traffic bypass on packet processor congestion (for `port_direct_mode: false`). congestion_bypass: false If the parameter value was false, no additional actions are required. If the parameter value was true, enable traffic bypass during congestion using the “Pass traffic without processing when system congestion occurs” option on the “Common Settings” page in the system settings.

Update to v25.10

Mon, 01 Jan 0001 00:00:00 +0000

Warning Make a backup before performing the following steps. Ensure that Docker Compose version 2 is installed: docker-compose version --short Upgrade if required. MITIGATOR no longer supports Docker Compose version 1. Remove elements unsupported by Docker Compose v2 from .env file: sed -e 's/\b$docker-compose.yml$:\1/\1/' -i .env Stop MITIGATOR: docker-compose down Remove version: "2.2" from all Docker Compose YAML files: for file in $(sed -n 's/^COMPOSE_FILE=$.*$$/\1/p' .env | tr : ' '); do sed -i '/^version: "2.2"$/d' $file; done Update all MITIGATOR instances using standard procedure.

Update to v25.06

Mon, 01 Jan 0001 00:00:00 +0000

Warning Make a backup before performing the following steps. Preparing for the Update Ensure that Docker Compose version 2 is installed: docker-compose version --short Upgrade if required. MITIGATOR no longer supports Docker Compose version 1. Remove elements unsupported by Docker Compose v2 from .env file: sed -e 's/\b$docker-compose.yml$:\1/\1/' -i .env If using NVIDIA (Mellanox) network adapters update OFED to the latest version.

Update to v25.02

Mon, 01 Jan 0001 00:00:00 +0000

Update procedure for v25.02 does not differ from the standard one, but requires additional steps: metrics migration; (optional) settings for distributing requests for plotting graphs; (optional) setting thresholds for incident registration. Metrics Migration Procedure Download the migration file to all ClickHouse instances. wget https://docs.mitigator.ru/master/kb/update2502/update2502.sql -O /srv/mitigator/update2502.sql Run the migration: docker-compose exec -T clickhouse clickhouse-client -mn < update2502.sql No messages are printed in case of success. Please report any error messages to the support.

Update to v24.08

Mon, 01 Jan 0001 00:00:00 +0000

Due to Docker updates in latest versions of operating systems, you may experience problems with Docker Compose. MITIGATOR, starting with v24.08, supports both Docker Compose versions v1 and v2. However, if you are planning to upgrade your operating system, there are some additional steps you should perform, depending on the OS distribution and version of Docker you are using. Otherwise, the correct operation of the commands specified on this site cannot be guaranteed.

Update to v23.12

Mon, 01 Jan 0001 00:00:00 +0000

Update procedure for v23.12 version does not differ from the standard one, but docker-compose down command should be executed with --remove-orphans key due to container renaming. However, v23.12 introduces several changes that require additional steps to be taken before running MITIGATOR. Such changes include: end of support of the old data-plane.conf configuration file format existed before v20.08. Renaming data-plane.conf file to dataplane.conf. Compatibility with the old name is maintained, but we recommend to update the file name. Renaming data-plane container to dataplane. Changes to pgfailover logic. Transferring VPN settings to the base configuration file docker-compose.yml. Therefore, when updating, make sure that:

Update to v23.06

Mon, 01 Jan 0001 00:00:00 +0000

Update procedure for v23.06 version does not differ from the standard one, but requires migrations. After updating you should: Download the migration file to all ClickHouse instances. wget https://docs.mitigator.ru/kb/update2306/update2306.sql -O /srv/mitigator/update2306.sql Run migration: docker-compose exec -T clickhouse clickhouse-client -mn < update2306.sql Messages are printed only in case of errors. Report the error text to developers if you get it. Restart Carbon Clickhouse: docker-compose restart carbon-clickhouse

Update to v23.02

Mon, 01 Jan 0001 00:00:00 +0000

Update The update procedure for v23.02 requires the mandatory replacement of all previously downloaded *.yml files from the site as docker.compose.yml, docker-compose.failover.yml etc. If you get the following error when trying to download new images: ERROR: for accesslog unknown: artifact product/accesslog:v23.02 not found ERROR: unknown: artifact product/accesslog:v23.02 not found Replace the remaining occurrences of docker.mitigator.ru/product/ and docker.mitigator.ru/vendor/ with docker.mitigator.ru/mitigator/ in all *.ymlfiles.

Update to v22.12

Mon, 01 Jan 0001 00:00:00 +0000

Before updating MITIGATOR, you need to update Docker on all instances up to the current version (20.10.10+ for docker-ce, 20.10.5+ for docker.io). An update from the software repositories for your OS is recommended. After that, the standard update procedure is performed.

Update to v22.08

Mon, 01 Jan 0001 00:00:00 +0000