NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Howdy,I've thoroughly read https://www.unidata.ucar.edu/data/conduit/ldm_idd/gfs_files.html
and find that we (tamu.edu) are receiving gfs004 files but not gfs002 or gfs003 files.
For example:
[ldm@bigbird logs]$ date Thu Jun 20 10:33:16 CDT 2013 [ldm@bigbird logs]$ ls -lth notify* -rw-rw-r-- 1 ldm ldm 5.6M Jun 20 10:32 notifyme-dlc-gfs-2ndtest20130619.txt -rw-rw-r-- 1 ldm ldm 1.1M Jun 19 17:00 notifyme-dlc-gfs-test20130619.txt [ldm@bigbird logs]$ grep "#002" notifyme-dlc-gfs-2ndtest20130619.txt | wc -l 0 [ldm@bigbird logs]$ grep "#003" notifyme-dlc-gfs-2ndtest20130619.txt | wc -l 0 [ldm@bigbird logs]$ grep "#000" notifyme-dlc-gfs-2ndtest20130619.txt | wc -l 24879 [ldm@bigbird logs]$
I see the same results on sasquatch. These relay machines have the same requests, that being:
$ grep -v ^# etc/ldmd.conf | grep -wi request | grep -wi conduit REQUEST CONDUIT "([09]$)" idd.unidata.ucar.edu REQUEST CONDUIT "([18]$)" idd.unidata.ucar.edu REQUEST CONDUIT "([27]$)" idd.unidata.ucar.edu REQUEST CONDUIT "([36]$)" idd.unidata.ucar.edu REQUEST CONDUIT "([45]$)" idd.unidata.ucar.edu REQUEST CONDUIT "([09]$)" weather3.admin.niu.edu REQUEST CONDUIT "([18]$)" weather3.admin.niu.edu REQUEST CONDUIT "([27]$)" weather3.admin.niu.edu REQUEST CONDUIT "([36]$)" weather3.admin.niu.edu REQUEST CONDUIT "([45]$)" weather3.admin.niu.edu $
Can anyone tell me why? I've been at this for two days, so if you want further details, just reply.
Donna -- Donna Cote Senior Research Associate The Academy for Advanced Telecommunications and Learning Technologies Texas A&M University 3139 TAMU College Station, Texas 77843-3139 Office: (979) 862-3982 Fax: (979) 862-3983 http://academy.tamu.edu/
ldm-users
archives: