Matt,
unfortunately I cannot look into an Nways box now but I suppose there is one
daemon not starting upon whom the others depend.
Try to look into their LRF's and you may get who's that. 0.02$
HTH,
Best regards,
Vladimir.
Matt Ashfield wrote:
>
> Hi,
> James thanks for the tips!
> I killed the midmand and then stopped the dameons and started them as
> you
> suggested. This time trapd started. I'm still having problems with my
> NWays
> daemons. 4 of them to be precise, that won't start, they have the
> UNSTARTABLE state when I do an ovstatus..They are
> nvot_server
> cmld
> ahmclp
> ahmbserver
> I know that these are the MAJOR dameons used for Nways, so I definetely
> need
> them running...Any advice?
>
> Thanks
>
> Matt
> mda@unb.ca
>
> -----Original Message-----
> From: James Shanks <James_Shanks@tivoli.com>
> To: NV-L@ucsbvm.ucsb.edu <NV-L@ucsbvm.ucsb.edu>
> Date: Thursday, July 15, 1999 5:47 PM
> Subject: Re: NWays Installation Help!
>
> >Do netstat -an. Is 162/udp shown? Then some process or other has it
> and
> you
> >will have to find that one and kill it for trapd to start. Do a ps -ef
> (or
> >even ovstatus) and see what you find. If Nways installed midmand, then
> kill it,
> >as he cannot run in the same box as NetView without reconfiguration.
> Not
> him?
> >Then find what new stuff is running and kill it one at a time. Or kill
> all
> the
> >daemons down to nvsecd, ovstart trapd, and then ovstart. I'll bet the
> guy
> who
> >has trapd's port won't start if trapd comes up first. This should get
> you
> back
> >and running while you review what took place.
> >
> >James Shanks
> >Tivoli (NetView for UNIX) L3 Support
> >
|