Softpanorama

May the source be with you, but remember the KISS principle ;-)
Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

Logfile Encapsulation (le) policies

News HP Operations Manager Recommended Links Reference Conditions Operations on Policies
Open Message Interface Policies Logfile Encapsulation (le) policies Scheduled Task Policies Measurement Threshold Policies SNMP trap policies Event correlation circuit  policies
HP Operations Manager Policy variables Event Correlation Integrated Applications as Actions History Humor Etc

Note: HP renamed the product called now HP operations manager way too many times. Also it is very inconsistent with using abbreviations. Here we will assume that the term "HP Operations manager" and abbreviations HPOM, OMU, and OVO  mean the same thing :-)

Log file messages and system log files can be intercepted by the HPOM log file encapsulator.  Tha t means that you can bring messages into HPOM from any application or service that writes a log file, without making any changes to the application or service. 

The log file policy defines the default message attributes that describe all messages from the source. The policy also includes monitoring options that specify how and when a log file is monitored.. Settings for a log file policy include:

NOTE If you do not use the NODE keyword in the log file policy, HPOM uses the node on which the log file encapsulator is running. In a clustered environment with HP Operations agents running on cluster nodes, you can specify a different node on which to monitor the log file.

Specify a different node when you modify log files located on NFS-mounted file systems, or if you have copied the log files from other remote nodes to the system where the HPOM log file encapsulator is running. Monitoring Log Files on External Nodes When an event occurs on an external node, the log file encapsulator is not automatically informed.

 To monitor log files from external nodes, choose between the following alternatives:

The corresponding log file policies must be configured so that the HPOM operator knows which system originated the log file, or which event triggered the message.

The following example monitors an application log file. The file is checked every 60 seconds and the log file encapsulator checks the contents of the file from the position where it last finished checking (keyword FROM_LAST_POS). File is opened just before and closed immediately after each reading (keyword CLOSE_AFTER_READ). Messages that have the word “missing” will be suppressed, messages with word failure will have their severity set to Critical, and all other messages will be forwarded to the server (this is achieved by using FORWARDUNMATCHED keyword). All messages will have their application attribute set to “App” and message group set to “AppLog”, and all unmatched messages will have severity Unknown.

LOGFILE “Application log”
DESCRIPTION “Logfile for Application”
LOGPATH “/opt/App/log/logfile.txt”
INTERVAL “60s”
FROM_LAST_POS
CLOSE_AFTER_READ
SEVERITY Unknown
APPLICATION “App
MSGGRP “AppLog”
FORWARDUNMATCHED
SUPPRESSCONDITIONS
DESCRIPTION “App messages to be ignored”
CONDITION
TEXT “<*> missing<*>”
MSGCONDITIONS
DESCRIPTION “App messages to be ignored”
CONDITION
TEXT “<*> failure<*>”
SET
SEVERITY Critical
TEXT “<$MSG_TEXT>”
Implementing Message Policies
HPOM Message Interface

For detailed information about encapsulating logfiles with the logfile encapsulator, see the HPOM Concepts Guide.

Logfile policies are configured to collect information from logfiles that are produced by standard installations. If you are monitoring a non-standard installation, you should modify the policies to suit your particular needs.

Listing Default Log-File Policies

To display details of the logfiles that are monitored by default, use the opcpolicy command with the following parameters:

# opcpolicy -list_pols pol_type=LOG

You can edit existing (and configure new) logfile policies by modifying the policy body. The corresponding logfile policies must be configured so that the HPOM operator knows which system the logfile originated from, or the event which triggered the message.

For information on policy grammar, refer to the HPOM Concepts Guide.

Logflle: Name of the file to be monitored

Execute: Name of the program to execute for adjusting the Logflle.

Read file: Name of the file to read after running the program in the Execute entry.

Read from: Where to start reading Logl'fle. This will apply to either the actual logtlle, or the "Read File".

o    Last File Position: Start where the last read finished.

o    Begin (First Time): Read from the beginning, but only the first time.
o    Begin (Always): Read the entire Logfile each time.

-     Codeset: Define the codeset for text characters in the Logflle.

-       Message on no Logflle: Send a message If Logfile does not exist.

Close after read: Explicitly close Logflle after reading.

Polling Interval: How often to read Logflle in days, hours, minutes, seconds.


Top Visited
Switchboard
Latest
Past week
Past month

Old News

IT Resource Center forums - opcle (Logfile Encapsulator) is always getting aborted.

opcle (Logfile Encapsulator) is always getting aborted. Rupesh K K Apr 20, 2009 19:10:30 GMT

  Hi all, We are using OVO unix 8.1.In our solaris managed nodes always the opcle is getting aborted.Other all processes are running fine and we are geting alerts also.if i restart the agent all process will be in running state.Within 10 mins it will agin go to Aborted state. Can any one help me to fix this issue. opcmona OVO Monitor Agent AGENT,EA (1322) Running opcmsga OVO Message Agent AGENT,EA (1323) Running coda OV Performance Core AGENT,CODA (1324) Running opcacta OVO Action Agent AGENT,EA (1325) Running opcmsgi OVO Message Interceptor AGENT,EA (1326) Running opcle OVO Logfile Encapsulator AGENT,EA Aborted Message Agent is not buffering.

Sort Answers By: Date or Points

