IBM Support

padmin commands fail with "Access to run command is not valid."

Troubleshooting


Problem

padmin commands fail with "Access to run command is not valid." after VIOS update.

Symptom

Example of padmin CLI failure include, but it's not limited to the following:

$ swrole - PAdmin                    
padmin's Password:                  
Access to run command is not valid.  
       
$ ioslevel
Access to run command is not valid.
                             
$ license -accept                    
Access to run command is not valid.

Other commands may fail with different errors, i.e.
$ oem_setup_env
rksh: oem_setup_env: cannot execute

Cause

The "Access to run command is not valid." error is indicative that something went wrong during the VIOS update, resulting in the ios.cli.rte fileset being partially updated.

/home/padmin/install.log file is key for determining what went wrong. This file should be carefully examined for error details around the time ios.cli.rte was being updated. Common causes include, but are not limited to, one of the following scenarios.

Scenario 1


Failure can be due to xmldaily entry being commented out in /etc/inittab.

Scenario 2
Failure to rename the Virtual Media Library (VML) Logical volume name, from VMLibrary_LV to VMLibrary during updateios process due to virtual optical device being loaded at the time updateios was executed.

Environment

VIOS 2.2 or higher

Diagnosing The Problem

See next section to determine if the scenarios described may be applicable to your environment.

Resolving The Problem

Scenario 1

xmldaily entry is commented out in /etc/inittab.

In this case, the install.log shows failure during lsitab. This is commonly due to the xmdaily entry being commented out or removed from /etc/inittab causing ios.cli.rte to be partially updated.

    ...
    installp:  APPLYING software for:
           ios.cli.rte 6.1.9.2

    . . . . . << Copyright notice for ios.cli >> . . . . . . .
    Licensed Materials - Property of IBM

    5765G3400
      Copyright International Business Machines Corp. 2004, 2014.

    All rights reserved.
    US Government Users Restricted Rights - Use, duplication or disclosure
    restricted by GSA ADP Schedule Contract with IBM Corp.
    . . . . . << End of copyright notice for ios.cli >>. . . .

    sysck: 3001-022 The file
           /usr/ios/utils/part
           was not found.

    Start Creating VIOS Authorizations
    Completed Creating VIOS Authorizations

    Warning:     lsitab failed...
    update:  Failed while executing the ios.cli.rte.post_u script.
    0503-464 installp:  The installation has FAILED for the "root" part
           ios.cli.rte 6.1.9.2

    installp:  Cleaning up software for:
           ios.cli.rte 6.1.9.2
    ...
    Installation Summary
    --------------------
    Name                  Level        Part        Event     Result
    ----------------------------------------------------------------
    ios.cli.rte           6.1.9.2      USR         APPLY     SUCCESS
    ios.cli.rte           6.1.9.2      ROOT        APPLY     FAILED
    ios.cli.rte           6.1.9.2      ROOT        CLEANUP   SUCCESS
    ...
    Recommendation:
    /etc/inittab is a critical system file and should NOT be modified.
    To correct the problem, ensure xmdaily identifier exists in /etc/inittab. Then ios.cli.rte must be forced-overwritten via oem_setup_env (root shell) prior to rerunning updateios again to complete the update.

    If oem_setup_env or root access is not possible, the VIOS must be booted into Maintenance Mode in order to enable root access temporarily by running the following command:

    # smitty  chuser =>root => change login=true and rlogin=true



    Then boot VIOS in normal mode and login as root to force-overwrite the fileset using VIOS 2.1 Migration Media, available on FixCentral.

    To verify existance of xmldaily in /etc/inittab, run:

    # lsitab -a|grep xmdaily > should return something similar to this:


    xmdaily:2:once:/usr/bin/topasrec -L -s 300 -R 1 -r 6 -o /home/ios/perf/topas/ -ypersistent=1 2>&1 >/dev/null #Start local binary recording

    To force overwrite the fileset, run:

    # smitty install_all      


    * SOFTWARE to install                     > select ios.cli.rte
    AUTOMATICALLY install requisite software? > no  
    OVERWRITE same or newer versions?         > yes  

    Last, run updateios again to complete the update.


Scenario 2

