See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for information on diagnosing and solving these type of problem.
Unknown error
This is displayed when the NIS+ error handling routine receives an error of an unknown type.
Unknown object
The object returned is of an unknown type.
This message is generated by the NIS+ error code constant: NIS_UNKNOWNOBJ. See the nis_names man page for additional information.
update_directory: nnnn objects still running.
This is a status message displayed on the server during the update of a directory during a replica update. You do not need to take any action.
User principalname needs Secure RPC credentials to login but has none.
The user has failed to perform a keylogin. This problem usually arises when the user has different passwords in /etc/shadow and a remote NIS+ passwd table.
Warning: couldn't reencrypt secret key for principalname
The most likely cause of this problem is that your Secure RPC password is different from your login password (or you have one password on file in a local /etc/shadow file and a different one in a remote NIS+ table) and you have not yet done an explicit keylogin. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for more information on these types of problems.
WARNING: db::checkpoint: could not dump database: No such file or directory
This message indicates that the system was unable to open a database file during a checkpoint. Possible causes:
The database file was deleted.
The server is out of file descriptors.
There is a disk problem
You or the host do not have correct permissions.
WARNING: db_dictionary::add_table: could not initialize database from scheme
The database table could not be initialized. Possible causes:
There was a system resource problem See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)).
You incorrectly specified the new table in the command syntax.
The database is corrupted.
WARNING: db_query::db_query:bad index
In most cases this message indicates incorrect specification of an indexed name. Make sure that the indexed name is found in the specified table. Check the command for spelling and syntax errors.
**WARNING: domain domainname already exists.
This message indicates that the domain you tried to create already exists.
If you are trying to promote a new nonroot master server or are recovering from a previous nisserver problem, continue running the script.
If domainname was spelled incorrectly, rerun the script with the correct domain name.
**WARNING: failed to add new member NIS+_principle into the groupname group. You will need to add this member manually: 1. /usr/sbin/nisgrpadm -a groupname NIS+_principal
The NIS+ command nisgrpadm failed to add a new member into the NIS+ group groupname. Manually add this NIS+ principal by typing:
**WARNING: failed to populate tablename table.
The nisaddent command was unable to load the NIS+ tablename table. A more detailed error message usually appears before this warning message.
**WARNING: hostname specified will not be used. It will use the local hostname instead.
This message indicates that you typed a remote host name with the -H option. The nisserver -rscript does not configure remote machines as root master servers.
If the local machine is the one that you want to convert to an NIS+ root master server, no other action is needed. The nisserver -rscript will ignore the host name you typed.
If you actually want to convert the remote host (instead of the local machine) to an NIS+ root master server, exit the script. Rerun the nisserver -rscript on the remote host.
**WARNING: hostname is already a server for this domain. If you choose to continue with the script, it will try to replicate the groups_dir and org_dir directories for this domain.
This is a message warning you that hostname is already a replica server for the domain that you are trying to replicate.
If you are running the script to fix an earlier nisserver problem, continue running the script.
If hostname was mistakenly entered, rerun the script with the correct host name.
**WARNING: alias-hostname is an alias name for host canonical_hostname. You cannot create credential for host alias.
This message indicates that you have typed a host alias in the name list for nisclient -c. The script asks you if you want to create the credential for the canonical host name, since you should not create credentials for host alias names.
**WARNING: file directory-path/tablename does not exist! tablename table will not be loaded.
The script was unable to find the input file for tablename.
If directory-path/tablename is spelled incorrectly, rerun the script with the correct table name.
If the directory-path/tablename file does not exist, create and update this file with the proper data. Then rerun the script to populate this table.
**WARNING: NIS auto.master map conversion failed. auto.master table will not be loaded.
The auto.master map conversion failed while trying to convert all the dots to underscores in the auto_master table. Rerun the script with a different NIS server.
**WARNING: NIS netgroup map conversion failed. netgroup table will not be loaded.
The netgroup map conversion failed while trying to convert the NIS domain name to the NIS+ domain name in the netgroup map. Rerun the script with a different NIS server.
**WARNING: nisupdkeys failed on directory domainname. This script will not be able to continue. Please remove the domainname directory using `nisrmdir'.
The NIS+ command nisupdkeys failed to update the keys in the listed directory object. If rpc.nisd is not running on the new master server that is supposed to serve this new domain, restart rpc.nisd. Then use nisrmdir to remove the domainname directory. Finally, rerun nisserver.
WARNING: nisupdkeys failed on directory directory-name You will need to run nisupdkeys manually: 1. /usr/lib/nis/nisupdkeys directory-name
The NIS+ command nisupdkeys failed to update the keys in the listed directory object. Manually update the keys in the directory object by typing:
**WARNING: once this script is executed, you will not be able to restore the existing NIS+ server environment. However, you can restore your NIS+ client environment using "nisclient -r" with the proper domainname and server information. Use "nisclient -r" to restore your NIS+ client environment.
These messages appear if you have already run the script at least once before to set up an NIS+ server and indicate that NIS+-related files will be removed and recreated as needed if you decide to continue running this script.
If it is all right for these NIS+ files to be removed, continue running the script.
If you want to save these NIS+ files, exit the script by typing "n" at the Do you want to continue? prompt. Then save the NIS+ files in a different directory and rerun the script.
**WARNING: this script removes directories and files related to NIS+ under /var/nis directory with the exception of the NIS_COLD_START and NIS_SHARED_DIRCACHE files which will be renamed to <file>.no_nisplus. If you want to save these files, you should abort from this script now to save these files first.
See "WARNING: once this script is executed,..." above.
**WARNING: you must specify the NIS domainname.
This message indicates that you did not type the NIS domain name at the prompt. Type the NIS server domain name at the prompt.
**WARNING: you must specify the NIS server hostname. Please try again.
This message indicates that you did not type the NIS server host name at the prompt. Type the NIS server host name at the prompt.
Window verifier mismatch
This is a debugging message generated by the _svcauth_des code. A verifier could be invalid because a key was flushed out of the cache. When this occurs, _svcauth_des returns the AUTH_BADCRED status.
You (string) do not have Secure RPC credentials in NIS+ domain 'string'
This message could be caused by trying to run nispasswd on a server that does not have the credentials required by the command. (Keep in mind that servers running at security level 0 do not create or maintain credentials.)See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)for additional information on credential, ownership, and permission problems.
You may not change this password
This message indicates that your administrator has forbidden you to change your password.
You may not use nisplus repository
You used -r nisplus in the command line of your command, but the appropriate entry in the NIS+ passwd table was not found. Check the passwd table in question to make sure it has the entry you want. Try adding nisplus to the nsswitch.conf file.
Your password has been expired for too long
Your password is expired
These messages refer to password aging and indicate that your password has been in use too long and needs to be changed now. See "The will expire Message"for further information.
Your password will expire in nn days
Your password will expire within 24 hours
These messages refer to password aging and indicate that your password is about to become invalid and should be changed now. See "The will expire Message" for further information.
Your specified repository is not defined in the nsswitch file!
This warning indicates that you have specified a password information repository with the -r option, but that password repository is not included in the passwd entry of the nsswitch.conf file. The command you have just used will perform its job and make whatever change you intend to the password information repository you specified with the -r flag. However, the change will be made to information that the nsswitch.conf file does not point to, so no one will ever gain the benefit of it until the switch file is altered to point to that repository.For example, suppose the passwd entry of the switch file reads: files nis, and you used
to establish a password age limit. That limit would be ignored, as the switch file remains set to files nis.
verify_table_exists: cannot create table for string nis_perror message.
To perform an operation on a table, NIS+ first verifies that the table exists. If the table does not exist, NIS+ attempts to create it. If it cannot create the table, it returns this error message. The string portion of the message identifies the table that could not be located or created; the nis_perror message portion provides information as to the cause of the problem (you can look up that portion of the message as if it were an independent message in this appendix). Possible causes for this type of problem:
The server was just added as a replica of the directory and it might not have the directory object. Run nisping -C to checkpoint.
You are out of disk space. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Database corruption.
Some other type of software error. Contact the Sun Solutions Center.
ypcat: can't bind to NIS server for domain domainname. Reason: can't communicate with ypbind.
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)
yppoll: can't get any map parameter.
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)