Back to OP5 Monitor FAQ

Understanding the Livestatus Multitool Daemon (LMD)

Introduction Copied

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.

Configuration Copied

**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 Copied

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:

/opt/monitor/var/rw/live_tmp

If you wish to query LMD you can use this socket path:

/opt/monitor/var/rw/live

Troubleshooting Copied

Make sure the service is running Copied

Make sure that both Naemon and the LMD service is running

EL7:

systemctl status naemon
systemctl status lmd

Check the logs Copied

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 Copied

EL7:

systemctl restart naemon
systemctl restart lmd

Reverting to old functionality Copied

It is possible to disable LMD, and get information directly from Livestatus:

EL7:

systemctl stop lmd
ln -s /opt/monitor/var/rw/live_tmp /opt/monitor/var/rw/live
mon restart

To enable LMD again:

systemctl enable lmd --now

Making the change permanent Copied

systemctl disable lmd

To enable LMD again:

service lmd start

Known issues Copied

The user interface is showing only 0 as values Copied

This could potentially be caused by LMD exceeding the limit of Livestatus’ response size. See this article on how to fix it.

["Geneos"] ["FAQ"]

Was this topic helpful?