Okay so I did what you asked.
It didn't worked, the custom notifications didn't worked for that service of course.
With the copy, it didn't worked neither :/
I created another user and contact and I tried to send to him, it didn't worked, I tried to create a new template based on the old one, it didn't worked neither...
Error loading a mib
Re: Error loading a mib
Try upgrading to the XI version 5.3.1 which just came out. Maybe something didn't get updated on your system and doing this one will work.
If it still fails, can you PM me your System Profile?
To send us your system profile. login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and PM it to me.
If it still fails, can you PM me your System Profile?
To send us your system profile. login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and PM it to me.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Error loading a mib
I send you a PM 
Oh and I just tried to add a linux workstation, and it works for his disk usages ... that means either "check_xiservice_snmp_win_storage.pl" or "check_snmp_storage.pl" or "xiwizard_windowssnmp_storage" are wrong since Linux do not uses the same !
Oh and I just tried to add a linux workstation, and it works for his disk usages ... that means either "check_xiservice_snmp_win_storage.pl" or "check_snmp_storage.pl" or "xiwizard_windowssnmp_storage" are wrong since Linux do not uses the same !
Re: Error loading a mib
Thanks for the profile.
I did not see the Drive D service in the config file for the srvatih host which leads me to be-leave that the config settings in the sql database are not synced up with the flat files.
To fix this, follow the procedure below and see if the notifications start to work for that service check.
Go to the Core Config Manager
Under "Tools", click "Write Config Files"
Click the click the "Write" button, then the "Delete" button then click the "Write" button and then the "Verify" button
If you get any errors, resolve them and click on the "Write", "Verify" until all of the errors are resolved.
Click the Apply Configuration link and click the "Apply Configuration" button
I did not see the Drive D service in the config file for the srvatih host which leads me to be-leave that the config settings in the sql database are not synced up with the flat files.
To fix this, follow the procedure below and see if the notifications start to work for that service check.
Go to the Core Config Manager
Under "Tools", click "Write Config Files"
Click the click the "Write" button, then the "Delete" button then click the "Write" button and then the "Verify" button
If you get any errors, resolve them and click on the "Write", "Verify" until all of the errors are resolved.
Click the Apply Configuration link and click the "Apply Configuration" button
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Error loading a mib
Thanks for the new profile. I still do not see the Drive D: configuration for that host so something is corrupt with that entry.
Best thing to do is to delete it, Apply the Config and recreate it and Apply the config again.
Try that and let us know if that works.
Best thing to do is to delete it, Apply the Config and recreate it and Apply the config again.
Try that and let us know if that works.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Error loading a mib
In fact, there is no Drive D: in srvatih ... But there is a C: for example, and notifications are not working for this one ! And neither for all the others disk usage. I just deleted one disk usage service, i created again and still doesn't work .. That is so weird
Re: Error loading a mib
In your last profile, I looked at the "Drive C: Disk Usage" for the host called srvatih and found that the Notification Interval is set to 720 minutes (12 Hours).
And the Notification Time Period and the Check Period is set for 06:00-18:00, everyday of the week.
So if that service is down during that period, it will not notify you as the Notification interval will fall outside of the time periods.
Try changing the Notification Period to a shorter time or increase the check/notification period and that should fix it for you.
Also, make sure those periods are set in the users account time periods.
And the Notification Time Period and the Check Period is set for 06:00-18:00, everyday of the week.
So if that service is down during that period, it will not notify you as the Notification interval will fall outside of the time periods.
Try changing the Notification Period to a shorter time or increase the check/notification period and that should fix it for you.
Also, make sure those periods are set in the users account time periods.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Error loading a mib
That is not the problem, because the custom notifications still doesn't work, even forced and broadcasted ...
Re: Error loading a mib
Run the following command as root on the XI server,
then run a custom notification for the Drive C: usage check and post the output of the tail command.
Thanks
Code: Select all
tail -f /usr/local/nagiosxi/var/e*Thanks
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Error loading a mib
Hello !
Here is the output :
When I ran again the command and did it a second time, I got that :
Here is the output :
Code: Select all
[root@srvnag ~]# tail -f /usr/local/nagiosxi/var/e*
==> /usr/local/nagiosxi/var/event_handler.lock <==
==> /usr/local/nagiosxi/var/event_handler.log <==
LOCKFILE '/usr/local/nagiosxi/var/event_handler.lock' CREATED
==> /usr/local/nagiosxi/var/event_handler.log-20161016 <==
[event_time] => 0000-00-00 00:00:00
[2] => 2
[event_source] => 2
[3] => 2
[event_type] => 2
[4] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";s:16:"nagios@localhost";s:4:"type";s:7:"PROBLEM";s:9:"escalated";s:1:"0";s:6:"author";b:0;s:8:"comments";b:0;s:4:"host";s:24:"srvhvsites.aural.asso.fr";s:11:"hostaddress";s:13:"192.168.1.110";s:9:"hostalias";s:23:"Serveur Hyper-V Secours";s:15:"hostdisplayname";s:24:"srvhvsites.aural.asso.fr";s:7:"service";s:13:"Etat Physique";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:8:"CRITICAL";s:14:"servicestateid";s:1:"2";s:16:"lastservicestate";s:8:"CRITICAL";s:18:"lastservicestateid";s:1:"2";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:2:"10";s:16:"serviceproblemid";s:1:"4";s:13:"serviceoutput";s:152:"Compaq/HP Agent Check: ProLiant DL360 G5 (rack-mount) overall condition of power supply subsystem (degraded) condition of the power supply (1.2: failed)";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Sun Oct 16 03:30:52 CEST 2016";}
[event_meta] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";s:16:"nagios@localhost";s:4:"type";s:7:"PROBLEM";s:9:"escalated";s:1:"0";s:6:"author";b:0;s:8:"comments";b:0;s:4:"host";s:24:"srvhvsites.aural.asso.fr";s:11:"hostaddress";s:13:"192.168.1.110";s:9:"hostalias";s:23:"Serveur Hyper-V Secours";s:15:"hostdisplayname";s:24:"srvhvsites.aural.asso.fr";s:7:"service";s:13:"Etat Physique";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:8:"CRITICAL";s:14:"servicestateid";s:1:"2";s:16:"lastservicestate";s:8:"CRITICAL";s:18:"lastservicestateid";s:1:"2";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:2:"10";s:16:"serviceproblemid";s:1:"4";s:13:"serviceoutput";s:152:"Compaq/HP Agent Check: ProLiant DL360 G5 (rack-mount) overall condition of power supply subsystem (degraded) condition of the power supply (1.2: failed)";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Sun Oct 16 03:30:52 CEST 2016";}
)
DELETED LOCKFILE '/usr/local/nagiosxi/var/event_handler.lock'
EVENT HANDLER EXITING
==> /usr/local/nagiosxi/var/event_handler.log-20161023 <==
LOCKFILE '/usr/local/nagiosxi/var/event_handler.lock' CREATED
DELETED LOCKFILE '/usr/local/nagiosxi/var/event_handler.lock'
EVENT HANDLER EXITING
==> /usr/local/nagiosxi/var/eventman.log <==
......
PROCESSED 1 EVENTS
==> /usr/local/nagiosxi/var/eventman.log-20161016 <==
Respond: http://192.168.1.47/nagiosxi/rr.php?uid=1-171-19bec87dbfddea7f185fe4a388fcf06a
Nagios URL: http://192.168.1.47/nagiosxi/
)
User has mobile text notifications disabled...
...
PROCESSED 5 EVENTS
==> /usr/local/nagiosxi/var/eventman.log-20161023 <==
....................
PROCESSED 0 EVENTS
==> /usr/local/nagiosxi/var/eventman.log <==
==> /usr/local/nagiosxi/var/event_handler.log <==
Array
(
[0] => 72550
[eventqueue_id] => 72550
[1] => 0000-00-00 00:00:00
[event_time] => 0000-00-00 00:00:00
[2] => 2
[event_source] => 2
[3] => 2
[event_type] => 2
[4] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";b:0;s:4:"type";s:7:"PROBLEM";s:9:"escalated";s:1:"0";s:6:"author";b:0;s:8:"comments";b:0;s:4:"host";s:10:"srvbuilder";s:11:"hostaddress";s:12:"192.168.1.88";s:9:"hostalias";s:27:"Serveur Builder Formulaires";s:15:"hostdisplayname";s:10:"srvbuilder";s:7:"service";s:16:"Pare-Feu Windows";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:7:"UNKNOWN";s:14:"servicestateid";s:1:"3";s:16:"lastservicestate";s:7:"UNKNOWN";s:18:"lastservicestateid";s:1:"3";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:4:"6775";s:16:"serviceproblemid";s:4:"3161";s:13:"serviceoutput";s:85:"ERROR: Process name table : The message size exceeded the buffer maxMsgSize of 15000.";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Thu Oct 27 08:41:24 CEST 2016";}
[event_meta] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";b:0;s:4:"type";s:7:"PROBLEM";s:9:"escalated";s:1:"0";s:6:"author";b:0;s:8:"comments";b:0;s:4:"host";s:10:"srvbuilder";s:11:"hostaddress";s:12:"192.168.1.88";s:9:"hostalias";s:27:"Serveur Builder Formulaires";s:15:"hostdisplayname";s:10:"srvbuilder";s:7:"service";s:16:"Pare-Feu Windows";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:7:"UNKNOWN";s:14:"servicestateid";s:1:"3";s:16:"lastservicestate";s:7:"UNKNOWN";s:18:"lastservicestateid";s:1:"3";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:4:"6775";s:16:"serviceproblemid";s:4:"3161";s:13:"serviceoutput";s:85:"ERROR: Process name table : The message size exceeded the buffer maxMsgSize of 15000.";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Thu Oct 27 08:41:24 CEST 2016";}
)
==> /usr/local/nagiosxi/var/eventman.log <==
ed...
...
==> /usr/local/nagiosxi/var/event_handler.log <==
Array
(
[0] => 72551
[eventqueue_id] => 72551
[1] => 0000-00-00 00:00:00
[event_time] => 0000-00-00 00:00:00
[2] => 2
[event_source] => 2
[3] => 2
[event_type] => 2
[4] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";b:0;s:4:"type";s:6:"CUSTOM";s:9:"escalated";s:1:"0";s:6:"author";s:20:"Nagios Administrator";s:8:"comments";s:2:"gg";s:4:"host";s:9:"srvbackup";s:11:"hostaddress";s:12:"192.168.1.37";s:9:"hostalias";s:19:"Serveur Sauvegardes";s:15:"hostdisplayname";s:9:"srvbackup";s:7:"service";s:19:"Drive C: Disk Usage";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:2:"OK";s:14:"servicestateid";s:1:"0";s:16:"lastservicestate";s:2:"OK";s:18:"lastservicestateid";s:1:"0";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:4:"6761";s:16:"serviceproblemid";s:1:"0";s:13:"serviceoutput";s:73:"C: Label: Serial Number 560905a0: 92%used(264392MB/286070MB) (93%) : OK";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Thu Oct 27 08:41:35 CEST 2016";}
[event_meta] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";b:0;s:4:"type";s:6:"CUSTOM";s:9:"escalated";s:1:"0";s:6:"author";s:20:"Nagios Administrator";s:8:"comments";s:2:"gg";s:4:"host";s:9:"srvbackup";s:11:"hostaddress";s:12:"192.168.1.37";s:9:"hostalias";s:19:"Serveur Sauvegardes";s:15:"hostdisplayname";s:9:"srvbackup";s:7:"service";s:19:"Drive C: Disk Usage";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:2:"OK";s:14:"servicestateid";s:1:"0";s:16:"lastservicestate";s:2:"OK";s:18:"lastservicestateid";s:1:"0";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:4:"6761";s:16:"serviceproblemid";s:1:"0";s:13:"serviceoutput";s:73:"C: Label: Serial Number 560905a0: 92%used(264392MB/286070MB) (93%) : OK";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Thu Oct 27 08:41:35 CEST 2016";}
)
==> /usr/local/nagiosxi/var/eventman.log <==
PROCESS EVENT: ID=72551, SOURCE=2, TYPE=2, TIME=2016-10-27 08:41:38
PHP Notice: unserialize(): Error at offset 839 of 922 bytes in /usr/local/nagiosxi/cron/eventman.php on line 145
*** GLOBAL HANDLER...
Array
(
[event_id] => 72551
[event_source] => 2
[event_type] => 2
[event_time] => 2016-10-27 08:41:38
[event_meta] =>
[logging_enabled] => 1
)
*** GLOBAL HANDLER (snmptrapsender)...
Array
(
[event_id] => 72551
[event_source] => 2
[event_type] => 2
[event_time] => 2016-10-27 08:41:38
[event_meta] =>
[logging_enabled] => 1
)
ERROR: Could not find user_id for contact ''
Code: Select all
==> /usr/local/nagiosxi/var/event_handler.log <==
LOCKFILE '/usr/local/nagiosxi/var/event_handler.lock' CREATED
Array
(
[0] => 72556
[eventqueue_id] => 72556
[1] => 0000-00-00 00:00:00
[event_time] => 0000-00-00 00:00:00
[2] => 2
[event_source] => 2
[3] => 2
[event_type] => 2
[4] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";b:0;s:4:"type";s:6:"CUSTOM";s:9:"escalated";s:1:"0";s:6:"author";s:20:"Nagios Administrator";s:8:"comments";s:1:"g";s:4:"host";s:9:"srvbackup";s:11:"hostaddress";s:12:"192.168.1.37";s:9:"hostalias";s:19:"Serveur Sauvegardes";s:15:"hostdisplayname";s:9:"srvbackup";s:7:"service";s:19:"Drive C: Disk Usage";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:2:"OK";s:14:"servicestateid";s:1:"0";s:16:"lastservicestate";s:2:"OK";s:18:"lastservicestateid";s:1:"0";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:4:"6761";s:16:"serviceproblemid";s:1:"0";s:13:"serviceoutput";s:73:"C: Label: Serial Number 560905a0: 92%used(264392MB/286070MB) (93%) : OK";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Thu Oct 27 08:44:57 CEST 2016";}
[event_meta] => a:26:{s:17:"notification-type";s:7:"service";s:7:"contact";s:11:"nagiosadmin";s:12:"contactemail";b:0;s:4:"type";s:6:"CUSTOM";s:9:"escalated";s:1:"0";s:6:"author";s:20:"Nagios Administrator";s:8:"comments";s:1:"g";s:4:"host";s:9:"srvbackup";s:11:"hostaddress";s:12:"192.168.1.37";s:9:"hostalias";s:19:"Serveur Sauvegardes";s:15:"hostdisplayname";s:9:"srvbackup";s:7:"service";s:19:"Drive C: Disk Usage";s:9:"hoststate";s:2:"UP";s:11:"hoststateid";s:1:"0";s:12:"servicestate";s:2:"OK";s:14:"servicestateid";s:1:"0";s:16:"lastservicestate";s:2:"OK";s:18:"lastservicestateid";s:1:"0";s:16:"servicestatetype";s:4:"HARD";s:14:"currentattempt";s:1:"1";s:11:"maxattempts";s:1:"1";s:14:"serviceeventid";s:4:"6761";s:16:"serviceproblemid";s:1:"0";s:13:"serviceoutput";s:73:"C: Label: Serial Number 560905a0: 92%used(264392MB/286070MB) (93%) : OK";s:17:"longserviceoutput";b:0;s:8:"datetime";s:29:"Thu Oct 27 08:44:57 CEST 2016";}
)
==> /usr/local/nagiosxi/var/eventman.log <==