[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference help::dns

Title:DECdns - Digital's Distributed Name Service
Notice:not to be confused with DNS: Domain Name Service (Kits: 1420,947))
Moderator:BULEAN::WHEATER
Created:Tue Apr 14 1987
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1443
Total number of notes:5833

1438.0. "clock went backwards" by CHR27::YEUNG (im2bz2p,ru?) Mon Apr 07 1997 01:37

In order to test the effects of the 19-May-1997 VMS RTL bug, my
customer took one of their test suites (which included its own
DECdns namespace, DEDdns server, and DTSS time provider) and
changed all system time to May 18, 1997.  

They've concluded all of their tests and have set all the system
clocks (including DTSS time provider and DECdns server) back to
today.  But DECdns stopped working, probably because the DECdns server
time went backwards.  If they were to set the DECdns server time
to 20-May-1997, then it would works again.

The customer does NOT want to shutdown the the DECdns server until
20-May-1997, and they do NOT want to recreate the namespace.
So how can they fix the DECdns server so that it can run with
today's time

And no, they did not save the checkpoint file prior to setting the
clocks forward to 18-May-1997.

Thanks

Tim
T.RTitleUserPersonal
Name		DateLines
1438.1dns$diag help badclockTECMAN::WHEATERMon Apr 07 1997 11:5022
    Hi Tim:

    Please tell the customer that they should always make a backup of the
    checkpoint, tlog, and version files before attempting such an
    experiment!!

    The dns$diag program has two commands to handle this situation

    analyze badclock
    repair badclock

    Make sure that you back up the database files before starting.

    Help backclock

    gives an explaination of how to use the command - read it before
    proceeding.


    Regards,
    Bob Wheater
    DECdns Engineering
1438.2My faultCHR27::YEUNGim2bz2p,ru?Mon Apr 07 1997 12:1814
re .1:

>    Please tell the customer that they should always make a backup of the
>    checkpoint, tlog, and version files before attempting such an
>    experiment!!

I'm to be blamed for this one since I'm their DECdns/DTSS administrator
and I'm the one who changed time without first saving the DECdns files.

I'll try your recommended commands today and will let you know the results.

Thanks Bob.

Tim
1438.3analyze badclock not workingCHR27::YEUNGim2bz2p,ru?Wed Apr 09 1997 01:3132
Bob:

The dna$diag analyze badclock command is not working ...

$ DIR DK0:[DNS$SERVER]

Directory DK0:[DNS$SERVER]

DNS.CONF;1
NSM1_CH.CHECKPOINT0000000453;1
NSM1_CH.TLOG0000000453;1
NSM1_CH.VERSION;1

Total of 4 Files

$ MCR DNS$DIAG
diag> analyze badclock NSM1_CH.CHECKPOINT0000000453
unknown clearinghouse
diag>

We can read from the DNS database, but we get BADCLOCK when we
try to write to it.

Sometimes, DNS problems go away after 24 hours; so I attempted to
leave the server up for whole.  But it dumps after every hour of
uptime.  DNS$SERVER.DMP and the VMDATA file are generated.
What do you recommend I do at this point.

Thanks

Tim
1438.4use clearinghouse nameTECMAN::WHEATERWed Apr 09 1997 10:1613
    Hi Tim:

    I recommend that you used the analyze badclock command correctly!

    The parameter for analyze badclock is the clearinghouse name
    (NOT THE NAME OF THE CHECKPOINT FILE AS YOU SPECIFIED).

    The command should be:

    analyze badclock .nsm1_ch

    regards,
    Bob
1438.5Working!CHR27::YEUNGim2bz2p,ru?Thu Apr 10 1997 17:306
All fixed now!
It's amazing how well things work when you use the command correctly.

Thanks Bob

Tim