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

[LDM #NJE-906346]: LDM Log Time Zone Issue

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: [LDM #NJE-906346]: LDM Log Time Zone Issue
  • Date: Mon, 10 Dec 2012 13:10:45 -0700
Justin,

> We are in the process of spinning up a new supercomputer here at NCEP and
> have run into an issue with the LDM logs.
> 
> The system time on the supercomputer is in UTC, but the LDM is giving the
> time stamp as local (EST) in the ldmd.log file. I've looked at the
> registry.xml file and LDM documentation but it's not obvious to me where
> this is being set. We run LDM on many of our systems and the the log has
> always returned in UTC, I'm at a loss as to what is causing EST to be the
> time stamp.
> 
> We are running LDM 6.11.1 on RHEL 6.2
> 
> Here is the behavior:
> [dbnet@t10d1 logs]$ date
> *Mon Dec 10 15:56:56 UTC 2012*
> [dbnet@t10d1 logs]$ tail ldmd.log
> *Dec 10 10:57:03* t10d1 pqact[26046] INFO:                file:
> -close#011/dcom/us007003/ldmdata/obs/upperair/nexrad_level2/KVNX/KVNX_20121210_155111.bz2
> and the ident is L2-BZIP2/KVNX/20121210155111/687/27/I/V06/0
> *Dec 10 10:57:03* t10d1 pqact[26046] INFO: [filel.c:297] Deleting closed
> FILE entry
> "/dcom/us007003/ldmdata/obs/upperair/nexrad_level2/KVNX/KVNX_20121210_155111.bz2"
> *Dec 10 10:57:04* t10d1 140.90.85.102[26052] INFO:    81020
> 20121210155703.648 NEXRAD2 522038
> L2-BZIP2/KLVX/20121210155231/522/38/I/V06/0
> *Dec 10 10:57:04* t10d1 pqact[26046] INFO:    81020 20121210155703.648
> NEXRAD2 522038  L2-BZIP2/KLVX/20121210155231/522/38/I/V06/0
> *Dec 10 10:57:04* t10d1 pqact[26046] INFO:                file:
> -close#011/dcom/us007003/ldmdata/obs/upperair/nexrad_level2/KLVX/KLVX_20121210_155231.bz2
> and the ident is L2-BZIP2/KLVX/20121210155231/522/38/I/V06/0
> *Dec 10 10:57:04* t10d1 pqact[26046] INFO: [filel.c:297] Deleting closed
> FILE entry
> "/dcom/us007003/ldmdata/obs/upperair/nexrad_level2/KLVX/KLVX_20121210_155231.bz2"
> *Dec 10 10:57:04* t10d1 140.90.85.102[26052] INFO:    27679
> 20121210155703.957 NEXRAD2 616005
> L2-BZIP2/KOTX/20121210155613/616/5/I/V06/0
> *Dec 10 10:57:04* t10d1 pqact[26046] INFO:    27679 20121210155703.957
> NEXRAD2 616005  L2-BZIP2/KOTX/20121210155613/616/5/I/V06/0
> *Dec 10 10:57:04* t10d1 pqact[26046] INFO:                file:
> -close#011/dcom/us007003/ldmdata/obs/upperair/nexrad_level2/KOTX/KOTX_20121210_155613.bz2
> and the ident is L2-BZIP2/KOTX/20121210155613/616/5/I/V06/0
> *Dec 10 10:57:04* t10d1 pqact[26046] INFO: [filel.c:297] Deleting closed
> FILE entry
> "/dcom/us007003/ldmdata/obs/upperair/nexrad_level2/KOTX/KOTX_20121210_155613.bz2"
> 
> Any suggestions?

We've seen that here but don't know why it happens. According to the code, it 
could only happen if the gmtime(3) system function returned a NULL, which is 
possible but unlikely.

What is the value of the LDM user's TZ environment variable?

Why did your date(1) invocation print the time in UTC rather than EST?

> Thanks,
> Justin Cooke
> NCEP Central Operations

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NJE-906346
Department: Support LDM
Priority: Normal
Status: Closed