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

[IDD #RUB-260067]: ldm cluster at A&M is doing some odd things (or perhaps my new client is?)

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: [IDD #RUB-260067]: ldm cluster at A&M is doing some odd things (or perhaps my new client is?)
  • Date: Wed, 12 Dec 2012 10:08:29 -0700
Gerry,

> I miscopied something. Problems with not enough methyl xanthine early in
> the morning (that is, before about 2pm). I really did get it right later
> on, I even caught my mistake, but when I did the copy/paste, I got too much
> stuff.
> 
> Still, the RECLASS statement is a little vexing.

The reclassification (denial, actually) of the notifyme(1) request is because 
that request overlaps with the previously-existing REQUEST entries: there's 
little sense in being notified of the remote existence of data-products that 
you've already received.

> Also, with the latest
> install, on a new VM, I'm seeing what looks like a good startup but no
> evidence it's doing anything: ldmadmin watch and ldmadmin tail fail to show
> anything.

That's a problem. Does it occur with the rolled-back LDM?

> Thanks gerry
> --
> Gerry Creager
> NSSL/CIMMS
> 405.325.6731

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RUB-260067
Department: Support LDM
Priority: Normal
Status: Closed