コンテンツにスキップ

postanalyticsモジュールのアップグレード

これらの手順は、別サーバー上にインストールされているpostanalyticsモジュール4.xをアップグレードする手順について説明しています。postanalyticsモジュールは、Wallarm NGINXモジュールのアップグレードの前にアップグレードする必要があります。

all-in-oneインストーラーによるアップグレード

バージョン4.10以降、個別のLinuxパッケージが廃止されたため、アップグレードはWallarmのall-in-oneインストーラーを使用して実施されます。この方法は、従来のアプローチと比べてアップグレードプロセスおよび継続的な展開メンテナンスを簡素化します。

インストーラーは自動的に以下の処理を行います：

  1. OSおよびNGINXのバージョンを確認します。
  2. 検出されたOSおよびNGINXのバージョンに応じてWallarmリポジトリを追加します。
  3. これらのリポジトリからWallarmパッケージをインストールします。
  4. インストールされたWallarmモジュールをNGINXに接続します。
  5. 提供されたトークンを使用してフィルタリングノードをWallarm Cloudに接続します。

all-in-oneと手動の比較

サポート終了モジュール (3.6以下) をアップグレードするには、こちらの別の手順をご使用ください。

必要条件

  • Access to the account with the Administrator role in Wallarm Console for the US Cloud or EU Cloud.

  • Access to https://meganode.wallarm.com to download all-in-one Wallarm installer. Ensure the access is not blocked by a firewall.

  • Access to https://us1.api.wallarm.com for working with US Wallarm Cloud or to https://api.wallarm.com for working with EU Wallarm Cloud. If access can be configured only via the proxy server, then use the instructions.

  • Executing all commands as a superuser (e.g. root).

  • Access to the IP addresses below for downloading updates to attack detection rules and API specifications, as well as retrieving precise IPs for your allowlisted, denylisted, or graylisted countries, regions, or data centers.

    34.96.64.17
34.110.183.149
35.235.66.155
34.102.90.100
34.94.156.115
35.235.115.105

    34.160.38.183
34.144.227.90
34.90.110.226

ステップ 1: クリーンなマシンを準備します

When upgrading modules with all-in-one installer, you cannot upgrade an old package installation - instead you need to use a clean machine. Thus, as step 1, prepare a machine with one of the supported OS:

  • Debian 10, 11 and 12.x

  • Ubuntu LTS 18.04, 20.04, 22.04

  • CentOS 7, 8 Stream, 9 Stream

  • Alma/Rocky Linux 9

  • RHEL 8.x

  • RHEL 9.x

  • Oracle Linux 8.x

  • Oracle Linux 9.x

  • Redox

  • SuSe Linux

  • Others (the list is constantly widening, contact Wallarm support team to check if your OS is in the list)

Using new clean machine will lead to that at some moment you will have both old and new node, which is good: you can test the new one working properly without stopping the old one.

ステップ 2: Wallarmトークンを準備します

To install node, you will need a Wallarm token of the appropriate type. To prepare a token:

  1. Open Wallarm Console → Settings → API tokens in the US Cloud or EU Cloud.
  2. Find or create API token with the Node deployment/Deployment usage type.
  3. Copy this token.
  1. Open Wallarm Console → Nodes in the US Cloud or EU Cloud.
  2. Do one of the following:
    • Create the node of the Wallarm node type and copy the generated token.
    • Use existing node group - copy token using node's menu → Copy token.

ステップ 3: all-in-one Wallarmインストーラーをダウンロードします

Wallarm suggests all-in-one installations for the following processors:

  • x86_64

  • ARM64 (beta)

To download all-in-one Wallarm installation script, execute the command:

curl -O https://meganode.wallarm.com/6.1/wallarm-6.1.0.x86_64-glibc.sh

curl -O https://meganode.wallarm.com/6.1/wallarm-6.1.0.aarch64-glibc.sh

ステップ 4: all-in-one Wallarmインストーラーを実行してpostanalyticsをインストールします

To install postanalytics separately with all-in-one installer, use:

