Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VDP Upgrade ISO not detected (66992)

Last Updated: 4/1/2020Categories: TroubleshootingTotal Views: 3754Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

VDP Upgrade ISO not detected

Steps performed in KB 57317 do not resolve the issue

Issue is generally noticed in VDP 6.1.7 or later

The iso has been mounted properly by the appliance:

root@vdp01:~/#: df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2        32G  6.0G   24G  20% /
udev            1.9G  148K  1.9G   1% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
/dev/sda1       128M   37M   85M  31% /boot
/dev/sda7       1.5G  166M  1.3G  12% /var
/dev/sda9       138G  5.3G  126G   5% /space
/dev/sdb1       256G  1.9G  254G   1% /data01
/dev/sdc1       256G  159M  256G   1% /data02
/dev/sdd1       256G  163M  256G   1% /data03
/dev/sr0        5.2G  5.2G     0 100% /mnt/auto/cdrom

Checking on the avinstaller service (which drives the upgrade) via CLI, we see that the avinstaller.pl script reports that avinstaller is up. However there is no process ID given, and searching for avinstaller processes on the VDP returns none:

root@vdp01:/home/admin/#: avinstaller.pl --test
Avistart process:
INFO: AVI is running.
root@vdp01:/home/admin/#: ps -ef | grep avi
root 4126 3081 0 16:02 pts/0 00:00:00 grep avi

Checking the version of curl in use on the VDP, we see version 7.37.0 is installed:

root@vdp01:/home/admin/#: curl --version
curl 7.37.0 (x86_64-suse-linux-gnu) libcurl/7.37.0 OpenSSL/0.9.8j zlib/1.2.7 libidn/1.10
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz

Cause

Curl 7.37.0 makes some changes to the output curl returns when checking the avinstaller webpage to see if it is up.
As a result, the VDP believes avinstaller is already started, so does not start it. Root cause of the curl upgrade is unconfirmed at this time.

Resolution

We can resolve this by making a small change to the logic the VDP uses to check if the avinstaller service is up. Workaround steps in order are as follows

Login to the VDP as the admin user, and elevate to the root account

Correct ownership on aviutils.pm:

chmod 644 /usr/local/avamar/lib/avi/aviutils.pm

Take a backup copy of aviutils.pm:

cp -p /usr/local/avamar/lib/avi/aviutils.pm /usr/local/avamar/lib/avi/x-aviutils.pm.`date -I`

Edit the current copy of aviutils.pm using vi:

vi /usr/local/avamar/lib/avi/aviutils.pm

Change line 82 (in the function "isAVIRunning") from:

if( $curl =~ /couldn't connect/ )

To:

my $return_code = $? >> 8;
if( $return_code == 7 )

NB: See the notes section for a before/after comparison in context.

Start the avinstaller service:

avinstaller.pl --start

Confirm that avinstaller service how has a running process:

root@vdp01:/home/admin/#: avinstaller.pl --test
Avistart process: 29578

INFO: AVI is running.

Restart the VDP appliance, and the upgrade tab should now show the upgrade as available.

Notes:

Before:

##
# Test if standalone AVI is running.
##
sub isAVIRunning()
{
parsePrefs();
my $avistart_proc = `ps aux | grep '/[a]vistart' | awk '{ print \$2 }'`;
print ("Avistart process: $avistart_proc \n");
my $curl = `curl $AvInstallerPrefs::testAviRunningUrl 2>&1`;
if( $curl =~ /couldn't connect/ )
{
return( 0 );
}
return( 1 );
}

After:

##
# Test if standalone AVI is running.
##
sub isAVIRunning()
{
parsePrefs();
my $avistart_proc = `ps aux | grep '/[a]vistart' | awk '{ print \$2 }'`;
print ("Avistart process: $avistart_proc \n");
my $curl = `curl $AvInstallerPrefs::testAviRunningUrl 2>&1`;
my $return_code = $? >> 8;
if( $return_code == 7 )
{
return( 0 );
}
return( 1 );
}

If these steps and those in KB 57317 do not resolve the issue, please open a Support Request with VMware.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
次のエラーで仮想マシンをパワーオンできない：仮想マシンのパワーオンに失敗する。Flash Read Cache を作成できない。操作に失敗しました。(Operation failed.) (66927)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
解决 SCSI 预留冲突 (1002293)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Data Protection

VMware vSphere

Related Versions:

VMware vSphere Data Protection 6.1.x

Take Our Survey

Support Assistant