Policies troubleshooting

Simple checklist for troubleshooting policies:

1. Was policy assigned to the node?
2. Was the most recent version of the policy distributed to the node ?
3. What is the date of the corresponding XML file. Is content of XML file corresponds to your expectations? Look at the content of folder

   /var/opt/OV/datafiles/policies

   For example:

   configsettings/
   configsettings/a1b6413e-f15e-11d6-83d0-001083fdff5e_data
   configsettings/a1b6413e-f15e-11d6-83d0-001083fdff5e_header.xml
   monitor/
   monitor/708b199a-4420-71e0-1e7f-0ac90d6a0000_data
   monitor/708b199a-4420-71e0-1e7f-0ac90d6a0000_header.xml
   msgi/
   msgi/8046512c-ec43-71df-06a5-0ac90d6a0000_data
   msgi/02cf4ecc-7a9d-71e0-1e7f-0ac90d6a0000_header.xml
   msgi/02cf4ecc-7a9d-71e0-1e7f-0ac90d6a0000_data
   msgi/7f9e236c-1f4c-71e0-1e7f-0ac90d6a0000_header.xml
   msgi/8046512c-ec43-71df-06a5-0ac90d6a0000_header.xml
   msgi/4b4d977e-1161-71e2-09e7-0ac91d6a0000_data
   msgi/7f9e236c-1f4c-71e0-1e7f-0ac90d6a0000_data
   msgi/4b4d977e-1161-71e2-09e7-0ac91d6a0000_header.xml
   sched/
   sched/3bb9a62a-1ea6-71e2-09e7-0ac91d6a0000_data
   sched/3bb9a62a-1ea6-71e2-09e7-0ac91d6a0000_header.xml	

   For example: 

   you can find your policy using grep, for example

   grep "tick_generator" /var/opt/OV/datafiles/policies/msgi/*

   SYNTAX_VERSION 6
   
   ADVMONITOR "tick_generator"
           DESCRIPTION "generating ticks each minute, if the server is alive"
           INTERVAL "1m"
           SCRIPTTYPE "Perl"
           INSTANCEMODE  SAME
           MAXTHRESHOLD
           SEVERITY Warning
           MSGGRP "Dev"
           OBJECT "ticker"
           PROGRAM "ticker"
             DESCRIPTION ""
             MONPROG "/usr/local/bin/montest.pl"
           SUPP_UNM_CONDITIONS
             DESCRIPTION "tick_generator"
             CONDITION_ID "86363298-067a-71e2-09e7-0ac91d6a0000"
             CONDITION
               OBJECT
                 SCRIPT "#PARAMETERS START
   
   #PARAMETER param1 STRING DEFAULT \"unknown\" VALUE \"$HOSTNAME\"     CAPTION \"param1\"
   my $param1;
   $param1 = \"$HOSTNAME\";
   
   #PARAMETER param2 STRING DEFAULT \"unknown\" VALUE \"$UPTIME\"     CAPTION \"param2\"
   my $param2;
   $param2 = \"$UPTIME\";
   
   #PARAMETERS END

   $timestamp=`date +"%y%m%d_%H%M"`;
   `echo "[ $timestamp ] got tick @ARGV" > /tmp/opcmon_tick_test_log.txt`;
   exit 1

4. Are all the necessary instrumentation files distributed to the node? Are their versions correct on the node.
5. Trace the opcmona process... you can see exactly what it is doing and why. The trace is not too ugly to look at.

   ovconfchg -ns eaagt -set OPC_DBG_EXCLUDE_AREA MUX,QM,MEMQ,MUX/CV
   ovconfchg -ns eaagt -set OPC_TRACE_AREA MSG
   ovconfchg -ns eaagt -set OPC_DBG_PROCS opcmon,opcmona
   ovconfchg -ns eaagt -set OPC_TRC_PROCS opcmon,opcmona
   ovconfchg -ns eaagt -set OPC_TRACE TRUE

   This will show you the opcmon processes running, ( hopefully it really does run more than once ) then it will put the result into the queue, then opcmona will pull it out make some decisions about it and then forward to opcmsga. Concentrate on the opcmona parts ( grep opcmona /var/opt/OV/tmp/OpC/trace ) and see why it is doing what it is doing and with what parameters opcmon is invoked.

   You can use a single command to set trace on the management node:

   ovconfchg -ns eaagt \
      -set OPC_TRACE TRUE -set OPC_TRACE_AREA ALL,DEBUG\
      -set OPC_TRACE_TRUNC FALSE \
      -set OPC_TRC_PROCS opcmsg,opcmsgi,opcmsga\
      -set OPC_DBG_PROCS opcmsg,opcmsgi,opcmsga\
      -set OPC_DBG_EXCLUDE_AREA MUX,QM,MEMQ,MUX/CV

   To disable the agent trace settings:

   ovconfchg -ns eaagt -set OPC_TRACE FALSE

   After that look at the file /var/opt/OV/tmp/OpC/trace
    

6. Is trace result correspond to your expectations?

   For example the following fragment crearly shows that OV system vairable <MGMTSV_KNOWN_MSG_NODE_NAME>  is missing $ sign (should be <$MGMTSV_KNOWN_MSG_NODE_NAME>) :

   10/25 10:18:01.029 opcmsga(15825:-1118177504)[init]: Out_txt echo  "<MGMTSV_KNOWN_MSG_NODE_NAME>"  > /tmp/ticker.log
   10/25 10:18:01.029 opcmsga(15825:-1118177504)[actn]: Local action request created: Auto c86d1798-1eae-71e2-04b0-0ac936350000 'echo  "<MGMTSV_KNOWN_MSG_NODE_NAME>"  > /tmp/ticker.log'
   10/25 10:18:01.029 opcmsga(15825:-1118177504)[debug]: SIG: Blocking signal 0.
   10/25 10:18:01.030 opcmsga(15825:-1118177504)[debug]: SIG: Unblocking signal 0.
   10/25 10:18:01.030 opcmsga(15825:-1118177504)[actn]: Local action request sent to action agent: Auto c86d1798-1eae-71e2-04b0-0ac936350000 'echo  "<MGMTSV_KNOWN_MSG_NODE_NAME>"  > /tmp/ticker.log'

7. See also Tracing

NEWS CONTENTS

• 20120924 : Re several opcmon from same Perl script ( 08-06-2012 , HP Communities )

Old News ;-)

[ Sep 24, 2012 ] Re several opcmon from same Perl script

08-06-2012 | HP Communities

Hello Gurus,

I'm stomped on this one. I have a Perl script that checks unsuccessful attempts on user IDs and when above 5, sends an opcmon like this one:

/usr/lpp/OV/bin/opcmon GenID_Attempts=$strresult[1] -option USER_ID=$userid

Fairly simple?! Yes. But..

When I have more than one ID that passes the threshold, the monitor only returns the last opcmon sent by the script. When I run the script manually with the exact same command line entered in the Monitor Program entry, both alerts show up in my browser. I cannot determine why I'm not getting the second (or first actually) alert when it is the monitor that triggers the script. I'm pretty sure that where I'm wrong is I gotta find a way to tell the monitor that these are two different thresholds, but I haven't found that option. I thought it was "Process each instances separately" but no. That's why I'm kinda baffled now.

I'm using OML 9.10.220.

Thanks

Marco

Cooperation is doing with a smile what you have to do anyhow. Solved! Go to Solution.

KAKA_2 (Respected Contributor)

Hi Marco,

Can you check if the second message which has come to console has duplicate count in it?

how many matching rules you have in your policy?

I have Diskmonitoring configured on AIX node in the same way and i get all the alerts processed by opcmona.

So i dont think that any additional configuration is required.

if possible upload your script.

-KAKA- 1

Marco Santerre (Honored Contributor)

I have checked the duplicate count and no there is not a duplicate count on the alert.

There is only one rule on my monitoring policy.

Like I mentioned, I know we have had several occurences of scripts and monitors sending many opcmon from the one script and never had any issues, yet this one seems to behave differently.

Cooperation is doing with a smile what you have to do anyhow. Attachments:
genid_policy.txt 2 KB
genericid_security_aix.pl.txt 2 KB 0 Reply 0

Re: several opcmon from same Perl scriptPost options

Trace the opcmona process... you can see exactly what it is doing and why. The trace is not too ugly to look at.

ovconfchg -ns eaagt -set OPC_DBG_EXCLUDE_AREA MUX,QM,MEMQ,MUX/CV
ovconfchg -ns eaagt -set OPC_TRACE_AREA MSG
ovconfchg -ns eaagt -set OPC_DBG_PROCS opcmon,opcmona
ovconfchg -ns eaagt -set OPC_TRC_PROCS opcmon,opcmona
ovconfchg -ns eaagt -set OPC_TRACE TRUE

This will show you the opcmon processes running, ( hopefully it really does run more than once ) then it will put the result into the queue, then opcmona will pull it out make some decisions about it and then forward to opcmsga. Concentrate on the opcmona parts ( grep opcmona /var/opt/OV/tmp/OpC/trace ) and see why it is doing what it is doing, once you verify that opcmon is running multiple times.

Marco Santerre (Honored Contributor)

08-10-2012 04:20 AM

I actually found the solution by trying something :

I added -object $user_id to differenciate between the various opcmon sent by the script.

And that worked.

Cooperation is doing with a smile what you have to do anyhow.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019