Re: Take Action log

You might try mapping STDERR to STDOUT::

exec 2>&1
exec 2>&1 > /path/myfile

The 2nd one would be preferable, just have to scp the file up to your local
machine. If the TakeAction is a literal command in the TakeAction field
then you can just prepend the above to the command using the standard ";"
delimiter.  If you're calling a script located on the agent, just put the
above on the second line of the script after the "#!..." line.  It might
yield nothing, but then you never know...

Toben



On Wed, Aug 14, 2013 at 2:29 PM, Annamalai Arunachalam <
[email protected]> wrote:

> I have take action configured for a klo log monitoring situation.
> Sometimes it doesnt run the script on the agent though i can see event in
> TEPS. In LGO/1 log, i dont see any entries but the situation status is open
> in tacmd listsit.
>
> For the sucessful execution I can see in LG0/LG1 logs <Date> Executed
> <script.sh> with status 0. Is there way to know return code details?
>
> Is there any log to know, why situation didnt execute action? Why it
> failed?
>
> _ms_time.log has the situation details, but i cudnt identify which lines
> refer take action. Can you help?
>
> Thanks,
> Annamalai
>
> On 14 Aug, 2013, at 12:04 AM, John Alvord <jalvord-r/[email protected]> wrote:
>
> The operations log
>
> Agent:  *.LG0
> Linux/Unix:  hostname_ms_time.log
> Windows: kdsmain.log
>
> will contain a record of action commands. Basically whether they started
> OK [status 0] or not. The command text message is limited size so there is
> truncation possible.
>
> I often use it during development to make sure the action command ran or
> not.
>
> There is nothing that is "Audit worthy" or a historical records etc.
>
> Regards,
> ______________________________________________
>   *John Alvord*
> Advisory Engineer
> IBM Tivoli Monitoring 6 Platform*
> Customer Support *
> Office: 1-720-396-2788
> Mobile: none *
> **jalvord-r/[email protected]* <jalvord-r/[email protected]>
> *
> **Cloud & Smarter Infrastructure* <http://www.ibm.com/software/tivoli/> *IBM
> Support Portal* <https://www.ibm.com/support/>*
> **Open a New Service Request*<http://www.ibm.com/support/entry/portal/Open_service_request/>
> *
> **Update your PMR via Email*<https://www-304.ibm.com/jct05001c/de/support/ecurep/send_email.html#naming>
> *
> **Escalate your PMR*<http://www-304.ibm.com/support/customercare/sas/f/handbook/getsupport.html#9>
> *
> **My Blog: Wonderful World of Situations*<https://www.ibm.com/developerworks/mydeveloperworks/blogs/jalvord>
> *
> **Secure upload to ECUREP* <https://www.ecurep.ibm.com/app/upload>
>
> <https://www.facebook.com/IBMTivolisupport><https://twitter.com/TivoliSupport><https://www.ibm.com/developerworks/servicemanagement/index.html>
>
>  <http://www.ibm.com/software/tivoli//>
>
>
>
>
> From:        Annamalai Arunachalam <[email protected]>
> To:        "Discussion list for Tivoli product and Tivoli Ready
> products." <[email protected]>,
> Date:        08/13/2013 08:59 AM
> Subject:        [TME10] Take Action log
> Sent by:        [email protected]
> ------------------------------
>
>
>
> Hi
>
> I have a situation configured with take action. It will call a script on
> the agent.
>
> Is there any log in TEMS or in Agent to know take action script has been
> called or not?
>
> I can see the situation status as open, but cannot confirm it evoked the
> action script on agent. Is there a way to confirm?
>
> Thanks,
> Annamalai
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>


-- 
"Sometimes I think that's the only right thing to do:
To dream. to live in the world of dreams.
But it doesn't last forever--wakefulness always comes to take me back..."

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]