Azure VM Backup - Barracuda CloudGen Firewall - Agent not responding & unable to upgrade agent

Anonymous_17 21 Reputation points
2020-06-17T11:19:12.933+00:00

Hi Everyone,

We have an Azure VM - Barracuda CloudGen Firewall release GWAY-8.0.3-0137 for which existing backup has stopped due to agent not responsding. We checked on portal & observed that VM agent state shows not ready & none of the extenstions are visible.
So, we checked the agent version & status within the Barracuda Firewall & following's the output (we did restart the agent - sudo service waagent restart)
WALinuxAgent-2.2.40 running on centos 8.0:3
Python: 2.7.5
Goal State Agent: 2.2.40
sudo service waagent status - active (running)
Loaded: Loaded (/etc/rc.d/init.d/waagent; bad;vendor preset: disabled) - is the bad causing the issue or the vendor preset being disabled?

The service restart didn't help. So, as a next step we are trying to upgrade the agent from 2.2.40 to higher version but it says there's no enabled repos & even the repolist is 0

sudo yum check-update WALinuxAgent
Following's the output,
There are no enabled repos.
Run "yum repolist all" to see the repos you have
To enable Red Hat Subscription Management repositories: subscription-manager repos --enable <repo>
To enable custom repositories: yum-config-manager --enable <repo>
output of "yum repolist all" is 0

So, what else needs to be checked & done in order to resolve

  1. the agent not responding status
  2. perform agent upgrade (from july onwards the minimum version required is 2.2.41)

Regards,
Anonymous_17

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,191 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 41,456 Reputation points Microsoft Employee
    2020-06-23T06:50:55.76+00:00

    Sorry for the delay in response to your query. Thanks for sharing the var log file, there seems to be DHCP send request failure and endpoints are not found. It suggests to rerun dhcp handler. Not an expert on the network front so cannot comment much on that. We need to further investigate this issue at the guest agent level to arrive at the conclusion whether the issue is with our agent or barracuda firewall. Suggest you to reach out to us by creating a technical support request using these steps. Let me know if you have any limitations creating a support request.