If any application reports a license failure and you believe that this is incorrect, it is possible that either the policy manager daemon, /etc/sco_pmd, has stopped and not restarted, or some crucial file required by the policy manager to satisfy the login request is missing or corrupted.
You may be logged out and be unable to log in to troubleshoot the problem. Additional error messages may also appear. If so, simply turn the system off and reboot. If the error messages persist when the system is brought up, follow the procedures described here.
Here are possible specific sources of corruption or malfunction:
The policy manager (/etc/sco_pmd) must be present and running for your system to function. If the /etc/sco_pmd file is missing, restore it from backups.
The directory /pmd or its contents -- the named streams pipes IPCCT_pipe and IPCST_pipe, and the file sco_pmd.pid -- are corrupted or missing.
If /pmd exists, but any of its file contents do not, they may be restored by stopping and restarting /etc/sco_pmd. To do this:
which should return a line similar to:
root 11 1 TS 70 0 Nov 26 ? 0:00 /etc/sco_pmd root 12 11 TS 80 0 Nov 26 ? 0:03 /etc/sco_pmd
Any of the numbers shown may vary on your system, with the exception that one of the entries should have "1" in the third field (parent process ID). This is the "parent" copy of sco_pmd, and the other entry is the "child", whose parent process ID should match the second field (process ID) of the parent entry.
IPCCT_pipe IPCST_pipe sco_pmd.pid
If licensing problems persist, kill all of the child
daemons shown in the ouptut from Step 1 and remove
the contents of /pmd, then enter:
This has been identified as a common reason for policy manager-related failures. Of course, in this case, the policy manager errors would accompany many write failures to the root filesystem, with corresponding error messages.
It is usually sufficient to check this by examining the file /etc/default/filesys for nondefault root filesystem settings, such as mountflags=-r, or mntopts="-o ro" If such settings are found, remove them.
First, determine how many users are already logged in to the system with the brand(ADM) command; see ``Displaying login licenses in use''. A user is defined as a distinct physical keyboard or a login over the network. If the system has run out of licenses to check out, the only way to avoid the error message is to add user licenses by purchasing an additional-user license product.
If the login user count has not been exceeded, it is possible that the license database itself has been corrupted. Follow the steps below to re-apply the user licenses on the system. This procedure assumes that user licenses are supplied only through the SCO OpenServer operating system License. If you have already licensed additional users with a separate user-license product, apply the procedure to that product first.
Repeat the grep command to verify that the sco_pmd daemon is now running.