Troubleshooting Tips; Novell Client Tray Sometimes Displays An Error Message On Logging In To A Desktop On Which Lum Is Configured - Novell CLIENT FOR LINUX 2.0 SP3 - ADMINISTRATION Administration Manual

Hide thumbs Also See for CLIENT FOR LINUX 2.0 SP3 - ADMINISTRATION:
Table of Contents

Advertisement

Troubleshooting Tips

6
This section describes some issues you might experience with Novell Client and provides
suggestions for resolving or avoiding them.
6.1 Novell Client tray sometimes displays an
error message on logging in to a desktop on
which LUM is configured.
After the user logs in to the desktop on which Linux User Management (LUM) is configured, Novell
Client tray might sometimes display the following error message:
The novfs kernel loadable module is not installed correctly
This occurs because namcd fails to start in the machine. Novell Client requires services such as
novell-xregd and namcd when they are configured. namcd fails to start because of one or more of
the following reasons:
Cause: The remote LDAP server to which LUM is configured against is not responding.
Symptom: The following error is displayed in
ldap_initconn: LDAP bind failed (error = [81]), trying to connect to
alternative LDAP server
Solution: Ensure that the LDAP Server LUM is configured against is available and restart
namcd.
Cause: namcd is attempted to start before Network Manager is started.
Symptom: The following error messages are displayed in
network: If service network should wait until connection is established
network: then set /etc/sysconfig/network/config:NM_ONLINE_TIMEOUT
Solution: Setting an appropriate value for the variable
sysconfig/network/config
Network Manager to come up at least for the specified timeout duration. A suggested duration
is 20, which indicates a timeout of 20 seconds.
NOTE: Alternatively, namcd can be configured to start from the local cache itself. This will allow
the desktop to startup without the error even when network is not available. To do this, run the
following command:
namconfig cache-only=yes
After any of the above mentioned solutions is implemented, restart the following services:
1. Restart namcd by running the following command:
rcnamcd restart
2. Restart novell-xregd as root by running the following command:
/var/log/messages
NM_ONLINE_TIMEOUT
will ensure that all other dependent services will wait for the
:
/var/log/messages:
in the file
Troubleshooting Tips
6
/etc/
45

Advertisement

Table of Contents
loading

Table of Contents