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

Re: data feed problems - ldmd.conf file attached

Steven,

Take the leading TAB character out of in front of your request action.
That should be the problem with that line not being processed by
rpc.ldmd.

Also, you can add the PRIMARY tag at the end of the request line:

request UNIDATA ".*" pluto.met.fsu.edu PRIMARY

The PRIMARY tag will be useful in LDM6 if you were to employ
an ALTERNATE request as per the documentation.


Steve Chiswell



On Mon, 2004-03-22 at 13:44, Steven Lazarus wrote:
> Steve -
>   See attached file. Note we are already receiving data via ldm on a Sun 
> machine
> in my office but we're trying to switch over to a linux box...FSU is the 
> feed on the
> other machine. I sent them an email this morning to make sure they 
> haven't crossed
> ip's on the two machines but haven't heard back....
> Thanks!
> Steven
> 
> Steve Chiswell wrote:
> 
> >Steven,
> >
> >See the message I sent regarding your request actions.
> >
> >You do see the notifyme I made from flip to verify that you weren't
> >seeing data. 
> >
> >I won't be in the office at 8:30AM. Looking at my calenday,
> >you could try around 11AM MST, or after 12:30 PM MST. But,
> >I will have to have your ldmd.conf file first siince it is clear
> >that your LDM isn't issuing any request actions to  your upstream.
> >
> >Steve Chiswell
> >Unidata User Support
> >
> >On Mon, 2004-03-22 at 13:13, Steven Lazarus wrote:
> >  
> >
> >>Steve:
> >>   The ldmd.log shows the following after a ldmadmin stop and 
> >>restart...We'd like to call you
> >>tomorrow and wonder if your available around 8:30 your time (MST)?  Thanks!
> >>Steven
> >>
> >>    
> >>
> >>>Mar 22 19:45:01 cumulus rpc.ldmd[19851]: Starting Up (version: 6.0.14; 
> >>>built: Jan  5 2004 15:52:40)
> >>>Mar 22 19:45:01 cumulus pqact[19854]: Starting Up
> >>>Mar 22 19:45:01 cumulus pqbinstats[19852]: Starting Up (19851)
> >>>Mar 22 19:45:01 cumulus rtstats[19855]: Starting Up (19851)
> >>>Mar 22 20:06:14 cumulus flip(noti)[20016]: Starting Up(6.0.14/5): 
> >>>20040322155826.419 TS_ENDT {{ANY,  ".*"}}
> >>>Mar 22 20:06:14 cumulus flip(noti)[20016]: topo:  
> >>>flip.unidata.ucar.edu ANY
> >>>      
> >>>
> >>
> >>Steve Chiswell wrote:
> >>
> >>    
> >>
> >>>Steven,
> >>>
> >>>Can you check the clock on cumulus and verify that it is correct,
> >>>and provide information on the logs from rpc.ldmd on your machine?
> >>>The logs from FSU show the notifyme connection exiting, but
> >>>no signs of your rpc.ldmd. We need to see your ldmd.log information
> >>>to see what is going on with your ldm.
> >>>
> >>>Also, can you set up cumulus to send rtstats so that we can
> >>>see what is/isn't reaching you.
> >>>
> >>>
> >>>Steve Chiswell
> >>>Unidata User SUpport
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>On Sun, 21 Mar 2004, Steven Lazarus wrote:
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>>>Hi,
> >>>> Can anyone assist with this problem? I'm sure others have seen this. We
> >>>>are trying to get ldm running on a linux box here at Florida Tech but are
> >>>>have problems grabbing the data for some reason. We seem to able to see
> >>>>the feed from FSU...but can't seem to grab it!
> >>>>
> >>>>Thanks ahead of time for any help on this one!
> >>>>
> >>>>Steven
> >>>>
> >>>>Dr. Steven M. Lazarus
> >>>>Florida Institute of Technology
> >>>>Department of Marine and Environmental Systems
> >>>>
> >>>>************************************************************
> >>>>
> >>>>Note that the following gives results:
> >>>>
> >>>>[ldm@cumulus ~/bin]$ ./notifyme -vl - -h pluto.met.fsu.edu
> >>>>Mar 21 16:00:56 notifyme[14454]: Starting Up: pluto.met.fsu.edu:
> >>>>20040321160056.730 TS_ENDT {{ANY,  ".*"}}
> >>>>Mar 21 16:00:56 notifyme[14454]: Connected to upstream LDM-5
> >>>>Mar 21 16:00:56 notifyme[14454]: NOTIFYME(pluto.met.fsu.edu): reclass:
> >>>>20040321160056.730 TS_ENDT {{FSL2|UNIDATA,  ".*"}}
> >>>>Mar 21 16:00:56 notifyme[14454]: NOTIFYME(pluto.met.fsu.edu): OK
> >>>>Mar 21 16:00:56 notifyme[14454]:     3282 20040321160056.737     HDS
> >>>>71367571  HRKB99 KWBC 211200 /mAVN
> >>>>!grib/ncep/AVN/#039/200403211200/F006/RH/1000 mb/
> >>>>Mar 21 16:00:56 notifyme[14454]:     3282 20040321160056.754     HDS
> >>>>71367572  HRJB99 KWBC 211200 /mAVN
> >>>>!grib/ncep/AVN/#038/200403211200/F006/RH/1000 mb/
> >>>>Mar 21 16:00:56 notifyme[14454]:     3282 20040321160056.770     HDS
> >>>>71367573  HRLB99 KWBC 211200 /mAVN
> >>>>!grib/ncep/AVN/#040/200403211200/F006/RH/1000 mb/
> >>>>
> >>>>
> >>>>Below are comments from FSU:
> >>>>
> >>>>
> >>>>Subject: Re: data feed problems
> >>>>Date: Fri, 19 Mar 2004 14:19:01 -0500
> >>>>From: Bret Whissel
> >>>>To: Steven Lazarus
> >>>>References: <address@hidden>
> >>>><address@hidden> <address@hidden>
> >>>>
> >>>>
> >>>>
> >>>>Steven,
> >>>>
> >>>>Below is a trace of the ldmd.log file pertaining to cumulus.  I don't
> >>>>know what would cause a 'pq_sequence failed: errno=5', but it's just a
> >>>>generic I/O error.  I'm not sure what the "Unable to receive" error
> >>>>means.  Is your queue file writable?  Is the disk partition mounted r/w?
> >>>>
> >>>>Bret
> >>>>
> >>>>Mar 19 14:06:58 pluto cumulus(noti)[13998]: Starting Up(6.0.14/5):
> >>>>20040319140541.299 TS_ENDT {{FSL2|UNIDATA,  ".*"}}
> >>>>Mar 19 14:06:58 pluto cumulus(noti)[13998]: topo:  cumulus.dmes.fit.edu
> >>>>FSL2|UNIDATA
> >>>>Mar 19 14:07:03 pluto cumulus(noti)[13998]: YVNA50 KWBE 191200 /mETA_84
> >>>>!grib/ncep/ETA_84/#207/200403191200/F000/VGRD/500 mb/ : RPC: Unable to
> >>>>receive
> >>>>Mar 19 14:07:03 pluto cumulus(noti)[13998]: pq_sequence failed:
> >>>>Input/output error (errno = 5)
> >>>>Mar 19 14:35:38 pluto cumulus(noti)[14018]: Starting Up(6.0.14/5):
> >>>>20040319143421.143 TS_ENDT {{FSL2|UNIDATA,  ".*"}}
> >>>>Mar 19 14:35:38 pluto cumulus(noti)[14018]: topo:  cumulus.dmes.fit.edu
> >>>>FSL2|UNIDATA
> >>>>Mar 19 14:36:02 pluto cumulus(noti)[14018]: SXUS67 KWOH 191431 /pRRSVEF:
> >>>>RPC: Unable to receive
> >>>>Mar 19 14:36:02 pluto cumulus(noti)[14018]: pq_sequence failed:
> >>>>Input/output error (errno = 5)
> >>>>Mar 19 14:44:44 pluto cumulus(noti)[14026]: Starting Up(6.0.14/5):
> >>>>20040319144327.242 TS_ENDT {{FSL2|UNIDATA,  ".*"}}
> >>>>Mar 19 14:44:44 pluto cumulus(noti)[14026]: topo:  cumulus.dmes.fit.edu
> >>>>FSL2|UNIDATA
> >>>>Mar 19 14:44:45 pluto cumulus(noti)[14026]: SDUS81 KLWX 191440 /pDPALWX:
> >>>>RPC: Unable to receive
> >>>>Mar 19 14:44:45 pluto cumulus(noti)[14026]: pq_sequence failed:
> >>>>Input/output error (errno = 5)
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>> 
> >>>
> >>>      
> >>>
> >
> >  
> >
> 
> 
> ______________________________________________________________________
> 
> #####
> # $Id: ldmd.conf,v 1.18 2003/02/27 17:12:57 steve 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 except noted
> # allow line entry below, try again.
> #
> ###############################################################################
> # WARNING: Pathological Product-ID Patterns
> ###############################################################################
> #
> # The REQUEST and ACCEPT entries both have product-ID patterns that are 
> regular
> # expressions (RE-s).  It is EXTREMELY IMPORTANT that these patterns not have 
> a
> # ".*" prefix because: 1) such a prefix accomplishes nothing (i.e., the set of
> # possible matches is unaltered by the prefix); and 2) such a prefix causes 
> the 
> # RE to take MUCH, MUCH LONGER TO EXECUTE (by 3 orders of magnitude in many
> # cases).  Therefore, DO NOT USE RE-s like
> #
> #     ".*UFPBA"
> #
> # Instead, simply use
> #
> #     "UFPBA"
> #
> # The regex(1) utility of this package can be used to examine the efficiency
> # of an RE.
> #
> ###############################################################################
> # 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.
> #
> # Regarding pqbinstats, while pqbinstats will generate .stats files in
> # your logs directory, it is necessary to also run 'ldmadmin dostats'
> # once per hour via cron in order to email the stats to the UPC and
> # remove the .stats files that are no longer needed.  See
> # http://www.unidata.ucar.edu/packages/ldm/ldmConfigInstallList.html#s7
> # for more information.
> exec  "pqbinstats"
> exec  "pqact"
> #
> # rtstats uses the LDM to send product latency statistics to the UPC.
> # We are currently evolving from pqbinstats to rtstats, but in the
> # mean time we hope sites will run both.  For more info on rtstats
> # please see the man page.
> #exec "rtstats -h rtstats.unidata.ucar.edu"
> #exec "pqsurf"
> #
> ###############################################################################
> # Request Entries
> ###############################################################################
> #
> # LDM5 servers request data from Data Sources
> #
> #     request <feedset> <pattern> <hostname pattern>
> #
> #request WMO ".*" uni0.unidata.ucar.edu
>       request UNIDATA ".*" pluto.met.fsu.edu
> #     request UNIDATA ".*" ldmarchive.agron.iastate.edu
> #     request UNIDATA ".*" 128.186.98.4
> #     request WMO ".*" pluto.met.fsu.edu
> #        request NMC3 ".*" your.floater.feed
> #
> ###############################################################################
> # 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
> #
> # Under no circumstances comment out the next allow entry to localhost
> # The LDM will NOT start if the lines are commented out.
> allow ANY
>     
> ^((localhost|loopback)|(127\.0\.0\.1\.?$)|([a-z].*\.unidata\.ucar\.edu\.?$))
> #
> ###############################################################################
> # 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
> #     accept UNIDATA ".*" pluto.met.fsu.edu
> #
> # WSI is using ldm4 protocol so the accept is still required
> #accept       WSI
> #    .*
> #    ^[a-z].*\.uni\.wsicorp\.com$
> #
> ###############################################################################
> # End 
> ###############################################################################