nv-l
[Top] [All Lists]

Re: [nv-l] nvaction.alog - command successful

To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] nvaction.alog - command successful
From: awatthey@mmm.com
Date: Thu, 17 Apr 2003 07:57:41 +0100
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Thu, 17 Apr 2003 08:07:24 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
List-help: <mailto:nv-l-help@lists.tivoli.com>
List-post: <mailto:nv-l@lists.tivoli.com>
List-subscribe: <mailto:nv-l-subscribe@lists.tivoli.com>
List-unsubscribe: <mailto:nv-l-unsubscribe@lists.tivoli.com>
Mailing-list: contact nv-l-help@lists.tivoli.com; run by ezmlm
James,

Has there been a big problem?  Today I am receiving emails from the 9
april.  They are arriving completely out of order.

Alan.


                                                                                
                                                       
                      James Shanks                                              
                                                       
                      <jshanks@us.ibm.co       To:       nv-l@lists.tivoli.com  
                                                       
                      m>                       cc:       (bcc: Alan 
Watthey/UK-Europe/3M/US)                                           
                                               Subject:  [nv-l] nvaction.alog - 
command successful                                     
                      09/04/2003 19:16                                          
                                                       
                                                                                
                                                       
                                                                                
                                                       





I'm a little unclear about what you are asking here so I'll just describe
the mechanism.

actionsvr assigns an arbitrary sequence number and forks a child process
to execute the command he has received.  That child inherits all his open
files and sockets, so when it writes, it writes to the same file,
nvaction.alog/blog, as the parent.  The  child process builds a command
stream and forks a process to run it, while maintaining a pipe to that
child so that stdout and stderr can be echoed back.  The child actionsvr
process invokes a routine to do that based on the return code from the
command.   When successful, he writes the successful message to the log
and echoes back stdout.  When unsuccessful, he writes that message and
echoes back stderr.  The he closes the pipe and exits.

Since each of those messages end with a newline, the stuff echoed back
would not appear in the output of your grep.  Are you asking about the
numbering sequence?  The numbers start over every time actionsvr is
recycled, so you could see several numbers the same, and they roll over at
1000 in any case.
Are you thinking that some actions were lost?



James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
----- Forwarded by James Shanks/Raleigh/IBM on 04/09/2003 02:03 PM -----


"Treptow, Craig" <Treptow.Craig@principal.com>
04/09/2003 09:06 AM


        To:     "NetView List (E-mail)" <nv-l@lists.tivoli.com>
        cc:
        Subject:        [nv-l] nvaction.alog - command successful



Hi.  We are running Netview 7.1.3 with FixPack1 on AIX 5.1.  I've been
looking at the nvaction.alog and noticed something that I don't have a
good explanation for.  We execute various scripts to process some traps.
They normally, do a little work, and then generate another trap that we
forward on to TEC.  I've noticed that sometimes I see this in the log:


2003/04/08 10:54:54 :   6 :/usr/local/nv/bin/pfg-int-down-trap~2003/04/08
10:53:
54~1.3.6.1.6.3.1.1.5.3~2~0~2887450316~270851068~public~78~Serial1/1/1:0.24~32~3~

A~4
2003/04/08 10:54:54 :   7 :/usr/local/nv/bin/pfg-int-down-trap~2003/04/08
10:53:
54~1.3.6.1.6.3.1.1.5.3~2~0~2887450316~270851068~public~78~Serial1/1/1:0.24~32~3~

A~4
2003/04/08 10:54:54 :   6 command successful. output data is:
corp2-wan-dist-3.net.principal.com
Serial1/1/1:0.24
Serial1/1/1:0.24

2003/04/08 10:54:54 :   7 command successful. output data is:
corp2-wan-dist-3.net.principal.com
Serial1/1/1:0.24
Serial1/1/1:0.24

Most of the time, however, we never see the "command successful" in the
log:

# grep "command successful" nvaction.alog
2003/04/08 10:53:57 :   5 command successful. output data is:
2003/04/08 10:54:54 :   6 command successful. output data is:
2003/04/08 10:54:54 :   7 command successful. output data is:
2003/04/08 10:55:11 :   8 command successful. output data is:
2003/04/08 10:55:11 :   9 command successful. output data is:
2003/04/08 11:11:03 :   12 command successful. output data is:
2003/04/08 11:11:03 :   13 command successful. output data is:
2003/04/08 11:42:58 :   24 command successful. output data is:
2003/04/08 11:43:58 :   25 command successful. output data is:
2003/04/08 11:43:58 :   26 command successful. output data is:
2003/04/08 11:43:58 :   27 command successful. output data is:
2003/04/08 11:44:01 :   28 command successful. output data is:
2003/04/08 22:34:10 :   65 command successful. output data is:
2003/04/08 22:35:18 :   66 command successful. output data is:
2003/04/08 22:35:18 :   67 command successful. output data is:
2003/04/08 22:35:18 :   68 command successful. output data is:
2003/04/08 22:35:20 :   69 command successful. output data is:
2003/04/08 22:37:15 :   70 command successful. output data is:
2003/04/08 22:38:26 :   71 command successful. output data is:


In all cases, the script runs just fine and does what we want.  They are
Korn shell scripts and I've put "exit 0" at the end to make sure they exit
with a good return code.  This didn't change the behavior.

Can anybody shed some light on what is happening here?

Thanks for any help!


Craig

A dozen, a gross, and a score,
Plus three times the square root of four,
Divided by seven,
Plus five times eleven,
Equals nine squared plus zero, no more.


---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)




---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)






---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web