Problem
How can I determine the nature of a license failure?
Although this particular article was written for OpenServer 6.0.0 the circumstances would also be similar for SCO UnixWare 7.1.4 and SCO OpenServer 5.0.7.
I am getting some of the errors below which appear at boot time or whilst the server is in Multi-User mode:
- Warning: !No system license was found on this machine.
- SEVERE: Could not determine OS type- The SCO License Policy Manager Daemon (sco_pmd) was unable to
start. This is usually due to a read-only root filesystem, lack
of a system license or a damaged program image file
(/etc/sco_pmd).If this is not the case, please contact your SCO service provider for help.
Depending on the reason for the failure, the system may shut down
without warning in one hour. Please boot single-user and correct
this problem.- SEVERE: no nodelock database- ERROR: Failed to build license list- WARNING: The Policy Manager has died. Please reboot your system.
- License already in use on another machine Solution
Licensing is checked at a number of places during the boot sequence in /etc/inittab:
The first will be:pmd::sysinit:/sbin/sh -c 'umask 022; exec /etc/sco_pmd <
/dev/null > /var/adm/pmd.log 2>&1'The second will be:tcp::sysinit:/etc/tcp start < /dev/null > /dev/null 2>&1The third will be from the /etc/rc2.d/S85tcp script which will be running during multi user mode and will call "/etc/sco_pmd -k".
Assuming there is not another server on the local LAN with the same license number then the nature of these errors/warnings appearing at boot time will require you to:
a) Run "scoadmin license" to determine whether your server is licensed or have a license that's expired.
Typically, you see "No system license was found on this machine".
Check that the nodelock file doesn't contain just one "nnul111" line which would indicate that the server is unlicensed.
b) Check that the date of the server.
Typically, BIOS problems on a server set the date to a non-supported dates such as 1970 or 2038 which will cause licensing problems.
Please note that beyond Tues Jan 19th 03:14:07 2038 the date is set back to Fri Dec 13th 20:45:53 1901.
The expiry date will vary depending on the license expiry, see:
# brand -XYou may see errors from "fixtimed: can't read hardware clock"
You will also see problems if the server date is set BEFORE the server's installation date.
If the system date is not valid, resetting the date to current, so
that it is back within the licensed period should correct this type
of problem. If the date was incorrect at the time the system was
licensed, then the system may need to be re-licensed or re-installed
once the date has been corrected.c) Check that /var/netls/nodelock exists.Typically, you will see any error regarding "no nodelock database"
These errors should be recorded in /var/adm/pmd.log and /var/adm/messages.
d) Seeing "FATAL: UNLICENSED SYSTEM SHUTTING DOWN NOW!"This is likely to appear on the screen after the server's grace period has finished due to the issues above and now the server will shut down until the problems are resolved.
e) Seeing "FATAL: UNLICENSED SYSTEM SHUTTING DOWN NOW!!!"This is a kernel call where the system's grace period has expired because the sco_pmd license daemon hasn't started.
NOTES: Other errors might include:- license: file not foundThe /stand/license file is missing and the server will not boot any
further. This file is created when licenses are entered into the
server.- Error: PMD Preservation [5/0] failed (30)The /stand filesystem is mounted as a read only filesystem at boot time.
See also
TA126956, "WARNING: The Policy Manager has died. Please
reboot your system." after fresh install of OpenServer
6.0.0TA127427, "I see "SEVERE: Could not determine OS type" when booting or using SCO OpenServer 5.0.7V"