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

Re: weather ldm



Hi,
     We are still seeing these, what appear to be, extranous
connect attempts from weather.cod.edu. I'm cc'ing Paul Sirvatka since he is
listed as the cod contact point.

It appears to me that there might be a problem with the ldm
on weather.cod.edu. I think this might also be causing
problems with our automated failover script since it
results in starting several ldmd processes that are
not acutually being used. Of course I could be completely
wrong...

Can somebody please check the ldm server on weather.cod.edu
and let us know if you are actually getting data from
redwood. Our entry in the ldmd.conf file indicates
we set this allow up as a temporary feed for Dana presumably
to fill some emergency need. Is it being used?
Is it required? If you are not actually feeding data
from redwood.atmos.albany.edu can you please turn
off your requests?

Hopefully somebody will reply to this request. If not
we might just comment out the allow to prevent the spurious
connect requests.

Thanks
David

David Knight
Department of Earth and Atmospheric Sciences   Tel: (518)-442-4204
SUNY Albany   ES-228                           Fax: (518)-442-4494
Albany, NY  12222                              Email: address@hidden

> Hi Dana,
>      There seems to be recuring problems with weather.cod.edu.
> We've been getting messages like the following in our logs
> for some time, but, today it seems to be worse than ever.
> 
> Are you even receiving any data from redwood.atmos.albany.edu?
> 
> David,
> every five minutes we get a rash of connect attempts like:
> 
> Apr 05 09:50:20 redwood weather[2060]: Connection from weather.cod.edu
> Apr 05 09:50:21 redwood weather[2060]: Connection reset by peer
> Apr 05 09:50:21 redwood weather[2060]: Exiting
> Apr 05 09:50:21 redwood weather[2061]: Connection from weather.cod.edu
> Apr 05 09:50:21 redwood weather[2061]: Connection reset by peer
> Apr 05 09:50:21 redwood weather[2061]: Exiting
> Apr 05 09:50:21 redwood weather[2062]: Connection from weather.cod.edu
> Apr 05 09:50:21 redwood weather[2062]: Connection reset by peer
> Apr 05 09:50:21 redwood weather[2062]: Exiting
> Apr 05 09:50:21 redwood weather[2063]: Connection from weather.cod.edu
> Apr 05 09:50:21 redwood weather[2063]: Connection reset by peer
> Apr 05 09:50:21 redwood weather[2063]: Exiting
> Apr 05 09:50:21 redwood weather[2064]: Connection from weather.cod.edu
> Apr 05 09:50:21 redwood weather[2064]: Connection reset by peer
> Apr 05 09:50:21 redwood weather[2064]: Exiting
> Apr 05 09:50:21 redwood weather[2065]: Connection from weather.cod.edu
> Apr 05 09:50:21 redwood weather[2065]: Connection reset by peer
> Apr 05 09:50:21 redwood weather[2065]: Exiting
> Apr 05 09:50:21 redwood weather[2066]: Connection from weather.cod.edu
> Apr 05 09:50:22 redwood weather[2066]: Connection reset by peer
> Apr 05 09:50:22 redwood weather[2066]: Exiting
> Apr 05 09:50:22 redwood weather[2067]: Connection from weather.cod.edu
> Apr 05 09:50:22 redwood weather[2067]: Connection reset by peer
> Apr 05 09:50:22 redwood weather[2067]: Exiting
> Apr 05 09:50:22 redwood weather[2068]: Connection from weather.cod.edu
> Apr 05 09:50:22 redwood weather[2068]: Connection reset by peer
> Apr 05 09:50:22 redwood weather[2068]: Exiting
> Apr 05 09:50:22 redwood weather[2069]: Connection from weather.cod.edu
> Apr 05 09:50:22 redwood weather[2069]: Connection reset by peer
> Apr 05 09:50:22 redwood weather[2069]: Exiting


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.