[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #VDD-713716]: data
- Subject: [LDM #VDD-713716]: data
- Date: Thu, 27 Sep 2012 14:47:09 -0600
Hi Pat,
re: contaminated grids
I agree with Steve E's comment:
> The problem is unlikely to be due to the LDM, per-se.
But, I have to throw in my $0.02:
A LONG time ago, we had interactions with a user who reported messed up
products received by the LDM/IDD. The eventual resolution of that
user's problem was:
- stop the LDM
<as 'ldm'>
ldmadmin stop
- shutdown and reboot the machine on which the LDM was running
- delete and remake the LDM queue
<as 'ldm'>
ldmadmin delqueue
ldmadmin mkqueue
- restart the LDM
Please do this and let us know if the problem clears.
One last comment: nobody else is reporting bad/munged grid (GRIB/GRIB2)
messages, so it is highly unlikely that the products are bad from the
source.
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: VDD-713716
Department: Support CONDUIT
Priority: Normal
Status: Closed