Did you do a  "ps -ef  | grep act" and see if one was still running?  If
the old one remains after ovstop, because it somehow got unparented, and
thus cannot be shut down by ovspmd any longer, then it will have 1670 open
and you will not be able to start a new actionsvr until all the old ones
have been killed.   I have seen this behavior occur when the action that
actionsvr has been set up to do itself gets hung, so that the actionsvr
child is not able to complete the action and exit even though his parent
has sent him the kill signal and gone away.

You can also check that 1670 really is in use by using netstat -a.  If you
find that it is, then you should go looking for the process which has it
open.  This is not easily done in UNIX unless you have lsof (which you can
obtain off the web and install), but if your actionsvr usually starts, then
it is a good bet that there is an old one still around.

You also should  investigate the action you have asked you actionsvr to do
and try to determine why it gets hung.  Remember that each iteration of an
action cause actionsvr to spawn a separate actionsvr child.  If each one is
going to do something like a database update, the later ones will have to
wait until the earlier ones complete since access to the database is a
serial process.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group




                                                                                
                  
                    anand anupam                                                
                  
                    <ananda@bharatpetr       To:     IBM NetView Discussion 
<nv-l AT tkg DOT com>        
                    oleum.com>               cc:                                
                  
                    Sent by:                 Subject:     RE: [NV-L] Actionsvr 
daemon not getting 
                    owner-nv-l AT tkg DOT com        started                    
                         
                                                                                
                  
                                                                                
                  
                    11/20/01 04:16 AM                                           
                  
                    Please respond to                                           
                  
                    IBM NetView                                                 
                  
                    Discussion                                                  
                  
                                                                                
                  
                                                                                
                  



Hi James,


I have experienced the same problem. Actionsvr was down and I was not able
to restart it. I checked all its references as suggested by you but I could
not locate any one. Usual ovstart/ovstop was also not helping and finally,
the server was rebooted to resolve this problem


Also, as clarified by you that opening the netview map should not be any
issue from any userid other than root even if actionsvr is down. In our
case, it was not happening. I mean no one was able to open the netview map
and every one was getting the same error message that required daemons
actionsvr is down.


In nvaction.alog there was an error saying that it could not open the port
1670 which is the default port. What could be the reason?





Regds....Anupam







From: owner-nv-l AT tkg DOT com
Date: 11/10/2001 11:35:38 AST
Subject: Re: [NV-L] Actionsvr daemon not getting started







First, do a "ps -ef  | grep actionsvr" and kill with -9 any you find
running.
My guess is that you have an old one that is no longer under control of
ovspmd and thus is not responding to ovstart/ovstop.


You will find this recommendation in the NetView diagnosis guide.





If that does not do it, then go to /usr/OV/log/nvaction.alog and look at
what is written there.  There may be error messages there to tell you what
is wrong.


If the console is not coming up then you are trying to start it as root.
When you are root, the netview script will try to start all the daemons
which are not up.


Use a different id and it will just give an error message and continue.
Since actionsvr is only used to process actions from rulesets, and to load
the background ones from ESE.automation, it does not have to be running for
the console to be active.


James Shanks
Level 3 Support
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks AT us.ibm DOT com







 Santosh R Karekar/India/IBM@IBMIN
Sent by: owner-nv-l AT tkg DOT com
10/11/2001 10:05 AM
Please respond to IBM NetView Discussion



        To:        nv-l AT tkg DOT com
        cc:
        Subject:        [NV-L] Actionsvr daemon not getting started









Hello all,


I had NetView 6.0.2 on AIX 4.3.3
I had made some changes to the ESE.automation and stopped the actionsvr
daemon, When I tried to start the daemon it does not get started , it does
not happen for so long also hence I used ovdelobj to delete the
registration of actionsvr.lrf and added back using ovaddobj the
actionsvr.lrf. Still after doing this I am not able to start the actionsvr
daemon.
Can anybody advice which configuration I need to look in to to get it
normal.
I am not able to get the NetView console up due to this demon not getting
started, If I remove the registration I am not able to get the
ESE.automation in action.
Please advice ASAP


Thax in advance Regards





_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l