Nsrexecd System Error
Contents |
General Technology General thoughts Licensing Linux NetWorker Policies Quibbles Recovery Scripting Security Support VBA Windows Links Chuck's Blog LTO Consortium Micromanuals Penguin Punk's Blog Reports Ronny Egner Storagebod StorageNerve StorageZilla About Nomenclature Contact Archives Why donations? Why the flag?
Emc Networker Authentication Error Why = Server Rejected Credential
Basics - Fixing "NSR peer information" errors Basics, NetWorker, Scripting Feb 232009 If authentication error; why = invalid client credential you're using a modern NetWorker environment, the chances are that you'll periodically notice entries such as the following in the daemon.log
To Correct The Error It May Be Necessary To Delete The Nsrla Database
/ daemon.raw files on the backup server: 39078 02/02/2009 09:45:13 PM 0 0 2 1152952640 5095 0 nox nsrexecd SYSTEM error: There is already a machine using the name: "faero". Either choose a different name to correct the error, it may be necessary to delete the %s database for your machine, or delete the "NSR peer information" entry for "faero" on host: "nox" While this may look confronting, it's actually a trivially easy error to fix that requires just a minute or so of your time with nsradmin. First, note the client that the error is about, and the client that the error is being recorded from. In this case, the error is about the client faero, while the conflicting nsr peer information resources detected for host error is being registered against the host nox. To fix, run up nsradmin against the client service on nox: # nsradmin -p nsrexec -s nox (alternatively, you can use: nsradmin -p 390113 -s nox) At the nsradmin> prompt, enter the command: delete type: NSR peer information; name: faero And answer yes when prompted to confirm. For example, the session might resemble the following: nsradmin> delete type: NSR peer information; name: faero                        type: NSR peer information;               administrator: root, "user=root,host=nox";                        name: faero;               peer hostname: faero;          Change certificate: ;    certificate file to load: ; Delete? y deleted resource id 17.0.83.117.0.0.0.0.210.37.85.73.0.0.0.0.10.0.0.1(1) There, you've done it. Note that you should be periodically scanning your daemon raw/log files for errors and trying to eliminate them. The goal should be that any error or warning reported in the file is something that you do need to worry about/investigate, rather than having a lot of "false positives" floating around in the system. [Update, 2009-05-12] I thought I'd mention that one of the most common times I see these warnings occur is after I've uninstalled/reinstalled NetWorker on a client, as opposed to having upgraded. Since on some clients it's more or less necessary to uninstall/reinstall rather than upgrade, that helps to under
site for the latest articles (and all old archived articles).
Enterprise Systems Backup and Recovery If you find this blog interesting, and either have an interest in or work inNsrexecd Rap Critical 162 Attributes
data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup nsrla resource do not resolve to the machine's hostname and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the
Could Not Get Session Key From For Gss Authentication
human element to ensuring that your company has a suitable and working backup system rather than just a bunch of copies made by unrelated software, hardware and processes. This blog has moved! This blog http://nsrd.info/blog/2009/02/23/basics-fixing-nsr-peer-information-errors/ has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
Twitter Error: Twitter did not respond. Please wait a few minutes and refresh this page. « Recommended reading: Asimov's 3 lawsunsafe Traps when upgrading from 7.3.x to 7.4.x -CDI » Basics - Fixing "NSR peer information" errors Posted by Preston on 2009-02-23 Hi! The text of https://nsrd.wordpress.com/2009/02/23/basics-fixing-nsr-peer-information-errors/ this article is moved, and is now over at its permanent location at the NetWorker Information Hub. You can read it here. Share this:RedditLike this:Like Loading... Related This entry was posted on 2009-02-23 at 17:52 and is filed under Basics, NetWorker, Scripting. Tagged: 390113, nsr peer information, nsradmin, nsrexec. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed. 18 Responses to "Basics - Fixing "NSR peer information" errors" Andrew Watkins said 2009-03-09 at 21:23 Great. Just what I was looking for. It fix the problem. Preston said 2009-03-10 at 09:59 I'm glad it helped, thanks for the feedback. VJ said 2009-04-16 at 22:45 Hi Preston I got fed up with the following error in my NetWorker server: 04/16/09 18:31:53 nsrexecd: GSS Legato authentication user session entry (warning): "User authentication session timed out and is now invalid.". Session number = 0:6617e, domain = eir.com, user name = root, NetWorker Instance Name = server01 04/16/09 18:31:53 nsrexecd: SYSTEM error: An error occured when a client attempted to acquire credentials: error: "A daemon requested the information for a user session, but the user session was not found in the list of valid sessions" session number: 0:60480, user id: (NONE). 04/16/have trouble starting NetWorker, the daemons may not be running properly. To check the daemons, enter the following command: # ps -ef | grep nsr The system displays output as shown below, showing these five daemons running. 111 ? IW 0:10 /usr/etc/nsrexecd -s localhost 116 ? S 176:15 http://csweb.cs.wfu.edu/~torgerse/Kokua/SGI/007-1458-060/sgi_html/apc.html /usr/etc/nsrd 158 ? IW 2:48 /usr/etc/nsrmmdbd 159 ? S 23:45 /usr/etc/nsrindexd 160 ? IW< http://www.tau.ac.il/cc/nmg/LegatoErrors.html 16:07 /usr/etc/nsrmmd -n 1 If you discover that you need to start the NetWorker daemons, enter these commands: # cd / # nsrd # nsrexecd Displaying NetWorker If you enter the nwadmin command and the NetWorker Administrator window does not appear, the DISPLAY variable on your system may not be set correctly. To set the DISPLAY variable authentication error correctly, follow these steps. Enter the following command at the system prompt for C shell or tcsh: # setenv DISPLAY hostname:0.0 For a Korn shell or a Bourne shell, enter these commands: # DISPLAY=hostname:0.0 # export DISPLAY Replace hostname with the name of the machine where the user initially logged in. Enter one of the following at the system prompt: # xhost machineName or # xhost + Replace machineName with the name to correct the of the machine where you are currently logged in, or the machine where you will log in. Restart nwadmin. Renaming a Client NetWorker maintains an index for every client it backs up. If you change the name of the client, the index for that client is no longer associated with the client, and the client will not be able to recover any files backed up under its old name. To change the name of a NetWorker client, you must first delete the old client name, then add the new client name, and rename the directory that contains the corresponding index. Follow these steps: In /etc/hosts or the NIS hosts map, make the old client name an alias of the new name: nnn.nn.nn.nn newClientName oldClientName Using the Clients window, create a client with the new hostname. Configure the new client to mimic the configuration of the old client. Using the Clients window, delete the old client. As root on the NetWorker server, shut down the NetWorker daemons: # /etc/init.d/networker stop Change to the directory containing the client index directory, by default /nsr/index: # cd /nsr/index Delete the new client index directory (which is empty): # rmdir newClientName Use the mv command to rename the client index directory. For example: # mv oldClientName newClientName
messages start with an astersik (*). Most other lines are informative and represent no error condition. This list might be updated from time to time as new messages will appear. If you encounter an error message which is not described here, please send mail to moked@aristo.tau.ac.il so that it can be investigated and added to this list. * hostname:file-system Warning: unsynchronized client clock detected There is an offset between legato's clock and your workstation. Make sure that your time is correct. It is advisable that you will run some kind of time synchronization program (such as timeslave, rdate, setclock, ntp). Also make sure that your timezone setting is correct. * hostname:All n retries attempted * hostname:All Connection timed out Your workstation didn't respond at all. This usually indicates that your station had a continous network problem or that it was turned off completely. * hostname:file-system n retries attempted * hostname:file-system save: Command not found nsrexecd, the daemon responsible for launching the backups could not launch the save command, probably because the save command is not in its path or you are having an NFS problem with the file server from which you are getting these binaries. Make sure that the script that launches nsrexecd at boot time (probably /etc/rc2.d/S95networker or /etc/rc.local) is having the correct path so that it can find the save and savefs commands. * hostname:file-system no cycles found in media db; doing full save Usually reported when a new filesystem (or station) is added to the system. It is not an error message by itself, but it should make you wonder why there are no full backups in the system. * hostname:All n retries attempted * hostname:All Permission denied. * hostname:All date time nsrexec: savefs -s legato.tau.ac.il -g 1st -p -l full -R -v * hostname:All Cannot connect to nsrexecd on client hostname and .rhosts permissions * hostname:All not allow