Wireless Access

last person joined: 23 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Upgrade issues from 7.6.1 to 7.7.1

This thread has been viewed 0 times
  • 1.  Upgrade issues from 7.6.1 to 7.7.1

    Posted Jul 30, 2013 12:25 PM

     

    I tried upgrading two of my Airwave servers one worked well but the other one gave me this error :

     

    [root@amp-g1 mercury]# start_amp_upgrade -v 7.7.1
    Directory not specified; using /root.
    Upgrade script found in local cache.
    Upgrade package found in local cache.
    Upgrade package found in local cache.
    Checking for any patches or modifications to the code
    This process may take a few minutes...
    No outstanding changes were found. Continuing with the upgrade.

    Validating the upgrade package...
    Upgrade package is OK.
    Upgrading AMP to version 7.7.1 from version 7.7.1...
    Detailed log will be written to /var/log/upgrade/AMP-7.7.1-upgrade.log

    STEP 1: Moving old version aside.

    STEP 2: Unpacking upgrade package.
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

    STEP 3: Checking for compatibility.
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

    STEP 4: Stopping AMP services.
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

    STEP 5: Installing upgrade.
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory


    Upgrade aborted.
    Please contact Aruba Networks Support at
    1-800-WiFi-LAN or support@arubanetworks.com
    DISABLED - 4!!

     

    I already open a TAC case but maybe somebody here has seen this before .

     

    Thanks in advance

     



  • 2.  RE: Upgrade issues from 7.6.1 to 7.7.1

    EMPLOYEE
    Posted Jul 30, 2013 04:30 PM

    Is your CLI session getting stale?  Try to refresh current directory:

    # cd /tmp

    # cd /root/svn/mercury

    (don't really need cd /tmp, but that's just precaution to make sure you exit current directory before returning to it)

    Then try the start_amp_upgrade command again.

     

    The reason this might work is because during the upgrade, the /root/svn/mercury directory is moved to mercury_old, while a new mercury folder is being built.  At failure, the AMP tries to back out by removing the new mercury and putting mercury_old back into the mercury directory.

     

    If this doesn't work, please open a support case to track.