VERITAS Volume Manager 3.2 for HP-UX Release Notes

Known Problems and Workarounds

Chapter 1 27

message is displayed:

Summary:

There is no such server (host1)

Detail:

java.net.UnknownHostException: Unknown host:

[host2:32839]; nested exception is:

java.net.UnknownHostException:host2

In this example, the administrator specified host1 for the VMSA connection, but the

server host machine was identified as host2.

In some cases, this may be a problem with the way DNS is set up. A DNS reverse lookup

(by IP address) may return a host name that differs from the host name provided to VMSA

at startup (host1). You may have to make appropriate changes to DNS so that the names

are consistent. In other cases, this happens because host1 is not the first host in the list of

hosts for the associated IP address in the /etc/hosts file.

• Workaround: Make sure host1 shows up as the first host in the list of names for the

address of host1 in /etc/hosts.

X Window Errors at VMSA Startup

• Problem: When the Storage Administrator is started, the following X Window System

error can occur:

Xlib: connection to "hostname:0.0" refused by server

Xlib: Client is not authorized to connect to Server

java.lang.InternalError: Can’t connect to X11 window

server using hostname:0.0’as the value of the DISPLAY

variable.

at sun.awt.motif.MToolkit.<init>(MToolkit.java:48)

at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:244)

• Workaround: Type xhost + hostname to explicitly authorize the hostname client, or omit

hostname to allow unlimited X server access.

VMSA Does Not Grow a Volume of use_type “gen”

• Problem: VMSA does not grow a volume of use_type “gen”.

• Workaround: None.