Address errors while Gatekeeper is terminating

[AltraMayor]

When Gatekeeper gracefully shuts down, it typically produces error messages such as the following example:

LLS/0 2024-06-26 13:22:16 NOTICE The LLS block is exiting
GGU/2 2024-06-26 13:22:16 NOTICE The GT-GK unit is exiting
GK/4 2024-06-26 13:22:16 NOTICE The GK block is exiting
CPS/1 2024-06-26 13:22:16 NOTICE The CPS block is exiting
GK/6 2024-06-26 13:22:16 NOTICE The GK block is exiting
SOL/8 2024-06-26 13:22:16 NOTICE The Solicitor block is exiting
GK/5 2024-06-26 13:22:16 NOTICE The GK block is exiting
EAL: Unable to open directory /var/run/dpdk/rte
EAL: rte_mp_request_sync failed
EAL: Failed to send device detach request to secondary
SOL/9 2024-06-26 13:22:16 NOTICE The Solicitor block is exiting
EAL: Unable to open directory /var/run/dpdk/rte
EAL: rte_mp_request_sync failed
EAL: Failed to rollback device detach on secondary.Devices in secondary may not sync with primary
CPS/1 2024-06-26 13:22:16 ERR kni_free(virtio_user0): failed to remove virtio_user port (errno=42): No message of desired type
GK/7 2024-06-26 13:22:16 NOTICE The GK block is exiting
EAL: Unable to open directory /var/run/dpdk/rte
EAL: rte_mp_request_sync failed
EAL: Failed to send device detach request to secondary
EAL: Unable to open directory /var/run/dpdk/rte
EAL: rte_mp_request_sync failed
EAL: Failed to rollback device detach on secondary.Devices in secondary may not sync with primary
CPS/1 2024-06-26 13:22:16 ERR kni_free(virtio_user3): failed to remove virtio_user port (errno=42): No message of desired type
DYC/3 2024-06-26 13:22:16 NOTICE The Dynamic Config block is exiting

These errors have no adverse side effects, but it would be nice to investigate and address their causes.