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

[Support #SPJ-206476]: LDM 6.5.1 question

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: [Support #SPJ-206476]: LDM 6.5.1 question
  • Date: Mon, 19 Mar 2007 11:18:12 -0600
Carl,

> We�ve been using LDM v.6.5.1 for awhile now ‹ I�m curious if something 
> has
> changed since 6.4.x with regards to how LDM requests and transfers data.  I
> wouldn�t expect a change, so maybe you can explain what I�m seeing:
> 
> In the ldmadmin script, this entry exists: rpc.ldmd �o 120   --- so we don�t
> request any data older than 120 seconds old.  After a restart with a newly
> created queue, here�s what I�m seeing:
> 
> [ldm@greenlantern KDIX]$ date -u
> Sat Mar 17 02:29:30 UTC 2007
> [ldm@greenlantern KDIX]$ ls -last | more
> total 442800
> 252 -rw-rw-r--    1 ldm ldm  253952 Mar 16 21:28 20070317015031.bz2
> 80 drwxrwxr-x    2 ldm ldm   77824 Mar 16 21:28 ./
> 0 -rw-rw-r--    1 ldm ldm       0 Mar 16 21:28 20070317022500.bz2
> 252 -rw-rw-r--    1 ldm ldm  262144 Mar 16 21:27 20070317014447.bz2
> 0 -rw-rw-r--    1 ldm ldm       0 Mar 16 21:27 20070317021915.bz2
> 252 -rw-rw-r--    1 ldm ldm  262144 Mar 16 21:27 20070317013901.bz2
> 260 -rw-rw-r--    1 ldm ldm  262144 Mar 16 21:26 20070317013316.bz2
> 
> Why would the 01:50:31 file even show up when the time is 02:29:30?  Also,
> the pqact.conf.state file was deleted before LDM was started...

Because you started with an empty queue, the first delivered product
should be the oldest one in the upstream queue that was inserted
there no earlier than 150 seconds before 02:29:30 UTC (150 seconds =
120 seconds + 30 seconds of "slop").  It could be that the product
in question arrived late at the upstream LDM -- although it should
have been filtered-out by the "from" time in the product-class
and should not have been sent.

Unfortunately, comparing the times encoded in product-identifiers
with the times in log messages is difficult because the two times
have different origins and don't need to correspond.

I just tried the command "ldmadmin -v -o 300" on the latest version
of the LDM and it performed correctly according to the log file.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: SPJ-206476
Department: Support LDM
Priority: Normal
Status: Closed