Thanks for sharing your experience George.
This is the primary reason I do not run the NMC on our NW Server... Too
much interaction or inter-dependency between the two that must be
learned through experiences such as yours. And EMC also recommends
running NMC on a stand alone NW client as opposed to running it on the
server, although they don't say you can't, they just suggest it runs
better on something other than the server... Which has also been my
experience so far. I first ran NMC on our NW server, then moved it to a
client when the 7.6 NMC came out. It works fine with our 7.4.4 server
and is an improvement over the previous release of NMC.
> -----Original Message-----
> From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of George Sinclair
> Sent: Wednesday, March 31, 2010 10:44 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Unable to start/login to NMC
> following RHEL update
>
> Goslin, Paul wrote:
> > Thank You both Frank and George,
> > I took the simpler approach as suggested by George (of
> simply moving
> > the csp.clb files from the /cst/ directory), rather than
> > uninstall/re-install. It worked great....
>
> One thing that I forgot to mention was that I really wanted
> to stop httpd before doing anything (this is on Unix), so I
> stopped/restarted and then stopped /etc/init.d/gst, but the
> silly httpd processes were still running! I managed to stop
> one of them (the last one), but every time I tried to stop
> the next oldest one, it would just restart, using a new PID.
> Sheesh! I finally stopped the first one (owned by 1 or
> init?), and that stopped everything. Usually, I prefer to
> work my way up the chain, but this stuff doesn't play very
> nice. Anyway, once everything was finally stopped, I then ran
> the fix as outlined in my earlier e-mail. But, heck,
> uninstalling/re-installing is always a solution, too.
>
> On other somewhat related note - maybe kinda dumb - is that
> one day I try to start NW on the primary backup server, and
> it hangs for a while, and then, after I get the prompt, I
> check to see what's running, and there's only one nsr process
> running?!!! I then stop/restart - same problem. Hmm ... OK,
> so then I notice that nmc is running, so I stop nmc, restart
> NW, and all is well. I then restart nmc. Apparently, nmc must
> be started after NW and not before. Otherwise, NW may not
> run. Not sure about Windows, but this is just a potential
> gotcha that might be easy to forget about. The clue seems to
> be that without nmc running, NW starts up right away (very
> little delay); otherwise, it hangs for a little while first,
> and then launches maybe just one process and that's it.
>
> George
>
>
> >
> > Thanks for the quick solutions
> >
> > Paul
> >
> >> -----Original Message-----
> >> From: EMC NetWorker discussion
> >> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Frank Swasey
> >> Sent: Tuesday, March 30, 2010 6:08 PM
> >> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> >> Subject: Re: [Networker] Unable to start/login to NMC
> following RHEL
> >> update
> >>
> >> Paul,
> >>
> >> I ran into the same issue on my RHEL 5.4 system that I
> updated last
> >> week. I wound up uninstalling NMC, killing off the httpd,
> and then
> >> installing the NMC rpm again. It is now working just fine again.
> >>
> >> Frank
> >>
> >> On 3/30/10 4:11 PM, Goslin, Paul wrote:
> >>> Server is 7.4.4 on a Windows 2003 se server. My NMC is
> >> installed on a
> >>> RHEL 5.3 client (nmc=7.6), has been working fine until today when
> >>> applied some RedHat updates. Now the gstd daemon will not
> >> stay up when
> >>> I start it, so I can't login to NMC as a result. The error
> >> log on the
> >>> NMC host shows:
> >>>
> >>> 31581 03/30/2010 03:50:11 PM 2 0 0 4146267840 6811 0
> >>> matrix.domain.com gstd *** gstd starting at Tue Mar 30
> >> 15:50:11 2010
> >>> 0 03/30/2010 03:50:27 PM 2 0 0 4146267840 6811 0
> matrix.domain.com
> >>> gstd
> >>> acm: Ex
> >>> ternal directory library initialization failed
> >>> 376 03/30/2010 03:50:27 PM 0 0 2 4146267840 6811 0
> >> matrix.domain.com
> >>> gstd SYSTE M error: Failed to retrieve csp_serviceManager.
> >> Error code:
> >>> -9, message:
> >>> System
> >>> fingerprint differences exceed the acceptable threshold.
> >>> 0 03/30/2010 03:50:27 PM 2 0 0 4146267840 6811 0
> matrix.domain.com
> >>> gstd wakeup error in ACM -- request shutdown 0 03/30/2010
> >> 03:50:35 PM
> >>> 2 0 0 4146267840 6811 0 matrix.domain.com gstd
> >>> http: W
> >>> eb server 6816 still running after 8 seconds
> >>> 31582 03/30/2010 03:50:40 PM 2 0 0 4146267840 6811 0
> >>> matrix.domain.com gstd *** gstd stopping at Tue Mar 30
> >> 15:50:40 2010
> >>> Did the RHEL update cause this ??? How are we to maintain
> >> our stuff if
> >>> an update breaks NMC ??
> >>> Guess maybe an un-intstall / re-install might fix this?
> >>>
> >>> Thanks ....
> >>>
> >>> To sign off this list, send email to
> >> listserv AT listserv.temple DOT edu and
> >>> type "signoff networker" in the body of the email. Please
> write to
> >>> networker-request AT listserv.temple DOT edu if you have any
> problems with
> >>> this list. You can access the archives at
> >>> http://listserv.temple.edu/archives/networker.html or via RSS at
> >>> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >> --
> >> Frank Swasey | http://www.uvm.edu/~fcs
> >> Sr Systems Administrator | Always remember: You are UNIQUE,
> >> University of Vermont | just like everyone else.
> >> "I am not young enough to know everything." - Oscar Wilde
> >> (1854-1900)
> >>
> >> To sign off this list, send email to
> listserv AT listserv.temple DOT edu and
> >> type "signoff networker" in the body of the email. Please write to
> >> networker-request AT listserv.temple DOT edu if you have any
> problems with
> >> this list. You can access the archives at
> >> http://listserv.temple.edu/archives/networker.html or via RSS at
> >> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >>
> >
> > To sign off this list, send email to
> listserv AT listserv.temple DOT edu and
> > type "signoff networker" in the body of the email. Please write to
> > networker-request AT listserv.temple DOT edu if you have any problems with
> > this list. You can access the archives at
> > http://listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
>
>
> --
> George Sinclair
> Voice: (301) 713-3284 x210
> - The preceding message is personal and does not reflect any
> official or unofficial position of the United States
> Department of Commerce -
> - Any opinions expressed in this message are NOT those of the
> US Govt. -
>
> To sign off this list, send email to
> listserv AT listserv.temple DOT edu and type "signoff networker" in
> the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any
> problems with this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS
> at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
