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

[IDD #EEH-918211]: LDM - Network Issues...

Hi Mike,

> In the meantime, I have run ping (the upstream server responds), ldmping
> (responses appear normal), and notifyme (responses appear normal).

OK.  If ldmping and notifyme show that the upstream LDM host is responding,
you should be able to receive data.  The second part of the LDM is
doing something with the data once it has been received into the local
LDM queue.  Many LDM newbies get tripped up by thinking that just because
they receive a product it will automatically get written somewhere
to their disk (other than in the LDM queue).  Products will only appear
on the local disk if there is/are pqact.conf action(s) that make that

> I examined ldmadmin-pl.conf and found $ldmhome was $LDMHOME.  I must
> have changed the spelling; old habits die hard.  So, I examined all
> related variables, changing a few to be sure, then running ldmadmin
> config, finding the values were missing, then changing them back to the
> originals and running ldmadmin config to check.  Everything appears OK.

Your comment about "changing a few to be sure" raises a red flag for me.
Please send along your ldmadmin-pl.conf file contents along with
the ldmping (and now notifyme) and ldmd.conf and pqact.conf contents
I requested previously.

> I'm now running ldm again.  Previously, although the log file appears in
> the correct directory, it has no data in it (there's that word again.)

Since you reinstalled the operating system, it is most likely that the
configurations you had previously made in /etc/syslog.conf, /etc/services,
and /etc/rpc (all done as 'root') were lost.  Also, new versions of Linux
have the SELINUX facility that governs how daemons can function.  If your
/etc/syslog.conf,rpc,services files are correctly configured and you are
still not logging to ~ldm/logs/ldmd.log, I would bet that a change is
needed in the /etc/selinix/config file:

if set, change the line:




Your system _must_ be rebooted for this configuration change to take effect.

After SELINUX is disabled (turns off rules for syslogd) and /etc/syslog.conf
is correctly configured, logging to the ~ldm/logs/ldmd.log file should work.
I suggest that if ~ldm/logs/ldmd.log does not already exist OR if it is
not owned by your 'ldm' user, that you create it making sure that it is
owned by your 'ldm' user.

> There is also no data in the data files:
> /var/data/ldm/data/point/metar/netcdf (and similar).

If the data is being received by your LDM, the problem is likely that
your ~ldm/etc/pqact.conf file does not contain one or more actions
that process the data being received.

One last thing that one should always look at after reinstalling an operating
system:  make sure that the system clock is correct.  We suggest doing this
by configuring and running 'ntpd'.  If the system clock is off enough, a
feed request to an upstream host might be requesting data whose time is
in the future.  Since there will be no data with that match those timestamps,
no data will flow until the future time is reached.  This situation is
completely avoided by insuring that the system clock is accutately maintained,
and this is best done by running 'ntpd'.

> Mike


Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: EEH-918211
Department: Support IDD
Priority: Normal
Status: Closed