System Troubleshooting and Diagnostics
5.6 Interpreting User Environmental Test Package (UETP) OpenVMS Failures
Using these two files, UETP provides the output from its tests and phases from
the two most recent runs.
The cluster test creates a NETSERVER.LOG file in SYS$TEST for each pass
on each system included in the run. If the test is unable to report errors (for
example, if the connection to another node is lost), the NETSERVER.LOG
file on that node contains the result of the test run on that node. UETP does
not purge or delete NETSERVER.LOG files; therefore, you must delete them
occasionally to recover disk space.
If a UETP run does not complete normally, SYS$TEST might contain other log
files. Ordinarily these log files are concatenated and placed within UETP.LOG.
You can use any log files that appear on the system disk for error checking,
but you must delete these log files before you run any new tests. You may
delete these log files yourself or rerun the entire UETP, which checks for old
UETP.LOG files and deletes them.
5.6.1.2 Possible UETP Errors
This section is intended to help you identify problems you might encounter
running UETP.
The following are the most common failures encountered while running UETP:
• Wrong quotas, privileges, or account
• UETINIT01 failure
• Ethernet device allocated or in use by another application
• Insufficient disk space
• Incorrect VAXcluster setup
• Problems during the load test
• DECnet–VAX error
• Lack of default access for the FAL object
• Errors logged but not displayed
• No PCB or swap slots
• Hangs
• Bug checks and machine checks
For more information refer to the
VAX 3520, 3540 OpenVMS Installation and
Operations (ZKS166)
manual.
5–70 System Troubleshooting and Diagnostics