Troubleshooting an advanced cluster on Microsoft Azure
I restarted the Secure Agent machine and now the status of the advanced cluster is Error.
Make sure that the Secure Agent machine and the Secure Agent are running. Then, stop the advanced cluster in Monitor. In an Azure environment, the cluster might take 10 minutes to stop. After the cluster stops, you can run a job to start the cluster again.
The init script failed with the following standard error on some nodes in the advanced cluster:
Created symlink from /etc/systemd/system/apt-daily.service to /dev/null. Created symlink from /etc/systemd/system/apt-daily-upgrade.service to /dev/null. Removed symlink /etc/systemd/system/timers.target.wants/apt-daily.timer. Removed symlink /etc/systemd/system/timers.target.wants/apt-daily-upgrade.timer. 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?
The init script failed because the node was running an internal process at the same time as the init script. If you continue to see the error, wait for the internal process to complete by placing a sleep command for the required duration in your init script.
For example, you might use a sleep command as follows:
#!/bin/sh
while(sudo lsof /var/lib/dpkg/lock-frontend) do echo "Sleeping 10s" sleep 10 done