System Administration Guide: Naming and Directory Services (FNS and NIS+)

Try re-executing the command.

CacheBind: xdr_directory_obj failed.

The most likely causes for this message are:
Bad or incorrect parameters being passed to the xdr_directory_obj routine. 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.

Cache expired

The entry returned came from an object cache that has expired. This means that the time-to-live value has gone to zero and the entry might have changed. If the flag -NO_CACHE was passed to the lookup function, then the lookup function will retry the operation to get an unexpired copy of the object.

This message is generated by the NIS+ error code constant: NIS_CACHEEXPIRED. See the nis_tables and nis_names man pages for additional information.

Callback: - select failed message nnnn

An internal system call failed. In most cases this problem will correct itself. If it does not correct itself, make sure that rpc.nisd has not been aborted. If it has, restart it. If the problem reoccurs frequently, contact the Sun Solutions Center.

CALLBACK_SVC: bad argument

An internal system call failed. In most cases this problem will correct itself. If it does not correct itself, make sure that rpc.nisd has not been aborted. If it has, restart it. If the problem reoccurs frequently, contact the Sun Solutions Center.

Cannot grow transaction log error string

The system cannot add to the log file. The reason is indicated by the string. The most common cause of this message is lack of disk space. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

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).

Cannot write one character to transaction log, errormessage

An attempt has been made by the rpc.nisd daemon to add an update from the current transaction into the transaction log, and the attempt has failed for the reason given in the message that has been returned by the function. Additional information can be obtained from the write routine's man page.

Can't compile regular expression variable

Returned by the nisgrep command when the expression in keypat was malformed.

Can't get any map parameter information.

See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

Can't find name service for passwd

Either there is no nsswitch.conf file or there is no passwd entry in the file, or the passwd entry does not make sense or is not one of the allowed formats.

Can't find name 's secret key

Possible causes:
You might have incorrectly typed the password.

There might not be an entry for name in the cred table.

NIS+ could not decrypt the key (possibly because the entry might be corrupt).

The nsswitch.conf file might be directing the query to a local password in an /etc/passwd file that is different than the NIS+ password recorded in the cred table.

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.

checkpoint_log: Called from read only child 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.

checkpoint_log: Unable to checkpoint, log unstable.

An attempt was made to checkpoint a log that was not in a stable state. (That is, the log was in a resync, update, or checkpoint state.) Wait until the log is stable, and then rerun the nisping command.

check_updaters: Starting resync.

This is a system status message. No action need be taken.

Child process requested to checkpoint!

This message indicates a minor software problem that the system is capable of correcting. 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.

Column not found: columnname

The specified column does not exist in the specified table.

Could not find string 's secret key

Possible causes:
You might have incorrectly typed the password.

There might not be an entry for name in the cred table.

NIS+ could not decrypt the key (possibly because the entry might be corrupt)

The nsswitch.conf file might have the wrong publickey policy. It might be directing the query to a local public key in an /etc/publickey file that is different from the NIS+ password recorded in the cred table.

See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for information on diagnosing and solving these types of problem.

Could not generate netname

The Secure RPC software could not generate the Secure RPC netname for your UID when performing a keylogin. This could be due to the following causes:
You do not have LOCAL credentials in the NIS+ cred table of the machine's home domain.

You have a local entry in /etc/passwd with a UID that is different from the UID you have in the NIS+ passwd table.

string: could not get secret key for 'string

Possible causes:
You might have incorrectly typed the password.

There might not be an entry for name in the cred table.

NIS+ could not decrypt the key (possibly because the entry might be corrupt)

The nsswitch.conf file might have the wrong publickey policy. It might be directing the query to a local publickey in an /etc/publickey file that is different from the NIS+ password recorded in the cred table.

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.

Couldn't fork a process!

The server could not fork a child process to satisfy a callback request. This is probably caused by your system reaching its maximum number of processes. You can kill some unneeded processes, or increase the number of processes your system can handle. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information.

Couldn't parse access rights for column string

This message is usually returned by the nistbladm -u command when something other than a + (plus sign), a - (minus sign), or an = (equal sign) is entered as the operator. Other possible causes are failure to separate different column rights with a comma, or the entry of something other than r,d,c, or m for the type of permission. Check the syntax for this type of entry error. If everything is entered correctly and you still get this error, the table might have been corrupted.

Database for table does not exist

At attempt to look up a table has failed. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)for possible causes.

This message is generated by the NIS+ error code constant: NIS_NOSUCHTABLE. See the nis_tables and nis_names man pages for additional information.

_db_add: child process attempting to add/modify _db_addib: non-parent process attempting an add

These messages indicate that a read-only or nonparent process attempted to add or modify an object in the database. In most cases, these messages do not require any action on your part. If these messages are repeated frequently, call the Sun Solutions Center.

db_checkpoint: Unable to checkpoint string

This message indicates that for some reason NIS+ was unable to complete checkpointing of a directory. The most likely cause is that the disk is full See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information).

