Introduction
Unimus version 2.7.1 introduced the automatic recognition and removal of unsolicited log messages (such as system logs, traps, or console messages) from the device CLI output stream.
This enhancement ensures that jobs running on network devices, particularly those with terminal monitor or similar logging settings enabled, will be less likely to fail with an “interaction error”
Before Unimus v2.7.1, when these log messages were encountered mid-job, they would interrupt the expected command-response sequence. Unimus would read the log message instead of the expected prompt or command output, leading to an INTERACTION_ERROR and subsequent job failure.
Configuration for Mass Config Push Jobs
While log stripping is enabled by default for Discovery and Backup jobs, it is disabled by default for Mass Config Push jobs. Note, terminal log messages that are identified will not cause the job to fail, instead they will be saved in the output of the device. This will create separate Output Groups if devices are not producing the same log message at the same time. If you simply wish to keep the Push job reports clean and focused only on the commands and responses, you can enable log stripping by modifying the Unimus configuration file.
The specific configuration argument to enable log message removal in Push jobs is:
-Dunimus.core.log-message-removal-active-in-push=true
Applying the Configuration
Note: After making any changes to the configuration file, you must Restart Unimus to apply the new setting.
1. Configuring on Windows
Environment | File Location |
Portable Installation | Create or edit a file named Unimus.l4j.ini in the same directory as the Unimus executable. |
Installer Installation | Edit the existing file Unimus.l4j.ini located in the installation directory (e.g., C:\Program Files\Unimus\). |
2. Configuring on Linux
Environment | File Location |
Standard Installation | Edit the contents of /etc/default/unimus. |