Error: Remote Logging Not configured alarms after NSX upgrade to 4.2.3
Article ID: 447067
Updated On:
Products
Issue/Introduction
- After upgrading VMware NSX to version 4.2.3 or later, an alarm stating "Remote Logging not configured" is triggered on one or more NSX Manager nodes.
- This issue may appear on a single manager node while others in the cluster remain in a normal state or may appear for all three managers.
- You may notice that syslog configuration is missing in the manager or edge nodes after the upgrade.
- You are using Aria Operations for Logs as syslog server
- In
/var/log/syslogyou see logs similar to:
2026-07-02T10:21:18.676Z ############## NSX 73621 - [nsx@6876 comp="nsx-manager" subcomp="node-mgmt" username="root" level="ERROR" errorCode="NOD110"] Error adding liagent to runlevels, rc=1, err=update-rc.d: error: unable to read /etc/init.d/liagentd
Environment
VMware NSX 4.2.3 and later
Cause
The liagent in the impacted versions changed its registration method as a systemd service and as a result NSX nodes fails to inherit the configuration from node profile.
Resolution
This is a known issue impacting VMware NSX and fixed in NSX 4.2.4
For a workaround, refer to the resolution section in KB: Aria Operations for Logs cannot be set as logging target in NSX
Additional Information
If version prior to NSX 4.2.3 and if you don't see the logs, refer below KBs for similar issues
Remote logging not configured alarm appears on NSX Manager node after upgrade
Feedback
