Systemd Returns 217/USER Error on System Boot when Using Directory Based Users

Chris H.
Chris H.
Altair Employee
edited February 2023 in Altair HPCWorks

Summary:

When using the systemd unit examples in $SWD/etc/boot and service accounts that run Altair products are not local accounts in /etc/passwd (LDAP, NIS, AD, etc.), applications may not start on boot. The same systemd unit file will run successfully after the system is booted. This problem could affect more than just the Monitor product.

 

Symptoms:

Errors can be found when running jounalctl and also systemctl [service unit name]. You will see errors like:

    • journalctl: Failed at step USER spawning /opt/licenseMonitor/2021.1.1/common/scripts/vovboot: No such process
    • systemctl altair-monitor.service: (code=exited, status=217/USER)

 

Solution:

Modify the systemd unit file to require nss (name service switch) to be available before attempting to run Monitor or other applications.

Change After=network.target to After=nss-user-lookup.target in the systemd unit file (i.e. altair-monitor.service)

Reboot to ensure all services run as expected.

If you continue to have issues please contact support.

 

Tagged:

Categories