Unsolved
This post is more than 5 years old
23 Posts
0
4981
NMC - an unsuccessful attempt to impersonate user ..
Hi All,
I've got an error showing up in the daemon.log of my NW server since I moved my networker console to a new server. It doesn't seem to cause any problems until now, but I'm trying to figure out how to fix it.
Every time I modify a client resource, I get an error like this. I'm still able to modify the client resource successfully, it justs shows that in the log.
nsrexecd RAP error: An unsuccessful attempt to impersonate user administrator@ was made by root@nmc-hostname. If root@nmc-hostname can be trusted, grant the user "Administrator" privileges on the NetWorker server.
When I look at my administrators list, I do have an entry for: user=root,host=nmc-hostname
I'm not sure what I'm missing exactly. Anyone has an idea ??
Thanks!
Frank.
ble1
14.3K Posts
0
February 20th, 2013 08:00
Try adding administrator@nmc-hostname. Also you mentioned - is this unknown to you or to nsrexecd?
lapfrank1234
23 Posts
0
February 20th, 2013 09:00
Hi Hrvoje,
I did try adding administrator@nmc-hostname. I get the same error. Actually, whichever user I log in with to the console, and this changes. When I log to the NMC with my user, I get lapfrank@ . My user also has an entry in the administrators group.
nsrexec actually shows . When I look at the daemon.log on the client I try to modify the resource for, I get the following. Not sure why it complains that the NMC is not in the servers file..? The second part looks OK.
7123 02/20/2013 10:04:54 AM 5 1 13 350521664 20603 0 client-hostname nsrexecd NetWorker server `nmc-hostname' is not in the servers file for the NetWorker client `client-hostname'
68616 02/20/2013 10:04:54 AM 2 0 0 350521664 20603 0 client-hostname nsrexecd User root@nmc-console authorized by server nwserver-hostname through optional remote NetWorker server based authentication.
ble1
14.3K Posts
0
February 20th, 2013 13:00
Is this nw8? I really can't imagine why NMC host would need to be in servers file in the first place (unless your are messing up with nsrla resource and you wish to change it remotely).
lapfrank1234
23 Posts
0
February 20th, 2013 13:00
It's networker 7.6.5.0 (including the NMC). I'm definitely not messing up with nsrla resource ;-)
bingo.1
2.4K Posts
0
February 20th, 2013 14:00
Look at the error message - NW does not complain about the user but about the computer,
Can it be that simple that the client's 'servers' file only allows to listen/connect to other servers? - If so, please correct the file and restart the NW client daemon.
lapfrank1234
23 Posts
0
February 20th, 2013 14:00
Bingo,
You are right about the error shown on the client side. If I add the NMC in the servers file, I do not get the "networker server is not in the servers file" error anymore on the client daemon.log file, but that one I don't really care about.
--> 7123 02/20/2013 10:04:54 AM 5 1 13 350521664 20603 0 client-hostname nsrexecd NetWorker server `nmc-hostname' is not in the servers file for the NetWorker client `client-hostname'
Even if I add the NMC console in the "servers" file or simply delete the file so that it allows everything, I still get the following error in the daemon.log of the NW server when I modify the client resource in the NMC.
FYI, it happens with *every* clients.
nsrexecd RAP error: An unsuccessful attempt to impersonate user lapfrank@ was made by root@nmc-hostname. If root@nmc-hostname can be trusted, grant the user "Administrator" privileges on the NetWorker server.