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

[LDM #WCO-560313]: LDM 6.5.1 oddity

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 #WCO-560313]: LDM 6.5.1 oddity
  • Date: Thu, 08 Mar 2007 17:13:24 -0700
Daryl,

> I've got a RHEL4u4 box that I just put LDM 6.5.1 on.  Here are the logs
> from this machine:
> 
> Mar 08 20:56:32 pircsds1 rpc.ldmd[18604] NOTE: Starting Up (version:
> 6.5.1; built: Mar  8 2007 14:22:46)
> Mar 08 20:56:32 pircsds1 rpc.ldmd[18604] NOTE: Using local address
> 0.0.0.0:388
> Mar 08 20:56:34 pircsds1 mesonet.agron.iastate.edu[18606] NOTE:
> Data-product with signature 3e80ad58e111bbd8c1548486a11eaba8 wasn't found
> in product-queue
> Mar 08 20:56:34 pircsds1 mesonet.agron.iastate.edu(feed)[18606] NOTE:
> Starting Up(6.5.1/6): 20070308195636.198 TS_ENDT {{EXP,
> "^ot0003_............\.dat"}}, SIG=3e80ad58e111bbd8c1548486a11eaba8,
> Primary
> Mar 08 20:56:34 pircsds1 mesonet.agron.iastate.edu(feed)[18606] NOTE:
> topo:  mesonet.agron.iastate.edu {{EXP, (.*)}}
> Mar 08 20:56:43 pircsds1 pircsl4.agron.iastate.edu[18610] NOTE:
> Data-product with signature 5a38e79d78b7dc73af1bd6eff770ea95 wasn't found
> in product-queue
> Mar 08 20:56:43 pircsds1 pircsl4.agron.iastate.edu(feed)[18610] NOTE:
> Starting Up(6.5.1/6): 20070308205146.118 TS_ENDT {{EXP,  "^ISUMM5"}},
> SIG=5a38e79d78b7dc73af1bd6eff770ea95, Primary
> Mar 08 20:56:43 pircsds1 pircsl4.agron.iastate.edu(feed)[18610] NOTE:
> topo:  pircsl4.agron.iastate.edu {{EXP, (.*)}}
> Mar 08 20:56:43 pircsds1 metfs1.agron.iastate.edu[18611] NOTE:
> Data-product with signature 5a38e79d78b7dc73af1bd6eff770ea95 wasn't found
> in product-queue
> Mar 08 20:56:43 pircsds1 metfs1.agron.iastate.edu(feed)[18611] NOTE:
> Starting Up(6.5.1/6): 20070308195646.125 TS_ENDT {{EXP,  "ISUMM5"}},
> SIG=5a38e79d78b7dc73af1bd6eff770ea95, Primary
> Mar 08 20:56:43 pircsds1 metfs1.agron.iastate.edu(feed)[18611] NOTE: topo:
> metfs1.agron.iastate.edu {{EXP, (.*)}}
> Mar 08 20:57:42 pircsds1 pircsl4.agron.iastate.edu[18653] NOTE: Exiting
> Mar 08 20:57:42 pircsds1 metfs1.agron.iastate.edu[18654] NOTE: Exiting
> Mar 08 20:58:04 pircsds1 mesonet.agron.iastate.edu[18656] NOTE: Exiting
> Mar 08 20:58:42 pircsds1 pircsl4.agron.iastate.edu[18670] NOTE: Exiting
> Mar 08 20:58:42 pircsds1 metfs1.agron.iastate.edu[18671] NOTE: Exiting
> Mar 08 20:59:04 pircsds1 mesonet.agron.iastate.edu[18680] NOTE: Exiting
> Mar 08 20:59:43 pircsds1 pircsl4.agron.iastate.edu[18686] NOTE: Exiting
> Mar 08 20:59:43 pircsds1 metfs1.agron.iastate.edu[18687] NOTE: Exiting
> Mar 08 21:00:04 pircsds1 mesonet.agron.iastate.edu[18694] NOTE: Exiting
> Mar 08 21:00:43 pircsds1 pircsl4.agron.iastate.edu[18699] NOTE: Exiting
> Mar 08 21:00:43 pircsds1 metfs1.agron.iastate.edu[18700] NOTE: Exiting
> Mar 08 21:01:04 pircsds1 mesonet.agron.iastate.edu[18705] NOTE: Exiting
> Mar 08 21:01:43 pircsds1 pircsl4.agron.iastate.edu[18717] NOTE: Exiting
> Mar 08 21:01:43 pircsds1 metfs1.agron.iastate.edu[18718] NOTE: Exiting
> Mar 08 21:02:04 pircsds1 mesonet.agron.iastate.edu[18719] NOTE: Exiting
> Mar 08 21:02:43 pircsds1 pircsl4.agron.iastate.edu[18722] NOTE: Exiting
> Mar 08 21:02:43 pircsds1 metfs1.agron.iastate.edu[18723] NOTE: Exiting
> Mar 08 21:03:04 pircsds1 mesonet.agron.iastate.edu[18726] NOTE: Exiting
> Mar 08 21:03:43 pircsds1 pircsl4.agron.iastate.edu[18734] NOTE: Exiting
> Mar 08 21:03:43 pircsds1 metfs1.agron.iastate.edu[18735] NOTE: Exiting
> 
> 
> What is all of those Exiting statements at the bottom?

The "Exiting" messages appear to be from downstream LDM-s on host
"pircsds1" that terminated.

> Why isn't there an
> accompanying NOTE: for when the connection is made?

If those processes are downstream LDM-s, then they should have
written a "Starting Up" message (and other messages).  This is
very odd.  Did you send a SIGTERM to the LDM or execute an
"ldmadmin stop"?

> Those appear to be new process IDs.
> 
> No such troubles with 6.4.1....  Hmmmm, any ideas?

It would help if I log onto host "pircsds1" as the LDM user.
May I?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WCO-560313
Department: Support LDM
Priority: Normal
Status: On Hold