Problem
FOR SCO OPENSERVER 5.0.0:I have upgraded my system from SCO XENIX/UNIX to SCO OpenServer Enterprise Release 5.0.0, and when I log in to the system on /dev/tty01 I get the error:
LOGIN: Upgrade license missing Overriding system login limit on tty01 only to allow emergency system administration.
Login attempts on other ttys fail with this message:
LOGIN: Upgrade license missingFOR SCO OPENSERVER 5.0.5:I have purchased an upgrade to SCO OpenServer Enterprise 5.0.5. I have installed SCO OpenServer 5.0.5 using a license I obtained for a pre-5.0.5 OpenServer Release. After installing, when I log in to the system from a character screen I get the warning:
LOGIN: Upgrade license missingbut logins are allowed anyway. However, login attempts from
scologin(XC) and the X Desktop are prohibited. Cause
The license used for the installation contained an "r" flag
as shown in the License Data string on the Certificate of
License and Authenticity (COLA). This license was not
intended to be used during Initial System Load (ISL), but was only
intended to be used for a Host->Enterprise or Desktop->
Enterprise post-ISL upgrade utilizing the Software Manager,
sometimes referred to as an "intra-upgrade". Furthermore,
These "r" flag licenses were only intended to be used in a
"two-step" upgrade, in which the first step is an ISL using
an "o" flag license, and the second step is the intra-upgrade.Thus, the upgrade procedure from SCO XENIX/UNIX to SCO OpenServer Enterprise System Release 5.0.0 is a two-stage process. First you must install your system using the SCO OpenServer Host System License (the "o" flag license), register the system with the Registration Key provided by the SCO Registration Center, and then upgrade the system to SCO OpenServer Enterprise System (using the "r" flag license).
A common error is to perform the first stage of this process using the wrong Certificate of License and Authenticity (COLA). In other words, it is a mistake to begin the installation by using the OpenServer Host->Enterprise COLA when prompted to enter licensing information within the Installation Query Manager (IQM).
Similarly, for OpenServer 5.0.5, it is common after purchasing an upgrade to 5.0.5 to use the "r" flag license in the ISL with the intention of performing an installation of OpenServer Enterprise 5.0.5.
An upgrade or fresh installation performed in this fashion will
proceed without any _apparent error_. However, after rebooting
the system and bringing it up to multiuser mode, logging in on
/dev/tty01 (the default Override tty) results in the message:LOGIN: Upgrade license missing Overriding system login limit on tty01 only to allow emergency system administration.
and login attempts on 5.0.0 all other ttys fail with the message:
LOGIN: Upgrade license missingOn SCO OpenServer 5.0.5, the same error is obtained, but it is merely a warning, as logins are subsequently permitted.
Furthermore, Scologin fails to start on /dev/tty02, hanging with the message:
Scologin is starting (/dev/tty02). Please wait... Solution
The best possible solution is to obtain a set of replacement
licenses from SCO Support. When calling into Support, please
have the license numbers from your existing COLAs handy, in
order to verify that replacement licenses are relevant. You
should have a license with either "r130/5.0" or "r128/5.0"
appearing within the License Data field one of the COLAs; you
should also have an OpenServer Host COLA containing an "o"
string (such as "o3.1") and an explicit user count string
(such as "u32" for 32 users) appearing in the License Data
field. SCO will not issue replacement licenses for greater
than 5 users unless this Host COLA can be verified.After obtaining the replacements, remove the existing
Enterprise license using the License Manager, and re-license
with the replacements. Reboot your system for the changes to
take effect.An alternative solution, which can be attempted immediately,
is described below. Additionally, a few other alternatives
are described in the NOTE section below. All of these
alternatives, while less desirable and not guaranteed to be
successful, are easy to implement and may save valuable time.Alternative Solution:One possible solution is to use the brand(ADM) utility to license
SCO OpenServer Host System. While logged in on /dev/tty01,
issue this command:brand -g -a "<License Data>" <License Number> <License Code>where <License Number>, <License Code>, and <License Data>
are the values of these three fields of information exactly
as they appear on your COLA for the SCO UNIX/XENIX->SCO
OpenServer Host System upgrade. For instance, suppose your
COLA has the following information on it:SCO OpenServer Host System 5-user License
Upgrade from 2-user UNIX
License Number : ALF000000
License Code : oicurmty
License Data : k;o1.0;u5;m7x51qpThen the command to enter in order to license SCO OpenServer Host System would be:
brand -g -a "k;o1.0;u5;m7x51qp" ALF000000 oicurmtyAfter entering this command, the problem should be resolved.
Verify this by attempting to log in on any other tty, other
than /dev/tty01. Logins should succeed.At this time, you may also reactivate Scologin by issuing these commands:
scologin stop
scologin startScologin should then start successfully on /dev/tty02.
After doing this, you should register SCO OpenServer Host System by issuing this command:
brand -R <License Number> <Registration Key>where <License Number> and <Registration Key> are the values of these fields of information exactly as they appear on your COLA and SCO Registration Confirmation, for the SCO UNIX/XENIX-> OpenServer Host System upgrade.
As a final step, install the Release Supplement provided in the software package.
NOTE: The above workaround involving the "brand -g" command is entirely
within the built-in functionality of the licensing scheme, and
should work in a majority of cases. However, recently, some of
the large-user licenses (there are confirmed 16-user, 32-user,
1024-user cases) have been observed to cause the workaround to
fail. Specifically, the policy manager demon, /etc/ifor_pmd, does
not start properly when the system is rebooted. This behavior has
been reported to SCO Engineering.One of the following temporary workarounds may be attempted; all steps should be performed by root.
1. Install OpenServer Host System from the SCO OpenServer 5.0
media. This is easily accomplished from the Software Manager.
A preliminary pop-up message will occur, informing the user
that some files from Host have already been installed. You
may choose to continue the installation at this point. This
should only be attempted on systems that have not undergone
any post-install configuration, as the effects on client files
are presently unknown. Reboot the system to determine whether
this fixes the system.2. Install the custom product database hierarchy for OpenServer
Host System from the SCO OpenServer 5.0 media. This can be
done as follows:(a) Mount the OpenServer cdrom:mount -f RCKRDG /dev/cd0 /mnt(b) Create the directory /opt/P/SCO/unixos/5.0.0b/.softmgmt:mkdir -p /opt/P/SCO/unixos/5.0.0b/.softmgmt(c) Copy the product.db file from the cdrom to the directory just created:
cd /mnt/opt/P/SCO/unixos/5.0.0b/.softmgmt
cp product.db /opt/P/SCO/unixos/5.0.0b/.softmgmtAgain, reboot the system to determine the validity of the fix.
3. Create temporary changes to the license database (in the
directory /usr/lib/netls/conf) just to start the policy
manager demon (/etc/ifor_pmd) at system startup. Do this
by performing the following steps:(a) Copy the current nodelock file to nodelock.full:
cd /usr/lib/netls/conf
cp nodelock nodelock.full(b) Next, with your favorite text editor, remove the line that ends with "oss_mu" from the nodelock file.
(c) Copy this new nodelock to nodelock.part:
cp nodelock nodelock.part(d) Compose a two-line shell script, /etc/prep.pmd, containing the following:
:
cd /usr/lib/netls/conf
cp nodelock.part nodelock(e) Compose another two-line shell script, /etc/post.pmd, containing the following:
:
cd /usr/lib/netls/conf
cp nodelock.full nodelockMake sure these scripts are executable.(f) Use these in /etc/inittab entries surrounding the "ifor" entry as follows:
prep::sysinit:/etc/prep.pmd </dev/console >/dev/console 2>&1
ifor::sysinit:/etc/ifor_pmd </dev/null >/usr/adm/pmd.log 2>&1
post::sysinit:/etc/post.pmd </dev/console >/dev/console 2>&1(Note that the "ifor" entry should already be in the inittab file).
Verify that the fix works (pmd starts and multiple logins succeed);
then make the same modification to /etc/conf/cf.d/init.base. Note
that the file nodelock.full will have to manually modified upon any
subsequent addition or removal of licenses. See also
Other articles in this database, using the keywords 'openserver' and 'upgrade', with special attention to:
TA104818, "Upgrading from SCO XENIX or SCO UNIX to OpenServer Enterprise 5.0.0."
TA104901, "OpenServer Enterprise is registered but registration messages still appear."
TA104902, "The IQM or License Manager is not accepting my license information."