Azure Batch 在池上安装 Blob 存储会导致错误 "Counld not install package"

Question

我有一个 Azure Batch 池，其中安装了三个 Blob 存储容器。但是，当节点第一次启动时，它会出现以下错误:

查看日志，节点似乎在安装 blobfuse 包时遇到问题。反复收到此错误消息:

2020-03-11T09:15:48,654579941+00:00 - INFO: Downloading: https://packages.microsoft.com/keys/microsoft.asc as microsoft.asc
2020-03-11T09:15:48,770319520+00:00 - INFO: Downloading: https://packages.microsoft.com/config/ubuntu/16.04/prod.list as /etc/apt/sources.list.d/microsoft-prod.list
Hit:1 http://azure.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://azure.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://azure.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Get:5 https://packages.microsoft.com/ubuntu/16.04/prod xenial InRelease [4,002 B]
Get:6 https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages [124 kB]
Fetched 128 kB in 0s (383 kB/s)
Reading package lists...
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
...

2020-03-11T09:16:53,361634408+00:00 - ERROR: Could not install packages (apt): blobfuse

然后节点进入状态不可用，直到我手动重新启动它们，这将“修复”问题，然后节点开始处理任务。

任务应该以提升的权限运行:

UserIdentity = new UserIdentity(
                new AutoUserSpecification(
                      elevationLevel: ElevationLevel.Admin,
                      scope: AutoUserScope.Pool
                  )
              ),

更新 1

我无法解决这个问题，所以我决定解决它。调整池大小或重新创建池没有帮助。相反，我在 Docker 镜像中安装了 blobfuse，并在任务本身中安装了 blob 存储容器。这工作得很好。

Answer 1

您的方法看起来不错，很高兴重新启动修复了它，在这种特定情况下，这是正确的修复以及重新调整大小。

感谢分享日志，这看起来像是 使用 Blobfuse 安装失败的问题

大的泄露是:**错误:无法安装软件包(apt):blobfuse**是最大的指标，本质上在引擎盖下节点看起来要安装 blobfuse 并且看起来像一些进程有一个长时间并行运行的 apt install。 The cause of this error is detailed here E: Could not get lock /var/lib/dpkg/lock-frontend - open .

2个可能的解决方案

• 就像您提到的重新启动修复了它。
• 另一个选项是调整池的大小。 或更好:重新创建池，然后尝试。

为什么重新启动或调整大小可以修复它:本质上，在这两种情况下，VM 都会在批处理结束时调用加入池进程并刷新内存，这将有助于解除 blobfuse 的锁定场景。在批处理节点级别，我们可以尝试某种退避机制。我也会密切关注 blobfuse 以及是否有内部原因导致此 https://github.com/Azure/azure-storage-fuse

希望这有帮助。