This chapter describes how to find and prevent errors.
To prevent problems, run MULTINET CHECK and MULTINET X11DEBUG at periodic intervals. These commands are described in the MultiNet Administrator's Reference. The CHECK command verifies your configuration is correct. The X11DEBUG command verifies your current X (X Window System) configuration is correct for X support over MultiNet.
If a problem occurs, capture OPCOM messages and look up the message in Chapter 2 of this book. Also, examine the index for messages that might be contained in another message string. If you cannot find the message, contact Process Software Technical Support.
Because "R" services problems constitute a majority of system problems, ensure all new user login command procedures and the system login command procedure contain these lines at the top of the file:
$ verify = 'f$verify(0)'
$ if fmode() .eqs. "OTHER" then exit
Be sure to insert the single quote before F$VERIFY and specify OTHER in uppercase.
Problems are reported to the system console and must be resolved by the system manager. This section provides guidance for the system manager in resolving common faults in the operation of networking software.
To display console messages on your terminal, enter the following command:
$ REPLY/ENABLE=NETWORK/TEMP
To suppress the display of these messages on your terminal, enter:
$ REPLY/DISABLE
Three types of messages appear on the system console:
1. Messages that occur when the MultiNet software is initialized. MultiNet reports a variety of configuration and version information, including the software versions and the Ethernet addresses the networking software thinks are its own.
2. Warnings that occur during system operation. These vary in severity, and may or may not indicate a severe problem that should be corrected.
3. Warning or trace information from various servers, such as the MULTINET_SERVER process.
To get more data when an error message appears, but additional information is unavailable:
1. Choose a user name with full privileges and at least as much quota as the SYSTEM account.
2. Stop the MULTINET_SERVER process.
3. Use the following commands to start the server as the chosen user name:
$ SET PROCESS/NAME=MULTINET_SERVER
$ RUN MULTINET:SERVER
Leave this process logged in and running the server. When an error occurs, a traceback or error message should appear.
Other sources of information are in the log files shown in the below table.
|
Service |
Error Log Name |
|
DECwindows |
SYS$MANAGER:DECW$SERVER_0_ERROR.LOG |
|
FTP server |
SYS$LOGIN:FTP_SERVER.LOG |
|
IPS |
MULTINET:FILTER_SERVER.OUT MULTINET:FILTER_SERVER.LOG |
|
MultiNet Server |
MULTINET:SERVER.LOG |
|
NFS Client |
SYS$MANAGER:NFS_MOUNT.LOG |
|
OPCOM |
SYS$MANAGER:OPERATOR.LOG |
|
POP2 |
SYS$LOGIN:POP2_SERVER.LOG |
|
POP3 |
SYS$LOGIN:POP3_SERVER.LOG |
|
R Services |
MULTINET:USER_ACCESS.LOG |
|
SMTP |
MULTINET:SERVER-SMTP.LOG |
|
SSH |
SSH_LOG:SSHD.LOG MULTINET:SSHD_MASTER.LOG |
|
TELNET |
TELNET.LOG (resides in the directory from which TELNET
is invoked) |
|
TRACEROUTE |
MULTINET:USER_ACCESS.LOG |
|
XDM |
MULTINET:XDM-ERRORS.LOG |
|
WHOIS |
MULTINET:USER ACCESS.LOG |
Tables in Chapter 5 list the UNIX (errno) errors alphabetically and by number. You can find additional information about errno values in the error message sections that follow.
In the following sections, error messages are listed alphabetically by the first word in the message. Special characters at either the start of a message or embedded within the message are ignored. For example, a message starting with ?Unknown is listed in the "U" section.
In the message listings in Chapter 2, if a message contains either vms_hex_error or vms_error_value, you can display a message string for the error value with the following command:
$ WRITE SYS$OUTPUT F$MESSAGE(“value”)
If the value is in hexadecimal, preface it with %x in the WRITE statement; if it is octal, preface it with %o.
For additional information, refer to the OpenVMS error message manual.