Nagios Support Forum

Hi,

We are monitoring Large unix file system monitoring in nagios Xi . we could not get all file system information in Status Information tab,

So we did not get the some file system alert from nagios xi.

Kindly let us know how to bring all file system ( large file system ) under nagios xi monitoring

We will need some more information in order to troubleshoot the issue.

1. Show us the actual check, run from the command line along with the output of it.
2. Also, show us a screenshot of error that you see in the Status Information tab.
3. When you say that you didn't get some file system alerts from Nagios XI, you mean you didn't get notifications, correct? Did the service go to a hard, non-ok state? Show us screenshots of the State History and Notifications reports for this service for the relevant timeperiod.
4. Who has issues with not receiving notifications - a specific contact, contact group, all contacts?

Hi,


Please find the enclosed.

bash-4.3# ./check_disk -w 90% -c 95% -l
DISK CRITICAL - free space: / 1373 MB (53% inode=92%); /usr 3453 MB (37% inode=83%); /var 940 MB (15% inode=92%); /tmp 2515 MB (27% inode=98%); /home 1457 MB (47% inode=98%); /proc 0 MB (0% inode=-); /opt 1782 MB (31% inode=92%); /Reuse 24730 MB (11% inode=54%); /admin 511 MB (99% inode=99%); /opentext/java 5118 MB (99% inode=99%); /oracle 5118 MB (99% inode=99%); /usr/local 867 MB (84% inode=99%); /usr/sap/JE3 15357 MB (99% inode=99%); /var/adm/ras/livedump 511 MB (99% inode=99%); /usr/sap/JE3/JERS12 15222 MB (99% inode=99%); /usr/sap/JE3/JC00 20076 MB (99% inode=99%); /usr/sap/JE3/SCS02 15222 MB (99% inode=99%); /opentext/tcp 10126 MB (99% inode=99%); /sapmnt/JE3 40510 MB (99% inode=99%); /usr/sap/transJE3 20191 MB (99% inode=99%); /usr/local/pgp 983 MB (96% inode=99%); /saptech 13901 MB (38% inode=58%); /saptech/entrust 5046 MB (99% inode=99%); /saptech/pgp 5046 MB (99% inode=99%); /opentext/tomcat 5062 MB (99% inode=99%); /opentext/hdsk1 10021 MB (98% inode=99%); /recall 14164 MB (98% inode=99%); /opentext/burnbuffer 6832 MB (14% inode=99%); /opentext/buffer2 9122 MB (89% inode=84%); /opentext/dp 8421 MB (82% inode=79%); /opentext/archivesw 1901 MB (17% inode=78%); /opentext/buffer 85696 MB (23% inode=19%); /opentext/oraredomirr 6078 MB (99% inode=99%); /opentext/oralogs 14017 MB (91% inode=99%); /opentext/oraredoarch 6078 MB (99% inode=99%); /opentext/dbindex 10326 MB (46% inode=99%); /opentext/oracle 13628 MB (53% inode=71%); /opentext/dbdata 21009 MB (68% inode=99%); /usr/local/shared_print 998 MB (98% inode=99%); /hpoms 117372 MB (25% inode=91%); /oracle/JE3 20254 MB (99% inode=99%); /oracle/stage 30414 MB (99% inode=99%); /oracle/JE3/sapreorg 10142 MB (99% inode=99%); /oracle/JE3/sapdata3 50733 MB (99% inode=99%); /oracle/JE3/sapdata4 50733 MB (99% inode=99%); /oracle/JE3/sapdata2 50733 MB (99% inode=99%); /oracle/JE3/sapdata1 50733 MB (99% inode=99%); /oracle/JE3/saparch 5062 MB (99% inode=99%); /oracle/JE3/origlogB 5062 MB (99% inode=99%); /oracle/JE3/oraarch 20254 MB (99% inode=99%); /oracle/JE3/origlogA 5062 MB (99% inode=99%); /oracle/JE3/mirrlogB 5062 MB (99% inode=99%); /oracle/JE3/mirrlogA 5062 MB (99% inode=99%); /oracle/JE3/102_64 20254 MB (99% inode=99%); /oracle/JE3/112_64 20254 MB (99% inode=99%);| /=1186MB;255;128;0;2560 /usr=5762MB;921;460;0;9216 /var=5203MB;614;307;0;6144 /tmp=6700MB;921;460;0;9216 /home=1614MB;307;153;0;3072 /proc=2147483647MB;2147483647;2147483647;0;2147483647 /opt=3849MB;563;281;0;5632 /Reuse=184165MB;20889;10444;0;208896 /admin=0MB;51;25;0;512 /opentext/java=1MB;511;256;0;5120 /oracle=1MB;511;256;0;5120 /usr/local=156MB;102;51;0;1024 /usr/sap/JE3=2MB;1535;768;0;15360 /var/adm/ras/livedump=0MB;51;25;0;512 /usr/sap/JE3/JERS12=17MB;1535;768;0;15360 /usr/sap/JE3/JC00=65MB;2029;1015;0;20300 /usr/sap/JE3/SCS02=17MB;1535;768;0;15360 /opentext/tcp=33MB;1023;512;0;10240 /sapmnt/JE3=130MB;4095;2048;0;40960 /usr/sap/transJE3=129MB;2047;1024;0;20480 /usr/local/pgp=33MB;102;51;0;1024 /saptech=21745MB;3571;1785;0;35716 /saptech/entrust=33MB;511;256;0;5120 /saptech/pgp=33MB;511;256;0;5120 /opentext/tomcat=17MB;511;256;0;5120 /opentext/hdsk1=139MB;1023;512;0;10240 /recall=255MB;1535;768;0;15360 /opentext/burnbuffer=39207MB;4607;2304;0;46080 /opentext/buffer2=1045MB;1023;512;0;10240 /opentext/dp=1805MB;1023;512;0;10240 /opentext/archivesw=8835MB;1075;537;0;10752 /opentext/buffer=276124MB;36249;18124;0;362496 /opentext/oraredomirr=17MB;614;307;0;6144 /opentext/oralogs=1231MB;1535;768;0;15360 /opentext/oraredoarch=17MB;614;307;0;6144 /opentext/dbindex=12120MB;2252;1126;0;22528 /opentext/oracle=11864MB;2559;1280;0;25600 /opentext/dbdata=9544MB;3071;1536;0;30720 /usr/local/shared_print=17MB;102;51;0;1024 /hpoms=349671MB;46796;23398;0;467968 /oracle/JE3=65MB;2047;1024;0;20480 /oracle/stage=66MB;3071;1536;0;30720 /oracle/JE3/sapreorg=17MB;1023;512;0;10240 /oracle/JE3/sapdata3=66MB;5119;2560;0;51200 /oracle/JE3/sapdata4=66MB;5119;2560;0;51200 /oracle/JE3/sapdata2=66MB;5119;2560;0;51200 /oracle/JE3/sapdata1=66MB;5119;2560;0;51200 /oracle/JE3/saparch=17MB;511;256;0;5120 /oracle/JE3/origlogB=17MB;511;256;0;5120 /oracle/JE3/oraarch=65MB;2047;1024;0;20480 /oracle/JE3/origlogA=17MB;511;256;0;5120 /oracle/JE3/mirrlogB=17MB;511;256;0;5120 /oracle/JE3/mirrlogA=17MB;511;256;0;5120 /oracle/JE3/102_64=65MB;2047;1024;0;20480 /oracle/JE3/112_64=65MB;2047;1024;0;20480


we are using larger filesystem in unix server. But we did not capture all filesystems in Nagios Xi . Please find the screen shot in attachment.

We only got the few file system in nagios xi. In that file system only route to snow ticket.

In Command Prompt Check_disk show all file systems and Capture the warning and critical status correctly .


From nagiosxi console status view, It did not show all file system . But it shows correctly warning and critical status.


if Rest of the filesystem is full . nagios not provide the file system notification.

please check and let us know.

Where is the "cut off" (how many characters) in the UI, under the Status Information column?

Most probably, you are hitting the 256 characters limit in the db. You would need to update the db tables, so that you could store more data in them. Please follow the steps, outlined in our "Nagios XI - Status Information Cut Off At 256 Characters" KB article here:

https://support.nagios.com/kb/article/n ... s-478.html

Let us know if this helped. Thank you!