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

Re: [Fwd: Re: [Fwd: 20030321: data feed problems]]

Steven,

The ldmd.log information you have below does not show any instances of
a request being created to ask for data from your upstream (Pluto).

You have 1 "Starting up" message for the lead rpc.ldmd process.
You should then have 1 "Starting Up" message for each of the request
lines in your ldmd.conf file. Each will show the name of the host and 
feedtype/pattern they are requesting.

You need to examine your ldmd.conf file and verify the "request" 
lines you are using and/or add the expected request to
pluto.

If you cannot find anything wrong with your ldmd.conf file,
please send the contents to address@hidden.

Steve Chiswell
Unidata User Support

On Mon, 2004-03-22 at 07:10, Steven Lazarus wrote:
> Steve - 
>   here are some diagnostics....
> Steven 
> 
> * The time on cumulus is very close to chinook, but about 2 minutes
> than another machine I checked.
> 
> chinook% date
> Mon Mar 22 08:48:53 EST 2004
> [ldm@cumulus ~/etc]$ date
> Mon Mar 22 08:48:48 EST 2004
> 
> 
> * I put the following line back into ldmd.conf:
> exec    "rtstats -h rtstats.unidata.ucar.edu"
> 
> After stopping and starting ldm:
> 
> [ldm@cumulus ~/logs]$ more ldmd.log
> Mar 22 13:51:24 cumulus rpc.ldmd[18319]: Starting Up (version: 6.0.14; 
> built: Jan  5 2004 15:52:40)
> Mar 22 13:51:24 cumulus pqbinstats[18321]: Starting Up (18319)
> Mar 22 13:51:24 cumulus pqact[18322]: Starting Up
> Mar 22 13:51:24 cumulus rtstats[18323]: Starting Up (18319)
> 
> * The following message was given when tyring send stats to unidata
> 
> ./ldmadmin dostats
> ls: *.stats: No such file or directory
> 
> Mike
> 
> 
> 
> >
> >
> > -------- Original Message --------
> > Subject: 20030321: data feed problems
> > Date: Sun, 21 Mar 2004 17:26:47 -0700 (MST)
> > From: Steve Chiswell 
> > Organization: UCAR/Unidata
> > To: Steven Lazarus 
> > CC: address@hidden, address@hidden
> > References: <address@hidden>
> >
> >
> >
> > 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)
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> 
> 
>