# If using the x86_64 version:
sudo env WALLARM_LABELS='group=<GROUP>' sh wallarm-6.1.0.x86_64-glibc.sh postanalytics

# If using the ARM64 version:
sudo env WALLARM_LABELS='group=<GROUP>' sh wallarm-6.1.0.aarch64-glibc.sh postanalytics

The WALLARM_LABELS variable sets group into which the node will be added (used for logical grouping of nodes in the Wallarm Console UI).

# If using the x86_64 version:
sudo sh wallarm-6.1.0.x86_64-glibc.sh postanalytics

# If using the ARM64 version:
sudo sh wallarm-6.1.0.aarch64-glibc.sh postanalytics

ステップ 5: 別サーバー上のNGINX-Wallarmモジュールをアップグレードします

別サーバー上にpostanalyticsモジュールがインストールされたら、異なるサーバーで稼働する関連するNGINX-Wallarmモジュールをアップグレードします。

ステップ 6: NGINX-Wallarmモジュールをpostanalyticsモジュールに再接続します

On the machine with the NGINX-Wallarm module, in the NGINX configuration file, specify the postanalytics module server address:

upstream wallarm_tarantool {
    server <ip1>:3313 max_fails=0 fail_timeout=0 max_conns=1;
    server <ip2>:3313 max_fails=0 fail_timeout=0 max_conns=1;

    keepalive 2;
    }

    # omitted

wallarm_tarantool_upstream wallarm_tarantool;

  • max_conns value must be specified for each of the upstream Tarantool servers to prevent the creation of excessive connections.

  • keepalive value must not be lower than the number of the Tarantool servers.

  • The # wallarm_tarantool_upstream wallarm_tarantool; string is commented by default - please delete #.

Once the configuration file changed, restart NGINX/NGINX Plus on the NGINX-Wallarm module server:

sudo systemctl restart nginx

sudo service nginx restart

sudo systemctl restart nginx

sudo systemctl restart nginx

sudo systemctl restart nginx

ステップ 7: NGINX-Wallarmモジュールと別サーバーのpostanalyticsモジュールの連携を確認します

To check the NGINX‑Wallarm and separate postanalytics modules interaction, you can send the request with test attack to the address of the protected application:

curl http://localhost/etc/passwd

If the NGINX‑Wallarm and separate postanalytics modules are configured properly, the attack will be uploaded to the Wallarm Cloud and displayed in the Attacks section of Wallarm Console:

Attacks in the interface

If the attack was not uploaded to the Cloud, please check that there are no errors in the services operation:

  • Analyze the postanalytics module logs

    sudo cat /opt/wallarm/var/log/wallarm/tarantool-out.log

    If there is the record like SystemError binary: failed to bind: Cannot assign requested address, make sure that the server accepts connection on specified address and port.

  • On the server with the NGINX‑Wallarm module, analyze the NGINX logs:

    sudo cat /var/log/nginx/error.log

    If there is the record like [error] wallarm: <address> connect() failed, make sure that the address of separate postanalytics module is specified correctly in the NGINX‑Wallarm module configuration files and separate postanalytics server accepts connection on specified address and port.

  • On the server with the NGINX‑Wallarm module, get the statistics on processed requests using the command below and make sure that the value of tnt_errors is 0

    curl http://127.0.0.8/wallarm-status

    Description of all parameters returned by the statistics service →

ステップ 8: 古いpostanalyticsモジュールを削除します

  1. Delete old postanalytics module in Wallarm Console → Nodes by selecting your postanalytics module node and clicking Delete.

  2. Confirm the action.

    When the postanalytics module node is deleted from Cloud, it will stop participation in filtration of requests to your applications. Deleting cannot be undone. The postanalytics module node will be deleted from the list of nodes permanently.

  3. Delete machine with the old postanalytics module or just clean it from Wallarm postanalytics module components:

    sudo apt remove wallarm-node-tarantool

    sudo apt remove wallarm-node-tarantool

    sudo yum remove wallarm-node-tarantool

    sudo yum remove wallarm-node-tarantool

    sudo yum remove wallarm-node-tarantool