[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020725: please allow Valparaiso to feed from you (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20020725: please allow Valparaiso to feed from you (cont.)
  • Date: Thu, 25 Jul 2002 13:31:15 -0600
>From: "Arthur A. Person" <address@hidden>
>Organization: PSU
>Keywords: 200207191908.g6JJ8H908347 data feeds

Art,

>On Thu, 25 Jul 2002, Unidata Support wrote:
>> >>
>> >> LDM machine: aeolus.valpo.edu
>> >> IP:          152.228.34.180
>> >> feed types:  UNIDATA|DIFAX|FSL2|NNEXRAD|FNEXRAD
>> >
>> >Okay, I added an entry.  I already have an entry for weather.valpo.edu...
>>
>> Evidently, the allow you have for Valparaiso is limited to NNEXRAD:
>>
>> -- from aeolus.valpo.edu --
>>
>> [ 8 ] > notifyme -vxl- -f ANY -h ldm.meteo.psu.edu
>> Jul 25 18:32:27 notifyme[25981]: Starting Up: ldm.meteo.psu.edu: 20020725183
> 227.720 TS_ENDT {{ANY,  ".*"}}
>>         NOTIFYME(ldm.meteo.psu.edu) returns RECLASS
>> Jul 25 18:32:27 notifyme[25981]: NOTIFYME(ldm.meteo.psu.edu): reclass: 20020
> 725183227.720 TS_ENDT {{NNEXRAD,  ".*"}}
>>
>> The notifyme request for ANY gets RECLASSed into NNEXRAD.  Is the allow
>> in your ldmd.conf file the same for weather.valpo.edu as for
>> aeolus.valpo.edu?  Does it include all the feeds listed above?
>
>When you ran the test, there was an old entry for "weather" which was for
>FSL2|UNIDATA-SPARE.  The entry for aeolus was as specified in the email.

Hmm...  I just reran the notifyme from aeolus.valpo.edu and got the exact
same RECLASS:

notifyme -vxl- -f ANY -h ldm.meteo.psu.edu
Jul 25 19:20:19 notifyme[27212]: Starting Up: ldm.meteo.psu.edu: 
20020725192019.124 TS_ENDT {{ANY,  ".*"}}
        NOTIFYME(ldm.meteo.psu.edu) returns RECLASS
Jul 25 19:20:19 notifyme[27212]: NOTIFYME(ldm.meteo.psu.edu): reclass: 
20020725192019.124 TS_ENDT {{NNEXRAD,  ".*"}}
        NOTIFYME(ldm.meteo.psu.edu) returns OK
Jul 25 19:20:19 notifyme[27212]: NOTIFYME(ldm.meteo.psu.edu): OK
^CJul 25 19:20:26 notifyme[27212]: Interrupt
Jul 25 19:20:26 notifyme[27212]: exiting


What may be happening is the following:

ldm.meteo.psu.edu may have an allow line for NNEXRAD for *.edu.  If the
new allow entry for aeolus.valpo.edu was put after this allow, then
notifyme requests will get reclassed since the first allow was for
NNEXRAD.  If this is true, it would mean that a feedme should also get
reclassed to only NNEXRAD.  If this assumption is true, you would have
to move the allow for the UNIDATA|FSL2|... above the allow for
NNEXRAD.

Could you check this on ldm.meteo.psu.edu and let me know?

Tom