User Cannot Remote Log In to Remote Domain

Symptoms:

User tries to rlogin to a machine in some other domain and is refused with a "Permission denied" type error message.

Possible Cause:

To rlogin to a machine in another domain, a user must have LOCAL credentials in that domain.

Diagnosis:

Run nismatch username.domainname. cred.org_dir in the other domain to see if the user has a LOCAL credential in that domain.

Solution:

Go to the remote domain and use nisaddcred to create a LOCAL credential for the user in the that domain.

User Cannot Change Password

The most common cause of a user being unable to change passwords is that the user is mistyping (or has forgotten) the old password.

Other possible causes:

• The password Min value has been set to be greater than the password Max value. See "Setting Minimum Password Life".

• The password is locked or expired. See "Login Incorrect Message" and "Password Locked, Expired, or Terminated".

Other NIS+ Problems

This section describes problems that do not fit any of the previous categories.

How to Tell if NIS+ Is Running

You may need to know whether a given host is running NIS+. A script may also need to determine whether NIS+ is running.

You can assume that NIS+ is running if:

• nis_cachemgr is running.

• The host has a /var/nis/NIS_COLD_START file.

• nisls succeeds.

Replica Update Failure

Symptoms:

Error messages indicating that the update was not successfully complete. (Note that the message: replica_update: number updates number errors indicates a successful update.)

Possible Causes:

Any of the following error messages indicate that the server was busy and that the update should be rescheduled:

• Master server busy, full dump rescheduled

• replica_update error result was Master server busy full dump rescheduled, full dump rescheduled

• replica_update: master server busy, rescheduling the resync

• replica_update: master server busy, will try later

• replica_update: nis dump result Master server busy, full dump rescheduled

• nis_dump_svc: one replica is already resyncing

(These messages are generated by, or in conjunction with, the NIS+ error code constant: NIS_DUMPLATER one replica is already resyncing.)

These messages indicate that there was some other problem:

• replica_update: error result was ...

• replica_update: nis dump result nis_perror error string

• rootreplica_update: update failednis dump result nis_perror string-variable: could not fetch object from master

(If rpc.nisd is being run with the -C (open diagnostic channel) option, additional information may be entered in either the master server or replica server's system log.

These messages indicate possible problems such as:

• The server is out of child processes that can be allocated.

• A read-only child process was requested to dump.

• Another replica is currently resynching.

Diagnosis:

Check both the replica and server's system log for additional information. How much, if any, additional information is recorded in the system logs depends on your system's error reporting level, and whether or not you are running rpc.nisd with the -C option (diagnostics).

Solution:

In most cases, these messages indicate minor software problems which the system is capable of correcting. If the message was the result of a command, simply wait for a while and then try the command again. If these messages appear often, you can change the threshold level in your /etc/syslog.conf file. See the syslog.conf man page for details.