So actionsvr is now back up?
It is possible that the child process finally completed and went away while
you were waiting for a reply from me, which is why it wasn't there when you
went back to check.
Anything interesting in /usr/OV/log/nvaction.alog or .blog (whichever was
active at the time)?
Tivoli (NetView for UNIX) L3 Support
Greg Redder <redder AT yuma.ACNS.ColoState DOT EDU> on 08/20/98 10:47:55 AM
Please respond to "REDDER Gregory J." <redder AT yuma.ACNS.ColoState DOT EDU>
To: James Shanks
cc: NV-L AT ucsbvm.ucsb DOT edu
Subject: Re: actionsvr not starting
I did a ps -ef | grep action - it isn't running.
There was only one core file in the entire /usr/OV directory and
that was in /usr/OV/PD/cores/actionsvr, but it was from July 21. I
moved it to a different name, just in case and tried again, but
The starting up the map without using nv6000 was helpful though! I
thought I was really stuck. Now, I'm just kind of stuck ;-)
I've stopped and started all daemons thinking that might help. I've
checked disk space and all appears well. Hmm....
Thank you -Greg Redder
On Thu, 20 Aug 1998 James_Shanks AT tivoli DOT com wrote:
> Date: Thu, 20 Aug 1998 08:29:09 -0400
> From: James_Shanks AT tivoli DOT com
> To: NV-L AT ucsbvm.ucsb DOT edu,
REDDER Gregory J. <redder AT yuma.ACNS.ColoState DOT EDU>
> Subject: Re: actionsvr not starting
> Do a ps -ef | grep actionsvr . Do you see one running? If so, kill it.
> This situation is usually caused by actionsvr dying or being killed while
> one of his children is still up. The child then owns the port that the
> next actionsvr is trying to get at startup.
> That won't tell you why this happened. If you want to pursue that, I'd
> start with /usr/OV/log/nvaction.alog and .blog.
> And look for cores in the / directory.
> Finally, you do not have to start the GUI with the nv6000 command if you
> are having problems with just one "non-essential" daemon. Issue ovw
> rather than nv6000 and the GUI will start. Then you can work on the
> daemon problem at your leisure. If ovwdb is down then the GUI will not
> start this way either. If ovtopmd is down, then the statuses will be
> wrong. But actionsvr just executes actions out of rulesets, so he is not
> really a show-stopper.
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
> Greg Redder <redder AT yuma.ACNS.ColoState DOT EDU> on 08/19/98 05:00:15 PM
> Please respond to "REDDER Gregory J." <redder AT yuma.ACNS.ColoState DOT EDU>
> To: NV-L AT UCSBVM.UCSB DOT EDU
> cc: (bcc: James Shanks)
> Subject: actionsvr not starting
> Dear all,
> I'm not able to search the nv-l archives - no answer after 4 hours.
> Also, the knowledge base at Tivoli is temporarily out of service.
> So, here I am ;-)
> I'm running NetView V5.0 on AIX4.2.1.
> When I try to start nv6000, I get the following error:
> ERROR: The following REQUIRED daemons are not running:
> As root user, start all the daemons by using one of the following
> a) use the smit (TME 10 desktop) utility
> b) issue the command: /usr/OV/bin/ovstart
> c) rerun this command
> So, as root, I run:
> and get:
> behavior: OVs_WELL_BEHAVED
> state: NOT_RUNNING
> PID: 33364
> last message:
> exit status: exit(1)
> I look in: /usr/OV/log/nvaction.alog and see:
> 98/08/19 14:58:29 : local host is delta
> 98/08/19 14:58:29 nl_Actionsvr.C : Unable To Open action
> Channel Trying Port 1670
> 98/08/19 14:58:29 nl_Actionsvr.C : Unable to open port
> 1670... exiting
> Any ideas, please?
> Thank you --Greg Redder
> Greg Redder Academic Computing & Networking
> Colorado State University, ACNS Phone:(970)491-7222 FAX:
> 601 S. Howes, Room 625 E-mail: redder AT yuma.colostate DOT edu
> Fort Collins, CO 80523 PGP
Greg Redder Academic Computing & Networking
Colorado State University, ACNS Phone:(970)491-7222 FAX:
601 S. Howes, Room 625 E-mail: redder AT yuma.colostate DOT edu
Fort Collins, CO 80523 PGP