Vapmd did not handle signal 15

Issue

When starting the vapmd process, it crashes immediately and logs the following error:

Child process vapmd[23412] did not handle signal 15, restart in 0 seconds

This issue occurs when a new policy from ESET PROTECT with VAPM enabled is scheduled for the current time window. For example, if it is 14:00, the policy might have a start time of 13:00 and an end time of 01:00.

Impact

This is a harmless issue and does not affect VAPM functionality.

Solution

Ensure that the policy from ESET PROTECT has a valid time window set. Although the issue is harmless, verifying that the policy time windows are correctly configured is the best practice.

˄˅