1 2 Previous Next 20 Replies Latest reply on Jun 18, 2017 11:53 AM by vspheretester Go to original post
      • 15. Re: External PSC upgrade error 6.0 -> 6.5
        sanjeebkumar Enthusiast
        VMware Employees

        Hi eai,

        Is your problem solved after referring the workaround below?

        The upgrade of a vCenter Server Appliance might fail because a dependency shared library path is missing
        The upgrade of a vCenter Server Appliance might fail before the export phase and the error log shows: /opt/vmware/share/vami/vami_get_network: error while loading shared libraries: libvami-common.so: cannot open shared object file: No such file or directory. This problem occurs due to missing dependency shared library path.

        Workaround:

        1. Log in to the appliance Bash shell of the vCenter Server Appliance.
        2. Run the following commands.
          echo "LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}/opt/vmware/lib/vami/" >> /root/.bashrc
          echo 'export $LD_LIBRARY_PATH' >> /root/.bashrc
        3. Log out of the appliance shell.
        4. Retry the upgrade.

         

         

        You mentioned there is a quote issue in this. Could you please give more details on that?

        • 16. Re: External PSC upgrade error 6.0 -> 6.5
          Neelei Novice

          Hi eai,

           

          First of all, sorry for my bad english.

           

          Have you tried to put in your /etc/profile of your PSC source AND destination (its important on both ) ? Thi

           

          I put in /etc/profile and not to bashrc because i can't execute it i don't know why.

           

          My error logs was in this file : /var/log/vmware/upgrade/upgrade-requirements.log on PSC destination.

           

          ERROR upgrade_commands Pre-upgrade checks failed. Check upgrade-source-requirements.log log for details.

          2016-11-18T14:22:13.43Z ERROR transport.guestops Invalid command: "/bin/bash" --login -c '/opt/vmware/share/vami/vami_get_network eth0 1>/tmp/vmware-root/exec-vmware181-stdout 2>/tmp/vmware-root/exec-vmware45-stderr'

          None

          2016-11-18T14:22:13.43Z ERROR upgrade_commands Unable to execute pre-upgrade checks on "PSC IP Source"


          And this one :

           

          ERROR apply_networking Failed to get source system network configuration stdout: , stderr: /opt/vmware/share/vami/vami_get_network: error while loading shared libraries: libvami-common.so: cannot open shared object file: No such file or directory

          , exit-code: 127.

           

          I created a ticket on vmware technical support and the answer was :

           

          "I validate this solution, this is a bug, I requested the publication of a KB "

           

          So a KB will be born soon, i guess.

           

          Thanks to PuliSukumar again !

          • 17. Re: External PSC upgrade error 6.0 -> 6.5
            PuliSukumar Enthusiast
            VMware Employees

            Could you please try below steps and let me know if your issue is solved or not.

            1. Log in to the appliance Bash shell of the Source vCenter Server Appliance.
            2. Run the following commands.

                    echo "LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}/opt/vmware/lib/vami/" >> /etc/profile

                    echo 'export LD_LIBRARY_PATH' >> /etc/profile

            1. Log out of the appliance shell.
            2. Retry the upgrade.
            1 person found this helpful
            • 18. Re: External PSC upgrade error 6.0 -> 6.5
              eai Novice

              Thanks to both of you, Neelei and PuliSukumar.

               

              Here is what I did -

               

              1) apply workaround with LD_LIBRARY_PATH to SOURCE PSC only

              2) I did this in /etc/profile NOT .bashrc

              3) it was not needed to do this on destination PSC, if you do this in /etc/profile on source PSC, it works

               

              I will say, the Release Notes are wrong, .bashrc does not work.  In addition, the Release Notes have a bug with the export command, you do not put the $ sign in front of the variable when exporting.

               

              So, yes, export LD_LIBRARY_PATH=/path is the correct solution as long as you do it in /etc/profile.

               

              I hope this gets resolved so others have a better experience - this upgrade to 6.5 has by far been the most buggy and difficult of any VMware upgrade, and I have been a user since 5.0.

              • 19. Re: External PSC upgrade error 6.0 -> 6.5
                zvadim3 Lurker

                Your solution worked for me.

                running echo "export LD_LIBRARY_PATH=/opt/vmware/lib/vami/" >> /etc/profile

                did the trick.

                 

                Thank you!

                • 20. Re: External PSC upgrade error 6.0 -> 6.5
                  vspheretester Lurker

                  Error stuff in upgrade-source-requirements.log (vm-support.tgz)

                   

                  2017-06-18T17:58:08.328Z ERROR apply_networking Failed to get source system network configuration stdout: , stderr: /opt/vmware/share/vami/vami_get_network: error while loading shared libraries: libvami-common.so: cannot open shared object file: No such file or directory

                  , exit-code: 127.

                   

                  2017-06-18T17:58:08.328Z ERROR __main__ Fatal error during upgrade collect requirements.

                  Traceback (most recent call last):

                    File "/tmp/vmware-root/tmpvmware206/bootstrap_scripts/run_linux_preupgrade_checks.py", line 1736, in main

                      deploymentType, applianceVersion)

                    File "/tmp/vmware-root/tmpvmware206/bootstrap_scripts/run_linux_preupgrade_checks.py", line 1391, in _addAppliancePnid

                      mismatches)

                    File "/tmp/vmware-root/tmpvmware206/bootstrap_scripts/run_linux_preupgrade_checks.py", line 1334, in _pickAppliance60Fqdn

                      _validatePnidDnsResolvable(legacyPnid, mismatches)

                    File "/tmp/vmware-root/tmpvmware206/bootstrap_scripts/run_linux_preupgrade_checks.py", line 1001, in _validatePnidDnsResolvable

                      nwConfig = vamiGetNetwork(processManager=LocalOperationsManager())

                    File "/tmp/vmware-root/tmpvmware206/bootstrap_scripts/apply_networking.py", line 144, in vamiGetNetwork

                      output = _execNetworkConfigCommand(processManager, [VAMI_GET_NETWORK_CMD, interface])

                    File "/tmp/vmware-root/tmpvmware206/bootstrap_scripts/apply_networking.py", line 72, in _execNetworkConfigCommand

                      raise NetworkConfigError(error)

                  NetworkConfigError: Failed to get source system network configuration stdout: , stderr: /opt/vmware/share/vami/vami_get_network: error while loading shared libraries: libvami-common.so: cannot open shared object file: No such file or directory

                  , exit-code: 127.

                   

                  2017-06-18T17:58:08.334Z INFO root Exiting with exit-code 1

                   

                  For the above error, the workaround helps!

                   

                  Thanks PuliSukumar.

                   

                  1 2 Previous Next