Nsrexecd System Error Unable To Register
Contents |
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ •
Delete Peer Information Networker
Memberlist • Log in Backup Central Forums Forum Index » EMC emc networker authentication error why = server rejected credential NetWorker » Problem with Virtual Linux server The time now is Fri Oct 21, 2016 4:17
Authentication Error; Why = Invalid Client Credential
pm View previous topic | View next topic Page 1 of 1 Problem with Virtual Linux server Author Message Matthew Powell Guest Problem with Virtual Linux server to correct the error it may be necessary to delete the nsrla database I am running Legato 7.5.3 on Solaris 10 and I am trying to back up a Linux virtual server. It was cloned from another server and then the client was installed but it will not start. I get the following error in the daemon.raw file. nsrexecd 14 %s error: %s%s 3 0 6 SYSTEM to correct the error, it may be necessary to delete the %s database 49 80 6919 53 Unable to register %ld version %ld on tcp. Aborting. 2 2 6 390436 2 1 1 0 0 78109 1305938262 2 0 0 3086431936 25460 0 moo1.clemson.edu nsrexecd 38 Unable to start authentication service 0 Any help would be greatly appreciated. Thanks and have a great day. Matt Powell Storage Administrator Clemson University CCIT (864) 656-0589 (office) (864) 247-2823 (cell) via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER Fri May 20, 2011 5:04 pm Francis Swasey Guest Problem with Virtual Linux server First, you need to run: nsr_render_log /nsr/logs/daemon.raw so you can see that error message in English instead of gibberish. Are you sure the /nsr directory was not present after the Linux virtual server was cloned until you installed networker and started it for the first time? If it is possible that the /nsr directory was cloned from the original server, I'd wipe it and then start networker (personally). Franky On 05/20/2011 9:00 PM, Matthew Powell wrote: I am running
AT CLEMSON DOT EDU> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU Date: Fri, 20 May 2011 21:00:57 -0400 I am running
Nsrexecd Rap Critical 162 Attributes
Legato 7.5.3 on Solaris 10 and I am trying could not get session key from for gss authentication to back up a Linux virtual server. It was cloned from another server and
Nsrla Resource Do Not Resolve To The Machine's Hostname
then the client was installed but it will not start. I get the following error in the daemon.raw file. nsrexecd 14 %s error: http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/emc-networker-19/problem-with-virtual-linux-server-111777/ %s%s 3 0 6 SYSTEM 49 80 6919 53 Unable to register %ld version %ld on tcp. Aborting. 2 2 6 390436 2 1 1 0 0 78109 1305938262 2 0 0 3086431936 25460 0 moo1.clemson.edu nsrexecd 38 Unable to start authentication service 0 Any help https://adsm.org/lists/html/Networker/2011-05/msg00129.html would be greatly appreciated. Thanks and have a great day. Matt Powell Storage Administrator Clemson University CCIT (864) 656-0589 (office) (864) 247-2823 (cell) 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 [Morewiththissubject...]
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 https://nsrd.wordpress.com/2009/02/23/basics-fixing-nsr-peer-information-errors/ 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 http://www.ibm.com/support/docview.wss?uid=swg21109108 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 authentication error 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. « 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 to correct 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. 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:60480nsrck; nsrmmdbd; WISS error; backup; /nsr/res/nsrla.res; ISM; Storage; Manager; onbar Technote (troubleshooting) Problem(Abstract) Solution for WISS error during the onbar backup with ISM. Symptom Following an operating system crash or the installation of an operating system patch, IBM Informix Storage Manager (ISM) fails to start and the following error appears in the daemon.log: 09/02/02 07:38:18 nsrd: server notice: started 09/02/02 07:38:19 nsrexecd: Can't initialize configuration file /nsr/res/nsrla.res 09/02/02 07:38:19 nsrexecd: SYSTEM error, resource file /nsr/res/nsrla.res already in use; check for another copy of this server already running 09/02/02 07:38:19 nsrexecd: error initializing resource file. 09/02/02 07:38:19 nsrmmdbd: error adding btrees to ss (an invalid slot number) 09/02/02 07:38:19 nsrmmdbd: WISS error, an invalid slot number 09/02/02 07:38:19 nsrd: unable to start nsrmmdbd 09/02/02 07:38:19 nsrd: shutting down 09/02/02 07:38:19 nsrd: successful shutdown Cause Corruption in the INFORMIX Storage Manager (ISM) nsrmmdbd database causes the WISS error. The following situations can cause corruption in the ISM nsrmmdbd database: 1. ISM process exits without shutting down properly. 2. Power failure to unprotected systems. 3. Hardware failure. 4. Disk crash. 5. Installing an operating system (OS) patch. Resolving the problem Perform the following steps as root to re-build the nsrmmdbd database: 1. Shut down the ISM server using the following command: ism_shutdown 2. Rename the corrupt client indexes and the media mmvol indexes using the following: mv nsr_home_directory /index/ server_name /db nsr_home_directory /index/ server_name /db.old mv nsr_home_directory /mm/mmvolume nsr_home_directory /mm/mmvolume.old nsr_home_directo ry The directory name where nsr installed. In most cases it will be "/nsr". server_name The name of your Backup server. Example: The following example uses /nsr as nsr_home_directory, a