docs: Changed check_mk service from xinetd to systemd (#8101)

* changed check_mk service from xinetd to systemd

* added xinetd section
This commit is contained in:
Lutz Willek 2018-01-26 21:51:45 +01:00 committed by Neil Lathwood
parent 2755763758
commit 881e0fe4c1

View File

@ -13,17 +13,28 @@ In config.php, enable Proxmox:
$config['enable_proxmox'] = 1;
```
Then, install [librenms-agent](http://docs.librenms.org/Extensions/Applications/) on the machines running Proxmox and enable the Proxmox-script using:
Then, install git and [librenms-agent](http://docs.librenms.org/Extensions/Applications/) on the machines running Proxmox and enable the Proxmox-script using:
```bash
cp /opt/librenms-agent/agent-local/proxmox /usr/lib/check_mk_agent/local/proxmox
chmod +x /usr/lib/check_mk_agent/local/proxmox
```
Then, restart the xinetd service
Then, enable and start the check_mk service using systemd
```bash
/etc/init.d/xinetd restart
cp /opt/librenms-agent/check_mk@.service /opt/librenms-agent/check_mk.socket /etc/systemd/system
systemctl daemon-reload
systemctl enable check_mk.socket && systemctl start check_mk.socket
```
Then in LibreNMS active the librenms-agent and proxmox application flag for the device you are monitoring.
You should now see an application in LibreNMS, as well as a new menu-item in the topmenu, allowing you to choose which cluster you want to look at.
### Note, if you want to use use xinetd instead of systemd
Its possible to use the librenms-agent started by xinetd instead of systemd. One use case is if you are forced to use a old Proxmox installation.
After installing the librenms-agent (see above) please copy enable the xinetd config, then restart the xinetd service:
```bash
cp check_mk_xinetd /etc/xinetd.d/check_mk
/etc/init.d/xinetd restart
```