Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

having a very strange issue with linux PERL scripts in APM

when running perl scripts through APM 4.0.2 SP 4 I am seeing issues where more often than not they fail with 'failed with 'Undefined' status. Script execution failed. Input string was not in a correct format.' I have searched the forums and seen that others are having these issues but there seems to have been no resolution, at least from what I can tell. the odd thing that I am having is that every once in a while it will pass. so I know it's not my script that is broken, is APM just not passing the correct input for my script.

here is a sample of one of my scripts checking time offset, ARGV[0] would be our NTP server. I can run the script on a server and it will pass every time, but running from APM it will fail about 60% of the time.

command line: perl ${SCRIPT} ntpserver

#!/usr/bin/perl -w # servicerestart.pl # Time offset test #god makes time.. I just make sure that it's right use strict 'vars'; if ($ARGV[0]) { my $offset = `sntp $ARGV[0] |cut -c29-37`; #print "$offset"; #my $mill = sprintf "%.0000000f", ($offset * 1000); #print $mill; if ($offset) { my $mill = sprintf "%.0000000f", ($offset * 1000); print "Message: current NTP offset time is $offset seconds\n"; print "Statistic: $mill \n"; exit (0); } else { print "could not connect to NTP server please check connections\n"; exit (1); } } else { print "did not recive NTP server\n"; exit (1); }

Find more posts tagged with

Linux

linux_script

apm_4.0.2

Perl

Accepted answers

All comments

aLTeReGo

From the looks of your script it appears the problem is with how the result conditions are being returned. You are correct that a success needs to return with an error level of zero "0" and that a failure returns an error level of one "1" but the format of your errors is incorrect. If you want to return the error message result you'll still need to return this as "print "Statistic:"' and 'print "Message: did not receive NTP server\n"'

The error you're currently receiving "Input string was not in a correct format" means what was returned was not a numerical statistic properly formatted.

FormerMember

On a side note, your sprintf appears to be formatted incorrectly - sprintf "%.0000000f"

If you were trying to output a number accurate to 7 decimal places you'd want to use "%.7f". As it is, it would just output a whole number (0 decimal places).

kcarson

I have implemented this I will see after a few hours if this changes anything. if it does that means I have bigger issues on my side to look at.

kcarson

after running for a few weeks with these changes I am still having a very high failure rate. between 14% and 50% on most of my boxes, occasionally it does pass so I know it is not 100% my scripts fault.

aLTeReGo

I would recommend enabling debugging on the application template then waiting for a failure and running the SolarWinds Diagnostics <Start -> Programs -> Solarwinds Orion -> Documentation and Support -> Orion Diagnostics). This will collect the necessary log files into a single archive. Then o pen a case with support explaining your issue (or point them to this thread) and include the Orion Diagnostics archive so support can review the debug logs.