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

Re: 20000613: LDM Start Problems

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: Re: 20000613: LDM Start Problems
  • Date: Tue, 13 Jun 2000 15:09:00 -0500
Steve,

Thanks for the quick response.  I made the suggested changes.  I should point 
out that
our other box has a similar line using the caret, backslashes, and dollar sign 
and seems
to work okay.  Another thought occurred to me while I was editing the file.  I 
found one
or two spaces in the line.  I deleted all the whitespace characters and 
inserted single
tabs between the fields.  After those changes were made, the LDM started like a 
charm.
I have a sneeking suspicion that deleting the spaces might have made the 
difference.

Anyway, I'm happy now!  Thanks again for the help.

Ken

Unidata Support wrote:

> Ken,
> The log message you have:
> /home/ldm/etc/ldmd.conf: line 22: syntax error
>
> Means that the process is getting hung from a bad entry in your ldmd.conf 
> file.
>
> In your ldmd.conf file you have:
>
> ># LDM5 servers request data
> >#
> >#request        AFOS
> >#       ".*"
> >#       ^192\.168\.2\.11$
> >
> >request     ANY ".*" ^192\.168\.2\.11$
> >
> >
> >
> >#
>
> In general, it is not correct to use regular expressions in your request line
> for the host pattern, since you would never want to request from a pattern of 
> hosts.
> You want to make the request to exactly 192.168.2.11. The only place that you
> would use regexps is in the pattern to request, eg ".*".
>
> Try changing the request line to:
> request ANY     ".*"    192.168.2.11
>
> After that fix, you may also want to comment out the apparently blank lines 
> around
> that request, just in case you have any hidden control characters floating 
> around.
>
> Let me know if this does not solve your problem.
>
> Steve Chiswell
> Unidata User Support