Wireless Access

last person joined: 16 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
This thread has been viewed 12 times
  • 1.  Upgrade path

    Posted Jul 15, 2013 06:40 PM

    I've been making my upgrades in lockstep with new releases - usually within hours of the code publication.

     

    This time we've had several high-profile projects all at once, and I haven't had time to squeeze in the 7.6.5 to 7.7.0 upgrade.

    Now 7.7.1 is out and I'm preparing to upgrade.

     

    I'm probably just going to do it in steps with a backup in the middle, but is it OK to go straight from 7.6.5 to 7.7.1?

     



  • 2.  RE: Upgrade path

    Posted Jul 15, 2013 06:45 PM

    Yes, upgrade to 7.7.1 should be just fine.

     



  • 3.  RE: Upgrade path

    EMPLOYEE
    Posted Jul 15, 2013 08:00 PM

    You can upgrade directly to 7.7.1 from 7.6.5.  In fact, you should be able to upgrade to 7.7.1 from as far back as 2 full releases (currently meaning 7.5.x) with the only requirement being that the OS needs to be Cent6.



  • 4.  RE: Upgrade path

    Posted Jul 16, 2013 06:30 PM

    I know I've read that previously -- if fact I may have told someone that -- I've just never tried and suddenly got cold feet.



  • 5.  RE: Upgrade path

    Posted Jul 16, 2013 07:37 PM

    Of course I had to open my big mouth!

     

    I got my first error on upgrade:

    tsdb-server: unrecognized service
    
    Upgrade aborted.
    Please contact Aruba Networks Support at
    1-800-WiFi-LAN or support@arubanetworks.com
    DISABLED - 2!!
    svn: The path '/root/svn/mercury' appears to be part of a Subversion 1.7 or greater
    working copy.  Please upgrade your Subversion client to use this
    working copy.

     On my way to TAC...



  • 6.  RE: Upgrade path

    EMPLOYEE
    Posted Jul 16, 2013 07:46 PM

    Subversion was upgraded, but that should be a seamless upgrade.  Try running 'svn upgrade' and then after that re-issue the start_amp_upgrade command.  Once the upgrade goes through, you can do 'amp_enable -now'.

     

    Make sure you're in /root/svn/mercury when giving the 'svn upgrade' command.



  • 7.  RE: Upgrade path

    Posted Jul 16, 2013 08:03 PM

    "svn upgrade" is an "Unknown command"

    Update perhaps?



  • 8.  RE: Upgrade path

    Posted Jul 16, 2013 08:05 PM

    The rest of the original error:

    STEP 5: Installing upgrade.
    tsdb-server: unrecognized service
    	glibc = 2.12-1.80.el6_3.5 is needed by (installed) glibc-devel-2.12-1.80.el6_3.5.x86_64
    make[3]: *** [security_patches] Error 4
    make[3]: Leaving directory `/root/svn/mercury/src/x86_64/rpms/CentOS-6'
    make[2]: *** [perllib] Error 2
    make[2]: Leaving directory `/root/svn/mercury/src'
    make[1]: *** [src_install] Error 2
    make[1]: Leaving directory `/root/svn/mercury'
    make: *** [upgrade] Error 2
    make: Leaving directory `/root/svn/mercury'
    tsdb-server: unrecognized service
    
    

     



  • 9.  RE: Upgrade path

    Posted Jul 16, 2013 08:08 PM

    subversion is at 1.6.11

     

    did it miss an RPM?

     

    [root@airwave mercury]# svn --version
    svn, version 1.6.11 (r934486)
       compiled Jun 23 2012, 00:44:03
    
    

     



  • 10.  RE: Upgrade path
    Best Answer

    EMPLOYEE
    Posted Jul 16, 2013 08:12 PM

    Looks like it missed a package.

     

    This should do the trick

    # yum install glibc

     

    Then double check to verify the rpm package is there:

    # rpm -qa | grep -i glibc



  • 11.  RE: Upgrade path

    Posted Jul 16, 2013 08:41 PM

    That got it, we're nearing completion now

     

    We're up to RRDTool restart.

    ...

    Starting SafeMigration

    ...

    Installing kernel bits

    ...

    Rebooting

     

    Yay!



  • 12.  RE: Upgrade path

    Posted Feb 06, 2015 04:31 PM

    Much later, same problem going from 8.0.6.1 to 8.0.6.3 was resolved by updating glibc.  Oh, sweet irony, had to update glibc manually in order to update to 8.0.6.3 to resolve the ghost glibc bug.