# Linux Release 4.0.9 – Group Settings Sync and Failed Logins Reliability

**URL:** <https://community.watchmanmonitoring.com/t/linux-release-4-0-9-group-settings-sync-and-failed-logins-reliability/2987>\
**Category:** Announcements\
**Created:** [July 9, 2026, 11:07pm UTC](https://community.watchmanmonitoring.com/t/linux-release-4-0-9-group-settings-sync-and-failed-logins-reliability/2987 "2026-07-09T23:07:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ianalexander](https://community.watchmanmonitoring.com/user_avatar/community.watchmanmonitoring.com/ianalexander/32/711_2.png) [@ianalexander](https://community.watchmanmonitoring.com/u/ianalexander)\
**Post date:** [July 9, 2026, 11:07pm UTC](https://community.watchmanmonitoring.com/t/linux-release-4-0-9-group-settings-sync-and-failed-logins-reliability/2987/1 "2026-07-09T23:07:36Z")

</div>

We’re releasing Linux Agent 4.0.9 today. This is a focused follow-up to 4.0.7 with two reliability fixes we’ve seen on real customer Linux hosts.

Upgrade through your normal package workflow:

```auto
sudo apt-get update && sudo apt-get install --only-upgrade monitoringclient # Debian/Ubuntu

```

```auto
sudo dnf upgrade monitoringclient # RHEL family

```

After upgrading, `monitoringclient version` should report 4.0.9.

* * *

## **Dashboard group changes now stick**

Some Linux computers were moving to a new group in the dashboard, then reporting back under the old group on the next check-in. That made it look like the dashboard was ignoring your change.

4.0.9 fixes that. Group, asset ID, and related contact fields from the dashboard are now kept in sync with what the agent reports locally.

If you hit this on a host, upgrade to 4.0.9, set the group once more in the dashboard if needed, and let the next check-in run.

* * *

## **Failed Logins recovers after journal changes**

On some Ubuntu and systemd-based hosts, the Failed Logins plugin could get stuck in a warning state after `journald` was restarted or reconfigured—even when SSH login monitoring was otherwise working fine.

4.0.9 clears that stuck state and picks the best available log source again, including falling back to `/var/log/auth.log` when it’s available.

If Failed Logins was warning on every check-in after a journal or logging change, upgrading should resolve it. If a warning persists after upgrade, contact support and we can walk you through a quick one-time reset.

* * *

We’re continuing to improve the Go Linux agent. If you notice anything that still doesn’t match the legacy agent’s behavior, let us know through [Watchman Monitoring Support](https://support.watchmanmonitoring.com/) or the [Community Forum](https://community.watchmanmonitoring.com/).

Ian, Garrett & Allen