Ok...so, here is part of the nvaction.alog:

2005/16/08 18:25:39  .//nl_Actionsvr.C[852] :   Varbind contained an
illegal character.
Issuing sanitized version of the varbind:
2005/16/08 18:25:39  .//nl_Actionsvr.C[853] :   NVATTR_2="CIP_CALL_BF"
2005/16/08 18:25:39  .//nl_Actionsvr.C[852] :   Varbind contained an
illegal character.
Issuing sanitized version of the varbind:
2005/16/08 18:25:39  .//nl_Actionsvr.C[853] :   NVATTR_3="Interface
Channel4_0 down\."
2005/16/08 18:25:39  .//nl_Actionsvr.C[852] :   Varbind contained an
illegal character.
Issuing sanitized version of the varbind:
2005/16/08 18:25:39  .//nl_Actionsvr.C[853] :   NVATTR_4="172\.19\.6\.117
1124227539 1353 660166"
2005/16/08 18:25:39  .//nl_Actionsvr.C[852] :   Varbind contained an
illegal character.
Issuing sanitized version of the varbind:
2005/16/08 18:25:39  .//nl_Actionsvr.C[853] :  
NVATTR_6="CIP_CALL_BF_Channel4_0660166"
2005/16/08 18:25:39  .//nl_Actionsvr.C[852] :   Varbind contained an
illegal character.
Issuing sanitized version of the varbind:
2005/16/08 18:25:39  .//nl_Actionsvr.C[853] :   NVATTR_7="172\.19\.6\.117"
2005/16/08 18:25:39 :   1 command failed. error data:
 /usr/OV/conf/scripts/hoevents.sh[21]: error:  not found.
/usr/OV/conf/scripts/hoevents.sh[24]: error:  not found.

2005/16/08 18:25:39 :   1 sending trap for failed command.
2005/16/08 18:25:39  .//nl_Actionsvr.C[1165] :  action failure
notification sent.
2005/16/08 18:25:39 :   2 command failed. error data:
 /usr/OV/conf/scripts/hoevents.sh[21]: error:  not found.
/usr/OV/conf/scripts/hoevents.sh[24]: error:  not found.

2005/16/08 18:25:39 :   2 sending trap for failed command.
2005/16/08 18:25:39  .//nl_Actionsvr.C[1165] :  action failure
notification sent.


...it seems that actionsvr is not finding the script...but the script is
there (/usr/OV/conf/scripts/hoevents.sh).

Thanks.

Mario




--- James Shanks <jshanks AT us.ibm DOT com> wrote:

> As I told you before.  the nvcorrd log will show the event, with the
> command to be executed, being sent to actionsvr.   The actionsvr logs.
> nvaction.alog/blog should show that command being received, at the same
> timestamp as in the nvcorrd.log.   If the script fails for some reason,
> that too should be logged in the nvaction.alog/blog.
> 
> James Shanks
> Level 3 Support  for Tivoli NetView for UNIX and Windows
> Tivoli Software / IBM Software Group
> 
> 
>                                                                         
>   
>              Mario Behring                                              
>   
>              <mariobehring@yah                                          
>   
>              oo.com>                                                   
> To 
>              Sent by:                  nv-l AT lists.us.ibm DOT com           
>  
>   
>              owner-nv-l@lists.                                         
> cc 
>              us.ibm.com                                                 
>   
>                                                                   
> Subject 
>                                        Re: [nv-l] script not running on 
>   
>              08/16/2005 04:57          ruleset                          
>   
>              PM                                                         
>   
>                                                                         
>   
>                                                                         
>   
>              Please respond to                                          
>   
>                    nv-l                                                 
>   
>                                                                         
>   
>                                                                         
>   
> 
> 
> 
> 
> James...that´s the problem...I think that the script is not being
> executed...and so far I do not know why...how can I be sure that the
> script is executed ?
> 
> Thanks
> 
> Mario
> 
> 
> 
> --- James Shanks <jshanks AT us.ibm DOT com> wrote:
> 
> > If the script is being executed, then there is nothing more to be done
> > on
> > the NetView side.
> > You'd need a diagnostic tool from TEC to see anything after that. 
> They
> > own
> > postemsg and the library where the code resides.
> > That's all the advice I can give you.
> > HTH
> >
> > James Shanks
> > Level 3 Support  for Tivoli NetView for UNIX and Windows
> > Tivoli Software / IBM Software Group
> >
> >
> >
> >
> >              Mario Behring
> >
> >              <mariobehring@yah
> >
> >              oo.com>
> > To
> >              Sent by:                  nv-l AT lists.us.ibm DOT com
> >
> >              owner-nv-l@lists.
> > cc
> >              us.ibm.com
> >
> >
> > Subject
> >                                        Re: [nv-l] script not running
> on
> >
> >              08/16/2005 04:36          ruleset
> >
> >              PM
> >
> >
> >
> >
> >
> >              Please respond to
> >
> >                    nv-l
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > James,
> >
> > You´re right...I am also running the internal adapter, but the
> > BufferEvents was set to NO for the postemsg command (I am using the -f
> > option pointing to a configuration file). In any case, just to see if
> > something happens, I´ve changed the BufferEvents to YES and set the
> > BufEvtPath a path different from the one that the internal adapter is
> > using (the default).
> >
> > Also, I have two different NV rulesets, one that the internal adapeter
> > points to and the other that calls the "Action" box, which calls the
> > postemsg script. The script gets the NVATTR_? variables from the
> memory
> > when the event occurs and fill the postemsg attributes...but still no
> > event reaches the TEC....
> >
> > Thanks.
> >
> > Mario
> >
> >
> >
> >
> >
> >
> >
> > --- James Shanks <jshanks AT us.ibm DOT com> wrote:
> >
> > > Are you also running the internal TEC adapter?  Then you must
> specify
> > > different and unique BufEvtPath values for the internal adapter (in
> > your
> > > tecint.conf) and on your postemsg command, or the TEC library code
> in
> > > each
> > > case will try to write to the same cache files and the two processes
> > > will
> > > interfere with each other doing cache management.
> > >
> > > You can issue the command "nvcdebug -n" to see what rulesets nvcorrd
> > is
> > > running by looking in the nvcorrd.alog.  And if you want to see it
> > > process
> > > traps through them, issue "nvcdebug -d all".  Look for the
> eyecatcher
> > > "Received a trap" and "Finished with the trap" in the log. 
> Everything
> > > that
> > > happens in between is him processing that event.  The nvcorrd.alog
> and
> > > blog
> > > swap every thousand lines or so.  But during the processing of your
> > > trigger
> > > trap, you should see him hand it off to actionsvr.   And you should
> > also
> > > see in actionsvr's nvaction.alog/blog that same event coming in and
> > the
> > > results of your script being logged.
> > >
> > > If that's not enough to help, I suggest you call Support.
> > >
> > > James Shanks
> > > Level 3 Support  for Tivoli NetView for UNIX and Windows
> > > Tivoli Software / IBM Software Group
> > >
> > >
> > >
> > >
> > >              Mario Behring
> > >
> > >              <mariobehring@yah
> > >
> > >              oo.com>
> > > To
> > >              Sent by:                  NetView List
> > >
> > >              owner-nv-l@lists.         <nv-l AT lists.us.ibm DOT com>
> > >
> > >              us.ibm.com
> > > cc
> > >
> > >
> > >
> > > Subject
> > >              08/16/2005 10:22          [nv-l] script not running on
> > >
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com