I’ve been working with DRD recently and have come across a couple of strange issues.
Issue #1:
The first issue deals with the format DRD expects patches to be in.
DRD cannot handle a “serial” or “tape” depot when installing products or patches on a clone disk via the ‘drd runcmd swinstall’. The serial/tape depots are the software depots that are self-contained in a single file (PHKL_1234.depot or Ignite_A.1.2.3.depot for example). The error that DRD will produce from a command like ‘drd runcmd swinstall -s /tmp/PHKL_1234.depot *‘ is:
ERROR: The source you have chosen is a tape device located on the booted system. Installing from this source is not supported under drd runcmd. To install software from this tape device, first copy the software to a non-tape device using swcopy.
The solution is to use swcopy to copy the software into a “directory” depot, which is the depot where you can traverse down the directory tree from the command line to see all files in the depot. For example, to create a directory depot of PHKL_1234.depot you would do: swcopy -s /tmp/PHKL_1234.depot * @ /tmp/PHKL_1234
Then you can do ‘drd runcmd swinstall -s /tmp/PHKL_1234 *‘ and it should proceed fine. Depending on what type of depot you are copying you may need to add the ‘-x enforce_dependencies=false’ option to the swcopy command.
I honestly do not understand why DRD cares what type of depot, serial/tape or directory, you use to install. Perhaps an enhancement request is in order.
Issue #2:
The next issue also involves utilization of ‘drd runcmd swinstall’ command syntax, but this issue is isolated to DRD version A.3.9.432. Occasionally you may get an error like the following, which will cause ‘drd runcmd swinstall’ to fail:
/usr/bin/X11/xauth: (argv):1: bad “add” command line
WARNING: Could not import X Authentication.
This error occurrs when the .Xauthority file is empty or has more than 1 entry. The two possible solutions are to:
1) move the .Xauthority file to another name and rerun the ‘drd runcmd’ command.
2) Modify the .Xauthority file, via the xauth command, to remove all but 1 entry.
This behavior changed between DRD A.3.7.4 and A.3.9.432. I have a call open with HP right now to try to determine what they are doing with the .Xauthority file.
According to HP this problem will be fixed in DRD version A.3.10 scheduled for release in March 2012.
Cool Feature:
A cool feature that I ran across recently is the ability to have DRD create a full mirror set during the clone operation. This is done via the following command:
drd clone -x overwrite=true -t /dev/dsk/c2t14d0 -x mirror_disk=/dev/dsk/c1t2d0
This will create the clone of the currently booted disk to /dev/dsk/c2t14d0 and then mirror c2t14d0 to c1t2d0. Both disks are now bootable and when you boot, you will have a full VG00 mirror set.
– See more at: http://serviceitdirect.com/blog/drd-strangeness#sthash.cfAj28mr.dpuf
Tags: HP-UX