问题描述
我有一组Ubuntu VM,将在它们上设置更新管理.第一个VM进行了2次运行以使其完全更新,但是第二个是一个真正的问题.
I have a set of Ubuntu VMs which I'm setting up Update Management on. The first VM took 2 runs to get it fully up to date, but the 2nd was a real problem.
在更新20次左右后出错,导致80个未安装.新的运行根本不会安装任何东西.在查看日志并手动运行第一个错误打包命令之后,该错误消息说运行"sudo dpkg --configure -a". 然后,这可以解除阻止"损坏的程序包,并且再次运行更新将允许某些操作通过,但只能等到下一个程序损坏为止.
It errored after 20 or so updates, leaving 80 not installed. New runs would simply not install anything. After looking at the logs and manually running the first erroring package command, the error message said to run "sudo dpkg --configure -a". This then 'unblocked' the broken package, and running the updates again allows some through, but only until the next one broke.
遵循相同的过程表示需要相同的手动修复.
Following the same process indicated that the same manual fix was required.
这是Linux更新管理的正常过程吗?
Is this the normal procedure for Linux Update Management?
推荐答案
欢呼声
这篇关于Azure Linux VM更新管理中断,需要手动干预的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!