This e-mail was sent the 10th of December and the TSC was advised some
days before.
>
> Hello Managers,
>
> Perharps it was a mistake to send
>
> SUMMARY: Migrating to NSR 5.2 : the war story continues
>
> as soon as it was working.
>
> 12/10/98 11:08:34 nsrd: server notice: started
> ............
> 12/10/98 13:16:13 nsrd: registration info event: Server is disabled
> update
> enabler required
> ......
> 12/10/98 13:48:14 nsrd: server notice: started
> ..................
> 12/10/98 15:49:00 nsrd: registration info event: Server is disabled
> update
> enabler required
>
> In fact the lifetime for the enablers is :
>
> 2 hours and 46 seconds !!!!
>
> I've tried several times.
>
> Daniel
The problem has been identified last week by Terry Carruthers :
+++++++++++++++++++++++++++++++++++++++++
Here is the debug output that seems pertinent. Note
that it reports the index update enabler version and license update
enabler versions are not the same.
01/26/99 07:37:49 nsrd: index update enabler version = V3.0A
01/26/99 07:37:49 nsrd: license update enabler version = 5
01/26/99 07:37:49 nsrd: check_all_mm_control(): entry.
01/26/99 07:37:49 nsrindexd: nsrfx_end: 917332669 op 1
01/26/99 07:37:49 nsrd: waitchild reaped, pid 1943
01/26/99 07:37:49 nsrd: registration info event: Server is disabled
update enabler required
In the program nsrd's main loop, it periodically (every 2 hours) does a
recheck
of licenses to make sure that nothing has expired. At this time, if the
server's index release number (V3.0A
as output above) is found not to match the product
release number (5 above) and there is not an update enabler on the
system then the server is disabled.
The question is why does your server index have this very old release
number associated with it?
For right now, I can't answer that question. My basic hypothesis is
that
the index was not correctly, fully converted when you upgraded, but I
don't know why.
So what I want to do is provide you with an Update Enabler and see if
that fixes the problem.
+++++++++++++++++++
So the problem has been fixed by this update enabler. Meanwhile it was
quite possible to work in evaluation mode by removing all the enablers
information in /nsr/res/nsr.res.
Daniel Clar
Computer Operations Manager
Supelec
France
Received on Thu Feb 04 1999 - 12:09:19 NZDT