After exiting the script, rerun it with just one of the options.
**ERROR: you must specify a fully qualified groupname.
This message indicates that you did not specify a fully qualified group name ending with a period. Rerun the script with a fully qualified group name.
**ERROR: you must specify both the NIS domainname (-y) and the NIS server host name (-h).
This message indicates that you did not type either the NIS domain name and/or the NIS server host name. Type the NIS domain name and the NIS server host name at the prompt or on the command line.
**ERROR: you must specify one of these options: -c, -i, -u, -r.
This message indicates that one of these options, -c, -i, -u, -r was missing from the command line. Rerun the script with the correct option.
**ERROR: you must specify one of these options: -r, -M or -R"
This message indicates that you did not type any of the -r or the -M or the -R options. Rerun the script with the correct option.
**ERROR: you must specify one of these options: -C, -F, or -Y
This message indicates that you did not type either the -Y or the -F option. Rerun the script with the correct option.
**ERROR: You must be root to use -i option.
This message indicates that an ordinary user tried to run nisclient -i. Only the superuser has permission to run nisclient -i.
Error while talking to callback proc
An RPC error occurred on the server while it was calling back to the client. The transaction was aborted at that time and any unsent data was discarded. Check the syslog on the server for more information.
This message is generated by the NIS+ error code constant: NIS_CBERROR. See the nis_tables man page for additional information.
First/Next chain broken
This message indicates that the connection between the client and server broke while a callback routine was posting results. This could happen if the server died in the middle of the process.
This message is generated by the NIS+ error code constant: NIS_CHAINBROKEN.
Generic system error
Some form of generic system error occurred while attempting the request. Check the syslog record on your system for error messages from the server.
This message usually indicates that the server has crashed or the database has become corrupted. This message might also be generated if you incorrectly specify the name of a server or replica as if it belonged to the domain it was servicing rather than the domain above. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information.
This message is generated by the NIS+ error code constant: NIS_SYSTEMERROR. See the nis_tables and nis_names man pages for additional information.
Illegal object type for operation
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for a description of these type of problems.
This message is generated by the NIS+ error code constant: DB_BADOBJECT.
insufficient permission to update credentials.
This message is generated by the nisaddcred command when you have insufficient permission to execute an operation. This could be insufficient permission at the table, column, or entry level. Use niscat -o cred.org_dir to determine what permissions you have for that cred table. If you need additional permission, you or the system administrator can change the permission requirements of the object or add you to a group that does have the required permissions.
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information about permission problems.
Invalid Object for operation
Name context. The name passed to the function is not a legal NIS+ name.
Table context. The object pointed to is not a valid NIS+ entry object for the given table. This could occur if it had a mismatched number of columns, or a different data type (for example, binary or text) than the associated column in the table.
This message is generated by the NIS+ error code constant: NIS_INVALIDOBJ. See the nis_tables and nis_names man pages for additional information.
invalid usecs Routine_name: invalid usecs
This message is generated when the value in the tv_usecs field of a variable of type struct time stamp is larger than the number of microseconds in a second. This is usually due to some type of software error.
tablename is not a table
The object with the name tablename is not a table object. For example, the nisgrep and nismatch commands will return this error if the object you specify on the command line is not a table.
Link Points to illegal name
The passed name resolved to a LINK type object and the contents of the object pointed to an invalid name.
You cannot link table entries. A link at the entry level can produce this error message.
This message is generated by the NIS+ error code constant: NIS_LINKNAMEERROR. See the nis_tables and nis_names man pages for additional information.
Load limit of number reached!
An attempt has been made to create a child process when the maximum number of child processes have already been created on this server. This message is seen on the server's system log, but only if the threshold for logging messages has been set to include LOG_WARNING level messages.
login and keylogin passwords differ.
This message is displayed when you are changing your password with nispasswd and the system has changed your password, but has been unable to update your credential entry in the cred table with the new password and also unable to restore your original password in the passwd table. This message is followed by the instructions:
These instructions are then followed by a status message explaining why it was not possible to revert back to the old password. If you see these messages, be sure to follow the instructions as given.
Login incorrect
The most common cause of a "login incorrect" message is mistyping the password. Try it again. Make sure you know the correct password. Remember that passwords are case-sensitive (uppercase letters are considered different than lowercase letters) and that the letter "o" is not interchangeable with the numeral "0," nor is the letter "l" the same as the numeral "1".
For other possible causes of this message, see "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
log_resync: Cannot truncate transaction log file
An attempt has been made to checkpoint the log, and the rpc.nisd daemon is trying to shrink the log file after deleting the checkpointed entries from the log. See the ftruncate man pages for a description of various factors that might cause this routine to fail. See also "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Malformed Name or illegal name
The name passed to the function is not a legal or valid NIS+ name.
One possible cause for this message is that someone changed an existing domain name. Existing domain names should not be changed. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
This message is generated by the NIS+ error code constant: NIS_BADNAME. See the nis_tables man page for additional information.
_map_addr: RPC timed out.
A process or application could not contact NIS+ within its default time limit to get necessary data or resolve host names from NIS+. In most cases, this problem will solve itself after a short wait. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)for additional information about slow performance problems.
Master server busy full dump rescheduled
This message indicates that a replica server has been unable to update itself with a full dump from the master server because the master is busy. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information.
String Missing or malformed attribute
The name of an attribute did not match with a named column in the table, or the attribute did not have an associated value.
This could indicate an error in the syntax of a command. The string should give an indication of what is wrong. Common causes are spelling errors, failure to correctly place the equals sign (=), an incorrect column or table name, and so forth.
This message is generated by the NIS+ error code constant: NIS_BADATTRIBUTE. See the nis_tables man page for additional information.
Modification failed
Returned by the nisgrpadm command when someone else modified the group during the execution of your command. Check to see who else is working with this group. Reissue the command.
This message is generated by the NIS+ error code constant: NIS_IBMODERROR.
Modify operation failed
The attempted modification failed for some reason.
This message is generated by the NIS+ error code constant: NIS_MODFAIL. See the nis_tables and nis_names man pages for additional information.
Name not served by this server
A request was made to a server that does not serve the specified name. Normally this will not occur; however, if you are not using the built-in location mechanism for servers, you might see this if your mechanism is broken.Other possible causes are:
Cold-start file corruption. Delete the /var/nis/NIS_COLD_START file and then reboot.
Cache problem such as the local cache being out of date. Kill the nis_cachemgr and /var/nis/NIS_SHARED_DIRCACHE, and then reboot. (If the problem is not in the root directory, you might be able to kill the domain cache manager and try the command again.)
Someone removed the directory from a replica.
This message is generated by the NIS+ error code constant: NIS_NOT_ME. See the nis_tables and nis_names man pages for additional information.
Named object is not searchable
The table name resolved to an NIS+ object that was not searchable.
This message is generated by the NIS+ error code constant: NIS_NOTSEARCHABLE. See the nis_tables man page for additional information.
Name/entry isn't unique
An operation has been requested based on a specific search criteria that returns more than one entry. For example, you use nistbladm -rto delete a user from the passwd table, and there are two entries in that table for that user name as shown as follows:
You can apply your command to multiple entries by using the -R option rather than -r. For example, to remove all entries for arnold:
NIS+ error
The NIS+ server has returned an error, but the passwd command determines exactly what the error is.
NIS+ operation failed
This generic error message should be rarely seen. Usually it indicates a minor software problem that the system can correct on it own. If it appears frequently, or appears to be indicating a problem that the system is not successfully dealing with, contact the Sun Solutions Center.
This message is generated by the NIS+ error code constant: NIS_FAIL.
string: NIS+ server busy try again later.
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for possible causes.
NIS+ server busy try again later.
Self explanatory. Try the command later.
See also "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for possible causes.
NIS+ server for string not responding still trying
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for possible causes.
NIS+ server not responding
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for possible causes.
NIS+ server needs to be checkpointed. Use nisping -Cdomainname
Caution - Checkpoint immediately! Do not wait!
This message is generated at the LOG_CRIT level on the server's system log. It indicates that the log is becoming too large. Use nisping -C domainname to truncate the log by checkpointing.
See also "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information on log size.
NIS+ servers unreachable
This soft error indicates that a server for the desired directory of the named table object could not be reached. This can occur when there is a network failure or the server has crashed. A new attempt might succeed. See the description of the -HARD_LOOKUP flag in the nis_tables and nis_names man pages.
This message is generated by the NIS+ error code constant: NIS_NaMEUNREACHABLE.
NIS+ service is unavailable or not installed
Self-explanatory. This message is generated by the NIS+ error code constant: NIS_UNAVAIL.
NIS+: write ColdStart File: xdr_directory_obj failed
The most likely causes for this message are:
Bad or incorrect parameters. Check the syntax and accuracy of whatever command you most recently entered.
An attempt to allocate system memory failed. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for a discussion of memory problems.
If your command syntax is correct, and your system does not seem to be short of memory, contact the Sun Solutions Center.
nis_checkpoint_svc: readonly child instructed to checkpoint ignored.
This is a status message indicating that a read-only process attempted to perform an operation restricted to the parent process, and the attempt was aborted. No action need be taken.
nis_dumplog_svc: readonly child called to dump log, ignore
This is a status message indicating that a read-only process attempted to perform an operation restricted to the parent process, and the attempt was aborted. No action need be taken.
nis_dump_svc: load limit reached.
The maximum number of child processes permitted on your system has been reached.
nis_dump_svc: one replica is already resyncing.
Only one replica can resync from a master at a time. Try the command later.
See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for information on these three error messages.
nis_dump_svc: Unable to fork a process.
The fork system call has failed. See the fork man page for possible causes.
nis_mkdir_svc: read-only child called to mkdir, ignored
This is a status message indicating that a read-only process attempted to perform an operation restricted to the parent process, and the attempt was aborted. No action need be taken.
nis_ping_svc: read-only child was ping ignored.
This is a status message indicating that a read-only process attempted to perform an operation restricted to the parent process, and the attempt was aborted. No action need be taken.
nis_rmdir_svc: readonly child called to rmdir, ignored
This is a status message indicating that a read-only process attempted to perform an operation restricted to the parent process, and the attempt was aborted. No action need be taken.
nisaddcred: no password entry for uid userid nisaddcred: unable to create credential.
These two messages are generated during execution of the nispopulate script. The NIS+ command nisaddcred failed to add a LOCAL credential for the user ID userid on a remote domain. (This only happens when you are trying to populate the passwd table in a remote domain.)To correct the problem, add a table path in the local passwd table:
The remote-domain must be the same domain that you specified with the -d option when you ran nispopulate. Rerun the script to populate the passwd table.
No file space on server
Self-explanatory.
This message is generated by the NIS+ error code constant: NIS_NOFILESPACE.
No match
This is most likely an error message from the shell, caused by failure to escape the brackets when specifying an indexed name. For example, failing to set off a bracketed indexed name with quote marks would generate this message because the shell would fail to interpret the brackets as shown as follows: