As far as I can see your first error is:
"nwrecover: lookup failed to server solegato1.xxxxxxxx.edu"

That means your client is not able to resolve or connect your server. I would start from that.

Try using:

nsrck -L6 clientname

- to see if you can repair the index. If not recover the index from backups using:

nsrck -L7 clientname

You could also try checking the media database:

nsrim -X

dhamson2,

Looks like nsrck -L1 fixed it:

[root@solegato1 root]# nsrck -L1
nsrck: checking index for 'csubds5.xxxxxxxxx.edu'
nsrck: /backup/nsrln/nsr/index/csubds5.xxxxxxxx.edu/.nsr is missing; re-creating

After this nwrecover works for that client.

Thanks
Vic

Hi Victor,

This is really strange. .nsr in index directory is nothing else then skip directive. L1 does check index headers, but then the question is why your .nsr was removed in the first place. But it seems like your index was slightly corrupted indeed and that L1 did the job. The reference to your error can be found in nsrinfo manual. It says there "The index server is running, but was unable to process the query." (another reference is in TB 374, but that one probably doesn't count here as cause was something else).

Usually there is no reason for index to get corrupted under normal circumstances so unless you had crash or not so clean shutdown recently one file system check against /backup file system would be a good thing. You can also grep daemon.log for word missing to see if any other index was affected.