_db_remib: non-parent process attempting an remove _db_remove: non-parent process attempting a remove

These messages indicate that a read-only or non-parent process attempted to remove a table entry. In most cases, these messages do not require any action on your part. If these messages are repeated frequently, call the Sun Solutions Center.

Do you want to see more information on this command?

This indicates that there is a syntax or spelling error on your script command line.

Entry/Table type mismatch

This occurs when an attempt is made to add or modify an entry in a table, and the entry passed is of a different type from the table. For example, if the number of columns is not the same. Check that your update correctly matches the table type.

This message is generated by the NIS+ error code constant: NIS_TYPEMISMATCH. See the nis_tables man page for additional information.

**ERROR: chkey failed again. Please contact your network administrator to verify your network password.

This message indicates that you typed the wrong network password.
If this is the first time you are initializing this machine, contact your network administrator to verify the network password.

If this machine has been initialized before as an NIS+ client of the same domain, try typing the root login password at the Secure RPC password prompt.

If this machine is currently an NIS+ client and you are trying to change it to a client of a different domain, remove the /etc/.rootkey file, and rerun the nisclient script, using the network password given to you by your network administrator (or the network password generated by the nispopulate script).

Error: Could not create a valid NIS+ coldstart file

This message is from nisinit, the NIS+ initialization routine. It is followed by another message preceded by a string that begins: "lookup:..". This second message will explain why a valid NIS+ cold-start file could not be created.

**ERROR: could not restore file filename

This message indicates that NIS+ was unable to rename filename.no_nisplus to filename.

Check your system console for system error messages.
If there is a system error message, fix the problem described in the error message and rerun nisclient -i.

If there aren't any system error messages, try renaming this file manually, and then rerun nisclient -i.

**ERROR: Couldn't get the server NIS+_server's address.

The script was unable to retrieve the server's IP address for the specified domain. Manually add the IP address for NIS+_server into the /etc/hosts or /etc/inet/ipnodes file, then rerun nisclient -i.

**ERROR: directory directory-path does not exist.

This message indicates that you typed an incorrect directory path. Type the correct directory path.

**ERROR: domainname does not exist.

This message indicates that you are trying to replicate a domain that does not exist.
If domainname is spelled incorrectly, rerun the script with the correct domain name.

If the domainname domain does not exist, create it. Then you can replicate it.

