Hi there,
I just migrated from CentOS 5.4 with FAN (Nagios + Centreon) to CentOS 7 with Nagios Core 4.1.1
On the old version, I had a ESXI Hardware check script, but sadly enough it's not working on the new host.
I keep receiving the following error in Nagios:
(No output on stdout) stderr: Traceback (most recent call last):
Does anyone has any idea what the issue could be?
Attached are the script files.
Kind regards,
Justin
No output on stdout
-
Justin2501
- Posts: 8
- Joined: Tue Mar 15, 2016 8:56 am
No output on stdout
- Attachments
-
- esxi_hardware.rar
- ESXI Check hardware
- (21.37 KiB) Downloaded 219 times
Re: No output on stdout
What are the permissions on these files? From the CLI, run ls -la /usr/local/nagios/libexec/check_esxi_hardware* and post back the result.
Former Nagios Employee
-
Justin2501
- Posts: 8
- Joined: Tue Mar 15, 2016 8:56 am
Re: No output on stdout
I've run the command:rkennedy wrote:What are the permissions on these files? From the CLI, run ls -la /usr/local/nagios/libexec/check_esxi_hardware* and post back the result.
[root@nagios ~]# ls -la /usr/local/nagios/libexec/check_esxi_hardware*
-rwxr-xr-x 1 nagios nagios 30735 Mar 12 2013 /usr/local/nagios/libexec/check_esxi_hardware.py
-rwxr-xr-x 1 nagios nagios 14780 Mar 12 2013 /usr/local/nagios/libexec/check_esxi_hardware.pyc
-rwxr-xr-x 1 nagios nagios 14780 Mar 12 2013 /usr/local/nagios/libexec/check_esxi_hardware.pyo
Do i need any specific packages, that i might be missing?
Or is this error something else
-
Justin2501
- Posts: 8
- Joined: Tue Mar 15, 2016 8:56 am
Re: No output on stdout
Hmm, i think i fixed it while trying out some stuff.
Downloaded the newest version of check_esxi_hardware
And installed the following python packages
After that i reloaded nagios and now it's working 
Downloaded the newest version of check_esxi_hardware
Code: Select all
http://www.claudiokuenzler.com/nagios-plugins/check_esxi_hardware.php#DownloadCode: Select all
yum install pywbem python-setuptoolsRe: No output on stdout
Thanks for that update and glad to hear this is resolved. I'll go ahead and close this thread now.
Be sure to check out the Knowledgebase for helpful articles and solutions!