CentOS release 6.8 (Final)
LSB_VERSION=base-4.0-ia32:base-4.0-noarch:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
CentOS release 6.8 (Final)
CentOS release 6.8 (Final)
[root@xxx-monitor ~]# uname -a
Linux xxx-monitor 2.6.32-642.el6.i686 #1 SMP Tue May 10 16:13:51 UTC 2016 i686 i686 i386 GNU/Linux
[root@xxx-monitor ~]# cat /usr/local/nagiosxi/html/includes/configwizards/windowswmi/windowswmi.inc.php | grep "CONFIGWIZARD_VERSION"
CONFIGWIZARD_VERSION => "2.0.7",
WMI Error
-
chillipepper
- Posts: 17
- Joined: Mon Dec 12, 2016 3:23 pm
Re: WMI Error
Last edited by chillipepper on Thu Dec 22, 2016 11:08 am, edited 1 time in total.
-
chillipepper
- Posts: 17
- Joined: Mon Dec 12, 2016 3:23 pm
Re: WMI Error
CentOS release 6.8 (Final)
LSB_VERSION=base-4.0-ia32:base-4.0-noarch:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
CentOS release 6.8 (Final)
CentOS release 6.8 (Final)
[root@xxx-monitor ~]# uname -a
Linux xxx-monitor 2.6.32-642.el6.i686 #1 SMP Tue May 10 16:13:51 UTC 2016 i686 i686 i386 GNU/Linux
[root@xxx-monitor ~]# cat /usr/local/nagiosxi/html/includes/configwizards/windowswmi/windowswmi.inc.php | grep "CONFIGWIZARD_VERSION"
CONFIGWIZARD_VERSION => "2.0.7",
LSB_VERSION=base-4.0-ia32:base-4.0-noarch:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
CentOS release 6.8 (Final)
CentOS release 6.8 (Final)
[root@xxx-monitor ~]# uname -a
Linux xxx-monitor 2.6.32-642.el6.i686 #1 SMP Tue May 10 16:13:51 UTC 2016 i686 i686 i386 GNU/Linux
[root@xxx-monitor ~]# cat /usr/local/nagiosxi/html/includes/configwizards/windowswmi/windowswmi.inc.php | grep "CONFIGWIZARD_VERSION"
CONFIGWIZARD_VERSION => "2.0.7",
Re: WMI Error
The only way i've been able to reproduce this is by submitting service/process checks without the Display Name field filled in:
I would suggest deleting the existing configuration (via the Core Config Manager), running through the WMI wizard again, and verifying there aren't any missing fields. It could be that a service/process's display name isn't being properly filled in. Can you share a screenshot of the wizard at this stage?
I would suggest deleting the existing configuration (via the Core Config Manager), running through the WMI wizard again, and verifying there aren't any missing fields. It could be that a service/process's display name isn't being properly filled in. Can you share a screenshot of the wizard at this stage?
You do not have the required permissions to view the files attached to this post.
Former Nagios employee
https://www.mcapra.com/
https://www.mcapra.com/
-
chillipepper
- Posts: 17
- Joined: Mon Dec 12, 2016 3:23 pm
Re: WMI Error
Here's the screenshot it is populating the display name so that shouldn't be a problem.
You do not have the required permissions to view the files attached to this post.
Re: WMI Error
Can you run the following command and share the resulting /tmp/wmiwizard_41668.zip file?
As a temporary work-around, you should be able to alter the service_description from the Core Config Manager directly and plug in "DNS Client" into the offending object definition:
Code: Select all
zip -r /tmp/windowswmi_41668.zip /usr/local/nagiosxi/html/includes/configwizards/windowswmi/
You do not have the required permissions to view the files attached to this post.
Former Nagios employee
https://www.mcapra.com/
https://www.mcapra.com/