namcd not starting correctly

  • 7023855
  • 03-May-2019
  • 04-May-2019

Environment

Open Enterprise Server 2018 (OES 2018) Linux

Situation

After upgrading OES 2015 SP1 server to OES 2018 SP1, namcd would start but LUM users were not being returned and the namcd process showed as a defunct process.  

Failed to start Novell Linux User Management(LUM).
namcd.service: Unit entered failed state.
namcd.service: Failed with result 'resources'.

# systemctl status namcd
● namcd.service - Novell Linux User Management(LUM)
   Loaded: loaded (/usr/lib/systemd/system/namcd.service; enabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Fri 2019-04-05 20:41:45 CEST; 44s ago
     Docs: man:namcd
           man:namconfig
  Process: 15497 ExecStart=/usr/sbin/namcd (code=killed, signal=TERM)
  Process: 15492 ExecStartPre=/usr/bin/rm -f /var/lib/novell-lum/.flush_check_file (code=exited, status=0/SUCCESS)
  Process: 15486 ExecStartPre=/usr/bin/rm -f /var/lib/novell-lum/.refresh_info (code=exited, status=0/SUCCESS)
  Process: 15480 ExecStartPre=/usr/bin/rm -f /var/lib/novell-lum/.user_info.* (code=exited, status=0/SUCCESS)
  Process: 15474 ExecStartPre=/usr/bin/rm -f /var/lib/novell-lum/.group_info.* (code=exited, status=0/SUCCESS)
  Process: 15466 ExecStartPre=/usr/bin/rm -f /var/lib/novell-lum/.namcdnotloaded (code=exited, status=0/SUCCESS)
  Process: 15461 ExecStartPre=/usr/bin/rm -f /var/lib/novell-lum/.namcdloaded (code=exited, status=0/SUCCESS)

/usr/sbin/namcd[15497]:  main: Daemonizing namcd
/usr/sbin/namcd[15497]:  daemonize: SIGTTOU caught
/usr/sbin/namcd[15497]:  daemonize: SIGTTIN caught
/usr/sbin/namcd[15497]:  daemonize: SIGTSTP caught
/usr/sbin/namcd[15497]:  daemonize: Parent Process: Forked Child with PID:15501
/usr/sbin/namcd[15501]:  daemonize: Beginning Child process
systemd[1]: namcd.service: Start operation timed out. Terminating.
systemd[1]: Failed to start Novell Linux User Management(LUM).
systemd[1]: namcd.service: Unit entered failed state.
systemd[1]: namcd.service: Failed with result 'timeout'.

And the result of 'ps -eaf|grep -i namcd' durning startup:

root     15497     1  0 20:39 ?        00:00:00 /usr/sbin/namcd
root     15501 15497  0 20:39 ?        00:00:00 [namcd] <defunct>

And we also see this in /var/log/messages after start, although not consistently:

namcd.service: PID 14973 read from file /var/run/novell-lum/namcd.pid does not exist or is a zombie.

Strace of the namcd process showed libcrypto.so.1.0.0 being found under /usr/lib/nsr - which had been install by another product.

namcd should be finding the libcrypto.so.1.0.0 under /lib64 first to load correctly.

Resolution

Work around:
To ensure namcd loads the correct libcrypto.so.1.0.0
Created a file called /etc/env

In that file place:

LD_LIBRARY_PATH=/lib64:$LD_LIBRARY_PATH

Then modify /etc/systemd/system/multi-user.target.wants/namcd.service file  and add the line under the [Service] section under Type=forking:

EnvironmentFile=-/etc/env

Then, run: systemctl daemon-reload