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.
Hi Harry, Yes, checking stats, volumes for sunny and freshair did indeed match (and showed freshair getting data from idd (via jackie), let's hope this was transitory and a factor brought on by freshair coming back up to speed. We will close this ticket, but will monitor feed. Cheers, Jeff Weber > We are no longer seeing the problem - I checked and the reception on > sunny and freshair, and they match. It only occurred when we were trying > to catch up. I do see the drop and started connections from idd, but > they appear to be starting at your end. What I see here (in PDT time) is: > > Sep 6 10:46:02 freshair2 idd.unidata.ucar.edu[4789] INFO: 116 > 200609061744 > 46.885 IDS|DDPLUS 10638175 SRXX20 KWAL 061743 > Sep 6 10:46:02 freshair2 idd.unidata.ucar.edu[4789] ERROR: Terminating > due to L > DM failure; Connection to upstream LDM closed > Sep 6 10:46:02 freshair2 idd.unidata.ucar.edu[4789] NOTE: LDM-6 desired > product > -class: 20060906174346.885 TS_ENDT {{IDS|DDPLUS, ".*"},{NONE, > "SIG=5920d67038f > 50364c6feeea016e0dcac"}} > Sep 6 10:46:02 freshair2 idd.unidata.ucar.edu[4789] INFO: Resolving > idd.unidata > .ucar.edu to 128.117.140.3 took 0.000108 seconds > Sep 6 10:46:05 freshair2 idd.unidata.ucar.edu[4789] INFO: Connected to > upstream > LDM-6 on host idd.unidata.ucar.edu using port 388 > Sep 6 10:46:05 freshair2 idd.unidata.ucar.edu[4789] NOTE: Upstream > LDM-6 on idd > .unidata.ucar.edu is willing to be a primary feeder > Sep 6 10:46:06 freshair2 idd.unidata.ucar.edu[4789] INFO: 260 > 200609061744 > 48.900 IDS|DDPLUS 10638176 SROH20 KWAL 061743 > > > Unidata IDD Support wrote: > > Hi Harry, > > > > Sorry for the tardy reply. Several of us are out of the office at the > > moment, > > and getting online is not a given. > > > > > >> My main data machine, freshair.atmos.washington.edu went down for a > >> awhile this morning, and its now about 90 minutes behind. However, the > >> IDS|DDPLUS feed is missing data from idd.unidata.ucar.edu as compared to > >> my backup system, sunny89.atmos.washington.edu. I have verbose logging > >> on, and I see no reason why products are not being shipped to freshair > >> from idd. Do you see anything in your log files that would explain this? > >> > > > > I just checked and see some (but not many) problems sending to freshair2: > > > > > > Sep 06 17:44:11 uni1 freshair2.atmos.washington.edu(f[27738] NOTE: topo: > > freshair2.atmos.washington.edu {{IDS|DDPLUS, (.*)}} > > Sep 06 17:45:47 uni1 freshair2.atmos.washington.edu(f[27738] ERROR: > > Couldn't flush connection; nullproc_6() failure to > > freshair2.atmos.washington.edu: RPC: Timed out > > Sep 06 17:46:06 uni1 freshair2.atmos.washington.edu(f[27820] NOTE: Starting > > Up(6.4.5/6): 20060906174446.891 TS_ENDT {{IDS|DDPLUS, ".*"}}, Primary > > Sep 06 17:46:06 uni1 freshair2.atmos.washington.edu(f[27820] NOTE: topo: > > freshair2.atmos.washington.edu {{IDS|DDPLUS, (.*)}} > > Sep 06 17:49:23 uni1 freshair2.atmos.washington.edu(f[27509] ERROR: > > Couldn't flush connection; nullproc_6() failure to > > freshair2.atmos.washington.edu: RPC: Timed out > > Sep 06 17:50:23 uni1 freshair2.atmos.washington.edu(f[27991] NOTE: Starting > > Up(6.4.5/6): 20060906174801.919 TS_ENDT {{DIFAX|FNEXRAD|FSL2, ".*"}}, > > Primary > > Sep 06 17:50:23 uni1 freshair2.atmos.washington.edu(f[27991] NOTE: topo: > > freshair2.atmos.washington.edu {{DIFAX|FNEXRAD|FSL2, (.*)}} > > Sep 06 17:54:25 uni1 freshair2.atmos.washington.edu(f[22034] NOTE: feed or > > notify failure; HEREIS: RPC: Unable to send; errno = Broken pipe > > Sep 06 17:54:51 uni1 freshair2.atmos.washington.edu(f[30496] NOTE: feed or > > notify failure; HEREIS: RPC: Unable to send; errno = Connection timed out > > Sep 06 18:10:29 uni1 freshair2.atmos.washington.edu(f[28794] NOTE: Starting > > Up(6.4.5/6): 20060906175825.716 TS_ENDT {{CONDUIT, "[36]$"}}, Primary > > Sep 06 18:10:29 uni1 freshair2.atmos.washington.edu(f[28794] NOTE: topo: > > freshair2.atmos.washington.edu {{CONDUIT, (.*)}} > > Sep 06 18:25:55 uni1 freshair2.atmos.washington.edu(f[22041] NOTE: feed or > > notify failure; HEREIS: RPC: Unable to send; errno = Connection timed out > > Sep 06 20:56:26 uni1 freshair2.atmos.washington.edu(f[27820] ERROR: > > Couldn't flush connection; nullproc_6() failure to > > freshair2.atmos.washington.edu: RPC: Timed out > > Sep 06 20:56:30 uni1 freshair2.atmos.washington.edu(f[22038] ERROR: > > Couldn't flush connection; nullproc_6() failure to > > freshair2.atmos.washington.edu: RPC: Timed out > > Sep 06 20:56:41 uni1 freshair2.atmos.washington.edu(f[27713] ERROR: > > Couldn't flush connection; nullproc_6() failure to > > freshair2.atmos.washington.edu: RPC: Timed out > > > > I don't know if this is indicating the problem you are seeing or not. > > > > What happens if you switch your IDS|DDPLUS feed to unidata2.ssec.wisc.edu? > > > > Cheers, > > > > Tom > > **************************************************************************** > > Unidata User Support UCAR Unidata Program > > (303) 497-8642 P.O. Box 3000 > > address@hidden Boulder, CO 80307 > > ---------------------------------------------------------------------------- > > Unidata HomePage http://www.unidata.ucar.edu > > **************************************************************************** > > > > > > Ticket Details > > =================== > > Ticket ID: XQD-109619 > > Department: Support IDD > > Priority: Normal > > Status: Closed > > > > Jeff Weber Unidata User Support http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: XQD-109619 Department: Support IDD Priority: Normal Status: Closed