This KB describes the error messages observed when collecting RSI (Request Support Information) on an MX304 router.

As part of the RSI process, the command "show vmhost support-info" is executed, which comprehensively collects vmhost logs using various cat commands. Some of these commands attempt to access files that do not exist on the MX304, leading to the display of error messages.
These messages are specifically generated by the following two cat commands.
Please note that these error messages do not have any functional impact, and therefore can be safely ignored.

cat /var/log/audit/audit.log
cat /var/log/lclksyncd.log

The output below shows the test results.

user@mx304-re0> show vmhost support-info | match "cat /|cat:" | no-more
vmhost# cat /proc/cpuinfo
vmhost# cat /proc/meminfo
vmhost# cat /var/log/daemon.log
vmhost# cat /var/log/syslog
vmhost# cat /var/log/auth.log
vmhost# cat /var/log/audit/audit.log
cat: /var/log/audit/audit.log: No such file or directory
vmhost# cat /var/log/lcmd.log
vmhost# cat /var/log/lclksyncd.log
cat: /var/log/lclksyncd.log: No such file or directory
vmhost# cat /var/log/resild
vmhost# cat /var/log/libdrv.log
vmhost# cat /etc/os-release

user@mx304-re0> show log messages| match cat:
Jan 11 11:11:11.111  mx304-re0 vhclient.XXXXX.daemon[XXXXX]: cat: /var/log/audit/audit.log: No such file or directory :error[1]
Jan 11 11:11:13.258  mx304-re0 vhclient.XXXXX.daemon[XXXXX]: cat: /var/log/lclksyncd.log: No such file or directory :error[1]

The issue has been resolved under PR1913540.
The fix is included in Junos 26.1R1 and later releases.

< audit.log >
The audit.log file is no longer collected on all platforms that use vmhost. This file was available in earlier versions of vmhost; however, it no longer exists in recent versions, which causes the error message to appear. Another reason for its removal is that even when it was available, the log did not contain information useful for debugging.

< lclksyncd.log >
The lclksyncd.log file is now filtered out and not collected only on the MX304. The lclksyncd daemon runs on the vmhost side to manage timing hardware components. Because the MX304 has a slightly different timing architecture, the required daemons and components run on the line card side instead of on the RE. As a result, the file does not exist on the RE, which leads to the error message being displayed.