Service fails to start on 1.6.65 - wrong directory

Open
#369 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
bash, linux, ubuntu
Domain
devops, operating-systems

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
12
Forks
20
Avg merge
3d 2h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/LinuxPatchExtension

All issues in Azure/LinuxPatchExtension

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.