Hi ,
we have recently upgrade SAM 5.0.1 from APM 4.2 but soon after that some of our linux script(perl and Sheel script) failing. These all were running fine.
Is there some feture or setting i need to look.
Regards,
Ashok
Double check the Credentials you used for the monitors if any. Make sure they are still assigned to the templates, and they didn't get deleted. What is the failure message you get from Orion when you try to run a test on the Templates in question?
If those are all still in place and you aren't getting a clear error message then I would open up a Wireshark session on the server and sniff the Ethernet port and then filter on one of the Server IP's you are trying to poll.. What is happening in the packet flow? Are they being sent at all from Orion? Do they get any replies back from the Server you are polling? That would be a good place to start.
Some of the other guys here with more knowledge of the internal workings of SAM and APM as it was called pre 5.0 may have a suggestion. More so after the huge upgrade you performed. 4.2 to 5.0.1 is a huge jump in code as far as what you had to what you upgraded too.
I have checked the credentials and all looks fine. All of this were working fine before upgrade.
Scripting Error: Script does not contain the expected parameters or is improperly formatted. 'Statistic' missing is the error we getting when we test.
Any thoughts?
Is this a custom script? If not which script are we talking about? If it's not a custom script; then check the syntax for any changes that the upgrade could have performed, or might have wiped a value you defined out and just need to re-enter. The error you are getting is the script is expecting value at a given point, but its missing or the parameters defining it are wrong.
Let me know once we start getting more information now that we know the error we can figure out what is causing this. Also, if you have the ability to run the script outside of SW, and locally on a test box this can be a huge help and you can get more error debugging. I also like to take the command syntax that is being run in the script and run it locally myself to see what expected values I am looking for. This helps me since I am not a coder or able to write scripts. I can troubleshoot as much on my own before I get one of our coders at my company to help me out, or ask on here. There are a ton of guys who are great with scripting on this forum.
