Installing missing plugins?


(Todde) #1

Hi,

I am trying out various things in OMDs check_mk. There I have noticed, that many plugins are missing which are mentioned within the official plugin list from Plugin LIst

Where do I get those plugins from and how do I install them on the monitored clients?

Cheers, todde


(Philipp Näther) #2
  1. Which OMD version exactly do you use? Check_mk RAW or OMD Labs? OMD Labs does not contain the most recent check_mk version!

  2. What are the missing plugins you are talking about for example? You have to differ between check plugins and agent plugins.

  3. You only can “install” agent plugins on the hosts (“monitored clients”). Check plugins reside on the cmk server and do not need installation or configuration per se. You COULD download the latest cmk raw package and extract agent and check plugins from it and copy it to the respective directories but it is not guaranteed newer plugins work on older versions.

  4. If you only need cmk features you probably should use check_mk raw edition which can easily be updated to newer versions. If you want particular OMD Labs features or packages, you should deal with having a slightly outdated cmk version or update cmk withing OMD Labs, which is not supported and could break your installation.


(Todde) #3

Hi

I am using omd 2.70 labs from a repository. Actually I didn’t think much of what I wanted. I just saw that that offers me an easy way to install check_mk. If it is posible to save my current Site and the config I put into it, I would consider switching to check_mk raw. The missing plugins I am looking for are “apache_status” and “mk_sshd_config”. I alreday downloaded the sources, but they are not included.

cheers, todde


(Philipp Näther) #4

I am not 100% sure if it is flawlessly possible to migrate from Labs to Raw, but just try it out. Nothing bad can happen. Do it this way:

  • check the cmk version of the labs 2.70 site
  • download and install the respective cmk raw version for your OS
  • create an omd backup of your old site
  • create a new site with the downloaded cmk raw version
  • restore the omd backup to the new site
  • download and install the latest cmk raw edition
  • update your new site to the latest cmk raw edition

If something does not work you simply delete the new site. You then can try to manually migrate the cmk configs in ~/etc/check_mk/ to a new site running the latest cmk version by simply copying the configs and import hosts via .csv. If you need performance data, it is also possible to copy these files but this will need some adjustments in user rights.

I checked my sites, apache_status is available since at least 1.2.8p25 and mk_sshd_config is available since at least 1.5.0p4.


(Todde) #5

Thanks for your detailled instruction. In the meanwhile i tried a different approach. I took an snaphot from my VM, just in case. Then I took a backup from my site with check_mk --backup. I deleted the site and deinstalled omd-labs. Ten I downloades check_mk raw from the official site and followed instructions from here.

Unfortunately dependencies weren’t installed, but I could fix that.Afterwards I created a new site and configure it with Appache2 listening on 0.0.0.0 insead of 127.0.0.1. Everything else was left as it was. Site seam s to run, but when I browse to https://myurl/SITE it only display a message, that site could not be found. Weird. Think I did everything correctly

root@nagios:~# netstat -tulpen | grep apache
tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 999 130627 57864/apache2
tcp6 0 0 :::80 :::* LISTEN 0 126646 56334/apache2
tcp6 0 0 :::443 :::* LISTEN 0 126650 56334/apache2

www-data 56337 0.0 0.4 162700 4708 ? S 10:13 0:00 /usr/sbin/apache2 -k start
www-data 56338 0.0 1.2 356300 11972 ? S 10:13 0:00 /usr/sbin/apache2 -k start
www-data 56339 0.0 1.2 356316 11972 ? S 10:13 0:00 /usr/sbin/apache2 -k start
www-data 56340 0.0 1.3 356404 12788 ? S 10:13 0:00 /usr/sbin/apache2 -k start
www-data 56341 0.0 1.3 356468 12896 ? S 10:13 0:00 /usr/sbin/apache2 -k start
www-data 56342 0.0 1.2 356292 11392 ? S 10:13 0:00 /usr/sbin/apache2 -k start
www-data 56477 0.0 1.2 356292 11392 ? S 10:14 0:00 /usr/sbin/apache2 -k start
root 56537 0.0 0.0 0 0 ? R 10:16 0:00 [kworker/u128:2]
SITE 57774 0.0 2.6 297524 25324 ? Sl 10:22 0:06 python /omd/sites/SITE/bin/mkeventd
SITE 57780 0.0 0.3 590048 3676 ? Ssl 10:22 0:00 /omd/sites/SITE/bin/rrdcached -t 4 -w 3600 -z 1800 -f 7200 -s SITE -m 660 -l unix:/omd/sites/SITE/tmp/run/rrdcached.sock -p /omd/sit
SITE 57800 0.0 0.1 155964 1640 ? S 10:22 0:00 /omd/sites/SITE/bin/npcd -d -f /omd/sites/SITE/etc/pnp4nagios/npcd.cfg
SITE 57822 0.0 0.6 1051700 6188 ? Ssl 10:22 0:03 /omd/sites/SITE/bin/nagios -ud /omd/sites/SITE/tmp/nagios/nagios.cfg
SITE 57864 0.0 1.0 102936 10232 ? Ss 10:22 0:00 /usr/sbin/apache2 -f /omd/sites/SITE/etc/apache/apache.conf
SITE 57871 0.0 0.3 102916 3740 ? S 10:22 0:00 /usr/sbin/apache2 -f /omd/sites/SITE/etc/apache/apache.conf
SITE 57873 0.0 7.3 315960 69808 ? S 10:22 0:03 /usr/sbin/apache2 -f /omd/sites/SITE/etc/apache/apache.conf
SITE 57908 0.0 7.3 315960 69808 ? S 10:23 0:03 /usr/sbin/apache2 -f /omd/sites/SITE/etc/apache/apache.conf

Any ideas?

cheers, todde


(Todde) #6

As I just noticed /opt/omd/sites/SITE/var/www is completely empty. I don’t think this is supposed to be.


(Philipp Näther) #7

Well that is kinda bad. check_mk --backup does not do a full site backup. omd backup should have been the way to backup your site. You did not have to delete the site nor omd labs. You can install many different omd versions and run many different sites at a time…

Why? The main apache process should be bound to 0.0.0.0:80 or :::80 by default. And for every omd site a child is forked that runs internally on 127.0.0.1:500x. The main apache process handles to the requests on 0.0.0.0 and forwards them internally to the child processes.
You kind of misconfigure your system right now.

That is normal.