[IDD #HBC-113243]: FNEXRAD not coming in

Hi Jennifer,
> 
> On Jan 15, 2014, at 11:07 AM, Unidata IDD Support wrote:
> 
> > Hi Jennifer,
> >
> >> Dear Experts,
> >> I have the following entries in my ldmd.conf file:
> >
> > Experts?...well, i will attempt to get you back up and going :)
> Hi, Jeff --
> I use the title 'Expert' with all due respect, I mean no sarcasm in any way. 
> I'm grateful for LDM support.

We appreciate humor :)

Looks like it might be on our end, we were making some mods to our product 
generation process that may have mucked things up.

More soon, wanted to let you know we are on it.


> 
> >
> > The product is still being generated and is current, i suspect we have a 
> > bad cluster node.
> >
> > Have you done an:
> >
> > ldmadmin restart  (as ldm at prompt)
> >
> > on your system? This would remake queue and hopefully get you off the bad 
> > cluster node, if that is in fact the issue.
> >
> > An "ldmadmin restart" will do no damage, and may clear things up. Let's try 
> > that first if it has not been done already.
> 
> I did an 'ldmadmin stop; ldmadmin clean; ldmadmin start' and that didn't 
> change anything. I also just now did an 'ldmadmin restart', which i presume 
> is a shorthand for stop/clean/start, and no change. The DDS data is coming 
> in, so I know my LDM is working. I am also not getting any logging on my 
> cola.gmu.edu server, although I have this in my $LDMHOME/etc/ldmadmin-pl.conf:
> 
> $numlogs = "7";
> $log_path = "$ldmhome/logs";
> $log_file = "$log_path/ldmd.log";
> $log_rotate = "1";
> 
> The file $LDMHOME/logs/ldmd.log is there but has 0 bytes.
> --Jennifer
> 
> 
> >
> >
> >>
> >> REQUEST FNEXRAD "^radar_mosaic" idd.meteo.psu.edu
> >> REQUEST FNEXRAD "^radar_mosaic" idd.unidata.ucar.edu
> >>
> >> But the data have not been coming in lately. The most recent files are:
> >>
> >> -rw-r--r-- 1 ldm cola 2589626 Jan 13 16:08 1401132108.mosaic
> >> -rw-r--r-- 1 ldm cola 2595007 Jan 13 16:04 1401132104.mosaic
> >> -rw-r--r-- 1 ldm cola 2586757 Jan 13 16:00 1401132100.mosaic
> >>
> >> This is the case for both of our LDM servers (cola.gmu.edu and
> >> wx.gmu.edu).
> >> In the log file on wx.gmu.edu, the most recent appearance of the string
> >> "FNEXRAD"  and the two subsequent entries are:
> >>
> >> Jan 14 10:28:45 wx idd.unidata.ucar.edu[13707] NOTE: LDM-6 desired
> >> product-class: 20140114092845.178 TS_ENDT {{FNEXRAD,  
> >> "^radar_mosaic"},{NONE,  "SIG=17bda373805794fb53eaaea4386e916f"}}
> >>
> >> Jan 14 10:28:45 wx idd.unidata.ucar.edu[13707] NOTE: Upstream LDM-6 on
> >> idd.unidata.ucar.edu is willing to be a primary feeder
> >>
> >> Jan 14 10:28:47 wx idd.unidata.ucar.edu[13705] ERROR: Disconnecting due
> >> to LDM failure; Upstream LDM died
> >>
> >> Can you help me get this data steam back on track?
> >> --Jennifer
> >
> >
> > Please let us know the impact of the ldmadmin restart,
> >
> >
> > Cheers,
> >
> >
> > Jeff
Cheers, 


Jeff
> 

Jeff Weber
Unidata User Support
http://www.unidata.ucar.edu

Ticket Details
===================
Ticket ID: HBC-113243
Department: Support IDD
Priority: Normal
Status: Open