Re: [Networker] Licensing errors

I had a problem like this too after the upgrade.  Deleting all the
licenses and reading them fixed it.  It was a big chore and I made sure
to backup everything first etc.  

Irene Reed

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Philippe Michel
Sent: Thursday, November 18, 2004 8:05 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Licensing errors

I seem to have a probleme with NetWorker licensing (NetWorker 7.1.2 on
Solaris 8). For some clients (not always the same), I get error messages
like :

* spleen:/usr savepnpc: RAP error: Unable to grant SERVER (UNIVERSAL)
CLIENT license to client spleen: Too many clients.  Maximum is 95

But I have a little less than 95 clients (92 connected clients + 2
defined, no applications or clusters).

I think this started after I accidentally added more than 95 clients. I
deleted the extra clients and their savesets, but it looks like this
somehow corrupted NetWorker databases.

Another symptom that may be related is that nsrlic -v gives weird
numbers of connected and defined clients, with some clients listed at
bots places and some only in connected clients (although they were
backed-up sucessfully) :

SERVER (UNIVERSAL) CLIENT LICENSES
                      Available: 95
                           Used: 84
           Borrowed from Server: 2
                      Remaining: 9
              Connected Clients: annuaire-cv, archibgx1,
                                 archisv, bgx-epo, bgx-epo3,
                                 bgxadr1, bgxadr2, bgxadrt1,
[...]
                Defined Clients: amsnt2, archibgx1, archisv,
                                 bgx-epo3, bgxadrt1, bgxdev1,
[...]

Has anyone else encountered this problem, or have any suggestions ?


There were a few messages in this list recently regarding "RAP error:
Unable to extract resource info for client ..." errors and the suggested
solutions were tricks like deleting all aliases.

Although these are different problems, could they both be related to a
more general lack of robustness in NetWorker resource database ? Are
there patches related to this ?

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=