nitTelemetry.service fails to run during the boot sequence nitconfig[xxxx]: Could not establish connection with NIT daemon

Environment

Open Enterprise Server (OES)
OES 23.4

Situation

If nitTelemetry.service fails to run during the boot sequence, looking up its status shows the following:

# systemctl status nitTelemetry.service
* nitTelemetry.service - NIT Telemetry Data service
     Loaded: loaded (/usr/lib/systemd/system/nitTelemetry.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-08-15 12:59:25 CEST; 12min ago
Triggeredby: * nitTelemetry.timer
   Main PID: 1606 (code=exited, status=210/CHROOT)

Aug 15 12:59:25 oesserver systemd[1]: Starting NIT Telemetry Data service...
Aug 15 12:59:25 oesserver nitconfig[1606]: Could not establish connection with NIT daemon
Aug 15 12:59:25 oesserver systemd[1]: nitTelemetry.service: Main process exited, code=exited, status=210/CHROOT
Aug 15 12:59:25 oesserver systemd[1]: nitTelemetry.service: Failed with result 'exit-code'.
Aug 15 12:59:25 oesserver systemd[1]: Failed to start NIT Telemetry Data service.

Cause

nitTelemetry.service depends on novell-nit.service, but is not configured to start after novell-nit.service during the boot sequence.

Read full article