Azure / Azure/LinuxPatchExtension

Service fails to start on 1.6.65 - wrong directory

Abierto
#369 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
12
Forks
20
Merge medio
6 d 4 h
PR fusionados (30 d)
1

Descripción

Two Ubuntu 24.04.4 LTS servers reported that the MsftLinuxPatchAutoAssess stopped running this morning (7/28/2026). When attempting to start the service, get the following error message:
Job for MsftLinuxPatchAutoAssess.service failed because the control process exited with error code.
See "systemctl status MsftLinuxPatchAutoAssess.service" and "journalctl -xeu MsftLinuxPatchAutoAssess.service" for details.

Running 'systemctl status MsftLinuxPatchAutoAssess.service' reports the message:
/bin/bash: /var/lib/waagent/Microsoft.CPlat.Core.LinuxPatchExtension-1.6.62/MsftLinuxPatchAutoAssess.sh: No such file or directory

This is quite correct, considering the new version is now 1.6.65 and 1.6.62 no longer exists.

I ran 'sudo apt --reinstall install walinuxagent' but ended up with the same result.

Having a look in the /var/lib/waagent/Microsoft.CPlat.Core.LinuxPatchExtension-1.6.65/ directory, the MsftLinuxPatchAutoAssess.sh script doesn't exist anymore, so I'm not seeing a way to fix the /etc/systemd/system/MsftLinuxPatchAutoAssess.service launcher.

Please forgive any miswording in my description. I'm a Linux tinkerer, not a full-blown developer.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start by checking the reported systemctl status and journalctl output, then inspect /etc/systemd/system/MsftLinuxPatchAutoAssess.service alongside the 1.6.65 extension directory under /var/lib/waagent. Confirm why the launcher still references 1.6.62 and whether the expected MsftLinuxPatchAutoAssess.sh is packaged in 1.6.65; done means the service starts using the current installation.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
bash, linux, ubuntu
Área
devops, operating-systems
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Necesita aclaración
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.