Re: 19991101: New LDM Installation

On Mon, 1 Nov 1999, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >From: address@hidden
> >Subject: New LDM Installation
> >Organization: NOAA/NCDC
> >Keywords: 199911012102.OAA15776
> 
> 
> 
> I have a new LDM installation and I am having trouble getting the data
> where I want it.  When I issue ldmadmin watch, I can see lots and lots of
> files streaming by and the date last modified of the ldm.pq is constantly
> updating, so I know entried are being put into the ldm.pq.  BUT!!  I never
> get the files created based on the pqact.conf file.  I have only one entry
> in the file:
> 
> WMO  ^(......) (....) ([0-3][0-9])([0-2][0-9])     FILE
> /npraid/noaaport/data/\1\2\3\4.wmo
> 
> If I understand this entry correctly, based on a WMO header of:
> SAUS80 KWBC 041400
> should be filed under:
> /npraid/noaaport/data/SAUS80KWBC0414.wmo
> 
Alan,

That's correct product construction SAUS80KWBC0414.wmo.  

Something to check is that the ldm has write
permission on dir /npraid/noaaport/data/   Also, if this was a binary
installation and LDMHOME is not /usr/local/ldm, then a link needs to be
made /usr/local/ldm.  Detail instructions at:

http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html#s8


> There are tabs between fields and the ldmadmin pqcheck says the file is
> syntactically correct.
> 
> 
> I'm also having a syslog problem that might be related.  When I issue
> ldmadmin newlog I get:
> 
> hupsyslog: kill -HUP 202: Permission Denied


This is because hupsyslog is not suid root. Instruction at:

http://www.unidata.ucar.edu/packages/ldm/ldmBinaryInstallList.html#s7

> 
> No logs are ever created anywhere that I can find.
> 

Start the ldm from the command line, ie

%  bin/rpc.ldmd -vl - -q data/ldm.pq etc/ldmd.conf

Look at the log messages on the screen.

Robb...




