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.
Ours had to do with TCP and UDP both having to have been forwarded if I recall. Turns out the packets for LDM are TCP, but the firewall firmware had some kind of issue, and the workaround was to forward both. Ray > -----Original Message----- > From: address@hidden > [mailto:address@hidden]On Behalf Of Robert Mullenax > Sent: Sunday, September 12, 2004 10:24 AM > To: 'address@hidden'; address@hidden > Subject: RE: help with serious LDM feed issues > > > Our IT folks have been all through the firewall and can't seem to find any > problems. > However, this was the likely suspect since the firewall is new. Do you have > any > details on what the issue was with your firewall? > > Thanks, > Robert > > > -----Original Message----- > From: address@hidden > [mailto:address@hidden]On Behalf Of Ray Weber > Sent: Sunday, September 12, 2004 9:10 AM > To: address@hidden > Subject: RE: help with serious LDM feed issues > > > We had an odd issue such as this once with a firewall. Might explore that > possibility. > > Ray Weber > MA Skywarn > > > -----Original Message----- > > From: address@hidden > > [mailto:address@hidden]On Behalf Of Robert Mullenax > > Sent: Sunday, September 12, 2004 8:09 AM > > To: 'address@hidden' > > Subject: help with serious LDM feed issues > > > > > > We are getting a CRAFT feed via LDM and another data feed from an external > > source. Starting about 4 days ago, the feed became useless. Even though > > there > > is gobs of bandwidth available even one CRAFT site ends up with latencies > > over 10-15 minutes, whereas it used to be 2-4 seconds. The upstream > > site gets a lot of I/O, can't connect errors while trying to send to our > > machine. > > Not only is latency a problem, but even the files we do get are usually > > incomplete. I am also receiving an LDM feed from a NOAAport SDI ingestor > > and that feed is absolutely fine and bulletproof. > > Our ldmd.log is full of messages like this: > > > > Sep 12 00:04:21 xxxxxxxx xxx.xxx.xxx.xx[25954]: ERROR: requester6.c:206: > > Connection to upstream LDM closed > > > > We also get a lot of these: down6.c:511: Discarding incomplete product > > > > Our IS folks checked the firewall and made sure everything is allowed > > through properly. I am losing hair and turning gray rapidly over this. > > Is this an LDM issue and not a network issue? Anyone have any thoughts? > > I have stopped and restarted the machine and rebuilt the queue a few > times. > > > > I am running ldm-6.0.14 on Solaris 9 x86. This combo has been 100% > > bulletproof > > for us. > > > > Thanks, > > Robert Mullenax > > > > > > > > > > > > >