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

Re: Sunset problems (fwd)

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: Re: Sunset problems (fwd)
  • Date: Tue, 5 Sep 2000 10:17:04 -0600 (MDT)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Sat, 02 Sep 2000 12:23:09 -0500
From: Pete Pokrandt <address@hidden>
To: Jim Koermer <address@hidden>
Subject: Re: Sunset problems 


In a previous message to me, you wrote: 

 >Pete,
 >
 >Is this why I haven't received and McIDAS AREA file satellite images,
 >since ~02/04Z?
 >
 >                      Jim
 >--
 >James P. Koermer             E-Mail: address@hidden
 >Professor of Meteorology     Office Phone: (603)535-2574
 >Natural Science Department   Office Fax: (603)535-2723
 >Plymouth State College       WWW: http://vortex.plymouth.edu/
 >Plymouth, NH 03264
 >

Jim,

Possibly. I did actually drive in last night to once again
reboot sunset, about 06:30 UTC, and built ldm 5.1.2, which
has been running since then. I've been getting data including
the MCIDAS area files since then, but I do see a lot of
failed connect attempts from these two machines.. is one of
these yours?


Sep 02 15:31:02 5Q:sunset vortex[10053]: Connection from 
vortex.weather.brockport.edu
Sep 02 15:31:02 5Q:sunset vortex[10053]: Connection reset by peer
Sep 02 15:31:02 5Q:sunset vortex[10053]: Exiting
Sep 02 15:40:11 5Q:sunset cirrus[10248]: Connection from cirrus.geo.msu.edu
Sep 02 15:40:11 5Q:sunset cirrus[10248]: Connection reset by peer
Sep 02 15:40:11 5Q:sunset cirrus[10248]: Exiting
Sep 02 15:51:03 5Q:sunset vortex[10329]: Connection from 
vortex.weather.brockport.edu
Sep 02 15:51:03 5Q:sunset vortex[10329]: Connection reset by peer
Sep 02 15:51:03 5Q:sunset vortex[10329]: Exiting
Sep 02 16:00:10 5Q:sunset cirrus[10315]: Connection from cirrus.geo.msu.edu
Sep 02 16:00:10 5Q:sunset cirrus[10315]: Connection reset by peer
Sep 02 16:00:10 5Q:sunset cirrus[10315]: Exiting
Sep 02 16:11:03 5Q:sunset vortex[10452]: Connection from 
vortex.weather.brockport.edu
Sep 02 16:11:03 5Q:sunset vortex[10452]: Connection reset by peer
Sep 02 16:11:03 5Q:sunset vortex[10452]: Exiting
Sep 02 16:20:10 5Q:sunset cirrus[10460]: Connection from cirrus.geo.msu.edu
Sep 02 16:20:11 5Q:sunset cirrus[10460]: Connection reset by peer
Sep 02 16:20:11 5Q:sunset cirrus[10460]: Exiting

I don't know if this is something relating to the ldm upgrade
or not.  Has anyone else had problems feeding downstream sites
after upgrading to 5.1.2?  I've got several other ldm 5.0.xx machines
feeding from sunset here locally with no problems.

What do the logs look like on your end?

--
+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
^ Systems Programmer               V Madison,         WI     53706    ^
^                                  V      address@hidden       ^
^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+