To anyone that can help,
Quite a few of you helped me out last month when my AlphaStation 200, running
OSF/1 v3.0, had an internal hard disk crash. You may remember that I am a
faculty member in the physics department at East Tennessee State University
with no computer support for my AlphaStation. I am happy to say that my
machine is back up and running with a much larger internal hard disk (the
second of two). I also increased the RAM from 64 Mb to 192 Mb and am very
happy with that. Thanks to all of you who responded. Now however, I have
encountered another problem since bringing my machine back on line -- a problem
with the licenses.
First, due the holidays, my new hard disk didn't come in until after the first
of the year and my machine was shut down during most of this time. The DEC
licenses were due to run out on 1/31/1999. In early January, before loading
the new hardware into my machine, I brought my machine up (I was able to
recover most of the crashed hard disk), copied over the new PAK script from DEC
to the nondamaged internal disk (my machine contains 2 internal disks)
containing the root partition and loaded the new licenses (as I'm sure most of
you are already aware, this script also deletes the old licenses before loading
the new ones). At the time I was loading them, I didn't realize that my
machine thought it was early January 1998 and not 1999 -- evidently the machine
does not increment the year on new years if the machine is turned off. The
license script ran with no errors and I thought I was AOK on that front.
Over the next few days, I replaced the damaged internal disk (again, this
wasn't the root partition disk) and added the additional memory. My machine
came up with no difficulties and I replaced the file system that was on the
previous disk. A few days after that, I noticed that my machine was still in
1998 and I reset the date to 1999. I didn't realized that anything was wrong.
Once classes started back up, one of my students tried to log in with telnet
and got a message that too many users were on. Since at the time, I was the
only user logged in, I realized something was wrong. I checked the
/var/adm/messages file and found the following at the end of the file:
Jan 13 17:38:56 torgo vmunix: tu0: selecting 10BaseT port
Jan 13 17:38:56 torgo vmunix: tga0 at pci0
Jan 13 17:38:56 torgo vmunix: tga0: depth 8, map size 4MB, 1280x1024
Jan 13 17:38:56 torgo vmunix: lvm0: configured.
Jan 13 17:38:56 torgo vmunix: lvm1: configured.
Jan 13 17:38:56 torgo vmunix: dli: configured
Jan 13 17:38:56 torgo vmunix: SuperLAT. Copyright 1993 Meridian Technology Corp.
All rights reserved.
Jan 15 19:01:53 torgo vmunix: OSF-USR PAK is outdated
The last line here shows the trouble -- there is something wrong with the
OSF-USR license, which allows more than one user to log in. I ran the license
manager and printed out the following with the command:
"lmf list full for OSF-USR > myfile.txt".
I have labeled what I think the problem might be with "*"s (continued after
this output).
Product Name: OSF-USR
Producer: DEC
Issuer: DEC
Authorization Number: B1098-CAMPUSWIDE-1877
Number of units: 0
Version:
Product Release Date:
Key Termination Date: 30-JAN-2000
Availability Table Code:
Activity Table Code: CONSTANT=100
Key Options:
Product Token:
Hardware-Id:
License status: active
Cancellation Date:
Revision Number: 0
Comment:
Cache Total Units: 200
Activity Charge: 100
Usable Units: 200
Cache Termination Date: 30-JAN-1998 <******************************
Product Name: OSF-USR
Producer: DEC
Issuer: DEC
Authorization Number: B1097-CAMPUSWIDE-1877
Number of units: 0
Version:
Product Release Date:
Key Termination Date: 30-JAN-1999
Availability Table Code:
Activity Table Code: CONSTANT=100
Key Options:
Product Token:
Hardware-Id:
License status: active, multiple
Cancellation Date:
Revision Number: 0
Comment:
Product Name: OSF-USR
Producer: DEC
Issuer: DEC
Authorization Number: B1096-CAMPUSWIDE-1877
Number of units: 0
Version:
Product Release Date:
Key Termination Date: 30-JAN-1998
Availability Table Code:
Activity Table Code: CONSTANT=100
Key Options:
Product Token:
Hardware-Id:
License status: terminated
Cancellation Date:
Revision Number: 0
Comment:
Product Name: OSF-USR
Producer: DEC
Issuer: DEC
Authorization Number: B895-CAMPUSWIDE-1877
Number of units: 0
Version:
Product Release Date:
Key Termination Date: 31-JAN-1997
Availability Table Code:
Activity Table Code: CONSTANT=100
Key Options:
Product Token:
Hardware-Id:
License status: terminated
Cancellation Date:
Revision Number: 0
Comment:
Product Name: OSF-USR
Producer: DEC
Issuer: DEC
Authorization Number: B-CAMPUSWIDE-1877
Number of units: 0
Version:
Product Release Date:
Key Termination Date: 30-NOV-1995
Availability Table Code:
Activity Table Code: CONSTANT=100
Key Options:
Product Token:
Hardware-Id:
License status: terminated
Cancellation Date:
Revision Number: 0
Comment:
Product Name: OSF-USR
Producer: DEC
Issuer: DEC
Authorization Number: OSF-BASE-IMPLICIT-USER
Number of units: 200
Version:
Product Release Date:
Key Termination Date:
Availability Table Code:
Activity Table Code: CONSTANT=100
Key Options:
Product Token:
Hardware-Id:
License status: active, multiple
Cancellation Date:
Revision Number: 0
Comment:
What is a "Cache Termination Date"? Even though the "Key Termination Date" was
set correctly, this "Cache Termination Date" was not. Also, I have never seen
this "date" before when upgrading licenses. I'm not sure why this was set (it
never was before) and why it was set to January of last year. Did this result
from the machine thinking it was still January 1998 when the license script was
ran? There are also a variety of X-Window licenses that also show this "Cache
Termination Date: 30-Jan-1998" entry. Once again, I am essentially alone when
it comes to taking care of my DEC Unix machine. Can anyone tell my what's
wrong and what's the exact way to fix it?
Thanks,
Don Luttermoser
P.S. After discovering this problem, I tried to rerun the PAK script and after
getting through the first 5 or so license entries in the script, each of which
claimed that the license was already loaded, the script ended withou going any
further.
Received on Sun Jan 24 1999 - 21:39:53 NZDT