Jeroen Peereboom Apr 20, 2009 20:17:11 GMT 4 pts

  Did you check for a recent agent patch? (For example Agent Solaris A.08.53, ITOSOL_00680 if you have a Solaris management server.)

I must admit that I (always) have big problems finding a problem like this in the patch descriptions or enhancement requests.I did not find a direct link to your problem.

JP

Rupesh K K Apr 20, 2009 20:26:15 GMT N/A: Question Author

  Hi JP,

Thanks for ur reply. 08.13.000 is the agent software version. Then management server version is A.08.30. Can u check this and tell me.

Regards Rupesh

Gagan kapahi Apr 20, 2009 21:43:19 GMT 10 pts

  Make sure there is no BAD logfile template assigned to the node:

whats the output of opctemplate -l

G

Rupesh K K Apr 20, 2009 21:50:00 GMT N/A: Question Author

  Hi, thanks for ur reply. What u mean by bad log?the output of the opctemplate -l is given below ONFIGSETTINGS "OVO settings" enabled 1 LOGFILE "Disk_Errors" enabled 1 LOGFILE "Inode_mon" enabled 1 LOGFILE "Kernel Messages" enabled 1 LOGFILE "PowerSupply_Errors" enabled 1 LOGFILE "SOL-Bad-Logs" enabled 1 LOGFILE "SOL-Su-log" enabled 1 LOGFILE "reboot_chk" enabled 1 mgrconf "OVO authorization" enabled 1 MONITOR "CPU_Offline" enabled 1 MONITOR "Mount_FS" enabled 1 MONITOR "SVM_mdmonitor" enabled 1 MONITOR "SVM_sdsmon" enabled 1 MONITOR "Sendmail-queue" enabled 1 MONITOR "Sol-CD_Cpu_Load" enabled 1 MONITOR "Sol-CD_Mem_Load" enabled 1 MONITOR "Sol-CD_Swap_Res" enabled 1 MONITOR "Sol-NP-Filesystem" enabled 1 MONITOR "UFS_monitoring1" enabled 1 MONITOR "Wtmpx_mon" enabled 1 MONITOR "core_check" enabled 1 MONITOR "proc_cron" enabled 1 MONITOR "proc_intd" enabled 1 MONITOR "proc_syslogd" enabled 1 OPCMSG "Sol-FilesystemMsg" enabled 1 OPCMSG "opcmsg(1|3)" enabled 1

Thanks

Rupesh

Gagan kapahi Apr 21, 2009 00:10:39 GMT 9 pts

  Well, as i can see lot many logfile templates assigned to the node in question, i would like to know the following:

1. Check the template conditions to verify if "close after read" option is enabled ??

2. Make sure there is no incorrect variable used in any condition under "pattern matching"??

3. Verify if there are "special files" mentioned under "file to be executed" ??

4. Make sure there is no corrupted application/system log file present on the node ??

If everything mentioned above looks good to you and there are no issues, then follow the following steps:

1. unassign the templates 2. distrib 3. kill the agent 4. kill any "opcle" process, if present (after killing of agent). 5. start the agent 6. reassign the templates

Let me know the results.

G

Srihari S Apr 21, 2009 03:21:22 GMT 7 pts

  ITOSOL_00438 is the patch OVO Server A.08.13 Solaris .

you can disable few templates and restarte opcle and find out which template is causing the problem. And then in the templates you can check if there is anythign weired in the RULES, to find out which is making opcle aborted.

What is the output of opcagt -status when opcle is aborted, does all the other subagents are fine?

jason_lee Apr 21, 2009 04:26:19 GMT 6 pts

  Hi Rupesh, As what Jeroen said, make sure you install the latest agents patch & then upgrade the managed node to this latest patch. I think there is no point to troubleshoot, if your agent is an old version & the newer version will solve your problem & you haven't installed it yet.

Jeroen Peereboom Apr 21, 2009 05:43:33 GMT 9 pts

  Since all your Solaris nodes have the same problem it is probably not due to configuration errors on the nodes themselves. How many Solaris nodes are we talking about?

The following website will give you the opportunity to search for patches: http://support.openview.hp.com/selfsolve/patches;jsessionid=92DACB0CAFE6359E 6E6E8920E3A57696

Or this one: http://support.openview.hp.com/selfsolve/document/KM322544

If you have a Solaris management server, you need to install ITOSOL patches. If you have an HP-UX management server, you have to install a PHSS patch (38511 for Solaris agent). As you can see ITOSOL_00680 will bring your Solaris agent to version A.08.53.

You install the patch for the Solaris Agent on the management server and next install the agent software 'as usual' (for example from the opc_adm GUI) on the managed Solaris nodes.

The patch mentioned by Srihari (ITOSOL_00438) is the patch for the Solaris management server, not for the Solaris agents.

'Bad' templates? Maybe check the /var/opt/OV/.../system.txt on the managed nodes for errors.

An opcragt -cleanstart may be worth a try, but maybe it is just best to upgrade the agent. Use opcragt -agent_version <mgd_node> on the management server to see versions of the agent components.

JP

Dwayne A Apr 21, 2009 11:42:00 GMT 7 pts

  Rupesh,

I recall having similar syslog issues on Solaris.

I believe the fix was to check the "close after read" option in the template.

HTH

Dwayne

 



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

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 quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard 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 DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting 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-MonthHow 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


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

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.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

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 author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: August 05, 2013