Availability data is not available when monitoring engine dn

[dfmco]

Nagios v 5.5.8 on CentOS 7 RPM install

Please reference locked ticket:
Availability data is not available when monitoring engine is
Topic locked
Availability data is not available when monitoring engine is
Postby raamardhani7 » Mon Apr 24, 2017 4:47 am

Seems we are having the same issue. How can we tell if RAMDISK is loaded or not as I think we did have a RAMDISK issue and I believe it may now be removed. I looked at the file mentioned in the ticket:
/usr/local/nagios/etc/commands.cfg

But nothing leaped out.

[scottwilkerson]

Run the following and report the results

Code: Select all

df -h
df -i
ls -al /var/nagiosramdisk/

[dfmco]

[root@bm-qr-nagiosxi ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 50G 6.3G 44G 13% /
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 410M 3.5G 11% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda1 1014M 296M 719M 30% /boot
/dev/mapper/centos-home 42G 96M 42G 1% /home
tmpfs 500M 500M 0 100% /var/nagiosramdisk
tmpfs 783M 0 783M 0% /run/user/1000
tmpfs 783M 0 783M 0% /run/user/0
[root@bm-qr-nagiosxi ~]# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/centos-root 26214400 74229 26140171 1% /
devtmpfs 998234 371 997863 1% /dev
tmpfs 1001206 1 1001205 1% /dev/shm
tmpfs 1001206 646 1000560 1% /run
tmpfs 1001206 16 1001190 1% /sys/fs/cgroup
/dev/sda1 524288 356 523932 1% /boot
/dev/mapper/centos-home 21557248 4180 21553068 1% /home
tmpfs 1001206 625522 375684 63% /var/nagiosramdisk
tmpfs 1001206 1 1001205 1% /run/user/1000
tmpfs 1001206 1 1001205 1% /run/user/0
[root@bm-qr-nagiosxi ~]# ls -al /var/nagiosramdisk/
total 440
drwxrwxrwt 4 nagios nagios 140 Mar 5 22:27 .
drwxr-xr-x. 21 root root 4096 Aug 13 2018 ..
-rw-r--r-- 1 nagios nagios 0 Mar 5 22:27 host-perfdata
-rw-r--r-- 1 nagios nagios 445648 Mar 5 10:00 objects.cache
-rw-r--r-- 1 nagios nagios 0 Mar 5 22:27 service-perfdata
drwxrwxr-x 5 nagios nagios 100 Jan 10 15:11 spool
drwxrwxr-x 2 nagios nagios 40 Mar 5 10:00 tmp

[dfmco]

I did some more digging. It is possible that I may have restored a backup of the system with a RAM disk configured but the new system does not have a RAM disk. The original system may have been an install and the new one is using rpm so we can update via Ansible.

Here is the ramdisk.service:
[Unit]
Description=Ramdisk
Requires=local-fs.target
After=local-fs.target
Before=nagios.service
[Service]
Type=simple
RemainAfterExit=yes
Restart=always
ExecStartPre=/usr/bin/mkdir -p -m 775 /var/nagiosramdisk /var/nagiosramdisk/tmp /var/nagiosramdisk/spool /var/nagiosramdisk/spool/checkresults /var/nagiosramdisk/spool/xidpe /var/nagiosramdisk/spool/perfdata
ExecStartPre=/usr/bin/mount -t tmpfs -o size=500m tmpfs /var/nagiosramdisk
ExecStartPre=/usr/bin/mkdir -p -m 775 /var/nagiosramdisk /var/nagiosramdisk/tmp /var/nagiosramdisk/spool /var/nagiosramdisk/spool/checkresults /var/nagiosramdisk/spool/xidpe /var/nagiosramdisk/spool/perfdata
ExecStart=/usr/bin/chown -R nagios:nagios /var/nagiosramdisk
[Install]
WantedBy=multi-user.target

And here is a search for ramdisk in /usr/local/nagios/etc/*

[root@bm-qr-nagiosxi ~]# grep nagiosramdisk /usr/local/nagios/etc/*
/usr/local/nagios/etc/commands.cfg: command_line /bin/mv /var/nagiosramdisk/host-perfdata /var/nagiosramdisk/spool/xidpe/$TIMET$.perfdata.host
/usr/local/nagios/etc/commands.cfg: command_line /bin/mv /var/nagiosramdisk/service-perfdata /var/nagiosramdisk/spool/xidpe/$TIMET$.perfdata.service
grep: /usr/local/nagios/etc/hosts: Is a directory
grep: /usr/local/nagios/etc/import: Is a directory
/usr/local/nagios/etc/nagios.cfg:service_perfdata_file=/var/nagiosramdisk/service-perfdata
/usr/local/nagios/etc/nagios.cfg:host_perfdata_file=/var/nagiosramdisk/host-perfdata
/usr/local/nagios/etc/nagios.cfg:check_result_path=/var/nagiosramdisk/spool/checkresults
/usr/local/nagios/etc/nagios.cfg:object_cache_file=/var/nagiosramdisk/objects.cache
/usr/local/nagios/etc/nagios.cfg:status_file=/var/nagiosramdisk/status.dat
/usr/local/nagios/etc/nagios.cfg:temp_path=/var/nagiosramdisk/tmp
grep: /usr/local/nagios/etc/pnp: Is a directory
grep: /usr/local/nagios/etc/services: Is a directory
grep: /usr/local/nagios/etc/static: Is a directory

[dfmco]

[root@bm-qr-nagiosxi ~]# ls /var/nagiosramdisk/spool/xidpe | wc -l
0
[root@bm-qr-nagiosxi ~]# ls /var/nagiosramdisk/spool/perfdata/ | wc -l
625721
[root@bm-qr-nagiosxi ~]# ls /var/nagiosramdisk/spool/checkresults/ | wc -l
0
[root@bm-qr-nagiosxi ~]# grep RAMDISK_SIZE /etc/sysconfig/nagios
grep: /etc/sysconfig/nagios: No such file or directory
[root@bm-qr-nagiosxi ~]# service npcd status
NPCD running (pid 16722).

Looks like performance data is killing it.

[scottwilkerson]

Can you show the results of the following

Code: Select all

service npcd status
grep perfdata_spool_dir /usr/local/nagios/etc/pnp/npcd.cfg