**ERROR: parent-domain does not exist.


	Try re-executing the command. `CacheBind: xdr_directory_obj failed.` The most likely causes for this message are: Bad or incorrect parameters being passed to the xdr_directory_obj routine. 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. `Cache expired` The entry returned came from an object cache that has expired. This means that the time-to-live value has gone to zero and the entry might have changed. If the flag `-NO_CACHE` was passed to the lookup function, then the lookup function will retry the operation to get an unexpired copy of the object. This message is generated by the NIS+ error code constant: `NIS_CACHEEXPIRED`. See the `nis_tables` and `nis_names` man pages for additional information. `Callback: - select failed message nnnn` An internal system call failed. In most cases this problem will correct itself. If it does not correct itself, make sure that `rpc.nisd` has not been aborted. If it has, restart it. If the problem reoccurs frequently, contact the Sun Solutions Center. `CALLBACK_SVC: bad argument` An internal system call failed. In most cases this problem will correct itself. If it does not correct itself, make sure that `rpc.nisd` has not been aborted. If it has, restart it. If the problem reoccurs frequently, contact the Sun Solutions Center. `Cannot grow transaction log error string` The system cannot add to the log file. The reason is indicated by the string. The most common cause of this message is lack of disk space. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP). `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). `Cannot write one character to transaction log, errormessage` An attempt has been made by the `rpc.nisd` daemon to add an update from the current transaction into the transaction log, and the attempt has failed for the reason given in the message that has been returned by the function. Additional information can be obtained from the `write` routine's man page. `Can't compile regular expression variable` Returned by the `nisgrep` command when the expression in `keypat` was malformed. `Can't get any map parameter information.` See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP). `Can't find name service for passwd` Either there is no `nsswitch.conf` file or there is no `passwd` entry in the file, or the `passwd` entry does not make sense or is not one of the allowed formats. `Can't find name 's secret key` Possible causes: You might have incorrectly typed the password. There might not be an entry for name in the `cred` table. NIS+ could not decrypt the key (possibly because the entry might be corrupt). The `nsswitch.conf` file might be directing the query to a local password in an `/etc/passwd` file that is different than the NIS+ password recorded in the cred table. 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. `checkpoint_log: Called from read only child 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. `checkpoint_log: Unable to checkpoint, log unstable.` An attempt was made to checkpoint a log that was not in a stable state. (That is, the log was in a resync, update, or checkpoint state.) Wait until the log is stable, and then rerun the `nisping` command. `check_updaters: Starting resync.` This is a system status message. No action need be taken. `Child process requested to checkpoint!` This message indicates a minor software problem that the system is capable of correcting. 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. `Column not found: columnname` The specified column does not exist in the specified table. `Could not find string 's secret key` Possible causes: You might have incorrectly typed the password. There might not be an entry for `name` in the `cred` table. NIS+ could not decrypt the key (possibly because the entry might be corrupt) The `nsswitch.conf` file might have the wrong publickey policy. It might be directing the query to a local public key in an `/etc/publickey` file that is different from the NIS+ password recorded in the cred table. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for information on diagnosing and solving these types of problem. `Could not generate netname` The Secure RPC software could not generate the Secure RPC netname for your UID when performing a `keylogin`. This could be due to the following causes: You do not have LOCAL credentials in the NIS+ cred table of the machine's home domain. You have a local entry in `/etc/passwd` with a UID that is different from the UID you have in the NIS+ passwd table. `string: could not get secret key for 'string` Possible causes: You might have incorrectly typed the password. There might not be an entry for `name` in the cred table. NIS+ could not decrypt the key (possibly because the entry might be corrupt) The `nsswitch.conf` file might have the wrong publickey policy. It might be directing the query to a local publickey in an `/etc/publickey` file that is different from the NIS+ password recorded in the cred table. 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. `Couldn't fork a process!` The server could not fork a child process to satisfy a callback request. This is probably caused by your system reaching its maximum number of processes. You can kill some unneeded processes, or increase the number of processes your system can handle. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information. `Couldn't parse access rights for column string` This message is usually returned by the `nistbladm` `-u` command when something other than a `+` (plus sign), a `-` (minus sign), or an `=` (equal sign) is entered as the operator. Other possible causes are failure to separate different column rights with a comma, or the entry of something other than `r,d,c`, or `m` for the type of permission. Check the syntax for this type of entry error. If everything is entered correctly and you still get this error, the table might have been corrupted. `Database for table does not exist` At attempt to look up a table has failed. See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)for possible causes. This message is generated by the NIS+ error code constant: `NIS_NOSUCHTABLE`. See the `nis_tables` and `nis_names` man pages for additional information. `_db_add: child process attempting to add/modify _db_addib: non-parent process attempting an add` These messages indicate that a read-only or nonparent process attempted to add or modify an object in the database. In most cases, these messages do not require any action on your part. If these messages are repeated frequently, call the Sun Solutions Center. `db_checkpoint: Unable to checkpoint string` This message indicates that for some reason NIS+ was unable to complete checkpointing of a directory. The most likely cause is that the disk is full See "NIS Troubleshooting" in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for additional information). `_db_remib: non-parent process attempting an remove _db_remove: non-parent process attempting a remove` These messages indicate that a read-only or non-parent process attempted to remove a table entry. In most cases, these messages do not require any action on your part. If these messages are repeated frequently, call the Sun Solutions Center. `Do you want to see more information on this command?` This indicates that there is a syntax or spelling error on your script command line. `Entry/Table type mismatch` This occurs when an attempt is made to add or modify an entry in a table, and the entry passed is of a different type from the table. For example, if the number of columns is not the same. Check that your update correctly matches the table type. This message is generated by the NIS+ error code constant: `NIS_TYPEMISMATCH`. See the `nis_tables` man page for additional information. `ERROR: chkey failed again. Please contact your network administrator to verify your network password.` This message indicates that you typed the wrong network password. If this is the first time you are initializing this machine, contact your network administrator to verify the network password. If this machine has been initialized before as an NIS+ client of the same domain, try typing the root login password at the Secure RPC password prompt. If this machine is currently an NIS+ client and you are trying to change it to a client of a different domain, remove the `/etc/.rootkey` file, and rerun the `nisclient` script, using the network password given to you by your network administrator (or the network password generated by the `nispopulate` script). `Error: Could not create a valid NIS+ coldstart file` This message is from `nisinit`, the NIS+ initialization routine. It is followed by another message preceded by a string that begins: "`lookup:.."`. This second message will explain why a valid NIS+ cold-start file could not be created. `ERROR: could not restore file filename` This message indicates that NIS+ was unable to rename filename`.no_nisplus` to filename. Check your system console for system error messages. If there is a system error message, fix the problem described in the error message and rerun `nisclient` `-i`. If there aren't any system error messages, try renaming this file manually, and then rerun `nisclient` `-i`. `*ERROR: Couldn't get the server NIS+_server's address.` The script was unable to retrieve the server's IP address for the specified domain. Manually add the IP address for NIS+_server* into the `/etc/hosts` or `/etc/inet/ipnodes` file, then rerun `nisclient` `-i`. `ERROR: directory directory-path does not exist.` This message indicates that you typed an incorrect directory path. Type the correct directory path. `ERROR: domainname does not exist.` This message indicates that you are trying to replicate a domain that does not exist. If domainname is spelled incorrectly, rerun the script with the correct domain name. If the domainname domain does not exist, create it. Then you can replicate it. `**ERROR: parent-domain does not exist.`