Unsolved
This post is more than 5 years old
39 Posts
0
3217
March 31st, 2011 02:00
nsrexecd invalid nsrd requester
Hi
I installed a new networker server (7.6.1) name: zhhsubnp-se0001
With this one i like to replace the old one (7.4.4) name : bwbckse1zhh
So i moved all DSN and SN from the old to the new one.
I did it the following way on the DSN and SN
Stoping Networker
Delete the old Networker server from /etc/hosts and insert the new one.
Delete Networker (rpm -e lgto .....)
delete /nsr
Install Networker 7.6.1 (rpm -i lgto...)
Start networker
Create /nsr/res/servers with the new Networker server in it.
Some of the DSN still connect to the old Server (nsrmmd -s bwbckse1zhh)
So i restart Networker on that DSN. Delete /nsr/tmp and /nsr/res/narladb
Then the connect to the new one.
Some DSN(all Linux) had the problems that the backup start normal. They have 2 Drives from the Datadoamin VTL.
So 2 Save Sets run at the same time the rest is in waiting status. That is normal.
After some time when a Saveset is finish a new one from the waiting isnt starting. Other saveset that are running. Stop and change to Waiting.
After a few Hours the group stop unsuccessfull.
I fond out that all the DSN that have the problems.
Have the following entris in the daemon.log
52981 03/31/2011 10:26:29 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:28:34 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:28:38 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:30:53 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:30:53 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:32:56 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:33:05 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:35:09 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:35:14 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:37:25 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:37:29 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:39:49 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:39:51 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:41:54 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:42:12 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:44:00 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:44:15 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
39078 03/31/2011 10:45:28 AM 0 0 5 3086870208 2077 0 zhbsubnp-dzst09 nsrmmd RPC error: Aborting client connection from 10.174.236.34; why = Connection timed out
52981 03/31/2011 10:46:18 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
52981 03/31/2011 10:46:19 AM 2 0 0 3086911168 9038 0 zhbsubnp-dzst09 nsrexecd invalid nsrd requester: bwbckse1zhh
I found out the my Backups crash exactli when i have the " Aborting client connection"
Question:
What can i do that the "nsrexeccd invalid nsrd requester:bwbckse1zhh" disapear.
Thanks for your help
Stephan
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
March 31st, 2011 06:00
invalid nsrd requster usually is seen if:
a) you have nsrmmd running on storage node from previous sessions
b) two or more different backup servers are trying to access same storage node
Since you deleted nsrladb make sure that auth model matches the one on server (for example if server has nsrauth disabled so should your storage nodes).
As for why fo you see nsrmmd pointing out to old server, there are two possible explanations:
a) older nsrmmd survived (I doubt)
b) in device configuration for server network ibterface you refer to older server (possible if resources have been coppied over)
I also assume that your new server should not have any referrence to old one so you can do something like grep bwbckse1zhh /nsr/res/nsrdb/*/* and see which resource contains reference (and then fix it not by editing resource directly, but by using nsradin or GUI).