|
Re: [Networker] client is not getting index entries written...
2006-07-25 08:26:12
Stuart Whitby wrote:
Back to basics first. Check that the browse policy isn't set by default to something like "2
minutes" and that the group doesn't have "no index save" checked.
Thankfully, your server's Solaris. Get hold of a copy of the appropriate lsof for your OS version and install it. Run a backup of this client from a savegroup. From the server, run a "ps -ef | grep ADD" to check the PID of the nsrindexd -ADD process for this client. Now run "lsof -p <PID>" to identify whether this is saving to a particular file. Otherwise, get in touch with Support (or maybe just a shout to the list) to get a hold of dbgcommand for Solaris and run 'dbgcommand -p <nsrindexd's PID> "Debug=9"' (the main nsrindexd, not any of its child processes), run your group, then run 'dbgcommand -p <nsrindexd's PID> "Debug=0"'. Check the daemon.log afterwards to see if the main nsrindexd is complaining about anything. Alternatively (or as well), run the savegrp for this client from the command line using -vvv to get more output, and then try again using D3 and D9 on the group if nothing else has helped as yet.
Completely and totally bizarre.
If I run a manual save, I see the ADD command running on the server as
follows:
/usr/sbin/nsrindexd -a ADD monitor4 index for backup on monitor4.foo.com
However, when run from the server with savegrp, instead it is
/usr/sbin/nsrindexd -a ADD nsrhost.foo.com index for backup on
monitor4.foo.com
And, lsof shows that it has the networker server's index open instead of
the correct one.
Here is the save command being run remotely:
/emul/ia32-linux/usr/sbin/save -s nsrhost.foo.com -g Wednesday_full -LL
-f - -m monitor4 -l full -q -W 78 -N /usr/local /usr/local
(Note: This is a 64-bit Ubuntu Linux installation, so the 32-bit
compatibility is at play - don't know if this makes a difference, but I
have others that work fine).
So, the 10GB question: Why is it saving to the server's index instead of
its own?
Someone did mention seeing this on multi-homed installations. This host
is multi-homed in a sense - there is a heartbeat interface talking to
another box directly via crossover, but it does not have routes to it
for any traffic other than local.
-Brian
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
wit 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
|
|
|
