Virtual TapeServer 8.3 Release Notes

Known Issues | 51
 HP SIM fails to function properly with a DL185. HP SIM does not show several
items on the System Management Homepage. (TL-5246)
 HP SIM and GFS conflict. A component of HP SIM could conflict with the port used by
GFS. This could cause one process to stop functioning if the other one is correctly working.
(TL-5252)
 Activity log is not displaying messages in date order. The latest job should be on the
top. (TL-4299)
WORKAROUND: Use the Clear Log button to correct the UI.
 Cannot open message log TAR file. If you attempt to open a message log TAR file, an
“Invalid Archive” error is displayed. (TL-4308)
WORKAROUND: Download and open the message log ZIP file.
 Cannot restart the httpd process because another process is using its port. After
stopping the httpd process, it cannot be restarted sometimes because another process is
listening on its port (80). (TL-4232)
WORKAROUND: Reboot or manually stop processes until port 80 is free.
 EMS service should be started before drives are initialized. EMS log reports that
the drive requested for the mount had an invalid BLTI because the drive had not been
started. This caused tapes to be mounted but no lock was in place, and the system
reported that a tape was locked when it was not. (TL-3456)
 Running getVTS_dbginfo from the command line displays errors. Errors similar
to the following are displayed if you run the utility as root. (TL-3877)
/etc/profile.d/idle-logout.sh: line 3: TMOUT: readonly variable
cp: cannot copy a directory, `/usr/local/tape/log', into itself,
`log/log'
cp: will not overwrite just-created `cfg/network' with `/etc/
sysconfig/networking/profiles/default/network'
cp: cannot stat `/usr/local/tape/patch': No such file or directory
ls: /vault: No such file or directory
WORKAROUND: Use the button on the web interface to obtain the logs.
 Message logged to console and /var/log/messages until iLO is configured. Until
HP-iLO is configured, the following message may continue to print:
INIT: Id “s1” respawning too fast: disabled for 5 minutes
The message is also logged to /var/log/messages with no other information. (TL-2279)
System restore
 Web interface does not clearly indicate location of system restore image. The
web interface does not indicate that the restore image file is saved on the local file system.
It also does not warn the user that the Save File dialog might be blocked. (TL-4011)
WORKAROUND: Ensure browser pop-ups are enabled.
 No indication of system restore failure in log files. If a system restore fails, the
systemrestore.log and other logs do not log information about the failure. The only
indicator is displayed on the web interface, which says “An unexpected error has occurred,
please contact support.” (TL-4313)