Encountered BSAFE SSL error: The SSL read operation did not complete
RPC Authentication: Client failed to obtain RPCSEC_GSS credentials: There is already a machine using the name: "archive-srv1". Either choose a different name for your machine, or delete the "NSR peer information" entry for "archive-srv1" on host: "cs-srv1".
NSR peer you get on server so that should not be related to client, but if you search how to remove nsr peer information you will find steps for it. If you try to run nsrexecd from CLI like /usr/sbin/nsrexecd -D3 - what error do you get?
Thanks, that worked. So when I attempted to removed the NSR peer information from the backup server, there was none. So the only thing I really did was rename /nsr/res/nsrladb and it worked. Did it get corrupted somehow?
ble1
4 Operator
•
14.4K Posts
0
October 3rd, 2014 15:00
That's from client? If so, make sure nsrexecd is not running (and from what you said it is not) and rename /nsr/res/nsrladb.
On backup server remove NSR peer information for it... you can run something like:
printf "delete type: NSR peer information; name: \n" | /usr/bin/nsradmin -p 390113 -i -
Once done, start nsrexecd on client.
theboogwa
12 Posts
0
October 3rd, 2014 15:00
I'm getting the following errors:
ble1
4 Operator
•
14.4K Posts
1
October 3rd, 2014 15:00
NSR peer you get on server so that should not be related to client, but if you search how to remove nsr peer information you will find steps for it. If you try to run nsrexecd from CLI like /usr/sbin/nsrexecd -D3 - what error do you get?
theboogwa
12 Posts
0
October 6th, 2014 09:00
Thanks, that worked. So when I attempted to removed the NSR peer information from the backup server, there was none. So the only thing I really did was rename /nsr/res/nsrladb and it worked. Did it get corrupted somehow?
ble1
4 Operator
•
14.4K Posts
0
October 6th, 2014 10:00
Can't say - one would need to see what previous data was pointing to.