Azure Batch 在池上安装 blob 存储导致错误“无法安装包”

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

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

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

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

更新 1

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

Answer 1

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

感谢分享日志，这看起来像是failure 到Installation with the Blobfuse 的问题

最大的好处是：**ERROR: Could not install packages (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

希望这会有所帮助。

Answer 2

我遇到了完全相同的问题，因为我正在创建动态池和任务，因此无法手动介入并重新启动。

我的解决方法是将批处理帐户链接到存储帐户，然后将资源文件指定为任务的一部分。这使容器在任务的工作目录中可见。

这是我在 NodeJS 中的示例，它应该可以转换为您选择的语言。

{
        id: taskId,
        commandLine: "",
        containerSettings: taskContainerSettings,
        environmentSettings: [
            {
                name: "USER_ID",
                value: userId
            },
            {
                name: "RUN_ID",
                value: runId
            }],
        resourceFiles: [{"autoStorageContainerName": userId}]
};