"Ghost" clients reappears after server update to version 7.5.3

Hello Vito,

I would suggest you to check the peer information, in case there is still some certificated stored for that client:

Under the "local hosts" list, click on the NW server  an, in the right hand side you will see the list of the peer information  for all the clients. If you can still see mail08 then you have to manually delete the peer information. Check also if mail08 appears itself under the "local hosts", in any case you will need to manually delete the peer information:

print type:NSR peer information; name: mail08

Regards,

Carlos.

mail08 may also have been configured as an alias for a different client or be mentioned in some other resource - you could try grepping the entire nsradmin output for mail08 to see if it is mentioned elsewhere.

Does this happen as Networker restarts or are you performing some particular action?

Did it.

No existing alias for mail08.

hi Vito,

I guess you are running nsradmin, and that won't show the peer information.

Please run on the NW server nsradmin -p nsrexec

Once you are in the nsradmin prompt then run:

print type:NSR peer information

Run it without specifying the name to ensure the output is valid, then run:

print type:NSR peer information; name: mail08

Check if the output now shows any trace of client mail08

Hi Vito,

After the upgrade, there may be some residual information that was left in the Networker Temporary Directory.  Please try the following:

The temporary files under /nsr/temp or \nsr\temp folder can be deleted with following procedure:

1. Make sure no backup or restore is in process on Networker server

2. Stop Networker daemons (Unix) or Stop Networker Services in Windows

3. Delete all files under /nsr/tmp or \nsr\temp folder and leave 'sec' folder as it is.

4. Start Networker Daemons (Unix) or Start Networker services on Windows

Let us know if the above helped at all.

Thanks,

Vivina

I do like a good mystery so I'll put my two cents on aliases also:

To check these create a file called client_in with notepad or vi:

. type: nsr client

show name;aliases

print

then type:

nsradmin –i client_in > client_aliases

The client_aliases file will give you all of the aliases for all of the clients and you will be able to see if you have the ghost in there.

-Bobby

I have already done the deletion of nsr\tmp content (except sec folder).

As David suggested I dumped all the output of nsradmin for all resources.

I have found a reference in my group of users

Administrators@mail08

was mentioned as authorized to make restores.

I have deleted the entry: let's see if the warning re-appear.

For the moment the warning for mail08 I see that in the daemon.log almost every 5 minutes (see below)

39076 17/08/2010 15:55:02  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:00:05  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:05:15  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:10:24  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:11:10  nsrd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:12:35  nsrexecd SYSTEM warning: DNS lookup failed for pcuc010259: No such host is known.

39076 17/08/2010 16:12:35  nsrexecd SYSTEM warning: DNS lookup failed for pcuc010259.consilium.eu.int: No such host is known.

39076 17/08/2010 16:15:34  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:20:43  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:25:52  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:31:01  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:32:30  nsrd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:36:00  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

39076 17/08/2010 16:41:10  nsrexecd SYSTEM warning: DNS lookup failed for mail08: No such host is known.

Best Regards,

Vito

Hi Carlos,

unfortunately no trace on peer information

I looked via the NMC GUI (Local Hosts) and via nsradmin (see below): no trace...

nsradmin> print type:NSR peer information; name: mail08
No resources found for query:
                        name: mail08;
                        type: NSR peer information;

I looked also at a possible alias mail08 defined for a client with another name: no trace as well.

Regards,

Vito

Actually the suggestion of David (grepping the entire nsradmin output) could have resolved my issue.

After one our I don't see anymore the warnings for mail08.

Thanks,

Vito