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.
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.
On Thu, 29 Apr 2010, Peter Laws wrote:
OK, so how come I see this in the logs? This (to me) says the downstream system can't get WMO products ... I get the same errors on the other system (they are twins) that has had all requests to Unidata consolidated into ANY (remember, my pqact is empty).Apr 29 15:18:36 ldmingest01 SomeSystem(feed)[11112] NOTE: feed or notify failure; COMINGSOON: RPC: Unable to receive; errno = Connection reset by peerApr 29 15:18:37 ldmingest01 SomeSystem(feed)[11187] NOTE: Starting Up(6.8.1/6): 20100429141836.229 TS_ENDT {{WMO, ".*"}}, SIG=50a07359f51b152896add720008fc9d4, PrimaryApr 29 15:18:37 ldmingest01 SomeSystem(feed)[11187] NOTE: topo: SomeSystem {{WMO, (.*)}}
I get these all the time. I forget the exact technical reason for why this occurs, but the bottom line is, no worries: you are fine. If you have a backup, I know exactly why: the latency of the feed is pretty much equal across the two servers you are feeding from, and the LDM is bouncing back and forth between them. I've been asking to have that stopped, but that would apparently cause more problems than not.
As they say, "it's all good". ******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** Staff Meteorologist, Northern Illinois University **** E-mail: sebenste@xxxxxxxxxxxxxxxxxxxxx *** web: http://weather.admin.niu.edu ** *******************************************************************************
ldm-users archives: