You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Linux VM Agent fails to process extensions. This causes some extensions to stop running, which affects some dependent Azure services, such as Azure Backup Azure Site Recovery.
20
+
The Linux VM Agent doesn't process extensions. Because of this failure, some extensions stop running. This issue affects some dependent Azure services, such as Azure Backup Azure Site Recovery.
21
21
22
-
You will see extension downgrade errors similar to this recorded in /var/log/waagent.log:
22
+
When this issue occurs, you see extension downgrade error entries in /var/log/waagent.log that resemble the following example:
[PerfInsights Linux](https://aka.ms/perfinsightslinuxdownload) is a self-help diagnostics tool that collects and analyzes the diagnostic data, and provides a report to help troubleshoot Linux virtual machine performance problems in Azure. Use Performance Diagnostics to identify and troubleshoot performance issues in one of two modes:
25
23
26
24
-**Continuous diagnostics** collects data at five-second intervals and reports actionable insights about high resource usage every five minutes.
@@ -31,6 +29,8 @@ This article explains how to download the Performance Diagnostics extension to y
31
29
32
30
If you are experiencing performance problems with virtual machines, before contacting support, run this tool.
You can use Performance Diagnostics to troubleshoot various scenarios. The following sections describe common scenarios for using Continuous and On-Demand Performance Diagnostics to identify and troubleshoot performance issues. For a comparison of Continuous and On-Demand Performance Diagnostics, see [Performance Diagnostics insights and reports](../windows/performance-diagnostics.md).
This article provides information about resolving a problem in which Azure Linux VMs that are running Azure Linux VM Agent 2.1.5 or 2.1.6 cannot process extensions.
Azure Linux virtual machines (VMs) that are running Azure Linux VM Agent 2.1.5 or 2.1.6 experience the following issues if they receive more than one automatic update of Azure Linux VM Agent:
The [Azure Linux Agent](/azure/virtual-machines/extensions/agent-linux) enables a virtual machine (VM) to communicate with the Fabric Controller (the underlying physical server on which the VM is hosted) on IP address 168.63.129.16.
25
23
26
24
>[!NOTE]
27
25
>This IP address is a virtual public IP address that facilitates communication and should not be blocked. For more information, see [What is IP address 168.63.129.16?](/azure/virtual-network/what-is-ip-address-168-63-129-16).
Check the agent status and version to make sure it is still supported. See [Minimum version support for virtual machine agents in Azure](../windows/support-extensions-agent-version.md) to check version support, or see [WALinuxAgent FAQ](https://github.com/Azure/WALinuxAgent/wiki/FAQ#what-does-goal-state-agent-mean-in-waagent---version-output) for steps to find the status and version.
When you upload or capture a generalized virtual machine (VM) image as a specialized VM image, a [provisioning timeout error](#provisioning-timeout-error-during-an-upload-process) will occur.
@@ -25,6 +23,8 @@ This article covers the possible combinations of generalized and specialized ima
25
23
> [!NOTE]
26
24
> For descriptions and comparison of generalized and specialized images, see [Generalized and specialized](/azure/virtual-machines/linux/imaging#generalized-and-specialized).
Many Linux Azure Marketplace images contain an **Azure Linux Agent**, which is responsible for completing the setup of the newly created Virtual Machine (VM), such as setting the hostname, username, password/ ssh keys, and mounting an ephemeral disk. This setup process is known as 'provisioning'. In addition, the agent provides support for Azure VM Extensions.
20
+
Many Linux Azure Marketplace images contain an **Azure Linux Agent** that's responsible for completing the setup of the newly created virtual machine (VM). The setup includes setting the hostname, username, and password/ ssh keys, and mounting an ephemeral disk. This setup process is known as 'provisioning'. Additionally, the agent provides support for Azure VM extensions.
24
21
25
-
The images themselves will be updated to be provisioned using an open-source provisioning agent, [cloud-init](/azure/virtual-machines/linux/using-cloud-init). cloud- init offers many additional benefits over the Linux Agent, including:
22
+
The images themselves are updated to be provisioned by using an opensource provisioning agent, [cloud-init](/azure/virtual-machines/linux/using-cloud-init). The cloud- init agent offers many additional benefits over the Linux Agent, including:
26
23
27
24
- Performance - Using cloud-init with Azure, you can see improved reduced VM creation times in most cases.
28
-
- VM customization - cloud-init allows you to pass down VM configurations to cloud-init via [custom-data](/azure/virtual-machines/linux/using-cloud-init#deploying-a-cloud-init-enabled-virtual-machine), such as running scripts, installing packages, and adding users.
29
-
- Migration - If you are migrating from other clouds, you can migrate cloud- init configurations, and modify them where necessary to work with your Azure deployments.
25
+
- VM customization - cloud-init enables you to pass down VM configurations to cloud-init through [custom-data](/azure/virtual-machines/linux/using-cloud-init#deploying-a-cloud-init-enabled-virtual-machine). This process includes such actions as running scripts, installing packages, and adding users.
26
+
- Migration - If you're migrating from other clouds, you can migrate cloud-init configurations, and modify them where necessary to work with together your Azure deployments.
- If you deploy these Azure Marketplace images, then there is nothing further that you need to do. You can immediately take advantage of the benefits after the update.
36
-
- If you are creating custom images that derive from these images, and use the Linux Agent to process custom-data, check that your images still work correctly.
34
+
- If you deploy these Azure Marketplace images, then there is nothing more that you have to do. You can immediately take advantage of the benefits after the update.
35
+
- If you create custom images from these images, and use the Linux Agent to process customdata, verify that your images still work correctly.
37
36
38
-
cloud-init supports multiple input types, including a bash script or a cloud-init config. Review the 'cloud-init'[user-data](https://cloudinit.readthedocs.io/en/latest/topics/format.html) documentation.
39
-
- See [this](/azure/virtual-machines/linux/using-cloud-init#cloud-init-overview) page for details on which images will be updated, and the timeline on when the updates will take place.
37
+
cloud-init supports multiple input types, including a bash script or a cloud-init config. Review the 'cloud-init'[user-data](https://cloudinit.readthedocs.io/en/latest/topics/format.html) documentation.
38
+
- See [this](/azure/virtual-machines/linux/using-cloud-init#cloud-init-overview) page for details about which images will be updated, and the timeline for when the updates occur.
40
39
41
40
## Frequently asked questions
42
41
43
-
Q1. Will the Azure Linux Agent still be installed in the images?
42
+
Q1. Is the Azure Linux Agent still installed in the images?
44
43
45
-
A1. Yes, the Azure Linux Agent is required for Azure VM extensions. The provisioning functionality will be disabled.
44
+
A1. Yes, the Azure Linux Agent is required for Azure VM extensions. The provisioning functionality is disabled.
46
45
47
46
Q2. Can the Azure Linux Agent and cloud-init be installed in the same image?
48
47
49
-
A2. Yes. To ensure that there is no conflict, the Linux Agent provisioning code is disabled and will not run.
48
+
A2. Yes. To ensure that there is no conflict, the Linux Agent provisioning code is disabled and won't run.
50
49
51
-
Q3. How can I tell if my image has been provisioned by cloud-init?
50
+
Q3. How can I tell whether my image is provisioned by cloud-init?
52
51
53
-
A3. Run `cloud-init status` to see if cloud-init has run.
52
+
A3. Run `cloud-init status` to learn whether cloud-init ran.
54
53
55
54
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
This article provides a solution to an issue in which the Linux VM extension status is not reported after an Azure Linux Agent update to version 2.2.19.
18
+
This article provides a solution to a problem in which the Linux VM extension status is not reported after an Azure Linux Agent update to version 2.2.19.
19
19
20
20
## Symptoms
21
21
22
-
On a Linux virtual machine (VM) that's running on an instance of Microsoft Azure that has Azure Linux Agent 2.2.19 installed, you don't see the extension status being reported by using either the portal or Azure Command-Line Interface (Azure CLI).
22
+
On a Linux virtual machine (VM) that's running on an instance of Microsoft Azure that has Azure Linux Agent 2.2.19 installed, you don't see the extension status reported. This problem occurs in both the Azure portal or Azure Command-Line Interface (Azure CLI).
23
23
24
24
## Cause
25
25
26
26
This problem occurs because of a [known issue](https://github.com/Azure/WALinuxAgent/wiki/Known-Issues#2219---protocolerror-varlibwaagentgoalstate1xml-is-missing).
27
27
28
28
## Resolution
29
29
30
-
Microsoft is taking steps to automatically resolve this problem. For VMs that have been automatically resolved, you will see the following additional Microsoft extension installed on the affected VMs:
30
+
Microsoft is taking steps to automatically resolve this problem. For VMs that were automatically resolved, you see the following additional Microsoft extension installed on the affected VMs:
31
31
32
32
-**Extension publisher:** Microsoft.CPlat.Core
33
33
-**Extension type:** RunCommandLinux
34
34
35
-
You can use [Azure CLI](/cli/azure/install-azure-cli)to query the extensions that are assigned to a VM. To do this, run the following command:
35
+
You can use [Azure CLI](/cli/azure/install-azure-cli) to query the extensions that are assigned to a VM. To use this query, run the following command:
36
36
37
37
```Azure CLI
38
38
az vm extension list --vm-name <vmName> -g <resGroupName>
This article provides solutions to an issue in which connecting to a Linux virtual machine (VM) via Secure Shell (SSH) fails because the _/var/empty/sshd_ directory in RHEL, the _/var/lib/empty_ directory in SUSE, or the _/var/run/sshd_ directory in Ubuntu, doesn't exist, or it isn't owned by the root user, or it's group-writable or world-writable.
When you connect to a Linux virtual machine (VM) via SSH, the connection fails. You may receive the following error message about the affected directory, depending on your Linux distribution.
This article provides three methods to reset local Linux Virtual Machine (VM) passwords. If the user account is expired or you want to create a new account, you can use the following methods to create a new local admin account and regain access to the VM.
You can reset the password without attaching the OS disk to another VM. This method requires that the [Azure Linux Agent](/azure/virtual-machines/extensions/agent-linux) be installed on the affected VM.
Having access to the Serial Console and GRUB will improve recovery times of your IaaS Linux Virtual Machine in most cases. GRUB offers recovery options that otherwise would take longer to recover your VM.
0 commit comments