[mrtg] Re: Problem with test y2k

[Scheidel, Greg]

Here's what I would do if I found myself in this situation.

(1) Prevent further processing of these devices so that you can update the
logs without worrying about the MRTG process trying to touch them at the
same time, and will not have more data being gathered while you update the
existing data.  Either comment out the section of your "mrtg.cfg" file that
refers to 195.130.100.1.[1, 2, 3], or just "crontab -e" to edit the cron
schedule and comment out the whole thing.

(2) Run 'PS -a | grep mrtg' to make sure that no MRTG processes are still
running.  If you see an MRTG process, wait another 5 minutes and check
again.

(3) Make sure that you have *FULL* backups of your log files before you go
on.

(4) Edit the log files.  You have two choices: to either simply toss all of
the data gathered during your testing, or try to massage it.  From what
you've described, massaging it should be no problem and will provide you
with *mostly* accurate data.

Either way, start looking for the line beginning with 946761002 and then
skim the file.  You will see that the numbers at the beginning of each line
grow larger towards the top of the file, except for the section where you
rolled the date back and forth.  These numbers are the timestamps, recorded
as non-skip seconds since your OS's 'base time.'

(4a) If you are going to toss the data gathered during tested, remove all
lines *between* 946761002 and the top line (line 1) of the file.  You may
want to add two extra lines at lines 2 and 3: '946761003 0 0 0 0' (line 2)
and ' 946761004 0 0 0 0' (line 3).  In any case, change the timestamp
starting line 1 to match the timestamp starting line 2.

(4b) If you are going to try and massage the data, you will need to update
the timestamps from line 1 (inclusive) down to 946761002 (exclusive).  The
timestamps should be sequential.  Start at 946761002 and work your way up.
If what you've described is accurate, the lines above 946761002 should occur
at 5 minute (or 300 second) intervals; the timestamp for the lines above
946761002 should be 946761302, 946761602, 946761902, etc.  When you get to
the top of the file, line 1 should just get the same timestamp as line 2.

This should provide you with data that is accurate *except* for the time
interval error between the lines with timestamp 946761002 and 946761302,
which will be probably be negligible.  The potential for error is because
this interval assumes there was 5 mins between these two data points.

(5) Make new backups of your editing log files (*not* overwriting the
backups you made of your originals).

(6) Run the MRTG command manually before restarting the cron job to ensure
that rateup does not report any errors.

(7) Assuming no errors, restart cron processing of these interfaces.

DISCLAIMER:
- This is by no means intended as a comprehensive set of steps.  This is off
the top of my head, and you need to use common sense in using these
suggestions.  Your use of these suggestions in no way implies liability for
your results or data on the part of myself, my employer, or my workplace.
- You should take the time to familiarize yourself with the
\doc\logfile-format.txt file distributed with your MRTG source.
- As mentioned previously by somebody else on the list, don't do testing
like you did on a production system in the first place (I'm sure you've
heard that a hundred times by now, tho. :).

Greg S.

-----Original Message-----
From: Kostas Papachristofis [mailto:kostaspa at teiath.gr]
Sent: Thursday, December 23, 1999 5:25 AM
To: mrtg at list.ee.ethz.ch
Subject: [mrtg] Problem with test y2k


I' ve changed the date to my from 22/12/99 to 01/01/2000 for one day.
Then I tried to bring it back to the correct date and now I receive the
following error. Is there any solution ??


Your "cron" job on hermes
/usr/local/MRTG-bin/mrtg /usr/local/MRTG-bin/mrtg.cfg

produced the following output:

Rateup ERROR: /usr/local/MRTG-bin//rateup found that 195.130.100.1.1's log
file
time of 946761002 was greater than now (945944401)
ERROR: Let's not do the time warp, again. Logfile unchanged.
Rateup ERROR: /usr/local/MRTG-bin//rateup found that 195.130.100.1.2's log
file
time of 946761002 was greater than now (945944401)
ERROR: Let's not do the time warp, again. Logfile unchanged.
Rateup ERROR: /usr/local/MRTG-bin//rateup found that 195.130.100.1.3's log
file
time of 946761002 was greater than now (945944401)


--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:mrtg-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/mrtg

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:mrtg-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/mrtg