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 Christian, re: failure to receive any CONDUIT data > Indeed, it does not make sense to me either... it is also weird because it > was working before, for months...! I was able to SSH to vkepler, and I've made numerous attempts to get a any data from CONDUIT feed REQUEST(s). One of the tests was to REQUEST all of CONDUIT from idd.unidata.ucar.edu, and not one product was received even though the LDM log file on the real-server backend of the cluster that the REQUEST was to showed the connection and then tried to send data. The only thing that struck me as being a possibility is the following: vkepler has been up for over 200 days (208 days, to be exact). As a last ditch test, I would suggest rebooting the machine (VM instance?). I've been talking with Steve about this, and he is scratching his head also. 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: AIZ-345619 Department: Support IDD Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.