[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020918: Decoder logs - removing

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20020918: Decoder logs - removing
  • Date: Thu, 19 Sep 2002 17:29:39 -0600
Nancy, 
Its up to the LDM administrator to rotate the log files.

I typically rotate them daily here using the LDM program newlog
executed from the ldm's crontab. For example, I keep 2 days logs
of most decoders with:
0 17 * * * bin/newlog data/gempak/logs/dcamos.log 2
0 17 * * * bin/newlog data/gempak/logs/dcmmos.log 2
0 17 * * * bin/newlog data/gempak/logs/dcnmos.log 2
0 17 * * * bin/newlog data/gempak/logs/dcnldn.log 2
0 17 * * * bin/newlog data/gempak/logs/dcncprof.log 2
0 17 * * * bin/newlog data/gempak/logs/dcprof.log 2
0 17 * * * bin/newlog data/gempak/logs/dctrop.log 2
0 17 * * * bin/newlog data/gempak/logs/dcwatch.log 2
0 17 * * * bin/newlog data/gempak/logs/dcwarn.log 2
0 17 * * * bin/newlog data/gempak/logs/dcwtch.log 2
0 17 * * * bin/newlog data/gempak/logs/dcffg.log 2
0 17 * * * bin/newlog data/gempak/logs/dcstorm.log 2
0 17 * * * bin/newlog data/gempak/logs/dcgrib.log 2
0 17 * * * bin/newlog data/gempak/logs/dcmetr.log 2
0 17 * * * bin/newlog data/gempak/logs/dcuair.log 2
0 17 * * * bin/newlog data/gempak/logs/dcuair_drop.log 2
0 17 * * * bin/newlog data/gempak/logs/dcacars.log 2
0 17 * * * bin/newlog data/gempak/logs/dcsuomi.log 2
0 17 * * * bin/newlog data/gempak/logs/dclsfc.log 2
0 17 * * * bin/newlog data/gempak/logs/dcmsfc.log 2
0 17 * * * bin/newlog data/gempak/logs/dcacft.log 2
0 17 * * * bin/newlog data/gempak/logs/dcscd.log 2
0 17 * * * bin/newlog data/gempak/logs/dcisig.log 2
0 17 * * * bin/newlog data/gempak/logs/dcncon.log 2
0 17 * * * bin/newlog data/gempak/logs/dcsvrl.log 2

You should also rotate the ldmd.log file, typically through 
something like:
0 17 * * * bin/ldmadmin newlog

(note that the ldmadmin perl script runs newlog for the ldmd.log file,
with the number of log files configured in the script...
but in the above, I am just using the newlog program and specifying the log
file name and the number of files to keep on the command line.)

The primary difference is that the ldmadmin script will issue the
"hupsyslog" program after rotating the ldmd.log file so that syslog
will start writing to the new file. This isn't necessary for the Gempak
decoders, as they reopen the log files themselves as necessary.

Steve Chiswell

>From: Nancy Selover <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200209192312.g8JNCg109688

>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
>
>--Boundary_(ID_9A7d9cZtU9gs1IOeSDhWAQ)
>Content-type: text/plain;      charset="iso-8859-1"
>
>Steve,
>
>We have been without an ldm/gempak administrator for awhile and are now
>trying to bring the system back up to it's proper condition.  Recently we
>began having some disk full problems on our ldm/gempak server, and we found
>that the decoder log files had become enormous - 100 to 400 MB.  How often
>should they be cleaned up - removed, and how quickly would you expect them
>to grow?  Is this something the scour utility does, or is it something the
>ldm administrator should be keeping up with?
>
>Thanks for the guidance,
>Nancy
>
>Nancy J. Selover
>Asst. State Climatologist
>Office of Climatology           tel:  480-965-0580
>Arizona State University      fax: 480-965-1473
>Tempe, AZ  85287-1508      e-mail: address@hidden
>
>
>--Boundary_(ID_9A7d9cZtU9gs1IOeSDhWAQ)
>Content-type: text/html;       charset="iso-8859-1"
>Content-transfer-encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
><HTML>
><HEAD>
><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>charset=3Diso-8859-1">
><META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
>5.5.2655.35">
><TITLE>Decoder logs - removing</TITLE>
></HEAD>
><BODY>
>
><P><FONT SIZE=3D2 FACE=3D"Arial">Steve,</FONT>
></P>
>
><P><FONT SIZE=3D2 FACE=3D"Arial">We have been without an ldm/gempak =
>administrator for awhile and are now trying to bring the system back up =
>to it's proper condition.&nbsp; Recently we began having some disk full =
>problems on our ldm/gempak server, and we found that the decoder log =
>files had become enormous - 100 to 400 MB.&nbsp; How often should they =
>be cleaned up - removed, and how quickly would you expect them to =
>grow?&nbsp; Is this something the scour utility does, or is it =
>something the ldm administrator should be keeping up with?</FONT></P>
>
><P><FONT SIZE=3D2 FACE=3D"Arial">Thanks for the guidance,</FONT>
><BR><FONT SIZE=3D2 FACE=3D"Arial">Nancy</FONT>
></P>
>
><P><B><I><FONT SIZE=3D2 FACE=3D"Arial">Nancy J. Selover</FONT></I></B>
><BR><I><FONT SIZE=3D2 FACE=3D"Arial">Asst. State =
>Climatologist</FONT></I>
><BR><FONT SIZE=3D2 FACE=3D"Arial">Office of =
>Climatology&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
>tel:&nbsp; 480-965-0580</FONT>
><BR><FONT SIZE=3D2 FACE=3D"Arial">Arizona State =
>University&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fax: 480-965-1473</FONT>
><BR><FONT SIZE=3D2 FACE=3D"Arial">Tempe, AZ&nbsp; =
>85287-1508&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; e-mail: address@hidden</FONT>
></P>
>
></BODY>
></HTML>=
>
>--Boundary_(ID_9A7d9cZtU9gs1IOeSDhWAQ)--
>