LMD (Livestatus Multitool Daemon) is a a transparent livestatus proxy and caching mechanism included in Monitor 8. LMD allows the user to access monitoring information in OP5 Monitor during configuration saves, or in other situations when the monitoring core (Naemon) is temporary unavailable.
- The LMD configuration file is located at: /etc/op5/lmd/lmd.ini
- The configuration option "StaleBackendTimeout", decides for how long LMD will serve data after Livestatus/Naemon is down. After this timeout no monitoring data will be accessible in the GUI. In setups were configuration saves duration often exceeds the StaleBackendTimeout, the timeout can be increase to improve the experience.
Note: In OP5 Monitor versions 8.0.0-8.0.5 the configuration file is located at: /opt/monitor/var/lmd/lmd.ini
Differences between LMD & Livestatus
The differences between LMD and Livestatus is explained in detail on the projects github page.
Querying Livestatus instead of LMD
If you wish to directly query Livestatus (for example due to the above mentioned differences, or for troubleshooting purposes) you can do so at the following socket:
If you wish to query LMD you can use this socket path:
Make sure the service is running
Make sure that both Naemon and the LMD service is running
systemctl status naemon
systemctl status lmd
Check the logs
Logs are stored at: /var/log/op5/lmd.log
Note: In OP5 Monitor versions 8.0.0-8.0.5 the log file is located at: /opt/monitor/var/lmd/lmd.log
Restart Monitor and LMD
systemctl restart naemon
systemctl restart lmd
Reverting to old functionality
It is possible to disable LMD, and get information directly from Livestatus:
systemctl stop lmd
ln -s /opt/monitor/var/rw/live_tmp /opt/monitor/var/rw/live
To enable LMD again:
systemctl enable lmd --now
Making the change permanent
systemctl disable lmd
To enable LMD again:
service lmd start
The user interface is showing only 0 as values
This could potentially be caused by LMD exceeding the limit of Livestatus' response size. See this article on how to fix it.