46.0 Novell Native File Access for UNIX Messages
This section describes the system messages of the various components of Novell native File Access for UNIX.
Source:
MakeNIS
Possible Cause:
The directory specified when creating the log file might be incorrect.
Action:
Check for the validity of the directory path you specified.
Required parameters are missing
Source:
MakeNIS
Explanation:
The domain name is mandatory.
Possible Cause:
The user has not specified the required parameters.
Action:
Enter all the mandatory parameters.
Source:
MakeNIS
Possible Cause:
The user has not specified the domain name.
Action:
Enter the domain name.
Source:
MakeNIS
Possible Cause:
There is no data corresponding to the map in the makefile.
Action:
Enter the record corresponding to the map.
File is older than corresponding map
Source:
MakeNIS
Possible Cause:
The text file used for making this map is older than the map that exists on eDirectory.
Action:
Change the time stamp on the text file by saving it again.
Object with same domain name already exists
Source:
MakeNIS
Possible Cause:
An eDirectory error occurred while adding the specified object.
Action:
Check whether the object already exists.
Unable to add users to group objects
Source:
MakeNIS
Explanation:
Users are already present.
Unable to get the host name or IP address of the machine
Source:
MakeNIS
Possible Cause:
The configuration files containing the host data are not correct.
Action:
Check the configuration file.
Opening configuration file
Source:
NIS Installation
Possible Cause:
Either the file is not present in the specified location or the input is illegal.
Action:
Check for the existence of the specified file or the validity of the input.
Reading configuration file
Source:
NIS Installation
Possible Cause:
It is not the correct configuration file.
Action:
Check the configuration file.
Getting default host names
Source:
NIS Installation
Possible Cause:
Unable to get the DNS name of the current host.
Action:
Check whether entries in relevant configuration files are correct.
Updating the configuration file
Source:
NIS Installation
Possible Cause:
Either the configuration file is not present or it is corrupted.
Action:
Check the configuration file.
Internal error with refresh watchdog
Source:
NIS Services
Possible Cause:
The refresh thread of the NIS Server is failing.
Action:
Unload the NISSERV.NLM and load it again.
Source:
NIS Services
Possible Cause:
There was an error on the RPC client call to NIS Server.
Action:
Unload the NISSERV.NLM and load it again.
Source:
NIS Services
Possible Cause:
Failure to allocate memory for the domain list of the NIS Server.
Action:
Unload the NISSERV.NLM and load it again.
Source:
NIS Services
Possible Cause:
An NIS Server internal error occurred while allocating memory for its internal structure.
Action:
Unload the NISSERV.NLM and load it again.
Unable to allocate space for domain index list
Source:
NIS Services
Possible Cause:
Failure to allocate memory for the domain list of NIS Server.
Action:
Unload the NISSERV.NLM and load it again.
Unable to respond to RPC request
Source:
NIS Services
Possible Cause:
Failure in sending the RPC response back to the client because of the PKERNAL.NLM.
Action:
Repeat the client call.
Unable to determine current server language
Source:
NFS Server
Possible Cause:
The language of the server is not set.
Action:
Set the language for the NetWare server.
Root not mapped to any user
Source:
NFS Server
Possible Cause:
No NetWare user has UNIX UID set to zero.
Action:
Make sure the schema is extended and the UNIX UID of the Superuser (admin) is set to zero.
Failed to register with PKERNEL
Source:
NFS Server
Possible Cause:
NFS Server registration with Portmapper failed.
Action:
Unload PKERNEL and load it again.
SVC_REGISTER failed for program, version
Source:
NFS Server
Possible Cause:
The RPC module cannot register the RPC service program.
Action:
Ensure that the program and version number are already registered.
RPC/UDP receive queues are full, packet dropped
Source:
NFS Server
Possible Cause:
Too many UDP packets have been received and have exceeded the UDP receive queue's capacity in the RPC module. Some UDP packets might be lost. This could be caused by an increase of activities such as a RPC broadcast storm.