Troubleshooting LUM

The following sections provide information about troubleshooting Novell Account Management 2.1 Update for Linux^TM (LUM):

• A User with Root Equivalent Rights Cannot Change the Passwords of Other Users
• A User Cannot to Log In
• Password Expiration Information for the User Is Not Available

A User with Root Equivalent Rights Cannot Change the Passwords of Other Users

• The root user is prompted for the user's old password while using the passwd command. This happens when a user's ID is changed to root through the su utility.

  To overcome this issue, log in as a root user through TELNET* or any other utility and use the passwd command.

• If Linux users are added through LDAP, [Public] must be given Read permission to various attributes of the created user.

A User Cannot to Log In

• A user cannot log in and is getting the following message: No such entry. The user entry is cached in two daemons, nscd and namcd. You specify an optimal cache interval. Within the cache interval, if you modify the user entries, it will not be reflected on the Linux host. For the changes to be effective immediately, you must stop and restart the nscd and namcd daemons. On Linux systems, the nscd daemon is available only with Red Hat Linux 6.0 and later.
• If the time to log in takes more than 60 seconds, the login utility times out. This is a limitation of the Linux operating systems.
• If you have created a user through ConsoleOne, and assigned a password that is longer than eight characters, the user might not be able to log in. This is because the passwd command cannot process passwords that are longer than eight characters. The password is truncated.
• The uids must be less than 65535. If you have assigned a uid greater than 65535 with ConsoleOne, the user will not be able to log in.

Password Expiration Information for the User Is Not Available

The pam_nam account management module should be stacked only after the pam_nam authentication module. If stacked directly after any other module, the behavior of pam_nam might be unpredictable. In this case, you might not be able to extract the user's password and account expiration, or other authentication details.

namcd Not Giving Desired Results

If tlte id command or the getent command is not displaying thc desired result, one of the reasons may be that the entries are cached by nscd (Name Service Caching Dacmon).

If you have changed the /etc/nsswitch.conf file or the /etc/passwd file or the /etc/group files, restart nscd using these commands.

/etc/rc.d/init.d/nscd stop

To restart nscd, use the following connnands:

/etc/rc.d/init.d/nscd start

namcd Not Coming Up after System Reboot

If LUM is configured against the eDirectory in thc same system, when thc system is rebooted for a minute, namcd tries to bind to the LDAP server while the system is coming up. If the LDAP server (eDirectory) takes more than one minute to come up, namcd tries to contact the replica servers, if any.

If replica servers do not exist or do not respond, namcd will not come up and has to be restarted manually. This is also applicable for scenarios where eDirectory and namcd are started simultaneously or within a very short time interval from each other.

The LDAP server startup status will be loeged into the ndsd.log file present in the server's var directory.

Log files Related to LUM

The log files shown in Table 3 are created, and can be referred to for more details on the functioning of the corresponding components.

Table 3.