> Any advice would be greatly appreciated,
> Alan.
> 
> PS: I am attaching the ldmd.conf and pqact.conf files.
> 
> #####
> # $Id: ldmd.conf,v 1.11 1999/08/05 16:18:09 rkambic Exp $
> # Sample ldmd.conf for ldm5
> ####
> #
> # This is the main configuration file for the LDM server. All lines that
> start
> # with a "#" sign are comments.
> #
> # To debug an LDM that hangs on start up, run the following from LDM home:
> # % bin/rpc.ldmd -vl - -q data/ldm.pq etc/ldmd.conf
> #
> # If the LDM still hangs, comment out all lines in this file, try again.
> #
> ###########################################################################
> ####
> # Exec Entries
> ###########################################################################
> ####
> #
> # Programs that can share a queue with rpc.ldmd server, these programs
> # are started by the "exec" command and are in the same process group.
> #
> exec "pqexpire"
> exec "pqbinstats"
> exec "pqact"
> #exec     "pqsurf"
> #
> ###########################################################################
> ####
> # Request Entries
> ###########################################################################
> ####
> #
> # LDM5 servers request data from Data Sources
> #
> #    request   <feedset> <pattern> <hostname pattern>
> #
> #request WMO ".*" uni0.unidata.ucar.edu
> #
> ###########################################################################
> ####
> # Allow Entries
> ###########################################################################
> ####
> #
> # Giving permission for a Data Sink to perform a request to your LDM
> #
> # allow   <feedset> <hostname pattern>
> #
> # Giving permission to your own machine and Unidata
> #allow    ANY
> ((localhost|loopback)|(127\.0\.0\.1\.?$)|([a-z].*\.unidata\.ucar\.edu\.?$))
> allow     ANY  ((localhost|loopback)|(127\.0\.0\.1\.?$))
> #
> ###########################################################################
> ####
> # Accept Entries
> ###########################################################################
> ####
> # ACCEPT: Who can feed us, currently this action is ONLY needed for WSI
> data
> #
> # accept <feedset> <pattern> <hostname pattern>
> #
> # accept anything from yourself
> #
> accept    ANY  ".*" ^((localhost|loopback)|(127\.0\.0\.1\.?$))
> #
> # accept from your upstream site
> #
> # WSI is using ldm4 protocol so the accept is still required
> #accept   WSI
> #    .*
> #    ^[a-z].*\.uni\.wsicorp\.com$
> #
> ###########################################################################
> ####
> # End
> ###########################################################################
> ####
> 
> 
> ####
> # $Id: pqact.conf,v 1.10 1999/07/28 15:34:54 rkambic Exp $
> #
> # This is an example pqact.conf file,
> # with some example entries commented out.
> #
> # The entries in this file control the local disposition
> # of data. There is a whole chapter in the LDM Site Manager's
> # Guide devoted to this file. We suggest you read and understand that
> material.
> # http://www.unidata.ucar.edu/packages/ldm/ldm5/LDM5-44.html#HEADING44-0
> #
> # The various display and analysis packages have various
> # conventions on how they want data handled. When you
> # install a package such as GEMPAK, you should find with that package
> # collection of entries to add to this file.
> #
> # Example entries for GEMPAK can be found at
> #  http://www.unidata.ucar.edu/packages/gempak/GEMPAK5.4/configuration.html
> # Example entries for LDM-McIDAS may be found at
> #  http://www.unidata.ucar.edu/packages/mcidas/mcidd/ldm-mcidas-pqact.conf
> # and annotated entries for McIDAS-XCD are found at
> #  http://www.unidata.ucar.edu/packages/mcidas/mcx/xcd_start.html
> #
> ##
> # Format is
> # feedtype tab pattern tab action [tab action_args]
> # where tab is \t or \n\t.
> #
> # Actions are
> #
> #    NOOP
> #         Do nothing
> #
> #    FILE [-overwrite|-flush|-close|-strip] filename
> #         write(2) to unix file (flush calls fsync(2))
> #
> #    STDIOFILE [-overwrite|-flush|-close|-strip] filename
> #         fwrite(3) (buffered io) to file (flush calls fflush(3))
> #
> #    DBFILE    dbfilename [dbkey]
> #         Put to gdbmfile.
> #
> #    PIPE [-close|-strip] commandname [args]
> #         Put data on stdin of a subprocess specified by
> #              commandname [args].
> #         Uses the execvp library call, so if commandname is not fully
> #         qualified, the PATH environment variable will be used.
> #
> #    EXEC [-wait] commandname [args ...]
> #         Run a program. No io channel between this process and it.
> #         Like PIPE above, uses execvp.
> #
> # The '-strip' option to FILE, STDIOFILE, & PIPE removes control characters
> # (other than the '\n') from the data before output. This is useful for
> # cleaning up WMO format text bulletins (like the ldm3  STRIP psuedo
> action).
> #
> # To check the syntax of the pqact.conf file, execute pqact with the
> product
> # queue specified as /dev/null:
> #
> #    pqact -vxl- -q /dev/null pqact.conf
> #
> #              or
> #    ldmadmim pqactcheck
> #
> # To send an HUP signal to pqact
> #
> #    ldmadmin pqactHUP
> #    ldmadmin tail     (used to check if HUP took, looking for ReRead msg)
> ###
> ####
> # Bin all the (Non-GRIB) WMO format data, using elements from the
> # identifier as path components. The minutes portion of the timestamp,
> # and the retransmit code is ignored. The day of the month portion
> # of the timestamp is not used as a path component, so it would be
> # a good idea to run 'scour' on a less than 24 hour basis.
> #
> #  "ASUS42 KRDU 012259" gets filed as
> #  data/US/KRDU/22/AS42.wmo
> #
> WMO  ^(..)(..)(..) (....) ([0-3][0-9])([0-2][0-9])      FILE
> /npraid/noaaport/data/\2\4\6\4_\5\6.wmo
> ##
> 
> 
> 
> 
>         National Climatic Data Center
> 
> 
> ------- End of Forwarded Message
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================