Networker

Re: [Networker] nsr daemons die on the server after upgrade from networker 7.4.2 to 7.5.1

2009-04-09 14:44:11
Subject: Re: [Networker] nsr daemons die on the server after upgrade from networker 7.4.2 to 7.5.1
From: Lam Nguyen <tien.lam.nguyen AT GMAIL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 9 Apr 2009 14:36:50 -0400
What is your upgrade process ? According to the upgrade manual you have to
uninstall the previous version and install 7.5.1 after that.
As for the authentication you can have LDAP capability with 7.5.1 but I
think there is a default login you can use to login.



On Thu, Apr 9, 2009 at 12:54 PM, Nico De Ranter <nico AT sonycom DOT com> wrote:

> I did install the upgrade enabled prior to the upgrade (and added the
> authorisation code I got from EMC) so that shouldn't be a problem.
>
> I haven't tried backing up anything because I'm unable to do anything at
> all.  Even running 'nsradmin -p nsrexec' complains nsrexec is not
> registered in RPC (eventough that's currently the only nsr process
> running and I can see it when doing an 'rpcinfo -p'.  I'm currently
> reinstalling Networker again hoping I made some mistake the first time.
>
> Nico
>
> On Thu, 2009-04-09 at 11:23 -0500, Fazil Saiyed wrote:
> > Hello,
> > Have you tried running some test backups and restore, the only error i
> can
> > relate to is " program not registered" this may pop up if the services
> are
> > not started up completely and you would try to connect to the Legato
> > server , this should go away as the services startup, or else you have
> not
> > applied the required licences prior to upgrade ( as mentioned in the
> > release doc).
> > Thanks
> >
> >
> >
> > Nico De Ranter <nico AT SONYCOM DOT COM>
> > Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
> > 04/09/2009 10:51 AM
> > Please respond to
> > EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please 
> > respond
> > to
> > Nico De Ranter <nico AT SONYCOM DOT COM>
> >
> >
> > To
> > NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > cc
> >
> > Subject
> > nsr daemons die on the server after upgrade from networker 7.4.2 to 7.5.1
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> > I just upgraded my Networker server from 7.4.2 to 7.5.1.  When I start
> > networker on the server (=storage node) after a while I see
> > only /usr/sbin/nsrexecd is still alive and I can't connect to the server
> > using NMC. I believe there should be also a nsrmmdbd and nsrd right?  In
> > the daemon.raw file I see:
> >
> > ==============================================================
> > 9870 1239291650 2 0 0 1 1787 0 myosotis nsrmmdbd 45 media db is
> > consistency checking the database 0
> > 10106 1239291651 2 0 0 1 1787 0 myosotis nsrmmdbd 29 media db is open
> > for business 0
> > 0 1239291654 2 0 0 1 1791 0 myosotis nsrjobd 2 %s 1 0 28 @(#) Product:
> > NetWorker
> > 0 1239291654 2 0 0 1 1791 0 myosotis nsrjobd 2 %s 1 0 34 @(#) Release:
> > 7.5.1.Build.269
> > 0 1239291654 2 0 0 1 1791 0 myosotis nsrjobd 2 %s 1 0 22 @(#) Build
> > number: 269
> > 0 1239291654 2 0 0 1 1791 0 myosotis nsrjobd 2 %s 1 0 47 @(#) Build
> > date:   Fri Mar 20 23:05:02 PDT 2009
> > 0 1239291654 2 0 0 1 1791 0 myosotis nsrjobd 2 %s 1 0 29 @(#) Build
> > arch.:  sol10amd64
> > 0 1239291654 2 0 0 1 1791 0 myosotis nsrjobd 2 %s 1 0 53 @(#) Build
> > info:   DBG=0,OPT=-O2 -fno-strict-aliasing
> > 0 1239291656 2 0 0 1 1780 0 myosotis nsrd 49 notification process "%s"
> > failed with status "%d" 2 0 40 /usr/ucb/mail -s "Backup status message"
> > 1 1 1
> > 0 1239291656 2 0 0 1 1780 0 myosotis nsrd 2 %s 1 0 28 @(#) Product:
> > NetWorker
> > 0 1239291656 2 0 0 1 1780 0 myosotis nsrd 2 %s 1 0 34 @(#) Release:
> > 7.5.1.Build.269
> > 0 1239291656 2 0 0 1 1780 0 myosotis nsrd 2 %s 1 0 22 @(#) Build number:
> > 269
> > 0 1239291656 2 0 0 1 1780 0 myosotis nsrd 2 %s 1 0 47 @(#) Build date:
> > Fri Mar 20 23:05:02 PDT 2009
> > 0 1239291656 2 0 0 1 1780 0 myosotis nsrd 2 %s 1 0 29 @(#) Build arch.:
> > sol10amd64
> > 0 1239291656 2 0 0 1 1780 0 myosotis nsrd 2 %s 1 0 53 @(#) Build info:
> > DBG=0,OPT=-O2 -fno-strict-aliasing
> > 9512 1239291656 2 0 0 1 1790 0 myosotis nsrindexd 29 Cannot open
> > resource database 0
> > 39078 1239291656 0 0 2 1 1790 0 myosotis nsrindexd 14 %s error: %s%s 3 0
> > 3 RPC 49 100 2445 92 Authentication failed or no valid authentication
> > methods supported by both client and server 0 0
> > 12541 1239291656 2 0 0 1 1780 0 myosotis nsrd 9 %s has %s 2 20 9
> > nsrindexd 0 20 exited with status 1
> > 38758 1239291656 2 0 0 1 1780 0 myosotis nsrd 9 %s %s: %s 3 0 17
> > networker daemons 0 8 critical 0 34 nsrindexd has exited with status 1
> > 12546 1239291656 2 0 0 1 1780 0 myosotis nsrd 13 shutting down 0
> > 10107 1239291656 2 0 0 1 1787 0 myosotis nsrmmdbd 18 media db is closed
> > 0
> > 39078 1239291656 0 0 2 1 1780 0 myosotis nsrd 14 %s error: %s%s 3 0 6
> > SYSTEM 49 60 962 14 SSL Error: %s  1 0 31 Unable to setup decryption key
> > 0 0
> > 12533 1239291656 2 0 0 1 1780 0 myosotis nsrd 19 successful shutdown 0
> > =================================================================
> >
> > I notice:
> >
> > "nsrindexd 29 Cannot open resource database 0"
> > Unfortunately it's not really telling me what resource database it's
> > trying to open or what could be the reason for this.  Running an 'nsrck
> > -L2' runs fine so all indexes seem fine to me.
> >
> > Then it says:
> >
> > "Authentication failed or no valid authentication methods supported by
> > both client and server"
> > This surprises me. The /nsr/res/servers file is the same as before the
> > update. Needless to say before the upgrade everything worked fine.  Did
> > the authentication scheme change in 7.5?  I seem to remember seeing
> > something about that but I didn't encounter any any specific
> > configuration changes required to make this work.
> >
> > "Unable to setup decryption key"
> > What decryption key, should I have installed a key somewhere? Again I
> > didn't see anything in the manual.
> >
> >
> > When trying to connect from the NMC (running on a separate system) I get
> > "unable to connect to server: program not registered"  but I guess
> > that's a result of the problems above.
> >
> > Any help would be very much appreciated.
> >
> > Nico
>
> 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