Failure to rename the Virtual Media Library (VML) logical volume name, from VMLibrary_LV to VMLibrary during updateios process due to a virtual optical device being loaded at the time updateios was executed. In this case, /home/padmin/install.log will show output similar to the following:

    ...
    installp: APPLYING software for:
    ios.cli.rte 6.1.9.1

    . . . . . << Copyright notice for ios.cli >> . . . . . . .
    Licensed Materials - Property of IBM

    5765G3400
      Copyright International Business Machines Corp. 2004, 2013.

    All rights reserved.
    US Government Users Restricted Rights - Use, duplication or disclosure
    restricted by GSA ADP Schedule Contract with IBM Corp.
    . . . . . << End of copyright notice for ios.cli >>. . . .

    sysck: 3001-022 The file /home/ios/vios_migration.bnd
    was not found.
    Verifying Media Repository Logical Volume Status:

    Media Repository successfully unmounted...
    Kernel tables will be updated after reboot.

    Start Creating VIOS Authorizations
    Completed Creating VIOS Authorizations

    Kernel tables will be updated after reboot.
    Kernel tables will be updated after reboot.
    Kernel tables will be updated after reboot.
    Kernel tables will be updated after reboot.
    Renaming Media Repository Logical Volume:
       VMLibrary_LV --> VMLibrary
    0518-307 odmdelete: 3 objects deleted.
    trustchk: Duplicate stanza: /dev/VMLibrary_LV
    trustchk: Error adding stanza: /dev/VMLibrary_LV
    trustchk: Duplicate stanza: /dev/rVMLibrary_LV
    trustchk: Error adding stanza: /dev/rVMLibrary_LV
    0516-704 chlv: Unable to change logical volume VMLibrary_LV.

    Media Repository Logical Volume rename failed. We cannot
    continue until it can be successfully renamed. Please
    address and retry.
    update:  Failed while executing the ios.cli.rte.post_u script.

    installp:  The installation has FAILED for the "root" part
    of the following filesets:
    ios.cli.rte 6.1.9.1

    installp: Cleaning up software for:
    ios.cli.rte 6.1.9.1
    ...

The following sample output may be seen if residual was left in /dev (/dev/VMLibrary) from the initial failure:

    ...
    Renaming Media Repository Logical Volume:  
        VMLibrary_LV --> VMLibrary                                
    0516-710 lchangelv: mknod function failure. Cannot create new  
            device special file /dev/VMLibrary.                    
    0516-704 chlv: Unable to change logical volume VMLibrary_LV.
    Media Repository Logical Volume rename failed. We cannot      
    continue until it can be successfully renamed. Please          
    address and retry.                                            
    update:  Failed while executing the ios.cli.rte.post_u script.
                                                                   
    installp:  The installation has FAILED for the "root" part    
            of the following filesets:                            
            ios.cli.rte 6.1.9.1                                    
    ....
    Recommendation:
    1. Ensure /dev/VMLibrary does NOT exist

      # cd /dev
      # ls -la > If VMLibrary exists, rename the file to something else, such as
      # mv VMLibrary VMLibary.old
    2. Manually rename the VML logical volume from VMLibrary_LV to VMLibrary

      # chlv -n VMLibraryLV VMLibrary_LV

    3. Force-overwrite ios.cli.rte using the 2.1 migration media mounted on the managed-system's local CD/DVD drive:

      # smitty install_all      
      * SOFTWARE to install                     > select ios.cli.rte
      AUTOMATICALLY install requisite software? > no  
      OVERWRITE same or newer versions?         > yes  

    4. Re-run updateios to complete the update

      $ updateios -commit
      $ updateios -accept -install -dev /<path_to_dir_containing_VIO_fixes>
[{"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":null,"Platform":[{"code":"","label":"Other"}],"Version":"2.2.4;2.2.3;2.2.2;2.2.1;2.2.0","Edition":"Enterprise;Express;Standard","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

More support for:
PowerVM Virtual I/O Server

Software version:
2.2.4, 2.2.3, 2.2.2, 2.2.1, 2.2.0

Operating system(s):
Other

Document number:
681569

Modified date:
19 February 2022

UID

isg3T1022888

Manage My Notification Subscriptions

Page Feedback