Member_2_6492660_1
asked on
Error: Can't locate perl510.dll
Nagios Core 4.3.4
Nsclient 4.3
Windows 10
Just restarted my Windows 10 Desktop VM after November Updates and Nagios reports this warning on two checks
Error: Can't locate perl510.dll
Check Windows Temp Folder WARNING 11-14-2018 22:01:47 0d 0h 32m 58s 10/10 Error: Can't locate perl510.dll
Explorer WARNING 11-14-2018 22:28:58 0d 0h 33m 34s 20/20 Error: Can't locate perl510.dll
I have the exact same checks on other Windows 10 VMs and Physical Windows 10 Desktop and they all work
I have no perl program installed on any of y computers
Searching for this dll shows nothing any where.
Any ideas?
Nsclient 4.3
Windows 10
Just restarted my Windows 10 Desktop VM after November Updates and Nagios reports this warning on two checks
Error: Can't locate perl510.dll
Check Windows Temp Folder WARNING 11-14-2018 22:01:47 0d 0h 32m 58s 10/10 Error: Can't locate perl510.dll
Explorer WARNING 11-14-2018 22:28:58 0d 0h 33m 34s 20/20 Error: Can't locate perl510.dll
I have the exact same checks on other Windows 10 VMs and Physical Windows 10 Desktop and they all work
I have no perl program installed on any of y computers
Searching for this dll shows nothing any where.
Any ideas?
I have the exact same checks on other Windows 10 VMs and Physical Windows 10 Desktop and they all work
I have no perl program installed on any of y computers
If you don't have perl installed on any of the computers, I'd be wondering why you're only getting that nagios alert for one of them, assuming the nagios check is configured for all of them.
You may want to uninstall all versions of Pearl and then install both the 32 bit and 64 bit of Pearl and then just uninstall them to get rid of the error.
ASKER
Arnold
I do not have perl installed hard to repair something that does not exist.
Fishmonger
That what I am wondering also. Yes I have the same check for over 50 computers.
Dana D I do not have Perl installed on any computer can not uninstall it
Guys any other ideas?
Thank you
Tom
I do not have perl installed hard to repair something that does not exist.
Fishmonger
That what I am wondering also. Yes I have the same check for over 50 computers.
Dana D I do not have Perl installed on any computer can not uninstall it
Guys any other ideas?
Thank you
Tom
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Dana D
Do you know where I can get the software from? Perl.org??? if so which version should I download Activestate Perl or Strawberry Perl?
Please provide a link
Thank you
Do you know where I can get the software from? Perl.org??? if so which version should I download Activestate Perl or Strawberry Perl?
Please provide a link
Thank you
I've previously used activeperl, https://www.activestate.com/products/activeperl/
Other option is to locate the two checks that complain about this issue and see whether you need the checks.
Other option is to locate the two checks that complain about this issue and see whether you need the checks.
ASKER
this is the actual error message from Nagios
WARNING
(for 2d 12h 40m 8s)
Status Information: Error: Can't locate perl510.dll
Make sure the ActivePerl bin directory is in your PATH
PATH=C:\WINDOWS\system32;C :\WINDOWS; C:\WINDOWS \System32\ Wbem;C:\WI NDOWS\Syst em32\Windo wsPowerShe ll\v1.0\;C :\WINDOWS\ system32\c onfig\syst emprofile\ AppData\Lo cal\Micros oft\Window sApp
It is looking for active perl
WARNING
(for 2d 12h 40m 8s)
Status Information: Error: Can't locate perl510.dll
Make sure the ActivePerl bin directory is in your PATH
PATH=C:\WINDOWS\system32;C
It is looking for active perl
If memory serves, nagios runs
If memory serves, it was/is perl driven.
This could be related to the web server.. processing.....
The "agent" that runs on the monitored system is commonly perl based script. much depends on the checks you are running.
which check failes with this error?
Do you need/use this check?
If memory serves, it was/is perl driven.
This could be related to the web server.. processing.....
The "agent" that runs on the monitored system is commonly perl based script. much depends on the checks you are running.
which check failes with this error?
Do you need/use this check?
ASKER
Arnold
Yes I require the checks and yes they was working fine on all systems except for this one
From the Nagios server I run them from the command line example of the failing machine and one that works
/usr/lib/nagios/plugins# ./check_nrpe -t 50 -H Desk004 -c check_explorer
Error: Can't locate perl510.dll
Make sure the ActivePerl bin directory is in your PATH
PATH=C:\WINDOWS\system32;C :\WINDOWS; C:\WINDOWS \System32\ Wbem;C:\WI NDOWS\Syst em32\Windo wsPowerShe ll\v1.0\;C :\WINDOWS\ system32\c onfig\syst emprofile\ AppData\Lo cal\Micros oft\Window sApps
/usr/lib/nagios/plugins# ./check_nrpe -t 50 -H DESK003 -c check_explorer
PROCESS OK - 55 process(es)|'processes'=55
Any ideas?
Yes I require the checks and yes they was working fine on all systems except for this one
define service{
use generic-service
host_name hostname
service_description Explorer
check_command check_nrpe!check_explorer! -a explorer.exe
max_check_attempts 20
servicegroups explorer
check_period backup_period
notification_period backup_period
}
define service {
host_name hostname
service_description Check Windows Temp Folder
check_command check_winfile
servicegroups Windows Temp
check_interval 60
notification_interval 60
check_period backup_period
notification_period backup_period
use generic-service
}
define command{
command_name check_winfile
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -t 120 -c check_winfile -a '--target c:\windows\temp --filter "size gt 1073741824" -delete'
}
define command{
command_name check_explorer
command_line $USER1$/check_procs -c 1:30 -C explorer
}
From the Nagios server I run them from the command line example of the failing machine and one that works
/usr/lib/nagios/plugins# ./check_nrpe -t 50 -H Desk004 -c check_explorer
Error: Can't locate perl510.dll
Make sure the ActivePerl bin directory is in your PATH
PATH=C:\WINDOWS\system32;C
/usr/lib/nagios/plugins# ./check_nrpe -t 50 -H DESK003 -c check_explorer
PROCESS OK - 55 process(es)|'processes'=55
Any ideas?
ASKER
Dana D
installed ActivePerl checked that perl is in the path
PATH=C:\Perl64\site\bin;C: \Perl64\bi n;C:\WINDO WS\system3 2;C:\WINDO WS;C:\WIND OWS\System 32\Wbem;C: \WINDOWS\S ystem32\Wi ndowsPower Shell\v1.0 \;C:\Users \maxg\AppD ata\Local\ Microsoft\ WindowsApp s;
Still getting the same errors
installed ActivePerl checked that perl is in the path
PATH=C:\Perl64\site\bin;C:
Still getting the same errors
ASKER
Guys,
After installing ActivePerl 5.24.3.2404 from perl.org site the error still occurred.
So I decided to restart the desktop and after the restart all the checks just started working again.
The error message lead to the resolution activeperl was not in the path.
Still does not explain why the other desktops and servers do not have this problem.
Thanks for all your help
Tom
After installing ActivePerl 5.24.3.2404 from perl.org site the error still occurred.
So I decided to restart the desktop and after the restart all the checks just started working again.
The error message lead to the resolution activeperl was not in the path.
Still does not explain why the other desktops and servers do not have this problem.
Thanks for all your help
Tom
How does this desktop differ from others?
Restarting the service that listens for inbound connections should reset, require the path.
Could it be that activeperl, perl was uninstalled, corrupted on this desktop during the win10 update/upgrade process.
Check targeting on whether this workstation updates/upgrades on the business,,, targeted channel, semi-annually versus quarterly?
Restarting the service that listens for inbound connections should reset, require the path.
Could it be that activeperl, perl was uninstalled, corrupted on this desktop during the win10 update/upgrade process.
Check targeting on whether this workstation updates/upgrades on the business,,, targeted channel, semi-annually versus quarterly?
Great News Thomas! Glad to help Sir and thank you for the points!
Since the upgrade it may have potentially unset..
Try running a repair on the perl install (presumably you are using activeperl)
Check which perl you have installed.
Scan the Windows.old for the referenced dll.