HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

DRD -X options_file unable to read

 
Mw_6
Occasional Advisor

DRD -X options_file unable to read

I'm trying to run a drd runcmd swinstall using the -f and -X (product input / option file input). But DRD saws it can't open/read the option file. If I put the optins on the command line then it says it can't read the software input file. Both files are there and I've even chmod them to 777 to see if that was the problem but it didn't matter.

# pwd
/cghbackup/depots/sep09
# ll sw*
-rwxrwxrwx 1 root sys 5641 Apr 13 11:27 swinput
-rwxrwxrwx 1 root sys 145 Apr 14 10:52 swxswitch

# drd runcmd swinstall -s /cghbackup/depots/sep09/cghsep09 -f /cghbackup/depots/sep09/swinput -X /cghbackup/depots/sep09/s>

======= 04/14/10 10:53:23 CDT BEGIN Executing Command On Inactive System Image (user=root) (jobid=hnadb4)

* Checking for Valid Inactive System Image
* Analyzing Command To Be Run On Inactive System Image
* Locating Inactive System Image
* Preparing Inactive System Image For Command Execution
* Selected inactive system image "sysimage_001" on disk "/dev/disk/disk164".
* Accessing Inactive System Image for Command Execution
* Setting Up Environment For Command Execution
* Executing Command On Inactive System Image
* Starting fsdaemon for drd runcmd
* Using unsafe patch list version 20080324
* Starting swagentd for drd runcmd
* Executing command: "/usr/sbin/swinstall -s /cghbackup/depots/sep09/cghsep09 -f /cghbackup/depots/sep09/swinput -X
/cghbackup/depots/sep09/swxswitch"
ERROR: Could not open/read the option file
"/cghbackup/depots/sep09/swxswitch" (No such file or directory
(2)).
ERROR: Command line parsing failed.
* Stopping swagentd for drd runcmd
* Stopping fsdaemon for drd runcmd
ERROR: Command executed on inactive system image returned an error
- The command "/usr/sbin/swinstall -s /cghbackup/depots/sep09/cghsep09 -f /cghbackup/depots/sep09/swinput -X
/cghbackup/depots/sep09/swxswitch" failed with 1.
* Executing Command On Inactive System Image failed with 1 error.
* Cleaning Up After Command Execution On Inactive System Image

======= 04/14/10 10:54:03 CDT END Executing Command On Inactive System Image failed with 1 error. (user=root) (jobid=hnadb4)

With the -x options on the command line.

# drd runcmd swinstall -s /cghbackup/depots/sep09/cghsep09 -f /cghbackup/depots/sep09/swinput -x logdetail=true \^J-x logl>

======= 04/14/10 10:15:56 CDT BEGIN Executing Command On Inactive System Image (user=root) (jobid=hnadb4)

* Checking for Valid Inactive System Image
* Analyzing Command To Be Run On Inactive System Image
* Locating Inactive System Image
* Preparing Inactive System Image For Command Execution
* Selected inactive system image "sysimage_001" on disk "/dev/disk/disk164".
* Accessing Inactive System Image for Command Execution
* Setting Up Environment For Command Execution
* Executing Command On Inactive System Image
* Starting fsdaemon for drd runcmd
* Using unsafe patch list version 20080324
* Starting swagentd for drd runcmd
* Executing command: "/usr/sbin/swinstall -s /cghbackup/depots/sep09/cghsep09 -f /cghbackup/depots/sep09/swinput -x
logdetail=true -x loglevel=2 -x log_msgid=1 -x patch_match_target=true -x mount_all_filesystems=false -x autorecover=true"
ERROR: Could not read input file "/cghbackup/depots/sep09/swinput".
ERROR: Command line parsing failed.
* Stopping swagentd for drd runcmd
* Stopping fsdaemon for drd runcmd
ERROR: Command executed on inactive system image returned an error
- The command "/usr/sbin/swinstall -s /cghbackup/depots/sep09/cghsep09 -f /cghbackup/depots/sep09/swinput -x
logdetail=true -x loglevel=2 -x log_msgid=1 -x patch_match_target=true -x mount_all_filesystems=false -x
autorecover=true" failed with 1.
* Executing Command On Inactive System Image failed with 1 error.
* Cleaning Up After Command Execution On Inactive System Image

======= 04/14/10 10:16:36 CDT END Executing Command On Inactive System Image failed with 1 error. (user=root) (jobid=hnadb4)

Anybody have any thoughts on why it can't open/read the files?
3 REPLIES
Mw_6
Occasional Advisor

Re: DRD -X options_file unable to read

I how verified this is an issue with DRD.

It is looking for the files to be on the clone image not the local system.

If I:
drd mount
cp the files to drd mounted image
drd umount

And then run my original command it find the input files. Though I don't think that should be the intended behavior.
Mw_6
Occasional Advisor

Re: DRD -X options_file unable to read

See previous message.
Judy Wathen
Advisor

Re: DRD -X options_file unable to read

Hello Mw -

As you saw, the files referenced in the SD command must reside on the inactive image. This information is included in drd-runcmd(1M):

Any file referenced by the command line, that is, the argument of the view command and any argument of any of the options -c, -f -P, -S, -X, -x logfile, or -x patch_filter, must reside on the inactive system image and must be designated by the path it would have if the inactive image were booted. This is the same as its path relative to the mount point of a mounted inactive image. For example, the location that will be /var/opt/list when the image is booted is either /var/opt/drd/mnts/sysimage_001/var/opt/list or
/var/opt/drd/mnts/sysimage_000/var/opt/list when the inactive image is mounted. If this file is an argument of one of the options listed above, it should be specified as simply /var/opt/list.

This restriction also applies to the arguments of "-x logfile" and "-x
patch_filter" that appear in a file that is the argument of the "-X" option, and to paths that appear in a file that is the argument of a "-S" option.

Note that this restriction does NOT apply to local directory depots, which must reside on the booted system, and be designated by their
location on the booted system.

Thanks,
Judy