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 Ioan, re: > thanks for your answer. No worries. > I am trying to get some data from lead server and while I used adir > request successfully aget failed. I tried a couple of channels/descriptors > but it was the same all over. > here is my log for channel 5 > > DEBUG:client.pyc:Issuing adde req type adir RTGOESR FDC05 -1 -1 TRACKING=0 > BAND=ALL VERSION=1 AUX=NO to server lead.unidata.ucar.edu > DEBUG:client.pyc:download lasted 0:00:00.202961 > DEBUG:client.pyc:server has sent 279 uncompr bytes decompressed into 1584 > bytes > DEBUG:client.pyc:created > /home/jano/Desktop/goesr/area/GOES16_B5_201711200845.area.tmp > DEBUG:client.pyc:Issuing adde req type aget RTGOESR FDC05 0 AU 0 0 X 10848 > 10848 BAND=ALL DAY=2017-11-20 LMAG=1 EMAG=1 UNIT=RAW TIME=08:45:39 > 08:45:39 I TRACKING=0 VERSION=1 SPAC=X to server lead.unidata.ucar.edu > [Errno 104] Connection reset by peer > Traceback (most recent call last): > File "/media/d/work/dev/python/pyadde/trunk/pyadde/client.py", line 876, > in get_area_file > data = query_server(adde_server=adde_server, req_type=req_type, > req_text=req_text, port=port, user=user, password=password,project=project, > timeout=timeout) > File "/media/d/work/dev/python/pyadde/trunk/pyadde/client.py", line 626, > in query_server > data = sock.recv(bufsz) > error: [Errno 104] Connection reset by peer > DEBUG:client.pyc:removed > /home/jano/Desktop/goesr/area/GOES16_B5_201711200845.area.tmp > > > I could however get data from goeseast.unidata.ucar.edu > > > I have turned off the GOES13&15 downloaders to be sure it is not happening > because of too many connections. There are IDV users scattered throughout Latin America (e.g., Brazil, Costa Rica, etc.) and McIDAS-X users in the U.S. that are accessing the RTGOESR datasets on lead.unidata.ucar.edu, so the issue should not be caused by a firewall block or the ADDE setup. Can you check access to the RTGOESR datasets using McIDAS-X (or McIDAS-V or the IDV) on your side? 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: YGF-361048 Department: Support McIDAS Priority: Normal Status: Closed =================== 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.