no license found

cannot locate a license server

The version of the product that the license is for doesn't match the version of the product.

The system date is set earlier than the start date listed on the license information sheet.

The nodelock file /var/netls/nodelock (/usr/netls/nodelock on IRIX Release 5.0 and earlier) contains an incorrect vendor ID or license password.

You have entered a license annotation when there is none or it was specified incorrectly. If the license annotation contains spaces, be sure to surround it with double quotes (").

On IRIX Release 5.0.1 and later, the file /usr/netls/nodelock is not a symbolic link to /var/netls/nodelock. Verify that /usr/netls/nodelock is a non-dangling symbolic link to /var/netls/nodelock using file(1).

You may have received a concurrent license but installed it as a node-locked license.

There are two or more Global Location Brokers on the network that do not “know about each other.” (See “Global Location Brokers That Don't Know About Each Other” in Chapter 9 for more information.)

Required daemons are not running. glbd(1M) and llbd(1M) should be running on the Global Location Broker, and netlsd(1M) and llbd should be running on the Network License Server.

The clock on the system running the applications differs from the clock on the Global Location Broker system by more than 12 hours.

The file /var/ncs/glb_site.txt (/usr/etc/ncs/glb_site.txt on IRIX Release 5.0 and earlier) lists systems that are not Global Location Brokers.

A /var/ncs/glb_obj.txt (/usr/etc/ncs/glb_obj.txt on IRIX Release 5.0 and earlier) file exists, but no Global Location Brokers are using the UUID in that file (there are no location brokers in that cell).

The daemons are in an inconsistent state. To fix this, try stopping all of the daemons on the network (see “Stopping Daemons” in Chapter 7) and restarting them (see “Restarting All Daemons on a Network” in Chapter 7).

The GLB database may be corrupt. Follow the instructions in “glbd Won't Run” in Chapter 9.

If you returned the Business Reply Mail card that came with the product (attached to the Software License Registration card) but have not yet received a permanent license, the license should arrive shortly. If you mailed it more than two weeks ago, contact Silicon Graphics License Administration or your service provider (see “Contacting Silicon Graphics License Administration” in Chapter 2).

If you have received a permanent license but haven't installed it yet, replace the temporary license with a permanent license using the guidelines in “Installing Replacement Licenses” in Chapter 6.

If you purchased the product and have not returned the Business Reply Mail card that came with it, return the card as explained in “Completing the Software License Registration Card” in Chapter 2.

If you've lost the Business Reply Mail card, see “Missing Software License Registration Card” in Chapter 2.

If you have installed a permanent license, you may be getting this message because you didn't delete the temporary license. See “Deleting a Node-locked License” in Chapter 6 or “Deleting a Concurrent License” in Chapter 6.

If you have not purchased the product and would like to, call the product manufacturer or distributor. For Silicon Graphics products, call SGI Express at 1-800-800-7441 in the United States and Canada, and in other countries call your local sales office.

If you are unsure about the status of licenses for this product, see “Contacting Silicon Graphics License Administration” in Chapter 2 for information on contacting Silicon Graphics License Administration or your service provider.

lb_admin is doing a lookup on a system where a Global Location Broker is not running:

lb_admin: set global ip:pele
lb_admin: use global
lb_admin: lookup 
?(lb_admin) communications failure (network computing system/RPC runtime)
No entries match.

drm_admin cannot contact a Global Location Broker:

drm_admin: set -o glb -h ip:pele 
Default object: glb  default host: ip:pele  status: not communicating communications failure (network computing system/RPC runtime)

ls_admin or ls_stat detect that a Network License Server went down without unregistering itself:

Connected to server: pele.wpd.sgi.com
?(command) communications failure (network computing system/RPC runtime)

A Network License Server can appear to go down without unregistering itself when the system crashes, the network becomes unavailable, or daemons are not running.

The network is unavailable.

A system is down.

Daemons are not able to locate other daemons; for example, glbd is unable to locate a llbd, or netlsd is unable to locate a llbd. To solve this problem, stop the daemons on the network and restart them using the instructions in “Stopping Daemons” in Chapter 7 and “Restarting Daemons” in Chapter 7.

A /var/ncs/glb_obj.txt or /var/ncs/glb_site.txt file (/usr/etc/ncs/glb_obj.txt or /usr/etc/ncs/glb_site.txt on IRIX Release 5.0 and earlier) is incorrect.

You weren't superuser when you tried to start llbd. Become superuser to start llbd.

llbd is already running. Confirm that it is running using ps(1).

When you give the lb_admin subcommand lookup, lb_admin reports “No entries match” if the Global Location Broker you've specified has no Network License Server entries in its database and you haven't specified arguments to lookup; for example:

/usr/etc/lb_admin 
lb_admin: lookup 
Data from GLB replica: ip:pele.wpd.sgi.com 
No entries match.

If you've given arguments to lookup and they don't match any entries, then the entire list of entries is displayed.

When you are modifying GLB database entries using the delete or unregister subcommand, this message appears when no entries are affected; for example:

/usr/etc/lb_admin 
lb_admin: delete sl slsl sl ip:pele 
No entries match.

Start up glbd using the existing database with this command:

/etc/init.d/nck start 

Remove the existing database and give the same glbd command again. On IRIX Release 5.0.1 and later, the files are /var/ncs/glb.e and /var/ncs/glb.p. On IRIX Release 5.0 and earlier, the files are /usr/etc/ncs/glb.e and /usr/etc/ncs/glb.p.

Merge the existing database with hostname's database and start glbd using this sequence of commands:

/usr/etc/drm_admin 
drm_admin: set -o glb -h ip:hostname 
drm_admin: addrep ip:thishost 
drm_admin: merge_all 
drm_admin: quit 
/etc/init.d/nck start 

thishost is the host name of your system.