Ldapproxy restart timeout error on worker node

[nrauso]

In a multi-node NS8 cluster, the ldapproxy container may fail to start on a worker node due to a start-pre operation timeout.
This issue typically occurs during module installation or container restart events.
During module installation:

May 30 15:19:49 rl3 systemd[29026]: ldapproxy.service: start-pre operation timed out. Terminating.
May 30 15:19:49 rl3 systemd[29026]: ldapproxy.service: Failed with result 'timeout'.
May 30 15:19:49 rl3 systemd[29026]: Failed to start ldapproxy4 LDAP account provider local proxy.
May 30 15:19:49 rl3 systemd[29026]: ldapproxy.service: Consumed 1.121s CPU time.
May 30 15:19:49 rl3 agent@ldapproxy4[29043]: Job for ldapproxy.service failed because a timeout was exceeded.
May 30 15:19:49 rl3 agent@ldapproxy4[29043]: See "systemctl --user status ldapproxy.service" and "journalctl --user -xeu ldapproxy.service" for details.
May 30 15:19:49 rl3 agent@ldapproxy4[29043]: task/module/ldapproxy4/566dcf77-9bcb-4d4c-94b0-e9425da05b26: action "create-module" status is "aborted" (1) at step 50start_service

During a restart event:

May 30 15:21:19 rl3 systemd[29026]: ldapproxy.service: start-pre operation timed out. Terminating.
May 30 15:21:20 rl3 systemd[29026]: ldapproxy.service: Failed with result 'timeout'.
May 30 15:21:20 rl3 systemd[29026]: Failed to start ldapproxy4 LDAP account provider local proxy.
May 30 15:21:20 rl3 systemd[29026]: ldapproxy.service: Consumed 1.197s CPU time.
May 30 15:21:20 rl3 systemd[29026]: ldapproxy.service: Scheduled restart job, restart counter is at 2.
May 30 15:21:20 rl3 systemd[29026]: Stopped ldapproxy4 LDAP account provider local proxy.
May 30 15:21:20 rl3 systemd[29026]: ldapproxy.service: Consumed 1.197s CPU time.

Logs don't provide more insight on the root cause.

Components

• core:3.8.0
• ldapproxy:1.1.0

[DavidePrincipi]

In Testing, Ldapproxy 1.1.1-dev.1

Test case

Check the bug is not reproducible with the version from Testing