Unsolved
This post is more than 5 years old
1 Message
0
1444
August 25th, 2011 11:00
Networker Failing to add host save sets
Hi,
I'm using 7.5version.
I reinstalled a system where I used to backup to.
Solaris 10 is the systems where my networker server is installed on, as well as the host being Solaris 10.
I installed the packages and so forth, when I add the host and try to select its save set on the networker console, I get this error inside daemon.raw
2495 1314297878 2 0 0 1 28861 0 db-host-2 nsrexecd 98 Impersonation was requested by: "%s", but the user does not have enough privileges to impersonate. 1 0 54 SYSTEM/emc-console.ops.patternmatched.com@NT AUTHORITY
The other error
39078 1314287232 0 0 2 1929 18411 0 db-host-2 nsrexecd 14 %s error: %s%s 3 0 6 SYSTEM 49 219 6637 145 There is already a machine using the name: "%s". Either choose a different name for your machine, or delete the "%s" entry for "%s" on host: "%s" 4 0 6 blade0 0 20 NSR peer information 0 6 blade0 12 9 db-host-2 0 0
Now this system was installed and running backups previously. I tested my same process against a system that hasnt been on the save sets, works instantly.
The networker console is run on a Windows system which points to the server.
I've tried nsradmin -u attempts as comments that have been previously made. I feel the issue lies with the fact this is a new system that has the same DNS entries.
I've removed the PEER's as well, and still experiencing this error.
Restarted the server, cleared the servers nsr/tmp, that didnt assist me. Now most issues with this error report it with nsr, and not nsrexecd.
Basic checks covered.
root@db-host-2 / : ping blade0.chassis1.vzn-gmanor.patternmatched.com
blade0.chassis1.vzn-gmanor.patternmatched.com is alive
root@blade0 pmt-gmanor /nsr/logs : ping db-host-2
db-host-2 is alive
root@blade0 pmt-gmanor /nsr/logs : nslookup db-host-2
Server: 192.168.108.7
Address: 192.168.108.7#53
db-host-2.ops.patternmatched.com canonical name = v-db-host-2.ops.patternmatched.com.
Any


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
August 26th, 2011 05:00
Disable nsrauth on server (and storage nodes if any), restart NW daemons and it should be fixed.