To: | nv-l@lists.tivoli.com |
---|---|
Subject: | RE: Actionsvr daemon not getting started |
From: | z_esm_karekars <z_esm_karekars@bharatpetroleum.com> |
Date: | Wed, 21 Nov 2001 11:41:56 +0530 |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. Hi James, I faced similar problem today. I had created few rulesets out of which I want to disable some during night time, hence I am running two scripts, one at night time and another in morning through cron which follows the following steps and this is working perfectly for almost two months without fail. 1. Stop actionsvr daemon 2. Rename the ESE.automation file with another file which does not have unwanted rulesets 3. Restart the actionsvr daemon 4. Check the nvaction.alog for registering all the rulesets Morning script will restore the original ESE.automation file with all the rulesets. Today morning it was observed that actionsvr was started but the rulesets failed to register and not a single ruleset was registered. I tried restarting the actionsvr, nvcorrd, nvserverd couple of times and did not helped me. Finally after ovstop and ovstart only I could register all the rulesets. What could be the reason for such behavoiur Regards, Santosh > ---------- > From: James Shanks[SMTP:jshanks@US.IBM.COM] > Reply To: IBM NetView Discussion > Sent: Tuesday, November 20, 2001 11:06 PM > To: IBM NetView Discussion > Subject: RE: [NV-L] Actionsvr daemon not getting started > > > Scott - > > There has got to be more than just vi here. I just did this three times > and had no problem starting or stopping the daemon. > Have you checked how many actionsvr processes are active and whether they > all have the same parent BEFORE you do your vi edit? > The children would all share the same file descriptors as the parent, but > once they are gone, they are gone. > And I don't see why you would have to delete and reallocate the file, if > you just kill any remaining daemons with "kill -9 <hung_actionsvr_pid>". > > You could, of course, always avoid the problem by stopping the daemon > before you edit the file. > > > I have never seen anything like what you describe. > > > If you want to pursue this with Support, feel free. > > > James Shanks > Level 3 Support for Tivoli NetView for UNIX and NT > Tivoli Software / IBM Software Group > > > > > > "Scott Bursik" <tivoliesm@HOTMAIL.COM> > Sent by: owner-nv-l@tkg.com > > 11/20/2001 12:05 PM > Please respond to IBM NetView Discussion > > To: nv-l@tkg.com > cc: > Subject: RE: [NV-L] Actionsvr daemon not getting started > > > > > I have had the smae issue, and I continue to have the same issue from time > > to time. If I use VI to edit ESE.automation the daemon will hang when I > try > to restart it. If this happens I open the file in VSedit and copy the > entries. I then delete the ESE.automation file and recreate it with VSedit > > and restart the daemon and everything loads perfectly. I don't know why? > There are no hidden characters, permissions on the file have not changed, > nothing... I use this little script so I can see the daemon restart and > see > the logging to the nvaction.alog as it loads the rules. PS - I have > checked > my rules I am loading 50 times at least and even reduced it down to 1 rule > > just to make sure and I still don't have an answer. > > Script: > +++++++++++++++++++++++++++++++++++++++++++++ > > #!/usr/bin/ksh > > echo RESETTING THE NVACTION DAEMON......... > cd /usr/OV/bin > ovstop actionsvr > ovstart actionsvr > tail -f /usr/OV/log/nvaction.alog > > ++++++++++++++++++++++++++++++++++++++++++++++ > > You will have to manually break out of the tail.... > > Let me know what you come up with! This has been bugging me for months. > > Scott > > > >From: anand anupam <ananda@bharatpetroleum.com> > >Reply-To: IBM NetView Discussion <nv-l@tkg.com> > >To: IBM NetView Discussion <nv-l@tkg.com> > >Subject: RE: [NV-L] Actionsvr daemon not getting started > >Date: Tue, 20 Nov 2001 14:46:56 +0530 > > > >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@tkg.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@us.ibm.com > > > > > > > > > > Santosh R Karekar/India/IBM@IBMIN > >Sent by: owner-nv-l@tkg.com > >10/11/2001 10:05 AM > >Please respond to IBM NetView Discussion > > > > > > To: nv-l@tkg.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 > > > > > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > _________________________________________________________________________ > NV-L List information and Archives: http://www.tkg.com/nv-l > > > > Hi James, I faced similar problem today. I had created few rulesets out of which I want to disable some during night time, hence I am running two scripts, one at night time and another in morning through cron which follows the following steps and this is working perfectly for almost two months without fail. 1. Stop actionsvr daemon
Morning script will restore the original ESE.automation file with all the rulesets. Today morning it was observed that actionsvr was started but the rulesets failed to register and not a single ruleset was registered. I tried restarting the actionsvr, nvcorrd, nvserverd couple of times and did not helped me. Finally after ovstop and ovstart only I could register all the rulesets. What could be the reason for such behavoiur Regards,
----------
Scott - There has got to be more than just vi here. I just did this three times and had no problem starting or stopping the daemon. Have you checked how many actionsvr processes are active and whether they all have the same parent BEFORE you do your vi edit? The children would all share the same file descriptors as the parent, but once they are gone, they are gone.
You could, of course, always avoid the problem by stopping the daemon before you edit the file. I have never seen anything like what you describe. If you want to pursue this with Support, feel free. James Shanks
"Scott Bursik" <tivoliesm@HOTMAIL.COM>
11/20/2001 12:05 PM
I have had the smae issue, and I continue to have the same issue from time
Script:
#!/usr/bin/ksh echo RESETTING THE NVACTION DAEMON.........
++++++++++++++++++++++++++++++++++++++++++++++ You will have to manually break out of the tail.... Let me know what you come up with! This has been bugging me for months. Scott >From: anand anupam <ananda@bharatpetroleum.com>
_________________________________________________________________
_________________________________________________________________________
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: vpn virtual addresses, Stephen Hochstetler |
---|---|
Next by Date: | Re: Turning Off TFTP Service, helmut . schroeder . hs |
Previous by Thread: | RE: Actionsvr daemon not getting started, James Shanks |
Next by Thread: | Re: RE: Actionsvr daemon not getting started, Haseneder, Martina |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web