NetWorker Blog

Commentary from a long term NetWorker consultant and Backup Theorist

  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new 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 in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the 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 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.

Basics – Fixing “NSR peer information” errors

Posted by Preston on 2009-02-23

Hi!

The text of this article is moved, and is now over at its permanent location at the NetWorker Information Hub. You can read it here.

Advertisements

18 Responses to “Basics – Fixing “NSR peer information” errors”

  1. Great. Just what I was looking for. It fix the problem.

  2. VJ said

    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/09 18:31:53 nsrexecd: GSS Legato authentication from server02 failed…

    04/16/09 18:31:53 nsrexecd: RPC error: Authentication error

    Is there any solution or ideas Please.

    Thanks & regards
    VJ

    • Preston said

      I can’t say I’m immediately familiar with that error, though it looks similarish to some nsrauth authentication errors I remember seeing around the early v7.3 releases of NetWorker. You might want to edit the authentication methods (covered in the administration manual) to switch from using “nsrauth” to “oldauth” for either the host (or temporarily, all machines), to see whether this makes a difference.

  3. […] to number 2, we have something that I get search results for every day without fail. That’s Basics – Fixing “NSR Peer information” errors. It’s actually a reasonably simple error to fix, but sometimes finding the information about […]

  4. Tom B. said

    Could this be put into a script where all that would need to be done is to add in the “offending” client?

    Example in this case: nsrdeletepeer faero
    Where “nsrdeletepeer” is the script and “faero” is (of course) the client.

    • Preston said

      In theory yes, although it would need to be part of the client install (e.g., if looking for an addition to NetWorker) since it actually can happen on any host in the environment; it’s just most likely to be reported on the backup server.

  5. Ray said

    Have a NW server that was reinstalled (windows 2008) and updated all windows based clients successfully using the above procedure; however the linux clients fails with “user not on machine is not on administrator list” How do I delete the NSR peer information on linux clients from a windows NW server?

    • Preston said

      Well typically NSR peer information needs to be deleted from the client that is experiencing the problem. So you may want to log onto the Linux hosts and (as the root user) run the command:

      nsradmin -p 390113 -s client

      Where client is the machine you’re currently logged onto. Then, look for the NSR peer information for the server and delete it.

      Alternatively you may also want to update any information stored in /nsr/res/servers on the client if the backup server hostname has changed (bearing in mind if you do so it requires a restart of the NetWorker services on the client.)

      • Ray said

        Is it safe to assume I need the nsradmin utility installed on my linux client? It’s failing with nsradmin: command not found. Thanks for your assistance.

      • Preston said

        The nsradmin utility is installed on every machine with the NetWorker client. I suspect it will be a search path issue for you.

        Make sure you run as root on the Linux client, and explicitly call /usr/sbin/nsradmin

        That should do the trick for you.

      • Ray said

        That did it! Thanks a bunch!

      • Preston said

        Happy to have been of help.

  6. […] popularity stakes. Driven by search engine referrals we have a return to the top of the “Basics – Fixing NSR Peer information errors“. This is something that a constant turnover of visitors to the […]

  7. Marco said

    when i re-install server-2-b-backupped i get the message ‘delete the nsr peer information’ in the daemon.raw file. when i then on the backupserver in nsradmin enter ‘delete type: NSR peer information; name:server-2-b-backupped’ i get the message no resource to delete!
    However i keep failing to re-install the client….
    Please advise

    • Preston said

      What nsradmin command are you using? Are you connecting to the client processes on the backup server?

      • Marco said

        the 3rd time the command somehow worked. don’t understand but thanks for replying.

  8. jt said

    Something so simple to fix and yet so hard to find the information to do..

    I had a LOT of these errors and no recourse previously…

Sorry, the comment form is closed at this time.

 
%d bloggers like this: