[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDD #OMZ-874415]: GOESR ldm feed
- Subject: [IDD #OMZ-874415]: GOESR ldm feed
- Date: Tue, 25 Sep 2018 11:23:20 -0600
Hi Carol,
re:
> It looks like our GOES-R ldm feed stopped about 9 am MDT or 15 UTC this
> morning. Greg checked to make sure ldm was running fine on our
> typhoon.eol.ucar.edu server, and he didn't see files come in through
> the ldmadmin watch.
Hmm...
re:
> Are we pointing to the correct server? idd.unidata.ucar.edu?
Yes.
re:
> Is there a different unidata server that we should be pointing to?
No, but you could also REQUEST the SATELLITE (aka DIFAX) feed from
our backup IDD relay cluster, iddb.unidata.ucar.edu.
We do not see a problem in the SATELLITE feed -- we use this feed
to distribute GOES-16 GRB products (ABI, GLM, etc.) to our top level
servers, and I see current GOES-16 imagery on both of the servers
that are actively feeding.
A random real time stats selection of the real server backends
of both of our relay clusters show continuous data:
iddb.unidata.ucar.edu - cluster0.unidata.ucar.edu
http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?DIFAX+cluster0.unidata.ucar.edu
idd.unidata.ucar.edu - uni14.unidata.ucar.edu
http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?DIFAX+uni14.unidata.ucar.edu
As an end-to-end test, I used McIDAS to list the 10 most recent Channel 13
Full Disk images received by the LDM on two of our data server machines.
These listings were generated at 17:08 UTC today:
<as 'mcidas'>
DATALOC ADD RTGOESR ATM.UCAR.EDU
Group Name Server IP Address
-------------------- ----------------------------------------
RTGOESR ATM.UCAR.EDU
<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done
IMGLIST RTGOESR/FDC13.-10
Image file directory listing for:RTGOESR/FDC13
Pos Satellite/ Date Time Center Band(s)
sensor Lat Lon
--- ------------- ------------ -------- ---- ---- ------------
192 G-16 IMG 25 SEP 18268 16:45:34 0 75 13
191 G-16 IMG 25 SEP 18268 16:30:34 0 75 13
190 G-16 IMG 25 SEP 18268 16:15:34 0 75 13
189 G-16 IMG 25 SEP 18268 16:00:34 0 75 13
188 G-16 IMG 25 SEP 18268 15:45:34 0 75 13
187 G-16 IMG 25 SEP 18268 15:30:34 0 75 13
186 G-16 IMG 25 SEP 18268 15:15:34 0 75 13
185 G-16 IMG 25 SEP 18268 15:00:34 0 75 13
184 G-16 IMG 25 SEP 18268 14:45:34 0 75 13
183 G-16 IMG 25 SEP 18268 14:30:34 0 75 13
182 G-16 IMG 25 SEP 18268 14:15:34 0 75 13
IMGLIST: done
DATALOC ADD RTOGESR LEAD.UNIDATA.UCAR.EDU
Group Name Server IP Address
-------------------- ----------------------------------------
RTOGESR LEAD.UNIDATA.UCAR.EDU
<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done
IMGLIST RTGOESR/FDC13.-10
Image file directory listing for:RTGOESR/FDC13
Pos Satellite/ Date Time Center Band(s)
sensor Lat Lon
--- ------------- ------------ -------- ---- ---- ------------
192 G-16 IMG 25 SEP 18268 16:45:34 0 75 13
191 G-16 IMG 25 SEP 18268 16:30:34 0 75 13
190 G-16 IMG 25 SEP 18268 16:15:34 0 75 13
189 G-16 IMG 25 SEP 18268 16:00:34 0 75 13
188 G-16 IMG 25 SEP 18268 15:45:34 0 75 13
187 G-16 IMG 25 SEP 18268 15:30:34 0 75 13
186 G-16 IMG 25 SEP 18268 15:15:34 0 75 13
185 G-16 IMG 25 SEP 18268 15:00:34 0 75 13
184 G-16 IMG 25 SEP 18268 14:45:34 0 75 13
183 G-16 IMG 25 SEP 18268 14:30:34 0 75 13
182 G-16 IMG 25 SEP 18268 14:15:34 0 75 13
IMGLIST: done
Question:
- what is the output of:
<as 'ldm' on typhoon>
notifyme -vl- -f DIFAX -h idd.unidata.ucadr.edu
notifyme -vl- -f DIFAX -h iddb.unidata.ucar.edu
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: OMZ-874415
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata
inquiry tracking system and then made publicly available through the web. If
you do not want to have your interactions made available in this way, you must
let us know in each email you send to us.