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

[LDM #PFX-311376]: LDM - Difficulties re: initial startup; delqueue, mkqueue missing



Hi Mike,

I looked through the files you sent... the one thing that caught
my attention was your runtime setup:

lrwxrwxrwx 1 ldm_user1 ldm_user1 9 Feb 19 15:45 logs -> data/logs
lrwxrwxrwx 1 ldm_user1 ldm_user1 11 Feb 19 15:37 bin -> runtime/bin
lrwxrwxrwx 1 ldm_user1 ldm_user1 12 Feb 19 15:37 data -> runtime/data
lrwxrwxrwx 1 ldm_user1 ldm_user1 15 Feb 19 15:37 include -> runtime/include
lrwxrwxrwx 1 ldm_user1 ldm_user1 11 Feb 19 15:37 lib -> runtime/lib
lrwxrwxrwx 1 ldm_user1 ldm_user1 11 Feb 19 15:37 man -> runtime/man
lrwxrwxrwx 1 ldm_user1 ldm_user1 11 Feb 19 15:37 src -> runtime/src
lrwxrwxrwx 1 ldm_user1 ldm_user1 9 Feb 19 15:37 runtime -> ldm-6.5.0

Since there is no 'data' directory under the ldm-6.5.0 directory,
I suspect that your 'data' link is invalid.  The directories
that will exist under ldm-6.5.0 after you run 'configure' followed
by 'make', then 'make install' and finally 'sudo make install_setuds'
is:

$ cd ~ldm/ldm-6.5.0
$ ls
bin  include  lib  man  src


If, on the other hand, you created a 'data' directory under ldm-6.5.0,
you should delete it since a future upgrade will not use it due to
switching of the 'runtime' link.

Please do the following to regularize your LDM installation:

<as 'ldm'>

cd ~ldm
ldmadmin stop          <- just to make sure the LDM is not running

rm -rf data
mkdir data
mkdir data/logs
touch logs/ldmd.log

-- check how you setup logging in /etc/syslog.conf.  It should look
   like:
 ...

*.info;mail.none;authpriv.none;cron.none;local0.none  /var/log/messages

# LDM logging
local0.debug                                          
/usr/local/ldm/logs/ldmd.log

 ...

(NB: whitespaces are tabs, not spaces!)


ldmadmin mkqueue
ldmadmin start                    <- but please see below before starting your 
LDM

I will continue to look through the files you sent to see if anything
else jumps out at me, but I expect that the data -> runtime/data link
is your problem.

Next, I note that you have 10 different request lines presumably for
MADIS data:

REQUEST FSL2 "^FSL\.CompressedNetCDF\.RSAS" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(metar)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(sao)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(snow)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(raob)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(radiometer)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(HDW)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(HDW1h)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(mesonet2)" eldm.fsl.noaa.gov
REQUEST FSL2 "^FSL\.CompressedNetCDF\.(hydro2)" eldm.fsl.noaa.gov

This seems excessive _UNLESS_ bandwidth is an issue for you.

Finally, the patterns you are using in your ldmd.conf 'request' lines
seem incorrect:

- you are missing 'MADIS' from all of the product IDs except the first
  one where it is not needed
- no FSL2 product IDs contain parentheses, so including parentheses
  do not do anything for you.  Parentheses are used in regular expressions
  to contain a list of ORs

For example, the correct pattern for your second 'request' line would be:

REQUEST FSL2 "^FSL\.CompressedNetCDF\.MADIS\.metar" eldm.fsl.noaa.gov

The best way to figure out product ID regular expressions is to use the
'notifyme' utility to list the data available from the upstream LDM that
you are requesting the data from.  Here is an example that you should run:

<as 'ldm'>

notifyme -vxl- -f FSL2 -h eldm.fsl.noaa.gov -o 3600 -p 
"^FSL\.CompressedNetCDF\."

The output will look something like:

Feb 20 06:30:59 notifyme[85537] INFO: 245b92b91f5993987b9a18e407c1cfd6    11649 
20070220061222.069    FSL2 000  FSL.CompressedNetCDF.MADIS.sao.20070220_0600.gz
Feb 20 06:30:59 notifyme[85537] INFO: f5ba28b5ba18e5da51e31121ac759fd3   805204 
20070220061233.440    FSL2 000  
FSL.CompressedNetCDF.MADIS.metar.20070220_0500.gz
Feb 20 06:30:59 notifyme[85537] INFO: c255b79eed707dcc9c8758245f39cf25    10384 
20070220061237.166    FSL2 000  FSL.CompressedNetCDF.MADIS.coop.20070220_0600.gz
Feb 20 06:30:59 notifyme[85537] INFO: 8f3efb8e0debdc37bd80e05c0f23ec80    62563 
20070220061248.313    FSL2 000  
FSL.CompressedNetCDF.MADIS.maritime.20070220_0500.gz
Feb 20 06:30:59 notifyme[85537] INFO: 0c2410ec67aa58f2aa7df4fe05b03f39   101439 
20070220061318.581    FSL2 000  FSL.CompressedNetCDF.MADIS.coop.20070220_0500.gz
Feb 20 06:30:59 notifyme[85537] INFO: a22db33871114c34ce2e374c804980f5 16195238 
20070220061454.972    FSL2 000  FSL.CompressedNetCDF.RSAS.20070220_0600.gz
Feb 20 06:30:59 notifyme[85537] INFO: 96710c6494160d6464bf634d50153147    70885 
20070220061702.209    FSL2 000  FSL.CompressedNetCDF.MADIS.map.20070220_0600.gz
Feb 20 06:31:00 notifyme[85537] INFO: 7ca9f1d617e85a7662daccfccea92c97     9651 
20070220061702.489    FSL2 000  FSL.CompressedNetCDF.MADIS.map.20070220_0630.gz
Feb 20 06:31:00 notifyme[85537] INFO: 557b97807ebbbd426d15d5c73dfcfc67  4990989 
20070220061725.350    FSL2 000  
FSL.CompressedNetCDF.MADIS.mesonet2.20070220_0500.gz
Feb 20 06:31:00 notifyme[85537] INFO: c83a856891ca0801297d4317f0435e38   730827 
20070220061750.193    FSL2 000  
FSL.CompressedNetCDF.MADIS.mesonet2.20070220_0600.gz
Feb 20 06:31:00 notifyme[85537] INFO: 51ac7e1d848dc6495ca7513adbd2cf67  5230600 
20070220061753.189    FSL2 000  
FSL.CompressedNetCDF.MADIS.mesonet2.20070220_0400.gz
Feb 20 06:31:00 notifyme[85537] INFO: fce4b9f5d5dc6085f96d2db950f6b589   805993 
20070220061755.274    FSL2 000  
FSL.CompressedNetCDF.MADIS.metar.20070220_0500.gz
Feb 20 06:31:00 notifyme[85537] INFO: 3fd0bac547037b975e52763433e3215a    62983 
20070220061810.200    FSL2 000  
FSL.CompressedNetCDF.MADIS.maritime.20070220_0500.gz
Feb 20 06:31:00 notifyme[85537] INFO: 9fa7abc6878d4b90f75a43319ef8508b   536647 
20070220061820.157    FSL2 000  
FSL.CompressedNetCDF.MADIS.metar.20070220_0600.gz
Feb 20 06:31:00 notifyme[85537] INFO: 1391db1da89d6e31ffb79bf49121ce5a    17535 
20070220061825.264    FSL2 000  FSL.CompressedNetCDF.MADIS.sao.20070220_0500.gz
Feb 20 06:31:00 notifyme[85537] INFO: 031a946202cda3a10e55b2970152f9fd    23186 
20070220061835.060    FSL2 000  
FSL.CompressedNetCDF.MADIS.maritime.20070220_0600.gz
Feb 20 06:31:00 notifyme[85537] INFO: 0dcb2e401523e7a6a6d7455ed2358ffc   120451 
20070220061840.525    FSL2 000  FSL.CompressedNetCDF.MADIS.coop.20070220_0500.gz
Feb 20 06:31:00 notifyme[85537] INFO: 27cf2ad3bb16184672a1ee662a1fb098    14387 
20070220061850.156    FSL2 000  FSL.CompressedNetCDF.MADIS.sao.20070220_0600.gz
Feb 20 06:31:00 notifyme[85537] INFO: 58f5397cde062fdc3e27e4277edabc53    10526 
20070220061905.489    FSL2 000  FSL.CompressedNetCDF.MADIS.coop.20070220_0600.gz
Feb 20 06:31:00 notifyme[85537] INFO: 7498746f087201b3e86daf31d5bd54af   143527 
20070220061905.547    FSL2 000  FSL.CompressedNetCDF.MADIS.coop.20070220_0400.gz
Feb 20 06:31:00 notifyme[85537] INFO: c8d01ef41923a708c909dba50351e1dd    30241 
20070220061920.839    FSL2 000  
FSL.CompressedNetCDF.MADIS.hydro2.20070220_0600.gz
Feb 20 06:31:00 notifyme[85537] INFO: 6f7ba850b11f9eb272dd3590c8b5c1cc    84088 
20070220062102.617    FSL2 000  
FSL.CompressedNetCDF.MADIS.radiometer.20070220_0500.gz

If you tried using one of the patterns you are specifying in your ldmd.conf 
file,
you would get nothing back from the server.  For instance:

/local/ldm% notifyme -vxl- -f FSL2 -h eldm.fsl.noaa.gov -o 3600 -p 
"^FSL\.CompressedNetCDF\.(metar)"
Feb 20 06:40:37 notifyme[86884] NOTE: Starting Up: eldm.fsl.noaa.gov: 
20070220054037.489 TS_ENDT {{FSL2,  "^FSL\.CompressedNetCDF\.(metar)"}}
Feb 20 06:40:37 notifyme[86884] NOTE: LDM-5 desired product-class: 
20070220054037.489 TS_ENDT {{FSL2,  "^FSL\.CompressedNetCDF\.(metar)"}}
Feb 20 06:40:37 notifyme[86884] INFO: Resolving eldm.fsl.noaa.gov to 
137.75.133.23 took 0.003574 seconds
Feb 20 06:40:37 DEBUG: NOTIFYME(eldm.fsl.noaa.gov) returns OK
Feb 20 06:40:37 notifyme[86884] NOTE: NOTIFYME(eldm.fsl.noaa.gov): OK


Parentheses would be appropriate if you want to combine several of your requests
into a single request line.  For example, your 2nd, 3rd, and 4th requests could
be combined into a single request as follows:

REQUEST FSL2 "^FSL\.CompressedNetCDF\.MADIS\.(metar|sao|snow)" eldm.fsl.noaa.gov

Please let us know the results of the regularization of the 'data' directory
portion of your LDM installation (referred to above).

Cheers,

Tom
****************************************************************************
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: PFX-311376
Department: Support LDM
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.