ON PREMISES SOLUTIONS

Error codes for GravityZonePatch Management

The GravityZone console displays relevant error messages after Patch Management tasks fail on endpoints. Here are listed the most common error codes and messages related to Linux endpoints.

Patch Management error codes for Linux

The endpoint received a policy with invalid data. [13]

Description

This error occurs when the GravityZone policy contains valid parameters and fields, but they are listing incorrect data.

Solution

Check the policy settings and make sure that they are applied to the target endpoint. Also verify the endpoint is supported, according to the requirements listed here.

The endpoint agent is not ready. [21]

Description

This error occurs when the Patch Management module failed to initialize on the endpoint due to internal issues. Patch Management also cannot initialize on unsupported Linux distributions.

Solution

Make sure that the target endpoint is able to receive the policy. Also verify the endpoint is supported, according to the requirements listed here.

The endpoint received a policy with invalid parameters. [87]

Description

This error occurs when the GravityZone policy contains invalid parameters such as different type expected, missing fields, unknown patch type, and invalid patch identifiers.

Solution

Check your settings and make sure the target endpoint is supported, according to the requirements listed here.

The endpoint agent could not access the Patch Management module. [126]

Description

This error occurs when Bitdefender Endpoint Security Tools for Linux could not access the Patch Management module to handle Patch Scan and Patch Install task settings.

Solution

Make sure that the target endpoint is supported, according to the requirements listed here.

Patch Install task stopped due to internal issues. [995]

Description

This error occurs in the following circumstances:

  • During a manual patch installation, pre-scan or getting patch details have failed due to internal issues.

  • During a manual patch installation, the task failed because the endpoint agent could not initialize the Patch Management module, the license key had expired, or some patch identifiers were invalid.

The automatic patch installation handles this error through a scheduler and any errors would only be visible in the debug logs.

Solution

Make sure that the target endpoint is supported, according to the requirements listed here.

Patch Scan task is already running. [1247]

Description

This error occurs when you trigger in GravityZone a manual patch scan while another scan task (manual or scheduled) is running.

Solution

Please wait until the current task is completed.

The endpoint received a deprecated policy. [1150]

Description

This error occurs when the endpoint receives a policy with deprecated settings for Patch Scan and Patch Install tasks.

Solution

Check the policy settings and make sure that they are applied to the target endpoint. Also verify the target endpoint is supported, according to the requirements listed here.

Policy name or action not supported. [2147942450]

Description

This error occurs when the GravityZone policy name is not listed in the endpoint configuration files or when the action provided is different from “install”.

Solution

Make sure that the policy is applied to the target endpoint. Also verify the endpoint is supported, according to the requirements listed here.