Networker

Re: [Networker] Failed to startup networker services after recovering "res"

2010-04-21 12:33:05
Subject: Re: [Networker] Failed to startup networker services after recovering "res"
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 21 Apr 2010 11:28:47 -0500
In regard to: [Networker] Failed to startup networker services after...:

I tried to migrate Networker from one server to another, I followed the DR 
guide to use mmrecov to restore media database(mm) and resource files(res).
I could restart networker after /nsr/mm was overwritten by "mmrecov", and I 
could see all media info. from the old server. However, I couldn't start the networker 
after I replaced /nsr/res with /nsr/res.R

# ps -ef | grep nsr
root     20693     1  0 18:20 ?        00:00:00 /usr/sbin/nsrexecd
root     20702     1  0 18:20 ?        00:00:00 /usr/sbin/lgtolmd -p /nsr/lic 
-n 1
root     20707     1  0 18:20 ?        00:00:00 /usr/sbin/nsrd
root     20720 20707  0 18:20 ?        00:00:00 [nsrd] <defunct>
root     20722 20707  0 18:20 ?        00:00:00 [nsrd] <defunct>
root     20730 10440  0 18:20 pts/0    00:00:00 grep nsr

I got the following messages in daemon.log:

04/20/10 15:14:18 nsrd: WARNING: NSR configuration database detected invalid 
resource /nsr/res/nsrdb/05/000f0260000000000000000042fcadd2820e230a
04/20/10 15:14:18 nsrd: Invalid resource saved at 
/nsr/res/nsrdb/dbg/000f0260000000000000000042fcadd2820e230a
04/20/10 15:14:18 nsrd: WARNING: NSR configuration database detected invalid 
resource /nsr/res/nsrdb/06/00100260000000000000000042fcadd2820e230a
04/20/10 15:14:18 nsrd: Invalid resource saved at 
/nsr/res/nsrdb/dbg/00100260000000000000000042fcadd2820e230a


Each of those resources are going to be files that you can view
(*carefully*) with a text editor even just "cat".  I recommend you take a
look at them and figure out what the resource is.  For example, here's one
that I have setting in the dbg directory on our NetWorker server:


# pwd
/nsr/res/nsrdb/dbg
# cat 07099e3b365e7c4786816f10 client: foo.nodak.edu;
data operation: save;
group: Email2Week;
media operation: mount;
name: "L700-PART2:2667";
nsrmmd host: nsrserverhost.nodak.edu;
nsrmmd id: 102;
nsrmmd mount id:;
operation: writing;
pool: Email2Week;
save set: /tmp;
type: NSR mount request;
volume name: "Email2Week:012";
resource identifier: 7.9.158.59.54.94.124.71.134.129.111.16(1)

Looking at the "type", this is a resource related to a mount request.
Some resources are critical for NetWorker to function at all.  Other
resources are much less critical.  The mount request resource I show
above would be less critical.  If it were preventing me from being
able to start the backup server, I would contact support and get
confirmation from them that it's OK for me to delete the resource
(probably using nsradmin with -d and a query).

Messing with the resource database is very, very dangerous, even
for the experienced.  You should get in touch with support and see
if they can determine what should be done about each of those resources.

sh: /BACKUP-REP/report.log: No such file or directory
04/20/10 15:14:18 nsrd: server notice: started
sh: /usr/ucb/mail: No such file or directory
sh: /BACKUP-REP/report.log: No such file or directory

You have resources (probably notifications) that reference things under
those paths.  They should be relatively straightforward to find.

        cd /nsr/res
        find . -type f -exec egrep '/usr/ucb/mail|/BACKUP-REP/' {} /dev/null \;

You could update those resources to use correct paths for your new system
using nsradmin with the -d or -f options while networker is offline.
nsradmin is also unfortunately a little unfriendly to newcomers.

04/20/10 15:14:18 nsrd: registration notice: invalid auth codes detected.

Not surprising.  Your hostid is almost certainly different.

...
04/20/10 15:43:31 nsrd: error initializing resource file.
04/20/10 15:43:31 nsrexecd: The user does not have the privileges perform the 
requested operation. Requester: EMCUserNone/bacchus@(Unknown)

That's likely a problem.  You are starting everything as root, correct?
You're not using any kind of mandatory access control on your new server,
are you?

Questions: 1. Where does Networker keep such "/BACKUP-REP/report.log"
and `/BACKUP-SCRIPTS/script' resource information on the original
server? I was not the guy who originally setup the server. I couldn't
find any settings in NMC according to such info. Can I force Networker
to ignore them during startup?

Probably not.  You'll probably have to fix the resources, which can be
done without NetWorker running.  See the nsradmin man page.

2. It looked like the enabler codes from the old server were recovered
to the new server, but the new server couldn't accept them. Can I keep
using the evaluation code to startup the services, then I can use NMC to
enter the new enabler codes?

That *should* work.  I think the issues you're running into are related to
the other problems, not the invalid enabler codes.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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