In Aria Suite Lifecycle, you're unable to Import or Trigger Inventory Sync of an Aria Operations for Logs cluster. The task fails at Stage 2 with a LCMVRLISYSTEM45018 error.
In the Aria Suite Lifecycle log /var/log/vrlcm/vmware_vrlcm.log we see the following errors:
2026-##-##T##:##:##.###Z ERROR vrlcm[####] [pool-3-thread-9] [c.v.v.l.p.v.VrliImportVcfWaterMarkingTask] -- Failed while creating SDDC Manager water mark for VMware Aria Operations for Logs , Check VMware Aria Operations for Logs is online and accessiblejava.net.ConnectException: Connection refused (Connection refused)
2026-##-##T##:##:##.###Z ERROR vrlcm[####] [pool-3-thread-9] [c.v.v.l.p.a.s.Task] -- Injecting task failure event. Error Code : 'LCMVRLISYSTEM45018', Retry : 'true', Causing Properties : '{ CAUSE :: skipTask === }'java.net.ConnectException: Connection refused (Connection refused)
Aria Operations for Logs 8.18.x
Aria Suite Lifecycle 8.18.x
Prior to performing an inventory sync or import, Aria Suite Lifecycles requires that each node in the Aria Operations for Logs cluster is able to resolve DNS and each node has its hostname properly configured. The hostname localhost is not valid for an Aria Operations for Logs node.
From KB 315950:
loginsight_set_hostname.service sets the hostname by
vmware-rpctool/usr/bin/vmware-rpctool 'info-get guestinfo.ovfEnv' | grep hostname
vmware-rpctool returns an empty value or no value, the hostname is set to the result of a reverse DNS query for the appliance VM's IP address.vmware-rpctool and reverse DNS lookup fail to return a value, the hostname is set to localhost.Log into each Aria Operations for Logs node via SSH using the root credential and note the hostname listed on the command line:
root@<hostname> [~]#
The <hostname> should be the same as the DNS shortname for the cluster node.
Reset the hostname of any node in the cluster which has localhost at the command prompt by following KB 315950.
Then shut down all the worker nodes within the Aria Operations for Logs cluster and reboot the primary node last. Once the primary node is started, we can then boot the worker nodes.