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.
Tom, I already had restarted and rebuilt my queue and that didn't help. Changing the request from thelma to the idd server seems to have done the trick. I am getting CONDUIT data again. Its weird that the other data types were unaffected though. Oh well, it works now. Thanks! Dave -----Original Message----- From: Unidata IDD Support [mailto:address@hidden] Sent: Monday, January 16, 2006 4:05 PM To: David Fitzgerald Cc: address@hidden Subject: [IDD #SKM-230294]: ldm CONDUIT feed missing Hi Dave, First, we are testing out a new inquiry tracking (helpdesk) system. Please remember to include the ticket ID in the Subject: line of all future emails related to this inquiry. Thanks! > I have not been receiving the CONDUIT feed since the fourteenth. > Normally I pull from Thelma, and my logs indicate that CONDUIT requests > have been sent to Thelma and there are no errors regarding this feedthat > I can see. A notifyme shows Thelma is receiving the data, but I simply > am not getting it here. First, the fact that a 'notifyme' run from your end that shows that your upstream is receiving data that you want indicates that you are allowed to request the data. Please check your ~ldm/logs/ldmd.log file to see if there are any comments about your feed request. Second, please change your request(s) from thelma.ucar.edu to idd.unidata.ucar.edu. The machine that was thelma previously (a Sun SunFire 480R) was retired back in late spring 2005. The toplevel IDD relay that we maintain, idd.unidata.ucar.edu, should honor requests made to thelma.ucar.edu, but it would be better to change your request so the real time statistics 'topology' page can display the path the data takes in getting delivered to you. > Other datatypes from Thelma are coming in just > fine. Could you check thelma's logs and see if there any problems > feeding twister.millersville.edu? We are seeing numerous messages of the following sort in idd.unidata.ucar.edu log files: Jan 16 18:34:39 uni2 twister(feed)[31021]: upc6.c:287: nullproc_6() failure to twister.millersville.edu: RPC: Timed out After getting a final 'errno = Connection timed out' message, we see a new 'topo' for CONDUIT feed to twister. > Any odeas on what to check on my end? Please check your log file(s) to see what kind of error messages you are seeing. If your problem persists, I suggest restarting your LDM, or, as a final resort, stopping the LDM; deleting and remaking the queue; and restarting. > Thanks! No worries. > Dave > +++++++++++++++++++++++ > David Fitzgerald > Department of Earth Sciences > Millersville University > Millersville Pa 17551 > Phone: 717-871-2394 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/esupport ************************************************************************ **** Ticket Details =================== Ticket ID: SKM-230294 Department: Support IDD Priority: Normal Status: Open