9.2.2. Procédure to configure the Gmalcore engine

9.2.2.1. Introduction

Configuring Gmalcore involves:

ensuring that the engines are started
ensuring that the engines up to date
ensuring that engine updates have been scheduled

The functions of the Gmalcore engine are described in the Overview of the Gmalcore engine section.
The status of the Gmalcore engines is provided via the `Gmalcore configuration` window.
The graphical configuration interface is described in `Gmalcore configuration` screen.

9.2.2.2. Prerequisites

User: member of Administrators Group

9.2.2.3. Preliminary operations

Connect to the GBox via a browser (see Connection to the web interface via a browser).

9.2.2.4. Procedure for checking whether Gmalcore engines have started

In the navigation bar, click on the `Analysers` command.

The following screen is displayed.

For the Gmalcore engine, the information displayed is:

If status (5) is `Ready` then the engines are prepared.

If status (5) is `Not ready` as shown above, then the engine configuration is not done (the engines are not ready).
Click on the `Config` link (3) to check.

9.2.2.4.1. Procedure for the `Ready` status

The following screen is displayed.

Check the following items:

The engines are listed (`ENGINE HASH` column)

All engines have the status ok (tick in the `STATUS` column)

The last update is less than 3 days old, as indicated by the colours of the `STATUS` column icon

If the updates are old, check the update system used in GUM (online, local...).

For online or local updates, refer to the Configuring automatic updates via GUM.

If this configuration does not work, contact GATEWATCHER support. .. sav2_en

If there is no automatic configuration then refer to the procedure in Manual installation of a signature update.

9.2.2.4.2. Procedure for the `Not Ready` status

The following screen is displayed.

In the Malcore configuration screen, the following message (1) is displayed: `Engine is running, but no AV found. Please update.`

In this case, there is no engine installed.

It is imperative to install a signature and engine update, i.e.:
- automatically via GUM (online, local): refer to the Configuring automatic updates via GUM
- manually then refer to the Manual installation of a signature update

Note

If necessary, configure a proxy (see the Configuring a proxy procedure).