Failing to upgrade AHV Proxy after Upgrading VBR to v11

[tpayne]

Hello,

I am getting the following error:
"VeeamBackupAppliance: Failed to upgrade host components. Error: 'Failed to upgrade Proxy - AHV Proxy upgrade failed. Error: Updates are not found. Please Contact Veeam customer support'"

I have a support case open: #02373809

Current AHV Proxy Version: 2.0.558

Attempting to check updates on the web UI gets the error:
"Failed to check for an update. Error: E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable) E: Unable to lock directory /var/lib/apt/lists/
X"

I tried rebooting the appliance and trying the check for updates again but get the same result.

Anyone else run into this and have a solution?

Thanks.

[Mildur]

Your AHV proxy needs access to the internet, if I‘m remember correctly. Do you have a firewall which restricts internet access from the proxy?

From the guide:

https://helpcenter.veeam.com/docs/van/u ... tml?ver=21

NOTE
Before you upgrade AHV Backup Proxy, make sure all required ports are open. For details, see Used Ports.

Needed Ports are here:
https://helpcenter.veeam.com/docs/van/u ... tml?ver=21

One of them:

Destination: Veeam Updater repository (repository.veeam.com)
Port 443
Description: Required to download required AHV Backup Proxy packages and information on available product updates.

[tpayne]

Possibly, I will check. What ports are required for outbound access from the Proxy?
Edit: I found the answer here: https://helpcenter.veeam.com/docs/van/u ... tml?ver=21

[Mildur]

I have updated my post

[tpayne]

Thanks,

I will check this and report back.

[tpayne]

So the network team said there should be no outbound restrictions or proxies on that subnet. Is there any way to get like ssh access to do some testing/troubleshooting? (I don't have access to the Nutanix console access of the VM).

Thanks.

[Mildur]

You have to enable it first over vm console:
https://helpcenter.veeam.com/docs/van/u ... tml?ver=21

[tpayne]

Mildur,

Thanks for that info. I found out it was a DNS misconfiguration. But I still get the same error when attempting the upgrade from the VBR console. When I check from the Proxy Web UI I get:

Code: Select all

"Failed to check for an update. Error: W: GPG error: https://repository.veeam.com/vbahv/1/public/updater stable InRelease: The following signatures were invalid: KEYEXPIRED 1525607146 KEYEXPIRED 1618576417 KEYEXPIRED 1618576417 KEYEXPIRED 1525607146 KEYEXPIRED 1618576417 KEYEXPIRED 1525607146 KEYEXPIRED 1618576417 W: The repository 'https://repository.veeam.com/vbahv/1/public/updater stable InRelease' is not signed. W: GPG error: https://repository.veeam.com/vbahv/1/public/proxy stable InRelease: The following signatures were invalid: KEYEXPIRED 1525607146 KEYEXPIRED 1618576417 KEYEXPIRED 1618576417 KEYEXPIRED 1525607146 KEYEXPIRED 1618576417 KEYEXPIRED 1525607146 KEYEXPIRED 1618576417 W: The repository 'https://repository.veeam.com/vbahv/1/public/proxy stable InRelease' is not signed. "

Any Ideas?

Thanks.

[Mildur]

No problem.

No, unfortunately not. I don‘t have an answer about the new issue.
It‘s best to inform your veeam technician in your support case about the new issues.

[tpayne]

Support just pointed me to this brand new KB: https://www.veeam.com/kb4150.

That did the trick! I was able to upgrade it from the VBR console.

[PTide]

Beat me by a few seconds... : ) Thanks for reporting back, glad you've resolved it.

[Mildur]

Thank you for the KB Link

[wa15]

Anyone else having this issue even after following KB4150? Just upgraded to V11 and having this issue.

[PTide]

Exactly the same messages? If so, then please open a support case and post your case ID here.

Thanks!

[wa15]

Yes, same error. Opened up case #04783623.

I called support to speak with a live person but was told the AHV team doesn't have a phone queue I can get transferred to. That's disappointing.