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

20031007: LDM and waldo at stc (cont.)

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: 20031007: LDM and waldo at stc (cont.)
  • Date: Tue, 07 Oct 2003 16:56:48 -0600
>From: "Anderson, Alan C. " <address@hidden>
>Organization: St. Cloud State
>Keywords: 200310071420.h97EK2k1007135 LDM IDD

Hi Alan,

>Well I did not accuse anyone, but I  I could have.  I may need
>to eat a little humble pie myself, but I did not start the problem.

Hmm...

>The problem was in our ldmd.conf file.   The request line for 
>Albany was ok, but those for papagayo had a  leading  space at 
>the left edge of the line.   Removing that space, stopping and 
>restarting the ldm and data is now flowing.   I saw this structure
>earlier today, but did not realize it could be the problem.

We just talked about this situation and agreed that the parser for
ldmd.conf should not interpret a line that begins with a space
as a comment.  Comment lines should be only those for which the
first non whitespace character is the '#' character.  This will
eliminate problems like the one you ran into.

>I think I know who edited it the last time but I won't get into that.
>So,  that is what part time administration gets us to.

This was not a big deal for us.  I was just concerned that you
were not getting data, and that was impacting your ability to
teach your classes.

>I asked our net guy to turn on ssh for waldo and he said it would
>be on by tomorrow morning.  Not sure why it was turned off.
>Any changes or suggestions you make would be welcome.

OK, I will upgrade you to LDM-6.0.14 and make any adjustments in
ldmd.conf that I think are warranted.  I will, of course, let you
know exactly what I did.

>I did not try to get data from emo.   Are you offering him as
>a failover site ?

I offered emo since it is under our immediate control, and so can
be changed to feed anybody we want.  We do not, however, want
folks to start using emo as an official failover site since it
is a development and test machine.

>Thanks for the prompt reply and concern on your part.  The support 
>we get from Unidata makes all these little snags seem minor.

It is my pleasure to help out when I can.

On to the next fire ;-)

Cheers,

Tom