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

20020219: realtime FTPs to motherlode.ucar.edu (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: 20020219: realtime FTPs to motherlode.ucar.edu (cont.)
  • Date: Mon, 18 Feb 2002 14:45:34 -0700
>From: "Kevin Polston" <address@hidden>
>Organization: NOAA
>Keywords: 200202012111.g11LBCx14907 LDM installation

Kevin,

>Forgot to send my pqact.conf file and ldmd.conf file.

Aha!  No wonder some of your comments didn't match with the copy of ldmd.conf
that I could look at.

>Here they are.
>Got so engrossed in writing to you that I forgot to attach them.

OK.  One quick thing that I see in pqact.conf (and this was a quick one):

#NOGAPS US058
        PIPE    /usr1/nawips/exe/linux/dcgrib2 -v 4 -d 
data/gempak/logs/dcgrib_fnoc.log
        -e GEMTBL=/usr1/nawips/gempak/tables

You commented out the first line of the action, but not the second and
third.  The effect this will have is the same as if you had the PIPE
and -e GEMTBL lines sitting by themselves.  This is a problem that should
be fixed.  I recommend removing the lines from pqact.conf or commenting
out all three.  Also, I notice that the white space between NOGAPS and US058
is a space, not a tab.

Onto ldmd.conf:

request DDPLUS|IDS|HRS ".*" papagayo.unl.edu
request NIMAGE ".*" 129.93.52.150
request NEXRAD "/p(N0R|NVL)" papagayo.unl.edu
request MCIDAS ".*" papagayo.unl.edu

These patterns request a lot of data:  all of the NOAAPORT GINI imagery
through the NIMAGE ".*" request; all satellite imagery in the MCIDAS
stream; N0R and NVL products for all NEXRADs; and all the textual and
model data in the NWSTG channel of NOAAPORT.  Again, this is a lot
of data!

One question: in your last email, did you mean that the FILE
actions like:

#
# Zone Forecasts (FPUS5[0-6], FPCA52, etc.)
WMO     ^...... .... ([0-3][0-9])([0-2][0-9]).*/pZFP
        FILE    /usr1/nawips/metdat/nwx/pubprod/zone/(\1:yyyy)(\1:mm)\1\2.zone
WMO     ^FPAK[56][789] .... ([0-3][0-9])([0-2][0-9])
        FILE    /usr1/nawips/metdat/nwx/pubprod/zone/(\1:yyyy)(\1:mm)\1\2.zone
WMO     ^FOPN00 .... ([0-3][0-9])([0-2][0-9])
        FILE    /usr1/nawips/metdat/nwx/pubprod/zone/(\1:yyyy)(\1:mm)\1\2.zone

were not working?  If not, then the /usr1/nawips/metdat/nws/pubprod/zone
directory is not writable by the user running the LDM ('ldm').  The FILE
actions themselves look fine.  Again, what I use to check to see if the
LDM should be able to write to a directory is something like:

<login as 'ldm'>
touch /usr1/nawips/metdat/nwx/pubprod/zone/xxx

If this fails, then the LDM FILE actions will fail.  The solution is to
change directory read/write/execute permissions to allow writes.

Tom