20020326: NMC2 feed

Mark,


There seems to be a confusion with your machine name
"ingest.joss.ucar.edu" and "torrent-fddi.joss.ucar.edu".
You are showing up as the ip alias "ingest" on motherlode. 
The allow lines on motherlode are:

*.joss.ucar.edu NMC2
torrent-fddi.jos.ucar.edu UNIDATA|FNEXRAD|FSL2

when ingest connects, it only matches the NMC2, and not the other
feeds, so you are getting the reclass message to just NMC2 from
your request of FSL2|WMO and NMC2.

You should be able to get the NMC2, but are reclassing on the other 
part of the request. I will change the allow line to expect 
both torrent-fddi as well as ingest for all data.

The preference would be to get NMC2 from thelma anyhow, but some
messages being sent out about idd up/down are confusing the issue.

Steve Chiswell
Unidata User Support




>From: Mark Bradford <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200203261948.g2QJmRa20624

>Hello!
>
>Janine Goldstein of our office has forwarded me several messages suggesting
>that motherlode.ucar.edu be used for the IDD feed, until the final thelma
>replacement is available.  However, if we do so, we get repeated messages
>of this sort in our ldmd.log:
>
>Mar 18 20:55:23 torrent motherlode[22759]: run_requester: 20020318202346.514 T
> S_
>ENDT {{FSL2|WMO,  ".*"},{NMC2,  "MT.eta.*awipak"}}
>Mar 18 20:55:23 torrent motherlode[22759]: FEEDME(motherlode.ucar.edu): reclas
> s:
> 20020318202346.514 TS_ENDT {{NMC2,  "MT.eta.*awipak"}
>Mar 18 20:55:23 torrent motherlode[22759]: FEEDME(motherlode.ucar.edu): OK
>Mar 18 20:55:23 torrent motherlode[22759]: RECLASS: 20020318195523.912 TS_ENDT
>  {
>{NMC2,  "MT.eta.*awipak"}}
>
>And, more to the point, we don't get our NMC2 data.  Switching back to
>thelma today, the data has begun to flow once more.
>
>What *should* work?
>
>Thanks!
>
>-- 
>Mark Bradford, Systems Administrator  <> address@hidden
>UCAR Joint Office for Science Support <> (303) 497-8169
>